[SOLVED] Wifi unable to associate on Atheros AR242x / AR542x
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Wifi unable to associate on Atheros AR242x / AR542x
I installed Precise Puppy 5.7.1 on an Acer Aspire One A0751h with a Atheros AR242x / AR542x card for wifi. Whenever I try to connect to my home WiFi network with any of the network connection software that comes one the distribution I get an error. Specifically when I use Puppy Network Wizard I get an error which's details say "Access Point: Not-Associated" and "wpa_state=ASSOCIATING". I've spent hours on google trying this supposed solution and that supposed solution and so far nothing has changed anything. Any Help would be greatly appreciated.
Please keep in mind that this is my first attempt to put linux on a computer and as such have very limited knowledge of the OS.
please open a terminal on your Linux-machine and execute (as root or with sudo) the command
Code:
lspci -k | grep -iA3 wire
or
Code:
lspci -k | grep -iA3 athe
which will show us exactly which wifi adapter you have and if an appropriate kernel-module is loaded. Post the output here. Also execute
Code:
iwconfig
and
Code:
iwlist wlan0 scan
both as root.
If you have already wpa_supplicant installed, you should use it (on the commandline) because it gives you verbose errormessages (which can be helpful). Edit the /etc/wpa_supplicant.conf file (maybe /etc/wpa_supplicant/wpa_supplicant.conf on your system) and enter the correct settings for your accesspoint (there should be an examplefile in /usr/share/doc/wpa_supplicant). Then execute
# iwconfig
wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
lo no wireless extensions.
eth0 no wireless extensions.
#
Code:
# iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down
I can however scan for networks with x network wizard
Initially I didn't have a wpa_supplicant.conf file, nor did I have the template. So, I google it and downloaded the sourcefile which had the template in it (or at least that's what I think it was), but after editing and saving and running the command you gave, I just got a couple pages of line #'s followed by errors. So, I'm pretty sure I did something wrong.
Code:
Jan 29 22:47:21 Netbook user.info kernel: [ 6688.663065] wlan0: associate with 74:d0:2b:66:96:1c (try 1/3)
Jan 29 22:47:21 Netbook user.info kernel: [ 6688.665280] wlan0: RX AssocResp from 74:d0:2b:66:96:1c (capab=0x411 status=18 aid=0)
Jan 29 22:47:21 Netbook user.info kernel: [ 6688.665297] wlan0: 74:d0:2b:66:96:1c denied association (code=18)
Jan 29 22:47:21 Netbook user.info kernel: [ 6688.665390] wlan0: deauthenticating from 74:d0:2b:66:96:1c by local choice (reason=3)
And there were pages of errors that looked like this, as far as I could tell they were all just copies of these 4 lines.
Well, you'll have to bring the wlan up before executing the iwlist-command.
As for the settings in the wpa_supplicant.conf, please tell us which Access point you're using and which settings (WPA2?) and then post the wpa_supplicant.conf (without the password(s) and the SSID).
The errormessages at the bottom of your post show that at least the wireless-adapter is working (the output of lspci shows that the appropriate module is loaded) and wpa_supplicant is installed. Furthermore there is no syntactical error in the wpa_supplicant.conf but it seems that the authentication is not configured correctly.
I'm not sure what you mean, or how to go about bringing the wlan up. If you could clarify that would be appreciated.
I'll be honest I wasn't really sure how to use this config file, so I'm not suprised I used it wrong.
It's WPA2 - Personal
Code:
.\" This manpage has been automatically generated by docbook2man
.\" from a DocBook document. This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "WPA_SUPPLICANT.CONF" "5" "12 January 2013" "" ""
.SH NAME
wpa_supplicant.conf \- configuration file for wpa_supplicant
.SH "OVERVIEW"
.PP
\fBwpa_supplicant\fR is configured using a text
file that lists all accepted networks and security policies,
including pre-shared keys. See the example configuration file,
probably in \fB/usr/share/doc/wpa_supplicant/\fR, for
detailed information about the configuration format and supported
fields.
.PP
All file paths in this configuration file should use full
(absolute, not relative to working directory) path in order to allow
working directory to be changed. This can happen if wpa_supplicant is
run in the background.
.PP
Changes to configuration file can be reloaded be sending
SIGHUP signal to \fBwpa_supplicant\fR ('killall -HUP
wpa_supplicant'). Similarly, reloading can be triggered with
the \fBwpa_cli reconfigure\fR command.
.PP
Configuration file can include one or more network blocks,
e.g., one for each used SSID. wpa_supplicant will automatically
select the best network based on the order of network blocks in
the configuration file, network security level (WPA/WPA2 is
preferred), and signal strength.
.SH "QUICK EXAMPLES"
.TP 3
1.
WPA-Personal (PSK) as home network and WPA-Enterprise with
EAP-TLS as work network.
.sp
.RS
.nf
# allow frontend (e.g., wpa_cli) to be used by all users in 'wheel' group
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
#
# home network; allow all valid ciphers
network={
ssid="[REDACTED]"
scan_ssid=1
key_mgmt=WPA-PSK
psk="[REDACTED]"
}
#
# work network; use EAP-TLS with WPA; allow only CCMP and TKIP ciphers
network={
ssid="work"
scan_ssid=1
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TLS
identity="user@example.com"
ca_cert="/etc/cert/ca.pem"
client_cert="/etc/cert/user.pem"
private_key="/etc/cert/user.prv"
private_key_passwd="password"
}
.fi
.RE
.TP 3
2.
WPA-RADIUS/EAP-PEAP/MSCHAPv2 with RADIUS servers that
use old peaplabel (e.g., Funk Odyssey and SBR, Meetinghouse
Aegis, Interlink RAD-Series)
.sp
.RS
.nf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
network={
ssid="example"
scan_ssid=1
key_mgmt=WPA-EAP
eap=PEAP
identity="user@example.com"
password="foobar"
ca_cert="/etc/cert/ca.pem"
phase1="peaplabel=0"
phase2="auth=MSCHAPV2"
}
.fi
.RE
.TP 3
3.
EAP-TTLS/EAP-MD5-Challenge configuration with anonymous
identity for the unencrypted use. Real identity is sent only
within an encrypted TLS tunnel.
.sp
.RS
.nf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
network={
ssid="example"
scan_ssid=1
key_mgmt=WPA-EAP
eap=TTLS
identity="user@example.com"
anonymous_identity="anonymous@example.com"
password="foobar"
ca_cert="/etc/cert/ca.pem"
phase2="auth=MD5"
}
.fi
.RE
.TP 3
4.
IEEE 802.1X (i.e., no WPA) with dynamic WEP keys
(require both unicast and broadcast); use EAP-TLS for
authentication
.sp
.RS
.nf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
network={
ssid="1x-test"
scan_ssid=1
key_mgmt=IEEE8021X
eap=TLS
identity="user@example.com"
ca_cert="/etc/cert/ca.pem"
client_cert="/etc/cert/user.pem"
private_key="/etc/cert/user.prv"
private_key_passwd="password"
eapol_flags=3
}
.fi
.RE
.TP 3
5.
Catch all example that allows more or less all
configuration modes. The configuration options are used based
on what security policy is used in the selected SSID. This is
mostly for testing and is not recommended for normal
use.
.sp
.RS
.nf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
network={
ssid="example"
scan_ssid=1
key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
pairwise=CCMP TKIP
group=CCMP TKIP WEP104 WEP40
psk="very secret passphrase"
eap=TTLS PEAP TLS
identity="user@example.com"
password="foobar"
ca_cert="/etc/cert/ca.pem"
client_cert="/etc/cert/user.pem"
private_key="/etc/cert/user.prv"
private_key_passwd="password"
phase1="peaplabel=0"
ca_cert2="/etc/cert/ca2.pem"
client_cert2="/etc/cer/user.pem"
private_key2="/etc/cer/user.prv"
private_key2_passwd="password"
}
.fi
.RE
.TP 3
6.
Authentication for wired Ethernet. This can be used with
\fBwired\fR or \fBroboswitch\fR interface
(-Dwired or -Droboswitch on command line).
.sp
.RS
.nf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
ap_scan=0
network={
key_mgmt=IEEE8021X
eap=MD5
identity="user"
password="password"
eapol_flags=0
}
.fi
.RE
.SH "CERTIFICATES"
.PP
Some EAP authentication methods require use of
certificates. EAP-TLS uses both server side and client
certificates whereas EAP-PEAP and EAP-TTLS only require the server
side certificate. When client certificate is used, a matching
private key file has to also be included in configuration. If the
private key uses a passphrase, this has to be configured in
wpa_supplicant.conf ("private_key_passwd").
.PP
wpa_supplicant supports X.509 certificates in PEM and DER
formats. User certificate and private key can be included in the
same file.
.PP
If the user certificate and private key is received in
PKCS#12/PFX format, they need to be converted to suitable PEM/DER
format for wpa_supplicant. This can be done, e.g., with following
commands:
.sp
.RS
.nf
# convert client certificate and private key to PEM format
openssl pkcs12 -in example.pfx -out user.pem -clcerts
# convert CA certificate (if included in PFX file) to PEM format
openssl pkcs12 -in example.pfx -out ca.pem -cacerts -nokeys
.fi
.RE
.SH "SEE ALSO"
.PP
\fBwpa_supplicant\fR(8)
\fBopenssl\fR(1)
Last edited by malsagenda; 02-01-2014 at 09:43 PM.
Reason: Added config file.
I used that code, and just that code. I deleted everything else and put in my ssid and psk and reran the code you gave before and got the following errors
Code:
Line 7: invalid cipher 'ccmp'.
Line 7: failed to parse pairwise 'ccmp'.
Line 9: failed to parse network block.
Failed to read or parse configuration '/mnt/home/etc/wpa_supplicant/wpa_supplicant.conf'.
i would disable network manager (or whatever) from within the gui and if possible disable security for the time being on the router (wep/wpa/wpa2). then run :
When I ran that code, it didn't display any error messages, just new lined, and the network symbol on the tray changed from not connected, to connected. However, when I opened the browser to try and open a webpage, it instantly gave me a no internet access error.
btw, ran without any security (not something I'd want to do as a long term fix).
Ok, so it must have generated an error before and I just not have noticed (sorry, I've been pretty sick the last few weeks), because this time when I ran the code it told me that dhclient was an invalid command. After a quick search I found the command that works in puppy Linux (and hopefully does the same thing) and ran that. It timed out. I ran the other code you gave and copied the content for you all the same, in case it'd be useful in fixing this.
Code:
# sudo ifconfig wlan0 up
# sudo iwlist wlan0 scan
wlan0 Scan completed :
removed for length
# sudo iwconfig wlan0 essid 'REDACTED'
# sudo dhclient wlan0
sudo: dhclient: command not found
# sudo dhcpcd wlan0
dhcpcd[5848]: version 5.6.4 starting
dhcpcd[5848]: all: configured as a router, not a host
dhcpcd[5848]: wlan0: waiting for carrier
dhcpcd[5848]: timed out
dhcpcd[5848]: allowing 8 seconds for IPv4LL timeout
dhcpcd[5848]: timed out
# echo uname: && uname -a -m -p && echo lspci: && lspci && echo lsusb: && lsusb && echo lsmod: && lsmod && echo ifconfig: && ifconfig && echo ifconfig -a: && ifconfig -a && echo iwconfig: && iwconfig && echo resolv.conf: && cat /etc/resolv.conf && echo route: && route -n && echo ping router: && ping -c 1 `route | awk '/default/ {print $2}'` && echo ping dns-server: && ping -c 1 `awk '/nameserver/ {print $2}' /etc/resolv.conf | head -n 1` && echo ping using ip: && ping -c 1 64.235.229.141 && echo ping using dns: && ping -c 1 www.02144.com
uname:
Linux Netbook 3.9.11 #1 SMP Sat Jul 27 19:40:54 GMT-8 2013 i686 i686 i386 GNU/Linux
lspci:
00:00.0 Host bridge: Intel Corporation System Controller Hub (SCH Poulsbo) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller (rev 07)
00:1b.0 Audio device: Intel Corporation System Controller Hub (SCH Poulsbo) HD Audio Controller (rev 07)
00:1c.0 PCI bridge: Intel Corporation System Controller Hub (SCH Poulsbo) PCI Express Port 1 (rev 07)
00:1c.1 PCI bridge: Intel Corporation System Controller Hub (SCH Poulsbo) PCI Express Port 2 (rev 07)
00:1d.0 USB controller: Intel Corporation System Controller Hub (SCH Poulsbo) USB UHCI #1 (rev 07)
00:1d.1 USB controller: Intel Corporation System Controller Hub (SCH Poulsbo) USB UHCI #2 (rev 07)
00:1d.2 USB controller: Intel Corporation System Controller Hub (SCH Poulsbo) USB UHCI #3 (rev 07)
00:1d.7 USB controller: Intel Corporation System Controller Hub (SCH Poulsbo) USB EHCI #1 (rev 07)
00:1f.0 ISA bridge: Intel Corporation System Controller Hub (SCH Poulsbo) LPC Bridge (rev 07)
00:1f.1 IDE interface: Intel Corporation System Controller Hub (SCH Poulsbo) IDE Controller (rev 07)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
03:00.0 Ethernet controller: Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
lsusb:
Bus 001 Device 003: ID 18a5:0302 Verbatim, Ltd
Bus 001 Device 002: ID 0c45:62c0 Microdia Sonix USB 2.0 Camera
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
lsmod:
Module Size Used by
cpufreq_ondemand 3477 2
iptable_mangle 896 0
ipt_REJECT 1525 1
nf_conntrack_ftp 4663 0
nf_conntrack_irc 2595 0
iptable_filter 768 1
xt_state 791 4
nf_conntrack_ipv4 8174 4
nf_conntrack 42245 4 nf_conntrack_ftp,nf_conntrack_irc,xt_state,nf_conntrack_ipv4
nf_defrag_ipv4 811 1 nf_conntrack_ipv4
ip_tables 7028 2 iptable_mangle,iptable_filter
i2c_isch 2427 0
snd_hda_codec_realtek 22208 1
arc4 1403 2
fan 1789 0
ath5k 107247 0
ath 10797 1 ath5k
mac80211 181381 1 ath5k
snd_hda_intel 21530 0
snd_hda_codec 89269 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 3815 1 snd_hda_codec
snd_pcm_oss 26945 0
cfg80211 135774 3 ath5k,ath,mac80211
snd_mixer_oss 9719 1 snd_pcm_oss
uvcvideo 51647 0
videobuf2_core 18049 1 uvcvideo
videodev 64085 2 uvcvideo,videobuf2_core
videobuf2_vmalloc 1832 1 uvcvideo
videobuf2_memops 1087 1 videobuf2_vmalloc
snd_pcm 49809 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
squashfs 18829 0
snd_seq_dummy 911 0
aufs 122047 0
snd_seq_oss 19135 0
fuse 50594 1
r8169 39780 0
snd_seq_midi 3212 0
pcspkr 1239 0
snd_rawmidi 12121 1 snd_seq_midi
snd_seq_midi_event 3604 2 snd_seq_oss,snd_seq_midi
snd_seq 32145 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
acer_wmi 19666 0
sparse_keymap 1932 1 acer_wmi
rfkill 10220 2 cfg80211,acer_wmi
lpc_sch 2057 0
mfd_core 1933 1 lpc_sch
snd_timer 11925 2 snd_pcm,snd_seq
snd_seq_device 3492 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd 34649 12 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
gma500_gfx 129575 2
drm_kms_helper 18983 1 gma500_gfx,[permanent]
drm 152919 3 gma500_gfx,drm_kms_helper
soundcore 3222 1 snd
snd_page_alloc 4970 2 snd_hda_intel,snd_pcm
agpgart 17727 1 drm
i2c_algo_bit 3659 1 gma500_gfx
i2c_core 12529 6 i2c_isch,videodev,gma500_gfx,drm_kms_helper,drm,i2c_algo_bit
shpchp 17789 0
wmi 5775 1 acer_wmi
evdev 6640 1
thermal 6616 0
battery 8870 0
video 9468 2 acer_wmi,gma500_gfx
acpi_cpufreq 5414 1
mperf 799 1 acpi_cpufreq
processor 23207 1 acpi_cpufreq
thermal_sys 11722 4 fan,thermal,video,processor
hwmon 877 1 thermal_sys
button 3357 0
ac 2385 0
fbcon 28611 69
tileblit 1557 1 fbcon
font 6952 1 fbcon
bitblit 3494 1 fbcon
softcursor 817 1 bitblit
ifconfig:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:104 errors:0 dropped:0 overruns:0 frame:0
TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7536 (7.3 KiB) TX bytes:7536 (7.3 KiB)
wlan0 Link encap:Ethernet HWaddr 00:25:56:06:45:85
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)
ifconfig -a:
eth0 Link encap:Ethernet HWaddr 00:23:8B:E2:72:4B
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
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:104 errors:0 dropped:0 overruns:0 frame:0
TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7536 (7.3 KiB) TX bytes:7536 (7.3 KiB)
wlan0 Link encap:Ethernet HWaddr 00:25:56:06:45:85
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)
iwconfig:
wlan0 IEEE 802.11bg ESSID:"REDACTED"
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
lo no wireless extensions.
eth0 no wireless extensions.
resolv.conf:
# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line
route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
ping router:
BusyBox v1.21.0 (2013-02-18 15:57:06 WST) multi-call binary.
Usage: ping [OPTIONS] HOST
Send ICMP ECHO_REQUEST packets to network hosts
-4,-6 Force IP or IPv6 name resolution
-c CNT Send only CNT pings
-s SIZE Send SIZE data bytes in packets (default:56)
-t TTL Set TTL
-I IFACE/IP Use interface or IP address as source
-W SEC Seconds to wait for the first response (default:10)
(after all -c CNT packets are sent)
-w SEC Seconds until ping exits (default:infinite)
(can exit earlier with -c CNT)
-q Quiet, only displays output at start
and when finished
#
Just as a note, had to remove the output from the wlan scan for me to be allowed to post it (length). It scanned, and you can see all my neighbors wonderful wifi names in previous post. =)
Last edited by malsagenda; 02-06-2014 at 09:16 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
