From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461; .NET
Description of problem:
When installing on a Intel 815E system (Desktop board D815EGEW w/1 GHz P-III)
at the final step I am asked to hit return to complete, which should result in
a reboot the system fails to proceed, although it is still responsive to the
keyboard and the mouse. Finally it is necessary to manually power down or to
init the machine. If you do so it boots properly and appears to work
correctly. If then you choose to 'shut down' it goes through all the steps,
but at the final line it fails to power down the computer. At this point it is
necessary to either manually power down or to hit the init button.
I do not believe it is the hardware as following this, and I repeated the
install several times, I installed Windows 2000 and it properly powers down as
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install LIMBO
2. When the final page is reached hit 'enter' as requested
3. System is locked up.
Actual Results: System hangs
Expected Results: It should have rebooted
Don't think it is hardware, as I then installed Windows 2000 and it works as it
should. Also I installed Limbo on a much older machine (a intel 810
motherboard 400 MHz Celeron) and it behaves exactly the same.
I can hear a small click comming from the machine at 'power down' time. It is
possible that the hard drive spins down, but the mainboard remains powered.
Error in original submission: Should have said: Reproducible: Yes, every time!
I have the same problem with powerdown on an ABIT BP6 (dual celeron 466).
Hard drive seems to power down, but computer stays on. I must hold down the
power switch for 5 seconds to actually power off the computer
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/