I'm trying to install Suse 10.0 on a Piii 800mhz machine. On the first 'live' boot after the install process, it appears to hang starting the HAL daemon. Depending on the install config, I either see the line "starting HAL daemon" and it sits there until I power off or I watch a wait cursor forever (I've left it over an hour). This happens no matter which mode I install, Minimal gui, text only, full gnome, with my raid card and without. Any suggestions on what the problem could be? Since I can't boot the machine, looking at config files etc doesn't seem to be an option. Be sure to come back and let us know if our suggestions helped!

The same thing happens when booting in safe mode. Be sure to come back and let us know if our suggestions helped!

The only post I have found about this problem mentioned that the guy changed CD drives, so I disconnected the CD drive (which caused a floppy failure? so I configed MB to no floppy) and I am able to boot now. Guess I'll change the CD drive. Any other suggestions still welcome. THis is the second instance of being able to completely thru install then on first live boot something fails. If the install process can use the CD successfully, why doesn't the live boot have the same configuration? In the other instance, the install had no graphical problems but then the live boot wasn't configed properly to use the graphics card. Is this a Suse feature? Be sure to come back and let us know if our suggestions helped!

During an install the base system tries to be as compatible with as much hardware as possible, eg using vesa for a GUI, which is why things like X may work OK to start but when you reboot it tries a config for your graphics card (ati, nv etc) which may not work straight off. I find a simple reconfigure after your first boot (with something like x11/orgcfg) fixes the problem. Same with things like HAL, the system can try to be too clever sometimes! You could decide either not to install HAL or disable the service at boot, perhaps by mounting the partition with something like knoppix or a live suse cd and removing the rcX.d symlinks.

I think Suse is BSD-parented, so it might not have /etc/rc.d/init.d. If it does, or has the equivalent run-level file scripts (e.g., in my case, /etc/rc.d/init.d/haldaemon), you can boot at level 1 and edit haldaemon before the first executable line: echo "XXXXX NO $0";exit 0 I use this to disable daemons "I don't need" until I find out I do need them.