Stefan Agner

Hm, that looks similar to #1960. Is that a new installation? Is that always reproducible? Can you test the latest release 8.2 (currenlty on the beta channel): https://github.com/home-assistant/operating-system/releases/tag/8.2

Hm, Raspberry Pi solves such kind of hardware modification using device tree overlays. I'd rather prefer not to add/support overlays for ODROID-N2(+). But we could just declare those pins as...

> And a look in the dtb file from home assistant os shows that the parameter and value for the blue LED pin are different to the solution from hardkernel....

Oh I see you are trying to use the LED on the pin header pin number 8, which is GPIOX_12. The button is GPIOX_3, so in theory it should work...

It sounds like the output gets lost when the kernel loads the actual DRM driver for this IP. I don't remember if I tested it with previous OS versions :cold_sweat:...

This sounds very much like #1705. > Downgrading virtualbox to .30 fixed the issue Hm, so probably a VirtualBox issue then?

> The virtualbox changelog doesn't list anything about EFI Yet the VirtualBox downgrade fixes it? So there was a change then which influences it... You can also give the latest...

@rct I am not aware that somebody linked this to a VirtualBox issue, but I agree it should be. HAOS uses a rather vanilla upstream Linux kernel, so something which...

The `modprobe` binary used in HAOS is not from the busybox package but from the kmod package (`BR2_PACKAGE_KMOD`). Afaict this gets selected implicitly somehow. This is the tool which comes...

Maybe another module is depending on it, which causes it to get loaded? There is a work around using a `install` instruction documented on the Arch Linux wiki: https://wiki.archlinux.org/title/Kernel_module#Blacklisting