From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0b; Windows 98; Win 9x 4.90)
Description of problem:
After install of Red Hat Linux 7.1, the system will not boot up, hanging
at "Configuring Kernel Modules".
Steps to Reproduce:
1. Run the Red Hat installer, either graphical or text
2. Reboot after install to start system
(please see below for machine configuration)
Actual Results: System will not start, instead hanging at "Configuring
Kernel Modules". Pressing Ctrl-C produces the following:
/etc/rc.d/rc: /var/run/runlevel.dir: Read-only file system
updating /etc/fstab failed to open /etc/fstab.NEW: Read-only file system.
Then, Checking for new hardware is successful, leading to:
/var/lock/subsys/kudzu: Read-only file system.
Then, Setting network parameters and Bringing up interface lo run. The
next error is:
/var/lock/subsys: Read-only file system
A lot more errors show up after Starting System Logger... runs for awhile,
all of them having to do with read-only file system. Finally, the system
gets stuck in a loop where the following message is repeated over and over
for each ID process:
INIT: Id "1" respawning too fast: disabling for 5 minutes. It does this
for Id "1" through "6".
At this point, the system must be rebooted. Ctrl-Alt-Del produces a few
error messages, finally hanging (requiring a hard power off) at "Setting
system clock to hardware clock".
Expected Results: RHL 7.1 should come up and run normally.
ASUS PSB-F motherboard w/IDE controller on board
P-III 600E CPU
512 MB RAM
Samsung 40GB IDE HD
Creative 52X IDE CD-ROM
no net card, no sound card
ATI Xpert 128 video w/16MB RAM, PCI
Philips 109S monitor
MS wheel mouse and Natural Keyboard
Weird. Did anything strange happen during the install or did everything go
The installer completed as normal; no problems evidenced. Looks like it
finishes happily, although the video card is incorrectly detected (which is a
separate bug) and therefore Xconfigurator fails.
Can you run 'ddcprobe' and attach the output? Also, can you attach you
I can't run ANYTHING. The system does not come up, AT ALL. Therefore, I never
get shell access to run what you're looking for.
Is this related to bug #46686 that you filed? It seems like you are having a
couple of different problems at the same time. Have you tried just starting
over and installing again? I would recommend using text mode and try skipping
the video card test.
I've done that. The system still doesn't come up, and spits out the same
errors as before. I'm not sure it's ever getting to the point where X is
started, to be honest, before it hangs.
Well, it sounds like it's trying to start X, and then having a problem. What I
meant to suggest to you was to do an install and select text login instead of
graphical login. If you can get the system to at least come up to the text
login prompt, we can then try running X manually.
I saw a problem like this a few months ago, but I can't remember what the
problem was. I know that the ATI Xpert 128 cards work, though.
Well ... I've done that, too. I never get to a prompt of any type - it just
hangs up at Configuring System Modules and then spits out all the error
messages which I listed earlier in the bug, finally hanging up in the ID "1"
Really? You selected text login and it's still doing this?
Absolutely. No matter what login type I select, I never even get to a login
prompt. The system hangs on boot, giving the error messages described earlier
in this bug report.
Wow. I'm stumped. I can't think of anything else to try.
I'm stumped too, as well as a few knowledgable friends. Right now, I suspect
the hard disk. After downloading the .ISO images for 6.2 I burned CDs, but 6.2
did the EXACT same thing as 7.1.
We also replaced the video card, to a Matrox Mystique 4 MB card that I had
lying around in a box in a closet. Handy :)
I'm attempting to install (evil) Windows ME on the machine now, just to see if
ANY installation will take. If not, the next step is to replace the hard
disk. I'll keep you posted, if you like.
I hate to close this bug, but it just seems to go in the category of the
unexplainable, so I don't know what else to do. It does sound like a hardware
problem to me since 6.2 didn't work either, and it had a completely different
kernel than 7.1 If you see this problem appear on any other machines, please
reopen this bug. Feel free to keep posting, though, about what you find with