Atheros AR9485 cuts connection, rejects WPA2 password

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
BuggyBY

Atheros AR9485 cuts connection, rejects WPA2 password

Post by BuggyBY »

Hello,

I'm running Linux Mint 14 MATE Edition on an Acer AOD257 netbook. At first glance everything appears to work as advertised. However, after a random amount of uptime (I have experienced anything from 20 minutes to several hours) wifi cuts out, and I am presented with a dialog asking me to retype the password. If I do so, no successful connection is made and the same dialog pops up again after half a minute or so.
The only way I have thus far found to get wifi connectivity back in these situations is to reboot the computer (fortunately this doesn't take much time as I have switched the internal hard drive for an SSD), but having to do so several times a day is quite annoying.

Does this sound like a driver/firmware issue, or could it be a problem with hardware overheating? The case does tend to feel quite warm to the touch after 30+ minutes of uptime ...

Below are the results of mintWifi.py:

Code: Select all

-------------------------
* I. scanning WIFI PCI devices...
  -- Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)
      ==> PCI ID = 168c:0032 (rev 01)
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
eth0      no wireless extensions.

lo        no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"dlink2"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:24:01:6E:6B:B5   
          Bit Rate=48 Mb/s   Tx-Power=16 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          Link Quality=41/70  Signal level=-69 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:891  Invalid misc:70430   Missed beacon:0

-------------------------
* IV. querying ifconfig...
eth0      Link encap:Ethernet  HWaddr 04:7d:7b:1d:f8:ba  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:9105 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9105 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1435782 (1.4 MB)  TX bytes:1435782 (1.4 MB)

wlan0     Link encap:Ethernet  HWaddr 60:d8:19:4e:f5:e8  
          inet addr:192.168.0.129  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::62d8:19ff:fe4e:f5e8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1083031 errors:0 dropped:2 overruns:0 frame:0
          TX packets:1101156 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:834506433 (834.5 MB)  TX bytes:652763736 (652.7 MB)

-------------------------
* V. querying DHCP...
-------------------------
* VI. querying nslookup google.com...
Server:		127.0.1.1
Address:	127.0.1.1#53

Non-authoritative answer:
Name:	google.com
Address: 173.194.35.135
Name:	google.com
Address: 173.194.35.136
Name:	google.com
Address: 173.194.35.137
Name:	google.com
Address: 173.194.35.131
Name:	google.com
Address: 173.194.35.142
Name:	google.com
Address: 173.194.35.133
Name:	google.com
Address: 173.194.35.132
Name:	google.com
Address: 173.194.35.134
Name:	google.com
Address: 173.194.35.129
Name:	google.com
Address: 173.194.35.130
Name:	google.com
Address: 173.194.35.128
And just for good measure, have the results of inxi -F as well:

Code: Select all

System:    Host: bugport257 Kernel: 3.5.0-27-generic x86_64 (64 bit) Desktop: N/A Distro: Linux Mint 14 Nadia
Machine:   System: Acer product: AOD257 version: V1.15
           Mobo: Acer model: JE06_PT Bios: INSYDE version: V1.15 date: 10/21/2011
CPU:       Dual core Intel Atom CPU N570 (-HT-MCP-) cache: 512 KB flags: (lm nx sse sse2 sse3 ssse3 vmx) 
           Clock Speeds: 1: 1000.00 MHz 2: 1000.00 MHz 3: 1000.00 MHz 4: 1666.00 MHz
Graphics:  Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller 
           X.Org: 1.13.0 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.0hz 
           GLX Renderer: Mesa DRI Intel IGD GLX Version: 2.0 Mesa 9.1.1
Audio:     Card: Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel Sound: ALSA ver: 1.0.25
Network:   Card-1: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver: r8169 
           IF: eth0 state: down mac: 04:7d:7b:1d:f8:ba
           Card-2: Atheros AR9485 Wireless Network Adapter driver: ath9k 
           IF: wlan0 state: up mac: 60:d8:19:4e:f5:e8
