Page MenuHomeSolus

Please include fix for "ath9k_htc: Failed to initialize the device solus"
Closed, InvalidPublic


Since a couple of kernel updates I've been having problems with my WiFi-adapter TP-LINK TL-WN722N.

Here is what's happening:

[  334.799337] usb 1-2: new high-speed USB device number 14 using xhci_hcd
[  334.821997] usb 1-2: New USB device found, idVendor=0cf3, idProduct=9271, bcdDevice= 1.08
[  334.822001] usb 1-2: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[  334.822003] usb 1-2: Product: USB2.0 WLAN
[  334.822004] usb 1-2: Manufacturer: ATHEROS
[  334.822005] usb 1-2: SerialNumber: 12345
[  334.824141] usb 1-2: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[  335.119430] usb 1-2: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
[  335.371294] ath9k_htc 1-2:1.0: ath9k_htc: HTC initialized with 33 credits
[  364.835620] ath9k_htc: Failed to initialize the device
[  364.835822] usb 1-2: ath9k_htc: USB layer deinitialized

For some reason the device gets deinitialized. I can re-plug it however I want, it doesn't matter.

I searched the net and found and saying it's a bug in the kernel that should have been fixed already.

Please include the fix to Solus. I must admit I don't know what exactly is to do or what has to be integrated.

Event Timeline

goek-han created this task.Aug 30 2020, 4:05 PM
JoshStrobl closed this task as Invalid.Aug 30 2020, 4:52 PM

Closing as invalid. The solution is a newer kernel after 5.7.10+ (so realistically 5.8 series), which is currently awaiting @DataDrake to bisect NVMe issues that are affecting him and @Girtablulu, which is the blocker for upgrading. If that doesn't get fixed then some people won't be able to boot their system, let alone get to the point where they could use wifi.

Ok, good to know that a fix in on its way.
Thanks for taking a look. Been using Solus since 2017 and I can live with tethering for a while.