HAL Failed to Initialize

Lothoir · 12-02-2007, 05:20 PM

At bootup, the computer hangs on "Starting Hardware abstraction layer: hald" for a few minutes, but then boots up. When I log into GNOME I get a pop up saying "HAL has failed to initialize."

Running /etc/init.d/dbus restart I get:

Code:

/etc/init.d/dbus restart
Stopping Hardware abstraction layer: hald.
Stopping DHCP D-Bus daemon: dhcdbd.
Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Stopping system message bus: dbus.
Starting system message bus: dbus.
Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon failed!
Starting DHCP D-Bus daemon: dhcdbd.
Starting Hardware abstraction layer: hald

At which point the terminal hangs.

pidof hal returns no results.

Also, when I try to do anything with Synaptic or apt-get I recieve the following error:

Code:

E: linux-image-2.6.18-5-686: subprocess post-installation script returned error exit status 2
E: hal: subprocess post-installation script returned error exit status 1
E: gnome-mount: dependency problems - leaving unconfigured
E: gnome-power-manager: dependency problems - leaving unconfigured
E: gnome-volume-manager: dependency problems - leaving unconfigured
E: hal-device-manager: dependency problems - leaving unconfigured
E: linux-image-2.6.22-2-686: subprocess post-installation script returned error exit status 2
E: linux-image-2.6-686: dependency problems - leaving unconfigured
E: network-manager: dependency problems - leaving unconfigured
E: network-manager-gnome: dependency problems - leaving unconfigured
E: update-notifier: dependency problems - leaving unconfigured

The package I'm installing will work fine, but I get that error every time, it also hangs on hald for a long time.

Nutria · 12-03-2007, 02:49 PM

Quote:

Originally Posted by Lothoir

At bootup, the computer hangs on "Starting Hardware abstraction layer: hald" for a few minutes, but then boots up. When I log into GNOME I get a pop up saying "HAL has failed to initialize."

Has it ever worked, or did it just stop?

Willy Gommel · 12-03-2007, 11:27 PM

I hate to say this, but ...

I had a similar problem on my AMD64 machine. In order to solve it, I eventually had to explicitly tell aptitude to replace the lenny version with the one from sid. For me, that worked.

Hope it helps you out too.

Lothoir · 12-05-2007, 07:27 PM

Quote:

Originally Posted by Nutria

Has it ever worked, or did it just stop?

It worked fine before I updated to Lenny and got a new kernel, I was running Etch 2.6.18 before.

Quote:

Originally Posted by Willy Gommel

I hate to say this, but ...

I had a similar problem on my AMD64 machine. In order to solve it, I eventually had to explicitly tell aptitude to replace the lenny version with the one from sid. For me, that worked.

Hope it helps you out too.

I'll try that, thanks!

EDIT: Just did it, and while my machine boots up much quicker I still recieve the error when I log in.

Nutria · 12-05-2007, 09:21 PM

Quote:

Originally Posted by Lothoir

It worked fine before I updated to Lenny and got a new kernel, I was running Etch 2.6.18 before.

Do you have the 2.6.18 .config file?

Lothoir · 12-05-2007, 09:54 PM

No, but it was the default configuration that comes with Sarge.