Drives:    HDD Total Size: 128.0GB (28.1% used) 1: id: /dev/sda model: M4 size: 128.0GB 
Partition: ID: / size: 116G used: 34G (31%) fs: ext4 ID: swap-1 size: 2.13GB used: 0.20GB (9%) fs: swap 
RAID:      No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors:   System Temperatures: cpu: 80.0C mobo: N/A 
           Fan Speeds (in rpm): cpu: N/A 
Info:      Processes: 183 Uptime: 13:27 Memory: 821.9/1991.4MB Client: Shell inxi: 1.8.4
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Top
AlbertP
Level 16
Level 16
Posts: 6701
Joined: Sun Jan 30, 2011 12:38 pm
Location: Utrecht, The Netherlands

Re: Atheros AR9485 cuts connection, rejects WPA2 password

Post by AlbertP »

AR9485 is still quite a new chip, maybe it's not fully working yet with the current driver version. You could try installing a newer driver.

Please download a package with newer drivers here: https://www.kernel.org/pub/linux/kernel ... 3-2.tar.xz
After extracting the XZ file, go to the folder where you extracted it, right-click > Open in Terminal, then run these commands to install it:

Code: Select all

./scripts/driver-select ath9k
make
sudo make install
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
Top
BuggyBY

Re: Atheros AR9485 cuts connection, rejects WPA2 password

Post by BuggyBY »

Thanks for the reply. I've installed the drivers, but found that the problem keeps recurring regardless.
Today I skimmed some of the system log files, and found the following in kern.log:

Code: Select all

