RPi4 model B rev 1.1 - USB devices still cooked

[ovenslighted08]

Describe the issue you are experiencing

HAOS 17.2-17.3 running on RPi4 model B rev 1.1 does not recognise any connected USB devices. This is despite updating to latest eeprom firmware (#4627 - which has since been stickied and locked)

What operating system image do you use?

rpi4-64 (Raspberry Pi 4/400 64-bit OS)

What version of Home Assistant Operating System is installed?

17.3

Did the problem occur after upgrading the Operating System?

Yes

Hardware details

v17.2 - exactly as described in #4627

Steps to reproduce the issue

1. Connect any USB device to HAOS - radio dongle, mass storage, peripheral, whatever
2. Nothing registered in Settings > System > Hardware

Anything in the Supervisor logs that might be useful for us?

Nope - attached

Anything in the Host logs that might be useful for us?

Nope - attached

System information

“There are currently no repairs pending”

Additional information

supervisor_2026-05-31T16-43-28.397Z.log
host_2026-05-31T16-56-36.959Z.log

`# cat /proc/cpuinfo
processor : 0
BogoMIPS : 108.00
Features : fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3

processor : 1
BogoMIPS : 108.00
Features : fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3

processor : 2
BogoMIPS : 108.00
Features : fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3

processor : 3
BogoMIPS : 108.00
Features : fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3

Revision : c03111
Serial : 1000000019e4b644
Model : Raspberry Pi 4 Model B Rev 1.1

rpi-eeprom-update

lspci: invalid option -- 'd'
BOOTLOADER: up to date
CURRENT: Sun May 17 19:13:18 UTC 2026 (1779045198)
LATEST: Thu May 8 15:21:35 UTC 2025 (1746717695)
RELEASE: default (/usr/lib/firmware/raspberrypi/bootloader-2711/default)

VL805_FW: Dedicated VL805 EEPROM
VL805: up to date
CURRENT:
LATEST: 000138c0

rpi-eeprom-update -a

lspci: invalid option -- 'd'
BOOTLOADER: up to date
CURRENT: Sun May 17 19:13:18 UTC 2026 (1779045198)
LATEST: Thu May 8 15:21:35 UTC 2025 (1746717695)
RELEASE: default (/usr/lib/firmware/raspberrypi/bootloader-2711/default)

VL805_FW: Dedicated VL805 EEPROM
VL805: up to date
CURRENT:
LATEST: 000138c0
#`

[sairon]

This doesn't seem to be the same as what I saw in #4627 but honestly can't rule it out, could you check a few more things?

1. HAOS 17.x doesn't check VL805 version correctly (as you can see by lspci: invalid option -- 'd'), so it may be actually outdated even if it reports "up to date". You'll need to run command from RPi 4B: Complete USB subsystem failure after update to HAOS 17.2 #4627 (comment) to check.
2. The bug from the above issue manifested as issue with xhci enumeration, reporting a timeout without VL805 appearing in the USB tree. In your host logs the VL805 appears (usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21). Can you check dmesg -w while re-plugging USB device that is known to work, both to USB2 and USB3 ports?

[Tom-Neverwinter]

This doesn't seem to be the same as what I saw in #4627 but honestly can't rule it out, could you check a few more things?

1. HAOS 17.x doesn't check VL805 version correctly (as you can see by lspci: invalid option -- 'd'), so it may be actually outdated even if it reports "up to date". You'll need to run command from RPi 4B: Complete USB subsystem failure after update to HAOS 17.2 #4627 (comment) to check.
2. The bug from the above issue manifested as issue with xhci enumeration, reporting a timeout without VL805 appearing in the USB tree. In your host logs the VL805 appears (usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21). Can you check dmesg -w while re-plugging USB device that is known to work, both to USB2 and USB3 ports?

so it will fail regardless as it cant do or handle version control...