You are not logged in.
Pages: 1
Topic closed
Hello Arch community, happy new year! Thanks for taking your time to read this and hopefully be able to help me today. I've recently made the switch from Ubuntu to Arch on my laptop and have been pleased with it so far. I've got most stuff set up to my wishes, using a wired ethernet connection. I'm running into some trouble, however, trying to set up my wireless connection. I've been following the wiki, both the manual and automated setup, both unsuccessfull. My router is using running WPA as well as WPA2, I temporarily tried using WEP, but failed to connect as well. I'll post output of the manual setup below. Tell me if any extra information is needed.
So following the wiki, I find this Qualcomm Atheros adapter. It uses the ath9k driver, which as far as I could find should work with this adapter.
$ lspci -k
03:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
Subsystem: AzureWave Device 2c97
Kernel driver in use: ath9k
Kernel modules: ath9k
Now bringing the wireless interface up.
# ip link set wlp3s0 up
$ ip link
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether e0:b9:a5:f8:33:72 brd ff:ff:ff:ff:ff:ff
Scanning for APs, I find two relevant APs since I've got a range extender on another floor.
# iw dev wlp3s0 scan | less
BSS 90:f6:52:2c:65:4e(on wlp3s0)
TSF: 303486977 usec (0d, 00:05:03)
freq: 2427
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -73.00 dBm
last seen: 626 ms ago
Information elements from Probe Response frame:
SSID: myssid
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 4
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: CCMP TKIP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: CCMP TKIP
* Authentication suites: PSK
ERP: <no flags>
Extended supported rates: 24.0 36.0 48.0 54.0
WMM: * Parameter version 1
* u-APSD
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
HT capabilities:
Capabilities: 0x11cc
HT20
SM Power Save disabled
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT RX MCS rate indexes supported: 0-15
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 4
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 1
* HT protection: 20 MHz
* non-GF present: 0
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 1 (Unconfigured)
* Response Type: 3 (AP)
* UUID: 00000000-0000-1000-0000-90f6522c654e
* Manufacturer: TP-LINK
* Model: TL-WA830RE
* Model Number: 1.0
* Serial Number: 1.0
* Primary Device Type: 6-0050f204-1
* Device name: Wireless N AP TL-WA830RE
* Config methods: Ethernet, Label, PBC
* RF Bands: 0x1
BSS 74:31:70:65:37:05(on wlp3s0)
TSF: 55154817445 usec (0d, 15:19:14)
freq: 2427
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -71.00 dBm
last seen: 656 ms ago
Information elements from Probe Response frame:
SSID: myssid
Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0
DS Parameter set: channel 4
ERP: Barker_Preamble_Mode
Extended supported rates: 6.0 12.0 24.0 48.0
HT capabilities:
Capabilities: 0x106e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 4
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: 20 MHz
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Secondary Channel Offset: no secondary (0)
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS Load:
* station count: 4
* channel utilisation: 29/255
* available admission capacity: 31250 [*32us]
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities: HT Information Exchange Supported
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* Selected Registrar: 0x0
* Response Type: 3 (AP)
* UUID: 00000000-0000-0003-0000-743170653705
* Manufacturer: Corporation
* Model: VGV7519KW22
* Model Number: 02.00.124
* Serial Number: J142038951
* Primary Device Type: 6-0050f204-1
* Device name: Wireless Router(WFA)
* Config methods: Label, PBC
Country: NL Environment: Indoor/Outdoor
Channels [1 - 13] @ 16 dBm
Now using the wpa_supplicant to try and connect. I've used several /etc/wpa_supplicant.conf files, all failing. Here I'll use the simplest one generated by wpa_passphrase.
# wpa_passphrase myssid mypassphrase > /etc/wpa_supplicant.conf
# wpa_supplicant -i wlp3s0 -c /etc/wpa_supplicant.conf
Successfully initialized wpa_supplicant
wlp3s0: Trying to associate with 74:31:70:65:37:05 (SSID='myssid' freq=2427 MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy
wlp3s0: Association request to the driver failed
wlp3s0: Associated with 74:31:70:65:37:05
wlp3s0: WPA: No SSID info found (msg 1 of 4)
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=74:31:70:65:37:05 reason=0
wlp3s0: Trying to associate with 90:f6:52:2c:65:4e (SSID='myssid' freq=2427 MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy
wlp3s0: Association request to the driver failed
wlp3s0: Associated with 90:f6:52:2c:65:4e
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:2c:65:4e reason=0
...
This keeps going on like this. What does this error message mean exactly? Is the ath9k device driver incorrect for my network adapter? Any help is appreciated, thanks.
P.S. This probably is irrelevant, but I'd like to mention it for completeness sake. I tried this while being connected to the internet through a wired ethernet connection. I've tried it while disconnected before as well, also resulting in failure, so I think it doesn't matter.
Last edited by Roxot (2014-01-01 18:59:09)
Offline
Great first post -- Welcome to Arch. It is refreshing to see a well researched first post that provides a plethora of good information.
A couple things to check -- The SSID and passphrase are case sensitive.
Is there any chance that something else is trying to control the NIC as well? Check that things like netctl are not running.
As to the driver, I cannot say, I don't have that hardware. You might use lspci -nn so that the specific vendor and product IDs are included in your output.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Welcome to our forums, Roxot :-)
Please edit your post.
When posting configs, code or command output, please use [ code ] tags, not [ quote ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and - in case of longer listings - more convenient to scroll through.
Offline
Thanks for your quick replies. I've changed my post to use code tags instead, karol. To ewaller: I'm sure that I'm using the correct SSID and paraphrase, using lower and upper case correctly. The processes I find running that might be relevant here are NetworkManager, wpa_supplicant and dhcpcd. I've automated my wired connection using the 'systemctl enable dhcpcd@eth0.service' command (the system seems to call my wired interface 'enp4s0' and not 'eth0', which I wasn't aware of at the time, but it works so I didn't change anything). As for the specific vendor and product IDs, here is the relevant output of the lspci -nn command:
$ lspci -nn
03:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01)
Offline
Yes, NetworkManager will interfere with trying to fly wpa_supplicant by hand. Were I you, I would kill NetWorkManager You also mentioned netctl. I would kill those too whilst debugging wpa_supplicant.
Ultimately, you should probably pick one of the automated tools and configure it. NetCtl works great for wireless. I have not enjoyed my NetworkManager experiences. There is also wicd.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I killed NetworkManager and successfully set up my wireless connection using NetCtl! It seems NetworkManager was indeed interefering with me trying to connect using wpa_supplicant. NetworkManager now starts automatically on boot but I don't think it will be much of a problem to fix that. I'm not sure how it usually works on this forum but I will mark this thread as solved by changing its title. Thanks a lot for your help!
Offline
I to am haveing a problem with my wireless card. Terminal gives me a device not found error. Sort of new to linux so any help would be appreciated... Thanks
Offline
Dog123, Welcome to Arc h Linux.
I am fairly certain that your problem is not related to this thread. Please feel free to open a new thread and provide the details of your problem. I am going to humbly suggest you create that thread in the newbie corner. In the mean time, the issue is probably that the name of your interface is different that is that of the original poster. Use the command ip link to get a list of all of the network interfaces on your computer.
In the mean time, I am going to close this thread as it has been marked as solved.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Pages: 1
Topic closed