I have Mandrake 10.0 installed, and have a dual boot with windoze XP Pro. I use LILO for the boot manager.

LILO does just fine when rebooting back to Mandrake, or if I choose to boot to XP from the login screen. If I choose "Restart Computer" from within a session, it works. If I choose "Turn Off Computer", from either the login prompt, or from within a session, it hangs, and I end up having to turn the computer off. (I've left it for 20 minutes - still hung).

I did not have this problem when ran 9.0, or 9.2. I hope someone can give me a place to look to solve the problem.

MDK has the default acpi=ht option passed to the kernel. Edit as root /etc/lilo.conf and try removing the option (if it's there). Don't forget to re-run lilo. You have to reboot in order to see if it works. This worked for me when i switched from AT to ATX.

Tried editing the file, turns out I have 4 lines with that string in it. the strings are:

"devfs=mount acpi=ht resume=/dev/hda6 splash=silent"
"devfs=mount splash=silent acpi=ht resume=/dev/hda6"
"devfs=mount acpi=ht resume=/dev/hda6 splash=silent"
"devfs=mount acpi=ht resume=/dev/hda6 splash=silent"

I'm still not using vi, or other line editor, but used Kwrite as root (I know I need to learn how to use vi/vim, but haven't yet).

I added a "#" at the front of each line, and ran lilo (as root), still hangs, giving me:

Halting system...
md: stopping all devices
md: md0 switched to read-only mode.
Power down

That's where it stops

Well, in fact you should have deleted only the "acpi=ht" part, not comment the whole line. Some entries are still useful . Each entry corresponds to a certain boot option.. You can either delete them all, all delete only the one in your current option. Also, you can try "acpi=off". Check my thread. The last post particularly. For me, removing the acpi option did the trick, then again, I'm using a custom-compiled kernel .

I was getting the "Power down." message and no power-off before I removed the "acpi=ht" option. After that, It went down by itself the first time.

OK, changing the *appropriate* portion of the line to "acpi=off", did nothing. Next step was to try deleting that portion entirely. That worked! Thanks for the help! Now, if I can only get help, or at least replies on a couple of other hitches (esp. the printer), I'll be estatic with this system!

I'm glad it works... The hardware can always be tricky, esp. when you have the wrong drivers or the right stuff doing a wrong thing (acpi should've been able to power down, but it couldn't, so it was up to the apm ).