> 21:17 <rworkman> hanska: sounds like the driver (or something) is returning > bad > information that leads wicd to thing that the connection has died, so it's > "reconnecting" > 21:17 <rworkman> That's odd though, because I used the ipw2200 driver for a > long time with no issues > 21:18 <rworkman> You might have him check for and install the newest firmware > available for it (assuming it doesn't need a newer kernel, which is quite > possible), but I doubt it will help > > Can you please follow the above instructions? We're completely clueless at > this point, and any information might be useful.
here is the Linux kernel that I use: uname -a Linux tchao 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686 GNU/Linux that sounds like a recent kernel to me. for some reason, I have two versions of the firmware installed. I am not sure which one is in used. lib/firmware/ipw2200-bss.fw /lib/firmware/ipw2200-ibss.fw /lib/firmware/ipw2200-sniffer.fw /usr/lib/hotplug/firmware/ipw2200-fw-3.0/LICENSE.ipw2200-fw /usr/lib/hotplug/firmware/ipw2200-fw-3.0/ipw2200-bss.fw /usr/lib/hotplug/firmware/ipw2200-fw-3.0/ipw2200-ibss.fw /usr/lib/hotplug/firmware/ipw2200-fw-3.0/ipw2200-sniffer.fw I have cleaned version 3.0 and installed the package firmware-ipw2x00 version 0.16 which provides 3.0. I'll send the consequences of those changes next week when I am back home. thanks, eric -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
