FS#1561 - [ath9k-htc-firmware]: not work
Description:
Ath9k wifi device not working, possibly bad compilation or issues with gcc
Additional info:
* package version(s)
- gcc-8.4.0-2
- ath9k-htc-firmware-1.4.0-8
* config and/or log files etc.
[ 8.302952] usb 1-1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested [ 8.303011] usbcore: registered new interface driver ath9k_htc [ 8.303067] usb 1-1: Direct firmware load for ath9k_htc/htc_9271-1.4.0.fw failed with error -2 [ 8.303073] usb 1-1: ath9k_htc: Firmware htc_9271.fw requested [ 8.623141] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51008 [ 9.683657] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive [ 9.683672] ath9k_htc: Failed to initialize the device
Steps to reproduce:
- Add wifi device with ath9k firmware, for example: TL-WN722N
- pacman -S ath9k-htc-firmware
References:
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
Is the issue now solved?
It might be...
At the very least, the wifi card in my computer works...
I don't know if usb wifi cards work though. I can always test if you want.
@winter: Yes, a test with positive result would be good. :)
It still does not work
We must analyze that it is failing in package-build
oop's missing log file
Please include the following patch until this is functional within GNU/linux-libre: https://patchwork.kernel.org/project/linux-wireless/patch/20200711043324.8079-1-shiftee@posteo.net/
@Tobias Dausend
This is already applied in the current Kernel of Hyperbola v0.4
From my point of view this is not a issue of kernel but compiler gcc-derivates:
- xtensa-unknown-elf-binutils
- xtensa-unknown-elf-gcc
Okay, can confirm: The firmware-files from the package linux-libre-firmware help, have tried to get that working with an alternative USB-device I had with a comparable chipset. With the firmware-files copied from into /lib/firmware/ the device is functional directly.
No issue therefore with the kernel as you've said. Therefore a problem on how the firmware-package is created with the gcc-derivates.
Forgotten: The files I have tried came from the package of Parabola.
Another problem for finding now the problems with the build-infrastructure: Debian has upgraded binutils-package and therefore also the patchset towards 2.37 so 2.34 is not available. Either we remove the concurrent patchset from Debian for rebuilding, do something else or go for a newer version (not the ideal choice for now). For now I'll try first to test if only one package is the cause of problems and therefore xtensa-unkown-elf-binutils.
Cofirming success: Building the firmware-package with a changed xtensa-unknown-elf-binutils makes it working for me. The following patch from Qualcomm is needed!
Yeah, with that patch this issue is solved. Can Tobias Dausend add that patch?
Tobias Dausend, I updated the binutils-qualcomm.patch patch so that it will not generate .orig files.
In PKGBUILD of xtensa-unknown-elf-binutils would be like this:
Yes, will update that later. But therefore another test as I also need to remove the Debian-patches - version 2.34 of binutils is no longer provided with a concrete patchset. So first I need to be sure there are no side-effects in occurence afterwards when building the xtensa-package and the firmware with it.