Hi Magnus, [email protected] <[email protected]> (2026-03-17): > Among other lines I found in the attached file syslog: > > usb 3-1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested > usb 3-1: firmware: failed to load ath9k_htc/htc_9271-1.4.0.fw (-2) > [...] > usb 3-1: ath9k_htc: Firmware htc_9271.fw requested > usb 3-1: firmware: failed to load htc_9271.fw (-2) > [...] > usb 3-1: Direct firmware load for htc_9271.fw failed with error -2 > usb 3-1: no suitable firmware found! > usb 3-1: ath9k_htc: Failed to get firmware htc_9271.fw > [...] > check-missing-firmware: looking at dmesg for the first time > check-missing-firmware: saving timestamp for a later use: [ 41.868765] > check-missing-firmware: failed to perform usb 3-1 lookup (got: 0 entries, > expected: 1) > check-missing-firmware: => sticking with the usb module > check-missing-firmware: using module usb instead of usb 3-1 > check-missing-firmware: looking for firmware file > ath9k_htc/htc_9271-1.4.0.fw requested by usb > check-missing-firmware: failed to perform usb 3-1 lookup (got: 0 entries, > expected: 1)
Let's quote the whole thing:
Feb 20 17:21:21 kernel: [ 41.868344] usb 3-1: ath9k_htc: Firmware
ath9k_htc/htc_9271-1.4.0.fw requested
Feb 20 17:21:21 kernel: [ 41.868388] usb 3-1: firmware: failed to load
ath9k_htc/htc_9271-1.4.0.fw (-2)
Feb 20 17:21:21 kernel: [ 41.868402] usb 3-1: firmware: failed to load
ath9k_htc/htc_9271-1.4.0.fw (-2)
Feb 20 17:21:21 kernel: [ 41.868416] usb 3-1: firmware: failed to load
ath9k_htc/htc_9271-1.4.0.fw (-2)
Feb 20 17:21:21 kernel: [ 41.868419] usb 3-1: Direct firmware load for
ath9k_htc/htc_9271-1.4.0.fw failed with error -2
Feb 20 17:21:21 kernel: [ 41.868424] usb 3-1: ath9k_htc: Firmware
htc_9271.fw requested
Feb 20 17:21:21 kernel: [ 41.868440] usb 3-1: firmware: failed to load
htc_9271.fw (-2)
Feb 20 17:21:21 kernel: [ 41.868452] usb 3-1: firmware: failed to load
htc_9271.fw (-2)
Feb 20 17:21:21 kernel: [ 41.868465] usb 3-1: firmware: failed to load
htc_9271.fw (-2)
Feb 20 17:21:21 kernel: [ 41.868467] usb 3-1: Direct firmware load for
htc_9271.fw failed with error -2
Feb 20 17:21:21 kernel: [ 41.868470] usb 3-1: no suitable firmware found!
Feb 20 17:21:21 kernel: [ 41.868471] usb 3-1: ath9k_htc: Failed to get
firmware htc_9271.fw
Feb 20 17:21:21 kernel: [ 41.868624] usb 3-1: ath9k_htc: USB layer
deinitialized
Feb 20 17:21:21 kernel: [ 41.868765] usbcore: registered new interface
driver ath9k_htc
Feb 20 17:21:22 check-missing-firmware: looking at dmesg for the first time
Feb 20 17:21:22 check-missing-firmware: saving timestamp for a later use: [
41.868765]
Feb 20 17:21:22 check-missing-firmware: failed to perform usb 3-1 lookup
(got: 0 entries, expected: 1)
Feb 20 17:21:22 check-missing-firmware: => sticking with the usb module
Feb 20 17:21:22 check-missing-firmware: using module usb instead of usb 3-1
Feb 20 17:21:22 check-missing-firmware: looking for firmware file
ath9k_htc/htc_9271-1.4.0.fw requested by usb
Feb 20 17:21:22 check-missing-firmware: failed to perform usb 3-1 lookup
(got: 0 entries, expected: 1)
Feb 20 17:21:22 check-missing-firmware: => sticking with the usb module
Feb 20 17:21:22 check-missing-firmware: using module usb instead of usb 3-1
Feb 20 17:21:22 check-missing-firmware: looking for firmware file
ath9k_htc/htc_9271-1.4.0.fw requested by usb
Feb 20 17:21:22 check-missing-firmware: failed to perform usb 3-1 lookup
(got: 0 entries, expected: 1)
Feb 20 17:21:22 check-missing-firmware: => sticking with the usb module
Feb 20 17:21:22 check-missing-firmware: using module usb instead of usb 3-1
Feb 20 17:21:22 check-missing-firmware: looking for firmware file
ath9k_htc/htc_9271-1.4.0.fw requested by usb
Feb 20 17:21:22 check-missing-firmware: failed to perform usb 3-1 lookup
(got: 0 entries, expected: 1)
Feb 20 17:21:22 check-missing-firmware: => sticking with the usb module
Feb 20 17:21:22 check-missing-firmware: using module usb instead of usb 3-1
Feb 20 17:21:22 check-missing-firmware: looking for firmware file
htc_9271.fw requested by usb
Feb 20 17:21:22 check-missing-firmware: failed to perform usb 3-1 lookup
(got: 0 entries, expected: 1)
Feb 20 17:21:22 check-missing-firmware: => sticking with the usb module
Feb 20 17:21:22 check-missing-firmware: using module usb instead of usb 3-1
Feb 20 17:21:22 check-missing-firmware: looking for firmware file
htc_9271.fw requested by usb
Feb 20 17:21:22 check-missing-firmware: failed to perform usb 3-1 lookup
(got: 0 entries, expected: 1)
Feb 20 17:21:22 check-missing-firmware: => sticking with the usb module
Feb 20 17:21:22 check-missing-firmware: using module usb instead of usb 3-1
Feb 20 17:21:22 check-missing-firmware: looking for firmware file
htc_9271.fw requested by usb
Feb 20 17:21:22 check-missing-firmware: missing firmware files
(ath9k_htc/htc_9271-1.4.0.fw htc_9271.fw) for usb
Feb 20 17:21:22 check-missing-firmware: mainloop iteration #1
Feb 20 17:21:22 check-missing-firmware: lookup with
/cdrom/firmware/Contents-firmware
Feb 20 17:21:22 check-missing-firmware: installing firmware package
/cdrom/firmware/firmware-ath9k-htc_1.4.0-110-ge888634+dfsg1-0.1_all.deb (main)
Feb 20 17:21:22 check-missing-firmware: installing firmware package
/cdrom/firmware/firmware-atheros_20250410-2_all.deb (non-free-firmware)
Feb 20 17:21:27 check-missing-firmware: modprobe: FATAL: Module usb not
found.
Feb 20 17:21:27 check-missing-firmware: modprobe: FATAL: Module usb not
found in directory /lib/modules/6.12.57+deb13-amd64
Feb 20 17:21:27 check-missing-firmware: removing and loading kernel module
usbcore as well (actual module for usb)
Feb 20 17:21:27 check-missing-firmware: modprobe: FATAL: Module usbcore is
in use.
That means the “what's the kernel module behind this specific USB port
actually needs to be reloaded” lookup didn't work, so firmware files
were deployed but the relevant wireless module wasn't reloaded.
The relevant code is:
https://salsa.debian.org/installer-team/hw-detect/-/blob/master/check-missing-firmware.sh?ref_type=heads#L24-48
If you could, it would be nice to let us know what that part of /sys
looks like for this specific port. Starting with `ls` or `find` for
/sys/bus/usb/devices/3-1/ (note the trailing slash, lots of symlinks)
should be a good start. `find` features `-L` but given the said maze of
symlinks, that can become unreadable quite quickly…
Cheers,
--
Cyril Brulebois ([email protected]) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
