Happy New Year everyone!
I've got a strange problem where my dad's laptop will sometimes associate with the wifi AP (but never ever get a DHCP response from it) when the laptop's running Kubuntu 9.04 or 9.10. A temporary install of Slackware 13 on the same machine showed that the laptop will associate with the AP and get an IP address very fast and with no problems. My laptop with a wifi device that uses the same driver works perfectly in Slackware 13...
Has anyone come across this problem? I've been on the #kubuntu channel today with not much useful help coming from there (understandable as it's New Years). There might be an issue with NetworkManager - that's now been uninstalled and replaced with wicd which seems to help a bit.
I was getting lots of "disassociating by local choice reason=3" in dmesg output which is output from the ieee80211 support layer in the kernel. The Kubuntu kernel that was tried also included 2.6.29.6 - which is the kernel that Slackware had. I suspect some weird ubuntu-ism or PEBKAC is at fault, but I'm running out of time to fix this.
The commands to reproduce: ifconfig wlan0 up iwconfig wlan0 essid myssid iwconfig wlan0 key s:mykey (yes the real key was correct but I'm not printing here) iwconfig wlan0 ap aa:bb:cc:dd:ee:ff dhclient wlan0
Somewhere after iwconfig key or ap, the wiconfig output lost all the ssid and key and ap settings (if they showed any beforehand). dhclient just sat there broadcasting for a response.
Wicd actually helped in the sense that once the GUI was told to connect, the iwconfig settings were set for essid/key/ap and the problem was that the interface could not get a DHCP response. The hardware RFKill switch was set to off (RF allowed).
Any ideas please?
Thanks, Srdjan