Verner Kjærsgaard wrote:
Hi list,
SuSE10.3, plain vanilla. Linksys 311 wireless PCcard, old ThinkPad.
I install the wireless Linksys PCcard, I configure it using YaST, type in the WEP code and I'm airborne. Just fine. I leave the office, go home. I fire up Suse and Knetwork manager doesn't give me any wireless to see and connect to. I reconfigure (YaST) the Linksys. Nothing still. I reconfigure Linksys again, nothing in Knetworkmanager. I reboot. Nothing. I reconfigure. Nothing. I reboot. Nothing.
I swear at the box and kick it. I switch it off and leave it.
3 Hours later I get back, switch it on - and I'm airborne. Just fine. Me not understand. Switch off.
This morning, switch on..no wireless to see in Knetworkmanager. I reconfiure (YaST always says "not configured" to the wireless). I reboot, I kick it, I swear at it. No wireless. A wifi0 is to be found nowhere.
The Linksys PCcard is on all the time, leds are fine.
Anyone know what's going on?
If the wireless signal is weak, this should not lead Knetworkmanager not to show it, am I right?
Any hints? Mantras to say ?
KNetworkmanager is flacky at times, that is with some wifi it just won't do what it's supposed to. ;) For example, it won't work with the Intel 3945 chipset with the ipw3945 driver if using WPA for security and the access point is hidden. Most of us know that WEP is worthless!! But, if you use Yast to setup the card with the standard "if up" instead of KNetworkmanager, the card works great. So what I'd recommend is that you setup the card to not use KNetworkmanger and see if it works then. Fred -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org