Bugzilla – Bug 136417
after adding a WLAN card, i need to restart NetworkManager manually
Last modified: 2005-12-09 19:08:41 UTC
i installed alpha3+ on a sony vgn-fs115b (e100 network, ipw2200 wlan). Since no firmware is available in alpha3+, i was not able to configure the WLAN card during installation. After installation, i added an extra installation source which provided the ipw-firmware package. I started yast, "network devices", "network card", selected the wireless card and pressed "managed by NetworkManager" button. ipw-firmware was installed, SUSEconfig ran and yast finished. After this, i had no network (only the lo interface) and the nm-applet icon showed me "No network connection". NetworkManager was still running (checked with "rcnetworkmanager status") but i had to restart it to get network connectivity back.
also, the wireless card does not show up in NM at all, although it has "STARTMODE=managed" set in its ifcfg-file.
after rebooting, wireless is now available, although i do not understand why. I did "rcnetworkmanager stop; rcnetwork stop; rcnetwork start; rcnetworkmanager start" before reboot but it did not help (and the nm-applet disappeared and had to be killed and restarted to reappear :-)
Are you saying that the problem went away? That it only happened on the first boot, before you setup the firmware? Can i close this? Or no ... ? I am unable to reproduce this -- I can hotplug wireless cards and they Just Work.
I'm trying to describe the problem again :-) After configuring (and thus "adding" the card) with YaST, there was no way to get it to work. It just did not show up in the nm-applet. After rebooting, it did show up, so i am not quite sure what changed. Maybe it has something to do with ipw2200 not having firmware at insmod time, later installing the firmware but the module not recognizing it and after reboot (with the firmware in place) everything was fine. I will retry this (but it might take until next week).
Alright. I think you are right about the firmware. In general, NM does not need the device to be configured, so long as it is present and the module is loaded (it really doesn't need anything but the HAL device). But if there are some firmware issues, that could be it. If the firmware is normally loaded during boot via hotplug, but not before it is YaST configured, that could be it. Not sure what we want to do about that.
Ah, Kay found the cause. HAL bug. Will track. *** This bug has been marked as a duplicate of 136657 ***