If I shutdown or reboot the PC grub does not initialize, it does not even give the blinking cursor in the upper left corner. BIOS does post. If I power off the power supply and listen for the power discharge, boots up fine after that.



Here is the best order of events I can come up with:

Loaded XP, everything was working fine, decided to go with Fedora Core 2

Loaded FC2, I had some crazy power issues like mentioned above, but did not seem to have the same problems in windows.

Reloaded XP, I did not have any power issues.

Loaded FC1 do not remember having power issues this time, loaded a new kernel 2.6.6 and started having similar issues as mentioned above with a compounded wireless NIC issue that was locking up linux.

Bought new power supply

Loaded FC2 as a multimedia pc, made my own config, eliminated from what I remember APIC and APM and changed the processor to intel P4, and changed nothing else from what I remember

Worked great no power issues, but had done many different things to the kernel after it was working and wanted to reload just to make sure I could get it working again.

Reloaded FC2, no power issues, loaded 2.6.6 disabling the same 2 things and changing the processor to P4 again and now I have the power issues again.

It's not so bad I just leave it on all the time anyway, but if I lose power for just a second or for some reason have to reboot, I have to go throught he power it off ritual again.

Any ideas on this very long winded explaination of what hopefully is a very easy problem to resolve? Thanks.

non-one seems to know so let me give my 2 cents worth.

1) In your bios have you enabled or disabled the power settings?

2) Are you compiling a new kernel or using a distro supplied one?

3) I can't help with Fedora but you may find in your /etc/rc.d/ an rc.inetd or inetd or inetd2 type files. In slackware these are used to enable the APM and ACPI daemons for power management. Have a peep without overwriting to see if theres any mention of these settings.

slackware does not use systemV boot up scripts so it may take some patient looking unless you know how to use find or locate or grep commands.