On Tue, 2008-04-29 at 08:57 -0200, Thomas M Steenholdt wrote: > Chuck Anderson wrote: > > On Mon, Apr 28, 2008 at 06:09:10PM -0400, Louis E Garcia II wrote: > >>> and if network does not come up on boot, could you mail me > >>> your /var/log/messages right after you've booted up so I can diagnose? > >> I think this is the problem: > >> > >> momcomputer NetworkManager: starting... > >> Apr 28 12:26:02 momcomputer NetworkManager: nm_hal_manager_new(): > >> Could not initialize connection to the HAL daemon. > > > > I just ran into this. The problem was that haldaemon wasn't starting > > before NetworkManger. I did this to fix all my problems with init > > script ordering: > > > > cd /etc/rc.d/init.d > > for script in *; do chkconfig --level 0123456 resetpriorities $script; done > > > > If this does indeed fix things on a fresh install, we probably want fix > whatever it broken to get the priorities right to begin with... Perhaps > this problem only occurs on installations that have been following > rawhide or something? Latest koji builds fix NetworkManager to handle HAL dropouts better, and to wait for HAL if HAL isn't yet started when NM starts. http://koji.fedoraproject.org/koji/buildinfo?buildID=47724 Dan -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
