From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Description of problem:
GUI install completes with no problems. All defaults taken. Kernel doesn't
finish loading, hangs at:
"Configuring kernel parameters [ok]"
Keyboard input is still echoed. Screen goes black after ~1 min.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: Hangs as described above.
Expected Results: Finish loading services and prompt for logon.
Pentium P3 550
20 gig IDE
Aureal Audio PCI
NetGear FA310 PCI
ATI Rage IIC PCI
can you add the parameter 'single' to the kernel commandline (in lilo or grub)
and check if there are files starting with __ in /var/lib/rpm ? (if so, delete
The rpm stuff isn't until a lot later in rc.sysinit; the next thing after runing
sysctl is setting the clock...
On this same machine I tried to install an old copy of RedHat 5.2 and it hung
after installation with a meesage about setting the clock. The machine was
previously running NT 4 with no problems.
It seems there is a problem with the RTC on this machine. The time can be set
from BIOS or DOS, but the RTC doesn't advance the time when the power is off.
The kernel may be waiting for the RTC to advance.
This isn't an rpm problem AFAICT
I have the same problem with 7.3.
I've observed the same on FC2. The cause was the following
My laptop computer (Evo N600c) remained on battery until complete
exhaution. When I put it back on power, linux refuses to boot
(blocked on "Configuring kernel parameter"), and w2k seems to work,
but the time is not running when I turn the computer again off.
Solution was very simple : remove the main battery from the laptop
and plug it again. At boot, RTC returns in the 80's, but at least
linux boots again.
I guess that the lithium RTC battery is exhausted, and the main power
supply is used to feed the RTC, probably when the main supply was
almost empty, RTC fell in an unstable state.
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/