Open varoudis opened 2 years ago
Hi,
please take a look here: https://github.com/qca/open-ath9k-htc-firmware/wiki/usb-related-issues
@olerem Thanks for the quick reply. I did check and for about an hour Im running a test with:
options "nohwcrypt=1 ps_enable=0 blink=0"
I think blink=0 is the same as the "sudo bash -c "echo none > /sys/class/leds/ath9k_htc-phy*/trigger"" ? LED isnt blinking anymore
yes. Will be interesting to know results.
The above test wasnt a success...
[ 5.411515] usb 1-1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[ 5.414339] usbcore: registered new interface driver ath9k_htc
[ 5.418440] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 5.715760] usb 1-1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
[ 5.997918] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
[ 6.751271] 8021q: adding VLAN 0 to HW filter on device eth0
[ 6.756850] br-lan: port 1(eth0) entered blocking state
[ 6.759396] br-lan: port 1(eth0) entered disabled state
[ 6.763735] device eth0 entered promiscuous mode
[ 6.770477] br-lan: port 1(eth0) entered blocking state
[ 6.775707] br-lan: port 1(eth0) entered forwarding state
[ 7.273586] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4
[ 7.278242] ath9k_htc 1-1:1.0: FW RMW support: On
[ 7.282485] ath: EEPROM regdomain: 0x833a
[ 7.285871] ath: EEPROM indicates we should expect a country code
[ 7.290866] ath: doing EEPROM country->regdmn map search
[ 7.295167] ath: country maps to regdmn code: 0x37
[ 7.299110] ath: Country alpha2 being used: GB
[ 7.302916] ath: Regpair used: 0x37
[ 7.343320] ieee80211 phy0: Atheros AR9271 Rev:1
[ 7.347709] device br-lan entered promiscuous mode
[ 8.838294] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 128.107954] wlan0: authenticate with 00:2a:10
[ 130.168660] wlan0: send auth to 00:2a:10: (try 1/3)
[ 130.177460] wlan0: authenticated
[ 130.189552] wlan0: associate with 00:2a:10: (try 1/3)
[ 130.210526] wlan0: RX AssocResp from 00:2a:10:cf (capab=0x431 status=0 aid=12)
[ 130.292239] wlan0: associated
[ 130.373981] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 6383.518119] ath: phy0: Unable to remove station entry for: 00:2a:10:c
[ 9807.054930] ath: phy0: Chip reset failed
[ 9807.057151] ath: phy0: Unable to reset channel (2447 Mhz) reset status -22
[ 9807.059751] ath: phy0: Unable to set channel
[ 9807.162394] ath: phy0: RX failed to go idle in 10 ms RXSM=0xc0b8b103
[ 9807.176010] ath: phy0: Failed to wakeup in 500us
[ 9807.279149] ath: phy0: RX failed to go idle in 10 ms RXSM=0x4056da01
[ 9807.484249] ath: phy0: RX failed to go idle in 10 ms RXSM=0xc0a8b103
[ 9807.496733] ath: phy0: Failed to wakeup in 500us
[ 9807.804791] ath: phy0: RX failed to go idle in 10 ms RXSM=0xc0a8b103
Do you think sending "none" in your command does something different?
This is what I had:
cat /sys/class/leds/ath9k_htc-phy0/trigger
none timer heartbeat default-on netdev phy0rx phy0tx phy0assoc [phy0radio] phy0tpt
Same error with LED totally off.
Sorry, Currently I have no idea. To get more information, you will need to get access to the UART pins (TXD1, RXD1) on the board of this adapter (baudrate 19200) and log this error on the firmware side.
ok thanks! Ill try to find some time to do it. (and find my ftdi adapter first :) )
I got some issue reports possible regarding this issue, too, and it looks like they don't appear on kernel 5.17.1 any longer. But that need some more investigations. The last test over a period of nearly 9h is looking good, so far: https://github.com/ZerBea/hcxdumptool/issues/209#issuecomment-1085460482
Hi,
At random times and tested with two different Linux distro running 5.10 and 5.15 the usb device goes dead until is physically removed from the system. Everything seems ok after USB in re-inserted until a random interval later same thing happens again.
Any ideas? USB card is ALFA AWUS036NHA