You are not logged in.
Hi, some days ago my wireless connection stopped working. Before it worked beautifully, then it suddenly stopped one morning without changing anything in the network configuration files (I use rc.conf with WEP). I think I updated the kernel to 2.6.34 the night before but I'm not sure.
Here's my lsusb:
Bus 002 Device 003: ID 07d1:3c03 D-Link System DWL-G122 802.11g Adapter(rev.C1) [ralink rt73]
Here's lsmod:
$ lsmod | grep rt
rt73usb 20705 0
rt2x00usb 6576 1 rt73usb
rt2x00lib 21985 2 rt73usb,rt2x00usb
led_class 1835 1 rt2x00lib
mac80211 161287 2 rt2x00usb,rt2x00lib
cfg80211 121416 2 rt2x00lib,mac80211
crc_itu_t 1045 2 rt73usb,firewire_core
gameport 7165 2 emu10k1_gp
parport_pc 27863 1
iTCO_vendor_support 1457 1 iTCO_wdt
parport 25403 3 ppdev,lp,parport_pc
usbcore 120437 6 rt73usb,rt2x00usb,usbhid,uhci_hcd,ehci_hcd
agpgart 23120 3 ttm,drm,intel_agp
rtc_cmos 7578 0
rtc_core 11823 1 rtc_cmos
rtc_lib 1486 1 rtc_core
And this is what I get from everything.log:
$ cat /var/log/everything.log | tail
Aug 9 18:49:33 maldiluna rpcbind: cannot create socket for udp6
Aug 9 18:49:33 maldiluna rpcbind: cannot create socket for tcp6
Aug 9 18:49:51 maldiluna kernel: wlan0: authenticate with 00:14:bf:c5:bb:a2 (try 1)
Aug 9 18:49:51 maldiluna kernel: wlan0: authenticated
Aug 9 18:49:51 maldiluna kernel: wlan0: associate with 00:14:bf:c5:bb:a2 (try 1)
Aug 9 18:49:51 maldiluna kernel: wlan0: RX AssocResp from 00:14:bf:c5:bb:a2 (capab=0x471 status=0 aid=2)
Aug 9 18:49:51 maldiluna kernel: wlan0: associated
Aug 9 18:49:53 maldiluna dhcpcd[2972]: version 5.2.7 starting
Aug 9 18:49:53 maldiluna dhcpcd[2972]: wlan0: broadcasting for a lease
Aug 9 18:50:23 maldiluna dhcpcd[2972]: timed out
It seems a timeout problem, but I tried increasing it up to 2 minutes without success. I have a laptop with an Intel wireless chipset and it connects without any problem, so I think the access point is working and that there might be a driver issue.
Thanks for the help.
Last edited by snack (2010-09-07 18:26:05)
Offline
I have found this similar discussion:
https://bbs.archlinux.org/viewtopic.php?id=96183
The problem they are reporting seems similar to mine. But my dongle worked fine when that discussion was opened, it stopped one week ago...
Offline
I resolved the problem: as I suspected it is a kernel issue. Downgrading to kernel26-2.6.33.4-1 and kernel26-headers-2.6.33.4-1 the problem disappeared. Since 2.6.35 is out and coming soon to the repos, should I file a bug?
Offline
With kernel 2.6.35 from [testing] everything works fine, so I think the problem is limited to 2.6.34. Hopefully it will not appear again in the future...
Offline
Just my 2 cents. If you can, switch to WPA2. WEP can be broken in under an hour.
Offline
Sadly for me, I have to revive this thread. Actually, kernel 2.6.35 doesn't solve the problem: it works only the first time I boot it after the installation. At successive boots the network won't start. The only way to make it work is to downgrade to 2.6.33, which works fine; if I then upgrade again to 2.6.35 it works only at first boot.
Does anyone have a similar issue / know what's going on / know what to look at? Thanks
Offline