Page MenuHomePureOS Tracker

USB ath9k Wi-Fi adapter doesn't initialise in PureOS installer
Open, Needs TriagePublic



I booted pureos-8.0-gnome-live_20180530-amd64.hybrid.iso on my Lenovo X230 with my (FSF RYF certified!) USB ath9k adapter plugged in. It wasn't recognised and looking at the kernel log, I see this:

[   10.374752] usb 3-2: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[   10.375218] usb 3-2: firmware: failed to load ath9k_htc/htc_9271-1.4.0.fw (-2)
[   10.375222] usb 3-2: Direct firmware load for ath9k_htc/htc_9271-1.4.0.fw failed with error -2
[   10.375225] usb 3-2: ath9k_htc: Firmware htc_9271.fw requested
[   10.375237] usb 3-2: firmware: failed to load htc_9271.fw (-2)
[   10.375239] usb 3-2: Direct firmware load for htc_9271.fw failed with error -2
[   10.375241] usb 3-2: no suitable firmware found!
[   10.375364] usb 3-2: ath9k_htc: USB layer deinitialized

The full kernel log is attached:

Event Timeline

rah created this task.Jun 25 2018, 09:22
rah added a comment.EditedJun 29 2018, 07:14

I have the same trouble in the installed system. I've installed firmware-ath9k-htc; this has an blob and also puts this in /etc/modprobe.d/ath9k_htc.conf:

options ath9k_htc use_dev_fw=1

however, the kernel is looking for htc_9271-1.4.0.fw and fails. I've tried linking the .dev.0.fw to .4.0.fw but it doesn't seem to work.

Do the kernel packages fiddle with the firmware loading at all? Such that possibly the use_dev_fw is ignored?

rah added a comment.Jun 29 2018, 07:33

Linking the .dev.0.fw to .4.0.fw apparently can work but there is an issue with NetworkManager using random MAC addresses that prevents associations:

chris.lamb assigned this task to mak.Jun 29 2018, 08:50
chris.lamb added subscribers: mak, chris.lamb.

Assigning @mak (in the first instance) as it's installer-related...

NB. this is an external, USB adaptor.

From Matrix discussions, this might affect Bluetooth as well (mentioning also to improve serch terms)