Hello, Stuart; Thanks for that reminder, it was, indeed, the root cause. I have rebooted using the previous kernel version and the wi-fi is now back running.
Stuart D. Gathman wrote: > On Sat, 26 Jan 2008, Bill Lee wrote: > >> Browsing the log/messages: after the update, the system was rebooted. I >> see in the log the messages about shutting down the wlan0 interface, but >> when the system rebooted, there is NO mention of wlan0 in the log. Looks >> like for some reason, wlan0 has been lost. >> >> The router is a Kyocera KR1. I am running it with a 128 bit WEP key. >> Nothing has changed on the router side, only the update to NM. >> >> Any idea what's going on? Everything was working perfectly before the >> update this afternoon. > > NetworkManager is not the problem. The updates installed a new kernel - > 2.6.23.14-107.fc8. The new kernel doesn't have a driver for wlan0. You don't > mention what you wlan device is (router is irrelevant). Sorry I didn't mention this. The machine includes a Broadcom BCM4306 802.11b/g Wireless LAN Controller (rev 02). > One guess > might be that you are using ndiswrapper, because it is a Broadcom or > other proprietary device. Ndiswrapper has not been updated on livna.org > for the new kernel yet. I am using "driverloader" from Linuxant.com. I have been using their software for several years, ever since I bought this laptop back in 2004. And, yes, it, too, is kernel-version sensitive and they, too, have not yet produced a version for the latest kernel, 2.6.23.14-107.fc8. > You can reboot and select your previous kernel > to see if that fixes your problem. Yes, that did fix the problem. > To make the previous kernel permanent > (until livna is updated), edit /etc/grub.conf as root and change the default. > And this will be done as well for now. Thanks for the help. Regards, Bill Lee _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
