Well, since I upgraded to kde4 my wifi has been painful see my recent string of messages). At kde4.1.3, I lost all access to wifi for a long time. Had to communicate via ethernet. Then I upgraded to 4.2.4, and got it back, though limping (it wouldn't come up automatically; I had to go through knetworkmanager each time I shut down, or my console timed out, or ...). NetworkManager worked fine, but wouldn't start up at boot or restart, even though it was configured in yast to do so. When I went on vacation to Alabama this past month, it wouldn't connect at all to the unsecured Windows wifi router at the beach (nor to any of the hotel wifi's as I traveled back to my home in Virginia). So I had to boot into xp to read my mail. When I got back to my son's home and connected to his Ethernet, it all functioned again without a hitch (well, after i started up NetworkManager). So now I'm home. I upgraded to 4.3 (I'd seen so much praise), hoping it would solve my problems. Applied all the updates up to this evening. NetworkManager still doesn't start up upon boot or restart. The new knetworkmanager won't connect automatically to my wifi even after I start NetworkManager manually (it did under 4.2.4). when I go through the knetworkmanager dialogs to connect to my home wifi, it sometimes connects for a few seconds, then goes offline and pops up the "secrets" dialog again (I know this because it downloaded my email several times, and allowed me to connect temporarily via Firefox twice). Usually it shows the "connecting to..." dialog, then pops up the "secrets" box again without connecting at all. It will do this many times. dmesg gives many repeats of the following: wlan0: authenticate with AP 00:1b:2f:46:e5:6c wlan0: authenticated wlan0: associate with AP 00:1b:2f:46:e5:6c wlan0: RX AssocResp from 00:1b:2f:46:e5:6c (capab=0x431 status=0 aid=11) wlan0: associated wlan0: disassociating by local choice (reason=3) (end of dmesg list) Occasionally, this sequence starts with wlan0: direct probe to AP 00:1b:2f:46:e5:6c try 1 wlan0 direct probe responded before the first line above. It doesn't seem to be my Netgear router; if I boot into xp, it connects immediately and lets me communicate, as it always has. It used to connect just like this with suse 10.3. It also lets me communicate using suse via ethernet (as I'm doing now). Data: hp dv6000 laptop opensuse 11.1, fully updated kde 4.3.00 "release 158" Intel Pro/Wireless 3945ABG iwl3945 driver Intel Pro/100 VE ethernet Linux 2.6.27.29-0.1-pae i686 2G ram 250G disk John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org