Atheros ath9k, doesn't it need to upload no firmware, ain't it?

For friendly off topic discussion not covered in a forum above.
Forum rules
No politics, please.
Y888099
Posts: 426
Joined: Mon Jul 11, 2016 11:00 am

Atheros ath9k, doesn't it need to upload no firmware, ain't it?

Unread postby Y888099 » Sat Apr 01, 2017 6:11 am

Code: Select all

RedQueen # lspci | grep Wireless
01:06.0 Network controller: Qualcomm Atheros AR922X Wireless Network Adapter (rev 01)


Atheros AR922X Wireless Network Adapters are described of being not like Intel ipw22xx's ones which need a firmware upload. They say they don't need to upload no firmware.

Code: Select all

RedQueen # modprobe ath9k


Code: Select all

RedQueen # dmesg
...
ath9k 0000:01:06.0: loading /lib/firmware/updates/4.9.6-Roaring/TGxffffffb0" failed with error -2
ath9k 0000:01:06.0: loading /lib/firmware/updates/TGxffffffb0" failed with error -2
ath9k 0000:01:06.0: loading /lib/firmware/4.9.6-Roaring/TGxffffffb0" failed with error -2
ath9k 0000:01:06.0: loading /lib/firmware/TGxffffffb0" failed with error -2
ath9k 0000:01:06.0: Direct firmware load for TGxffffffb0" failed with error -2
__fw_free_buf: fw-TGxffffffb0" buf=000000012e475360 data=(null) size=0
ath: phy0: Unable to load EEPROM file TGxffffffb0"
ath9k 0000:01:06.0: Failed to initialize device
ath9k: probe of 0000:01:06.0 failed with error -22


What. The. Frog. is the kernel expecting to load from "/lib/firmware/TGxffffffb0" ?!?!?

I am not expert of linux, I simply need a working Wifi card :roll:


It seems it's for calibration data ( also see How to change Atheros AR9xxx aka ath9k EEPROM values ), for devices w/o a separate EEPROM chip can be specified via the 'eeprom_data' field of 'ath9k_platform_data'. The 'eeprom_data' is usually filled from board specific setup functions. It is easy if the EEPROM data is mapped to the memory, but it can be complicated if it is stored elsewhere.

BTW, it seems the Ath9k (PCI && miniPCI) driver is broken for Kernel 4.9.* :roll:
(I am on linux v4.9.6-Roaring)


~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

Intel ipw2200

Code: Select all

RedQueen # lspci | grep Wireless
01:06.0 Network controller: Intel PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)


Code: Select all

RedQueen # ipw2200


Code: Select all

RedQueen # dmesg

bus: 'pci': really_probe: probing driver ipw2200 with device 0000:01:06.0
devices_kset: Moving 0000:01:06.0 to end of list
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
__allocate_fw_buf: fw-ipw2200-bss.fw buf=000000012108a750
ipw2200 0000:01:06.0: loading /lib/firmware/ipw2200-bss.fw success
ipw2200 0000:01:06.0: direct-loading ipw2200-bss.fw
fw_set_page_data: fw-ipw2200-bss.fw buf=000000012108a750 data=000000000043c000 size=191154
__fw_free_buf: fw-ipw2200-bss.fw buf=000000012108a750 data=000000000043c000 size=191154
device: 'phy1': device_add
device: 'eth1': device_add
ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
driver: 'ipw2200': driver_bound: bound to device '0000:01:06.0'


Intel cards are supposed to load their firmware, and they actually load /lib/firmware/ipw2200-bss.fw with success.
Head Full of Snow. Lemon Scented You

Return to “Everything Else”

Who is online

Users browsing this forum: No registered users and 2 guests