From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 Description of problem: IBM T42 FC3 kernel-2.6.10-1.741 hal 0.4.7.1 dbus 0.22-10 e1000 driver for Intel Corp. 82540EP Gigabit Ethernet Controller ipw2200-0.21 driver for Intel Corp. PRO/Wireless 2200BG setup: network service turned off, eth0 onboot=no (wired) eth1 onboot=no (wireless) NM = NetworkManager-CVS-1-25-05 hal-device-manager reports values for the key net.80203.link for the Intel Corp. 82540EP Gigabit Ethernet Controller The value for net.80203.link stuck at 1 under certain boot conditions. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. NM service on, NMInfo on or off (NM brings up eth0 and eth1 at boot) plug in wire, boot hal-device-manager: net.80203.link value = 1 unplug wire: hal-device-manager: net.80203.link value = 1 plug in wire: hal-device-manager: net.80203.link value = 1 service hald restart: hal-device-manager: net.80203.link value = 1 plug in wire: hal-device-manager: net.80203.link value = 1 unplug wire: hal-device-manager: net.80203.link value = 1 net.80203.link value is frozen at 1 2. unplug wire reboot hal-device-manager: net.80203.link key not shown plug in wire: hal-device-manager: net.80203.link value = 1 unplug wire: hal-device-manager: net.80203.link value = 0 plug in wire: hal-device-manager: net.80203.link value = 1 unplug wire: hal-device-manager: net.80203.link value = 0 net.80203.link value is changing correctly 3. NM service off plug in wire, reboot ifup eth0 hal-device-manager: net.80203.link value = 1 unplug wire: hal-device-manager: net.80203.link value = 0 plug in wire: hal-device-manager: net.80203.link value = 1 unplug wire: hal-device-manager: net.80203.link value = 0 plug in wire: hal-device-manager: net.80203.link value = 1 net.80203.link value is changing correctly Actual Results: In experiment 1, the value of net.80203.link is frozen at 1. hal should be immuned to whatever NM is doing to it. Expected Results: In experiment 1, I would expect the value of the net.80203.link to change to 0 when the wired is unplugged. Additional info:
I think I've found the bug. Please try these packages http://people.redhat.com/davidz/hal-cvs20050126/ If it fails please include the relevant output of 'hald --daemon=no --verbose=yes' (e.g. from when you plug/unplug the cable). Thanks, David
I installed the hal packages and repeated the tests I reported a few hours ago. These packages appear to have fixed the bug. Wow, that was fast.
Thanks for testing this. The fix will appear in hal-0.4.7-2 which will hit Rawhide tomorrow.