Stefan Agner

Ok, thanks for the details. From your description it sounds more like a rollback of Core gets triggered, similar to this report https://community.home-assistant.io/t/homeassistant-update-failed-rollback/676682/5. This is triggered by the Supervisor. I'd...

@lennartschulte do you use a USB SSD as well? It sounds like a corrupted boot partition (first partition on the SD card). You can try to rescue it by coping...

I can reproduce this problem on my end. It seems that the kernel Bluetooth initialization creates an hci0 device in any case. I am not sure if we can prevent...

For completeness, Yellow hciconfig reports this: ``` # hciconfig hci0: Type: Primary Bus: UART BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0...

IMHO, #2948 is *really* a work around. It could even be problematic in cases a external connected Bluetooth adapter is used :cold_sweat: I guess the typical use case is a...

@bdraco so there is another case where an hci device shows up with 00:00:00:00:00:00: Systems running HAOS with a newer Intel WiFi/Bluetooth adapter.

> generic-x86-64 (Generic UEFI capable x86-64 systems) That hardly seems correct. What Raspberry Pi image are you using? 32-bit or 64-bit? Did you adjust `config.txt` on your system?

> This seems to indicate an issue related to the i915 integrated GPU. I am using Frigate as an add-on, with (CPU) accelerated video decoding, so it's possibly some interaction...

> Failed to boot after upgrading OS to 10.0. How does this exactly manifest? - Which leds to light up? - Does removing and repluggin power helps? - Anything shown...

> OS is running on virtual machine on Qemu. > generic-x86-64 (Generic UEFI capable x86-64 systems) We have a specific image for virtualization, named "ova". I recommend using this over...