From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008041301 Fedora/3.0-0.54.beta5.fc9 Firefox/3.0b5 Description of problem: NetworkManager fails to start if it can't talk to HAL. If I run_init /etc/init.d/NetworkManager restart the stop fails (no NM to stop) and the start succeeds and the network comes up. in /var/log/messages during boot: Apr 23 11:10:52 comms NetworkManager: <info> starting... Apr 23 11:10:52 comms NetworkManager: <WARN> nm_hal_manager_new(): Could not initialize connection to the HAL daemon. when I restart NM: Apr 23 13:54:46 comms NetworkManager: <info> starting... Apr 23 13:54:46 comms NetworkManager: <info> Trying to start the supplicant... Apr 23 13:54:46 comms NetworkManager: <info> eth0: Device is fully-supported using driver 'tg3'. Apr 23 13:54:46 comms NetworkManager: <info> Found new Ethernet device 'eth0'. Apr 23 13:54:46 comms NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_11_85_8d_38_44 Apr 23 13:54:46 comms NetworkManager: <info> Trying to start the system settings daemon... Apr 23 13:54:46 comms nm-system-settings: ifcfg-fedora: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Apr 23 13:54:46 comms nm-system-settings: ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... Apr 23 13:54:46 comms nm-system-settings: ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... Apr 23 13:54:50 comms NetworkManager: <info> Bringing up device eth0 Apr 23 13:54:51 comms NetworkManager: <info> Deactivating device eth0. Apr 23 13:54:51 comms NetworkManager: <info> Deactivating device eth0. Apr 23 13:54:51 comms NetworkManager: <WARN> auto_activate_device(): Connection 'System eth0' auto-activation failed: (2) Device not managed by NetworkManager Apr 23 13:54:53 comms NetworkManager: <info> Activation (eth0) starting connection 'System eth0' Apr 23 13:54:53 comms NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Apr 23 13:54:53 comms NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... Apr 23 13:54:53 comms NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Apr 23 13:54:53 comms NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Apr 23 13:54:53 comms NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... Apr 23 13:54:53 comms NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. Apr 23 13:54:53 comms NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Apr 23 13:54:53 comms NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. Apr 23 13:54:53 comms NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Apr 23 13:54:53 comms NetworkManager: <info> Activation (eth0) Beginning DHCP transaction. Apr 23 13:54:53 comms NetworkManager: <info> dhclient started with pid 3036 Apr 23 13:54:53 comms NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Apr 23 13:54:53 comms NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit Apr 23 13:54:56 comms NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound Apr 23 13:54:56 comms NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... Apr 23 13:54:56 comms NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started... Apr 23 13:54:56 comms NetworkManager: <info> address 192.168.20.101 Apr 23 13:54:56 comms NetworkManager: <info> netmask 255.255.255.0 Apr 23 13:54:56 comms NetworkManager: <info> broadcast 192.168.20.255 Apr 23 13:54:56 comms NetworkManager: <info> gateway 192.168.20.1 Apr 23 13:54:56 comms NetworkManager: <info> nameserver '151.164.20.201' Apr 23 13:54:56 comms NetworkManager: <info> nameserver '208.67.222.222' Apr 23 13:54:56 comms NetworkManager: <info> nameserver '151.164.11.201' Apr 23 13:54:56 comms NetworkManager: <info> nameserver '208.67.220.220' Apr 23 13:54:56 comms NetworkManager: <info> hostname 'rawhide' Apr 23 13:54:56 comms NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... Apr 23 13:54:56 comms NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. Apr 23 13:54:56 comms NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... Apr 23 13:54:57 comms NetworkManager: <info> Policy set (eth0) as default device for routing and DNS. Apr 23 13:54:57 comms NetworkManager: <info> Activation (eth0) successful, device activated. Apr 23 13:54:57 comms NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. /etc/sysconfig/network-scripts/ifcfg-eth0: # Broadcom Corporation NetXtreme BCM5782 Gigabit Ethernet DEVICE=eth0 BOOTPROTO=dhcp HWADDR=00:11:85:8D:38:44 IPV6INIT=yes IPV6_AUTOCONF=yes ONBOOT=yes TYPE=Ethernet NM_CONTROLLED=yes USERCTL=no PEERDNS=yes hald is running: [root@rawhide ~]# ps -C hald PID TTY TIME CMD 1902 ? 00:00:00 hald Version-Release number of selected component (if applicable): NetworkManager-0.7.0-0.9.2.svn3566.fc9.i386 How reproducible: Always Steps to Reproduce: Boot :( Actual Results: Expected Results: Additional info: MLS/Permissive/Rawhide
fixed in latest koji builds; NM handles HAL dropouts and if HAL isn't started before NM, NM will wait