Server blew up, so repaired but now freezing on boot, caused by either Hald or messagebus
 

Hi all,

So my server gave up the ghost. PSU went for a pop, so I decided I may as well upgrade the M/B at the same time as replacing the PSU.
Anyway, that led to some issues with disc drives being renamed, (were originally hdc/hdd/sda and sdb - renamed to hda/hdb, with sda and b not changing), so a quick boot from Slackware13.0 usb allowed me to rewrite both fstab and lilo.conf (thanks vi)
Rebooted and looked good, until the GTK-Update called from rc.M.
The thing just stops, no warnings, no error messages in logs anywhere. The magickeys don't work, and the only thing to do is press the reset button.
A bit of digging, and disabling the following startup services:- httpd, mysql, udev, hal, cups and fuse soon had me up and running, and then starting them manually worked with no issues.

Then tried a reboot having re-enabled all of the services and immediately a freeze again. Anyway, a work through of the services seems to point to the culprit being either Hald or messagebus as disabling either of these allows the server to boot. Anyone got any ideas why these services will stop the server when started automatically, but when started manually it seems to run OK and how to get it running again without manual intervention?

TIA