Lantiq xrx200 FB 3370: usb wifi device not working (kmod-ath9k-htc)

Installing and Using OpenWrt
1

I have a AVM Fritz!Box 3370 which is supported by the lantiq xrx200 target in the master branch.

I also have USB WiFi Sticks TP-Link TL-WN722N which are supported by the kmod-ath9k-htc driver together with the ath9k-htc-firmware.
These are working fine using e.g. a WDR3600 and the ath79 target, which uses kernel 4.14 like the lantiq xrx200 target.

But when trying to use this stick with the FB 3370, i get the following dmesg entries:

[   12.197251] usb 2-1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
[   12.451281] ath9k_htc 2-1:1.0: ath9k_htc: HTC initialized with 33 credits
[   12.857799] ath: phy1: Mac Chip Rev 0x0f.3 is not supported by this driver
[   12.863331] ath: phy1: Unable to initialize hardware; initialization status: -122
[   12.870811] ath: phy1: Unable to initialize hardware; initialization status: -122
[   12.878341] ath9k_htc: Failed to initialize the device
[   12.904928] usb 2-1: ath9k_htc: USB layer deinitialized

on the WDR3600 it looks like this and works:

[   10.638597] usb 1-1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
[   10.889454] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
[   11.487096] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4
[   11.492746] ath9k_htc 1-1:1.0: FW RMW support: On

sometimes even "lsusb" (from usbutils) isn't working and shows:

unable to initialize libusb: -99

maybe someone has an idea if this is a bug or what i can try next?
Thanks in advance!

2

copy firmware from WDR3600 dir /lib/firmware/ath9k_htc to your other router

3

i managed to resolve the libusb error message, but the actual problem persists:

the driver reports that it doesn't support "Mac Chip Rev 0x0f.3" although this works with the device from another target.

when i attach the usb stick using a USB hub with external power, i get a different error message:

[  389.503123] usb 2-1.3.3: new high-speed USB device number 9 using dwc2
[  389.630891] usb 2-1.3.3: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[  390.647319] usb 2-1.3.3: ath9k_htc: Firmware - ath9k_htc/htc_9271-1.4.0.fw download failed
[  390.654848] usb 2-1.3.3: ath9k_htc: USB layer deinitialized

tried it, doesn't help. also, both fw files have the same sha256sum

4

probably that target's usb subsystem does not have at least average support..

i get the very same message if i try loading firmware with more VAPs/NODES enabled which could also indicate errors in htc usb driver.

can you try loading with nohwcrypt parameter set?

5

how to do this on OpenWrt? i created /etc/modprobe.d/99-ath9k.conf with options ath9k_htc nohwcrypt=1 but it doesn't work

6

You add it to the module loading stanza in /etc/modules.d/ath9k

7

and this should look how exactly? tried some variants, after loading nohwcrypt stays 0

8

Looking at the title again, the file would be /etc/modules.d/ath9k-htc, with the contents ath9k_htc nohwcrypt=1, I won't give you any assurances that ath9k_htc can enable hwcrypto for your desired mode of operation.

9

also tried that file of course, unloaded all ath9k related modules with "rmmod" changed the file /etc/modules.d/ath9k-htc like you suggest and after modprobe the nohwcrypt parameter still says 0 in /sys/module/ath9k_htc/parameters/nohwcrypt

10

You aren't on a desktop distro, where kmod and udev take care of this.

/etc/modules.d/ath9k-htc is only used during system boot, that's when it would apply the module parameter. If you use busybox' insmod/ modprobe implementation you will have to specify the module parameter yourself.

11

thanks.
now the parameter is set - but the error message stays the same, Mac Chip Rev 0x0f.3 is not supported by this driver

12

Same problem with 21.02.1
I have

  1. ZyXEL P-2812HNUL-F1 (which is based on Lantiq XRX200 platfiorm)
  2. tl-wn722n v1 (ath9k)
  3. EDUP EP-AC1605 (MT76x2U)

EDUP EP-AC1605 works fine, I can see wireless SSID and I can connect to it. However tl-wn722n is not working. I get the same error @rotanid reported.

I don't think this is a hardware limitation of the router, otherwise EDUP adapter wouldn't work too