LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-08-2015, 05:38 PM   #1
orexisx89
LQ Newbie
 
Registered: Sep 2015
Posts: 1

Rep: Reputation: Disabled
Trouble with Atheros wireless (AR9565) can not connect to open networks


Okay so here's my current problem, My acer aspire (ES1-711-P1UV) has been having connectivity issues, Only from what I can see, on open networks.

I tried using wicd at first, though with no success, so I dropped it, purged the packaged using slackpkg and tried just using the command line

iwconfig wasn't working to gain a connection either, Note that this computer is dual boot and runs windows 10 in which the connection in question works fine. after using iwconfig manually, I tries the network manager that is built in to slackware-14.1 (I'm running a modified kernel, the default suffered the same problem, but for clarity I'm running a custom compiled 4.2)

So I reset my rc.inet1.conf to it' default state, made the network manager daemon executable and went on my way.

It sees the network, much like before, it will attempt to connect, but doesn't finish and it deauthenticates and drops the connection. Here's what I've brought for potentially relevant diagnostic material.

Code:
bash-4.2# lspci | grep 02.00.0 -A3
02:00.0 Network controller: Atheros Communications Inc. AR9565 Wireless Network Adapter (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 0c)
Code:
ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c4:54:44:e5:08:18  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 0  (Local Loopback)
        RX packets 16  bytes 800 (800.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 16  bytes 800 (800.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 30:10:b3:dd:8b:05  txqueuelen 1000  (Ethernet)
        RX packets 359  bytes 124649 (121.7 KiB)
        RX errors 0  dropped 6  overruns 0  frame 0
        TX packets 10  bytes 4066 (3.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions
So these tell me what card I have and that it IS being recognized by the system so next I checked to see which driver it was using.

Code:
bash-4.2# nm-tool

NetworkManager Tool

State: disconnected

- Device: eth0 -----------------------------------------------------------------
  Type:              Wired
  Driver:            r8169
  State:             unavailable
  Default:           no
  HW Address:        C4:54:44:E5:08:18

  Capabilities:
    Carrier Detect:  yes

  Wired Properties
    Carrier:         off


- Device: wlan0 ----------------------------------------------------------------
  Type:              802.11 WiFi
  Driver:            ath9k
  State:             disconnected
  Default:           no
  HW Address:        30:10:B3:DD:8B:05

  Capabilities:

  Wireless Properties
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points 
    linksys:         Infra, 50:67:F0:31:EE:33, Freq 2437 MHz, Rate 54 Mb/s, Strength 57
    linksys:         Infra, 98:FC:11:C1:3E:64, Freq 2437 MHz, Rate 54 Mb/s, Strength 17

    
    
    
bash-4.2# lspci -nnk | grep 02.00.0 -A3
02:00.0 Network controller [0280]: Atheros Communications Inc. AR9565 Wireless Network Adapter [168c:0036] (rev 01)
        Subsystem: Lite-On Communications Inc Device [11ad:0642]
        Kernel driver in use: ath9k
        Kernel modules: ath9k
Alright so I know it's running the ath9K module as the driver, So I attempt to check if the ath9k supports the chipset, the result for me in the past using this command usually gives one alias, however this time it gave me a whole mess.

Code:
bash-4.2# modinfo ath9k | grep -i 0036
alias:          pci:v0000168Cd00000036sv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001028sd0000020Ebc*sc*i*
alias:          pci:v0000168Cd00000036sv00001043sd000085F2bc*sc*i*
alias:          pci:v0000168Cd00000036sv000017AAsd00004026bc*sc*i*
alias:          pci:v0000168Cd00000036sv000017AAsd00003026bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000105Bsd0000E099bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000105Bsd0000E091bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000105Bsd0000E081bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000105Bsd0000E08Fbc*sc*i*
alias:          pci:v0000168Cd00000036sv0000105Bsd0000E07Fbc*sc*i*
alias:          pci:v0000168Cd00000036sv0000185Fsd0000A120bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000185Fsd00003027bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001B9Asd000028A4bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001B9Asd000028A2bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001B9Asd00002813bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001B9Asd00002810bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000144Fsd00007202bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001A3Bsd00002F82bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001A3Bsd0000218Cbc*sc*i*
alias:          pci:v0000168Cd00000036sv00001A3Bsd0000218Bbc*sc*i*
alias:          pci:v0000168Cd00000036sv00001A3Bsd00002182bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001A3Bsd0000213Bbc*sc*i*
alias:          pci:v0000168Cd00000036sv00001A3Bsd00002130bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00000813bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00000803bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00000692bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00001832bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00000832bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00000612bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00000652bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00000642bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000168Csd0000302Cbc*sc*i*
alias:          pci:v0000168Cd00000036sv0000168Csd00003027bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000144Dsd0000412Abc*sc*i*
alias:          pci:v0000168Cd00000036sv0000144Dsd00004129bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000144Dsd0000411Ebc*sc*i*
alias:          pci:v0000168Cd00000036sv0000144Dsd0000411Dbc*sc*i*
alias:          pci:v0000168Cd00000036sv0000144Dsd0000411Cbc*sc*i*
alias:          pci:v0000168Cd00000036sv0000144Dsd0000411Bbc*sc*i*
alias:          pci:v0000168Cd00000036sv0000144Dsd0000411Abc*sc*i*
alias:          pci:v0000168Cd00000036sv00001028sd0000020Cbc*sc*i*
alias:          pci:v0000168Cd00000036sv0000103Csd00002005bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000103Csd0000217Fbc*sc*i*
alias:          pci:v0000168Cd00000036sv0000103Csd000018E3bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001A3Bsd0000213Cbc*sc*i*
alias:          pci:v0000168Cd00000036sv00001A3Bsd0000213Abc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00000682bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd000006A2bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00000662bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00000672bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00000622bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000185Fsd00003028bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000105Bsd0000E069bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000168Csd0000302Bbc*sc*i*
alias:          pci:v0000168Cd00000036sv0000168Csd00003026bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000168Csd00003025bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001A3Bsd00002F8Abc*sc*i*
alias:          pci:v0000168Cd00000036sv00001A3Bsd0000218Abc*sc*i*
alias:          pci:v0000168Cd00000036sv00001B9Asd000028A3bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001B9Asd000028A1bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001B9Asd00002812bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001B9Asd00002811bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00006671bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00001842bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00000842bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd000006B2bc*sc*i*
alias:          pci:v0000168Cd00000036sv000011ADsd00000632bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000185Fsd0000A119bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000105Bsd0000E068bc*sc*i*
alias:          pci:v0000168Cd00000036sv00001A3Bsd00002176bc*sc*i*
alias:          pci:v0000168Cd00000036sv0000168Csd00003028bc*sc*i*
alright, now that I've got that listed, what happens when I try to make a connection, according to dmesg:

Code:
[  910.676147] wlan0: authenticate with 50:67:f0:31:ee:33
[  910.694825] wlan0: send auth to 50:67:f0:31:ee:33 (try 1/3)
[  910.697117] wlan0: authenticated
[  910.698988] wlan0: associate with 50:67:f0:31:ee:33 (try 1/3)
[  910.703214] wlan0: RX AssocResp from 50:67:f0:31:ee:33 (capab=0x401 status=0 aid=1)
[  910.703416] wlan0: associated
[  940.759125] wlan0: deauthenticating from 50:67:f0:31:ee:33 by local choice (Reason: 3=DEAUTH_LEAVING)
[  940.780520] cfg80211: World regulatory domain updated:
[  940.780530] cfg80211:  DFS Master region: unset
[  940.780533] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[  940.780540] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[  940.780545] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
[  940.780550] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
[  940.780555] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[  940.780559] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
Now, during the connection attempt iwconfig displayed.

Code:
bash-4.2# iwconfig
eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"linksys"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: 50:67:F0:31:EE:33   
          Bit Rate=13 Mb/s   Tx-Power=15 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=49/70  Signal level=-61 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.
so this is what I have, I don't know what to try from here, if you guys could shed some light on the issues. let me know if you need additional information or need me to run additional commands to get what you need. Any help greatly appreciated
 
Old 09-09-2015, 07:08 AM   #2
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,558
Blog Entries: 15

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
Not sure if this will help but this is all I could find:

https://wireless.wiki.kernel.org/en/users/drivers/ath9k

Dunno if it will help.
 
Old 09-10-2015, 01:22 PM   #3
xnue
LQ Newbie
 
Registered: Sep 2015
Posts: 3

Rep: Reputation: Disabled
Unfortunately ath9k driver is totally broken when using certain cards, this is known problem. I don't have any link to bugtracker with this bug ATM, so I don't know if they eventually fixed it in the kernel. Anyway, you have two options:

1. If driver was fixed (to be honest, I highly doubt it), you can try to compile latest kernel.
2. Use ndiswrapper with Windows XP driver for your card (this is the easiest route, and almost certainly it will work)

Last edited by xnue; 09-10-2015 at 01:24 PM.
 
Old 09-11-2015, 07:17 AM   #4
oldtechaa
Member
 
Registered: May 2015
Location: US
Distribution: Fedora
Posts: 364

Rep: Reputation: 83
Here is the kernel.org bug link:
https://bugzilla.kernel.org/buglist.cgi?bug_status=__all__&content=ath9k&order=relevance%20desc&product=&query_format=specific
And Ubuntu:
https://bugs.launchpad.net/ubuntu/+b...by=-importance

I haven't really looked through them.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Getting Wifi to work -- Atheros AR9565, Debian Wheezy wspark Linux - Newbie 17 11-23-2014 09:44 AM
Atheros wireless fails to connect samhill5215 Linux - Hardware 8 12-30-2012 10:22 PM
Atheros wireless not detecting networks on resume from sleep taro_curly Linux - Wireless Networking 1 11-11-2009 09:05 PM
Why can I see wireless networks but never connect, WPA/WEP or open? Dan.b Linux - Newbie 3 09-03-2009 10:43 PM
Trouble connecting to wireless networks. Bryanlee Linux - Wireless Networking 1 05-30-2006 11:11 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:54 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration