Sorry, I forgot to mention: this is a Raspberry Pi 4 Model B
 
"Hermogenes Oliveira" [email protected] – 30 de maio de 2026 
às 11:03
> Package: raspi-firmware
> Version: 1.20260408+ds-1
> Severity: important
> 
> Dear Maintainer,
> 
> After upgrading my system and installing version 1.20260408 of
> raspi-firmware, USB devices stopped working.
> 
> Running lsusb gave no output at all and I saw the following during
> boot:
> 
> xhci_hcd 0000:01:00.0: can't setup: -110
> 
> After wrestling with this for a couple of days, I finally grabbed the
> version of the package from stable, unpacked it, and copied over the
> files under /usr/lib/raspi-firmware to the firmware partition of the
> SD card. I also changed /boot/firmware/config.txt to boot an earlier
> version of the kernel. The system is booting normally and USB is now
> working again.
> 
> If a reinstall the latest version of raspi-firmware with `apt clean`
> and `apt reinstall raspi-firmware`, the problem returns. This problem
> seems to be related to this upstream issue:
> 
> https://github.com/raspberrypi/firmware/issues/2026
> 
> So I guess updating the package to the latest upstream release
> 1.20260521 should fix things.
> 
> -- System Information:
> Debian Release: forky/sid
> APT prefers unstable
> APT policy: (990, 'unstable')
> Architecture: arm64 (aarch64)
> 
> Kernel: Linux 6.19.10+deb14-arm64 (SMP w/4 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_CRAP
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages raspi-firmware depends on:
> ii dosfstools 4.2-1.2+b1
> ii dpkg 1.23.7
> 
> raspi-firmware recommends no packages.
> 
> Versions of packages raspi-firmware suggests:
> ii bluez-firmware 1.2-13
> ii firmware-brcm80211 20260410-1
> ii firmware-misc-nonfree 20260410-1
> 
> -- Configuration Files:
> /etc/default/raspi-firmware changed:
> CMA=256M@128M
> 
> 
> -- no debconf information
>

Reply via email to