2010/1/1 MJ Ray mjr@phonecoop.coop:
Srdjan Todorovic wrote:
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. [...] Any ideas please?
I wonder if one or the other had patched the kernel.
I think the only patch the Slackware kernel had was the recent security bugfix with afaik IP networking. Maybe this is making it work. I can't say about ubuntu - do they patch their kernels? I suspect they do. I did actually try 2.6.29.6 vanilla, and had no luck getting wifi to work.
Similar problems seem to appear at https://bugs.launchpad.net/ubuntu/intrepid/+source/knetworkmanager/+bug/2721...
Comment #81 seems to suggest this is a kernel issue, and one should try earlier kernels, but I doubt this is the case for me as 2.6.29.6 works on a different distro.
Also I should have mentioned (sorry) that this is with WEP. Most of the problems I've seen in bug reports are due to WPA and wpa_supplicant; (and also with NetworkManager).
http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1629 but I hate networking and don't know enough to spot the cause.
Only comment #11 seems relevant - the same reason value is given for disassociating, but the machine in question has not been doing a suspend/resume cycle.
The fixes suggested on intellinuxwireless.org don't look quick, while I think ubuntu haven't got a fix yet but their page is rather confusing.
Thanks for the links - it did bring up a possible command i could try: modprobe -v iwl3945 disable_hw_scan=1
It might be some hardware scan feature is causing a problem.
Thanks
Srdjan