Apr 25 14:53:00 bugport257 kernel: [11728.201996] cfg80211: Found new beacon on frequency: 2472 MHz (Ch 13) on phy0
Apr 25 14:53:00 bugport257 kernel: [11728.305528] wlan0: authenticate with 74:44:01:49:cf:aa
Apr 25 14:53:00 bugport257 kernel: [11728.309275] wlan0: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded
Apr 25 14:53:00 bugport257 kernel: [11728.314561] wlan0: send auth to 74:44:01:49:cf:aa (try 1/3)
Apr 25 14:53:00 bugport257 kernel: [11728.330616] wlan0: authenticated
Apr 25 14:53:00 bugport257 kernel: [11728.332149] wlan0: associate with 74:44:01:49:cf:aa (try 1/3)
Apr 25 14:53:00 bugport257 kernel: [11728.345165] wlan0: RX AssocResp from 74:44:01:49:cf:aa (capab=0x411 status=0 aid=3)
Apr 25 14:53:00 bugport257 kernel: [11728.345423] wlan0: associated
Apr 25 16:42:13 bugport257 kernel: [18281.100215] ath: phy0: Failed to wakeup in 500us
Apr 25 16:42:13 bugport257 kernel: [18281.125841] ath: phy0: Failed to wakeup in 500us
Apr 25 16:42:13 bugport257 kernel: [18281.143867] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Apr 25 16:42:13 bugport257 kernel: [18281.143971] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Apr 25 16:42:13 bugport257 kernel: [18281.207548] ath: phy0: Failed to stop TX DMA, queues=0x10f!
Apr 25 16:42:13 bugport257 kernel: [18281.321116] ath: phy0: Chip reset failed
Apr 25 16:42:13 bugport257 kernel: [18281.321130] ath: phy0: Unable to reset channel, reset status -22
Apr 25 16:42:14 bugport257 kernel: [18282.800150] ath: phy0: Failed to wakeup in 500us
Apr 25 16:42:15 bugport257 kernel: [18283.318646] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Apr 25 16:42:15 bugport257 kernel: [18283.318684] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Apr 25 16:42:15 bugport257 kernel: [18283.383090] ath: phy0: Failed to stop TX DMA, queues=0x10f!
Apr 25 16:42:15 bugport257 kernel: [18283.496896] ath: phy0: Chip reset failed
Apr 25 16:42:15 bugport257 kernel: [18283.496910] ath: phy0: Unable to reset channel, reset status -22
Apr 25 16:42:15 bugport257 kernel: [18283.496944] ath: phy0: Unable to set channel
Apr 25 16:42:15 bugport257 kernel: [18283.500407] cfg80211: All devices are disconnected, going to restore regulatory settings
Apr 25 16:42:15 bugport257 kernel: [18283.500422] cfg80211: Restoring regulatory settings
Apr 25 16:42:15 bugport257 kernel: [18283.500438] cfg80211: Calling CRDA to update world regulatory domain
Apr 25 16:42:15 bugport257 kernel: [18283.515114] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
Apr 25 16:42:15 bugport257 kernel: [18283.504059] ath: phy0: RX failed to go idle in 10 ms RXSM=0xffffffff
Apr 25 16:42:15 bugport257 kernel: [18283.504059] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Apr 25 16:42:15 bugport257 kernel: [18283.516034] ath: phy0: Failed to wakeup in 500us
Apr 25 16:42:15 bugport257 kernel: [18283.639878] ath: phy0: RX failed to go idle in 10 ms RXSM=0xffffffff
Apr 25 16:42:15 bugport257 kernel: [18283.639878] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Apr 25 16:42:15 bugport257 kernel: [18283.760102] cfg80211: World regulatory domain updated:
Apr 25 16:42:15 bugport257 kernel: [18283.760111] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Apr 25 16:42:15 bugport257 kernel: [18283.760122] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 25 16:42:15 bugport257 kernel: [18283.760143] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 25 16:42:15 bugport257 kernel: [18283.760162] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 25 16:42:15 bugport257 kernel: [18283.760174] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 25 16:42:15 bugport257 kernel: [18283.760182] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 25 16:42:15 bugport257 kernel: [18283.764091] ath: phy0: Failed to wakeup in 500us
Apr 25 16:42:15 bugport257 kernel: [18283.774987] ath: phy0: RX failed to go idle in 10 ms RXSM=0xffffffff
Apr 25 16:42:15 bugport257 kernel: [18283.774987] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Apr 25 16:42:15 bugport257 kernel: [18283.901966] ath: phy0: Failed to wakeup in 500us
Apr 25 16:42:16 bugport257 kernel: [18283.918094] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Apr 25 16:42:16 bugport257 kernel: [18283.918124] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Apr 25 16:42:16 bugport257 kernel: [18283.981904] ath: phy0: Failed to stop TX DMA, queues=0x10f!
Apr 25 16:42:16 bugport257 kernel: [18284.095183] ath: phy0: Chip reset failed
Apr 25 16:42:16 bugport257 kernel: [18284.095201] ath: phy0: Unable to reset channel, reset status -22
Apr 25 16:42:16 bugport257 kernel: [18284.095235] ath: phy0: Unable to set channel
Apr 25 16:42:16 bugport257 kernel: [18284.106906] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Apr 25 16:42:16 bugport257 kernel: [18284.106927] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Apr 25 16:42:16 bugport257 kernel: [18284.170605] ath: phy0: Failed to stop TX DMA, queues=0x10f!
Apr 25 16:42:16 bugport257 kernel: [18284.284278] ath: phy0: Chip reset failed
Apr 25 16:42:16 bugport257 kernel: [18284.284291] ath: phy0: Unable to reset channel, reset status -22
Apr 25 16:42:16 bugport257 kernel: [18284.284327] ath: phy0: Unable to set channel
Apr 25 16:42:16 bugport257 kernel: [18284.295806] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Apr 25 16:42:16 bugport257 kernel: [18284.295827] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Apr 25 16:42:16 bugport257 kernel: [18284.359412] ath: phy0: Failed to stop TX DMA, queues=0x10f!
Apr 25 16:42:16 bugport257 kernel: [18284.473148] ath: phy0: Chip reset failed
Those messages starting with "ath:phy0:" then kept repeating every few seconds for several hours (thanks to those repetitions, last week's log seems to have grown to almost 40MB), until the next reboot. Sadly, being a relatively inexperienced *nix user I understand little of what they refer to, and only know that during the time they kept looping, I was unable to connect to any wireless network.
Top
Locked

Return to “Networking”