You are not logged in.
Hi,
After several months I updated my laptop with pacman -Syu (407 new packages), and now DHCPCD fails over my wireless connection (not eth0). I connect through netcfg/net-profiles with the profile Wireless. The card us a Ralink RT2500 Wireless 802.11bg.
Does someone have an idea why it doesn't work? This is the various relevant configs and outputs:
CONNECTION="wireless"
DESCRIPTION="A wpa_supplicant configuration based wireless connection"
INTERFACE="wlan0"
SECURITY="wpa-config"
WPA_CONF="/etc/wpa_supplicant.conf"
IP="dhcp"
network={
ssid="sorry voor de hobo"
proto=WPA
key_mgmt=WPA-PSK
pairwise=CCMP
group=CCMP
psk=X
}
DEBUG: Loading profile Wireless
DEBUG: Configuring interface wlan0
:: Wireless up [BUSY]
DEBUG: status reported to profile_up as:
DEBUG: Loading profile Wireless
DEBUG: Configuring interface wlan0
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up start_wpa wlan0 /etc/wpa_supplicant.conf nl80211,wext
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up ifup
DEBUG: wireless_up start_wpa wlan0 /etc/wpa_supplicant.conf nl80211,wext
DEBUG: wireless_up wpa_check
DEBUG: wpa_cli -p /var/run/wpa_supplicant -i wlan0 status
DEBUG: Loading profile Wireless
DEBUG: Configuring interface wlan0
DEBUG: ethernet_iproute_up ifup
DEBUG: ethernet_up dhcpcd -qL -t 10 wlan0
DEBUG:
> DHCP IP lease attempt failed.
DEBUG: Loading profile Wireless
DEBUG: Configuring interface wlan0
DEBUG: Loading profile Wireless
DEBUG: Configuring interface wlan0
DEBUG: ethernet_down if_down
DEBUG: wireless_down stop_wpa wlan0
DEBUG: profile_up connect failed
[ 314.761284] wlan0: authenticate with 00:1a:70:9e:3a:70 (try 1)
[ 314.763050] wlan0: authenticated
[ 314.763180] wlan0: associate with 00:1a:70:9e:3a:70 (try 1)
[ 314.765555] wlan0: RX AssocResp from 00:1a:70:9e:3a:70 (capab=0x411 status=0 aid=2)
[ 314.765561] wlan0: associated
[ 327.763676] wlan0: deauthenticating from 00:1a:70:9e:3a:70 by local choice (reason=3)
[ 327.783818] cfg80211: Calling CRDA to update world regulatory domain
[ 327.794838] cfg80211: World regulatory domain updated:
[ 327.794850] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 327.794856] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 327.794861] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 327.794865] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 327.794870] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 327.794874] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Thanks!
Last edited by anadyr (2012-04-21 22:36:11)
Offline
Try the workaround indicated in this thread (increasing the carrier timeout).
Burninate!
Offline
For some reason the option CARRIER_TIMEOUT=60 is not read from my network profile. I set it to 60 seconds, but it uses a timeout of 10 seconds (as it still issues the command "dhcpcd -qL -t 10 wlan0"). Or should I set the option CARRIER_TIMEOUT=60 somewhere else?
Edit1: I added the option "timeout 60" to dhcpcd.conf, but netcfg still uses a dhcpcd timeout of 10 seconds...
Edit2: I now added DHCP_TIMEOUT=60 to my profile, and now netcfg does use 60 seconds. But unfortunately it does not solve the problem...
Last edited by anadyr (2012-04-06 06:56:27)
Offline
I didn't fix it yet. Here is the output of "iwconfig wlan0". Does this output give any indications why the last command "dhcpcd wlan0" timeouts?
[root@../etc]# iwconfig wlan0
wlan0 IEEE 802.11bg ESSID:"sorry voor de hobo"
Mode:Managed Frequency:2.437 GHz Access Point: 00:1A:70:9E:3A:70
Bit Rate=9 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality=60/70 Signal level=-50 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:2 Invalid misc:5 Missed beacon:0
[root@../rogier]# wpa_cli status
Selected interface 'wlan0'
bssid=00:1a:70:9e:3a:70
ssid=sorry voor de hobo
id=0
mode=station
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=WPA-PSK
wpa_state=COMPLETED
Thanks!
Last edited by anadyr (2012-04-14 07:37:49)
Offline
I have the same problem. Or rather had. I updated my laptop after a few weeks (including kernel update) and wpa_supplicant would timeout , the option -ddt (maximum verbose) didn't give me any useful information. So I decided to compile and install an older version of the ath9k driver from compat-wireless. This solved the problem. So the update somehow breaks ath9k. Maybe it's the case for your driver too.
A convenient way to install your own driver is to use the package
https://aur.archlinux.org/packages.php?ID=41472
from AUR, the PKGBUILD file allows you to select the driver you want (uncomment a line in it) so that you don't spend 5 hours compiling useless stuff, it will take you 15 seconds. But maybe this is bad advice I am by no means an expert.
Last edited by anon1054572 (2012-04-14 17:08:46)
Offline
I also had a similar problem after an important update (long time).
I got a few gray hairs, then tried to reinstall the kernel (pacman -S linux)—and it did fix it.
Offline
I still haven't been able to fix it; I am not able to bring up a wireless connection, also not in the latest kernel 3.3.2.
I also tried the solution suggested here, but that doesn't work either as it somehow disables the wireless switch ("RTNETLINK answers: Operation not possible due to RF-kill". The rfkill command doesn't change this and the physical wireless switch is not responsive). I haven't tried the AUR-version of compat-wireless, but I'll give it a try if there are no further suggestions.
To resume: the last working kernel was 2.6.31. Then the minimum kernel became 2.6.32 and I had to update. From then on wireless stopped working. It is a rather old laptop (about 2004 I think, a Twinhead E12BL).
Offline
I found the problem. I had an ndiswrapper.conf file in the /etc/modprobe.d with the line "alias wlan0 ndiswrapper". I really can't remember anymore why I had this, but I uncommented it and works again...
Edit: the problem returned soon after, so this wasn't the problem. Instead it turned out that it was the power saving function. I can connect now after turning this off (iwconfig wlan0 power off).
Last edited by anadyr (2012-04-23 13:36:07)
Offline