Re: DHCPCD no carrier
Hugo Barrocas <[email protected]>
| Newsgroups | gmane.linux.distributions.gobo.general |
|---|---|
| Message-ID | <CAMZ98SGrWbcrH-z4ncv2LTc-AhPXm9rDJ4bkFmiEogM8=ijy-A@mail.gmail.com> |
Hi, $lspci -nn shows that I have a Qualcomm Atheros AR9485 $lsmod ath9k 79613 0 ath9k_common 1406 1 ath9k ath9k_hw 372820 2 ath9k_common,ath9k ath 15635 3 ath9k_common,ath9k,ath9k_hw $iwconfig shows that wlan0 is listed, all seems ok. 2014-07-20 11:59 GMT, Jonas Neumann <[email protected]>: > Hi, > do you have the driver and the kernel module installed? > > Jonas > > On Sun, Jul 20, 2014 at 11:13 AM, Hugo Barrocas <[email protected]> > wrote: >> It's DHCPCD, not DHCPclient. >> DHCPCD doesn't have the -v option. >> But the problem may be another... >> >> At home I have a WPA network, so I've created a wpa.conf file with the >> setup to connect to it, like explained here: >> http://linux.icydog.net/wpa.php >> >> also noted that the > simbol removes all passwords from the wpa.conf file! >> if it's for adding, the » simbol can be used. >> >> so, running: >> $ sudo wpa_supplicant -D wext -i wlan0 -c /System/Settings/wpa.conf >> >> initializes ok, and outputs: >> ioctl[SIOCSIWFREQ]: Device or resource busy >> wlan0: Association request to the driver failed >> wlan0: Associated with f8:d1:11:2c:b7:fa >> wlan0: WPA: Key negotiation completed with f8:d1:11:2c:b7:fa [PTK=CCMP >> GTK=TKIP] >> wlan0: CTRL-EVENT-CONNECTED - Connection to f8:d1:11:2c:b7:fa >> completed [id=0 id_str=] >> >> opening another Terminology, and running >> $ iwconfig wlan0 >> shows that the network was associated ok. >> >> then >> $ sudo dhcpcd wlan0 >> dhcpcd[3794]: version 6.1.0 starting >> dhcpcd[3794]: wlan0: starting wpa-supplicant >> dhcpcd[3794]: wlan0: waiting for carrier >> dhcpcd[3794]: timed out >> dhcpcd[3794]: allowing 8 seconds for IPv4LL timeout >> dhcpcd[3794]: timed out >> dhcpcd[3794]: exited >> >> when dhcpcd is executed, the other window with the wpa_supplicant reports: >> ioctl[SIOCSIWFREQ]: Device or resource busy >> wlan0: failed to initiate AP scan >> ...and it goes in cycles trying to reconnect and failing. >> >> A wext driver problem? >> wpa_supplicant.conf file is the default with the Gobo015 release. >> >> -- >> Cumprimentos, >> D.er Hugo Barrocas >> _______________________________________________ >> gobolinux-users mailing list >> [email protected] >> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users > _______________________________________________ > gobolinux-users mailing list > [email protected] > http://lists.gobolinux.org/mailman/listinfo/gobolinux-users > -- Cumprimentos, D.er Hugo Barrocas