Bugzilla – Bug 136657
HAL not detected add/remove network interface if not add/remove related device
Last modified: 2007-06-05 11:04:25 UTC
Using the latest-and-greatest NM packages on a Vaio vgn-fs115b (ipw2200 wireless, e100 wired): testuser@linux:~> rpm -qa Network* NetworkManager-0.5.1cvs20051201-1 NetworkManager-gnome-0.5.1cvs20051201-1 If i start network manager without ipw2200 loaded, i get the following: (====== are my comments :-) linux:/home/testuser # rmmod ipw2200 linux:/home/testuser NetworkManager --no-daemon linux:/home/testuser # NetworkManager --no-daemon NetworkManager: <information> starting... NetworkManager: <information> eth1: Driver 'ipw2200' does not support carrier detection. You must switch to it manually. ===== the driver is not loaded ============ NetworkManager: <information> nm_device_new(): waiting for device's worker thread to start NetworkManager: <information> nm_device_new(): device's worker thread started, continuing. NetworkManager: <information> Now managing wired device 'eth1'. ===== it is not wired, and it does not exist ===== NetworkManager: <information> Deactivating device eth1. NetworkManager: <information> Will activate wired connection 'eth0' because it now has a link. NetworkManager: <information> Device eth0 activation scheduled... NetworkManager: <debug info> [1133521482.554844] (): found config /etc/sysconfig/network/ifcfg-eth-id-00:01:4a:19:1e:cb for if eth0 ===== this works now ====== Also, nm-applet now shows me 2 wired interfaces (i will attach a small screenshot). if i now modprobe ipw2200, NM does not notice this (no output on the console at all) and wireless does not work.
Created attachment 59687 [details] screenshot of the nm-applet popup
further investigation shows that this looks like a HAL problem. - boot, but don't load ipw2200 - start hal - lshal shows, that the pci device is found, but no network device is found. - now load ipw2200 - hal does not recognize this. - start NetworkManager - NM only sees eth0, the wired interface. The other way round it is the same: if you rmmod ipw2200, HAL insists that there is a device with sysfs path /sys/class/net/eth1 although there is no eth1 anymore. lshal --monitor shows nothing when insmod/rmmoding ipw2200. taking HAL maintainer into CC:
Yes, this is a HAL bug or a bug in our module handling / hotplugging of network devices. Also - does everything work if you don't mess with anything? E.g., let the modules load as intended. I am reassigning to dkukawka, but someone else might want to own this.
NM requires the info.linux.driver property set at the physical device. A later module load seems not to create that property. Only the coldplug scan during HAL startup does this.
Should be fixed in HAL CVS now.
*** Bug 136417 has been marked as a duplicate of this bug. ***
submitted new package to STABLE