Network, HAL, avahi not started on boot

[daytooner]

Okay, I finally got my i2o raid array controller to boot. But several daemons, as well as the network failed to start. These include HAL and avahi.

When I boot up in rescue mode, and look in /var/log/messages, I see a lot of "permission denied"s. In particular: "localhost rpcbind" (cannot access /etc/hosts.*), and "localhost avahi-daemon[1612]: Failed to chroot():Permission denied"

Anyone know what's going on here?

Please, I need your help.

TIA

ken

[Seve]

Hello:

You might want to try starting the daemons in verbose or debugging mode to see if there is any more information provided.

See

man hald
man avahi-daemon

for more options / information.

If this is a new or relatively new install and you just got your hardware raid to boot, then you might consider a fresh install?

Seve

[daytooner]

Originally Posted by Seve

Hello:

You might want to try starting the daemons in verbose or debugging mode to see if there is any more information provided.

This is kind of a catch-22: since this is the first boot post installation, fedora wants to launch its firstboot program. This starts the X server, which can't find a mouse or keyboard - since HAL is not started - and so I have the welcome screen but no input devices. All I can do is a hard reset.

Is there something I can do from rescue mode? Or perhaps tell the kernel to start up in single user mode maybe?

If this is a new or relatively new install and you just got your hardware raid to boot, then you might consider a fresh install?

Seve

This is essentially a fresh install. I did have to make changes to the initrd init script, as well as rerun mkinitrd (from rescue mode) to get the kernel to boot from my array controller. But I don't know how any of those changes might have affected these daemons starting up.

ken