From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Description of problem:
This is the first boot of this machine after OS install.
The machine seems to boot fine
Enabling Local Filesystem quotas initializes fine, but enabling swap
space seems to initialize (it gets an [ OK ]) yet the computer
Version-Release number of selected component (if applicable):
Fedora Core 1 base install from cd
Steps to Reproduce:
1.Power on Machine
Actual Results: It froze
Expected Results: I would have expected the machine to bring up the
Initial Setup (after first boot)
If i change the default runlevel in /etc/inittab to run level '3' I
am able to boot into the system. I am still unable to boot the system
into X, I will try installing the proprietary Nvidia drivers as this
machine has a Nvidia GF2Pro Vid. card and see if this solves problems
Not sure if this is related to X or not, but I am sure it isn't
related to fedora-release... :-)
Changing component to xfree86 as a first attempt to find the relevant
Reassigning to kernel component, as there's no evidence of this
being related to X in any way. If swap is failing, that is likely
to be kernel related perhaps at least. Much more information
is required in order for conclusive analasys to be made in any
case at least.
This also happens using FC2 and booting kernel 2.6.6-1.435.2.3 or
kernel 2.6.7-1.494.2.2 into runlevel 3.
The original FC2 kernel, 2.6.5, will not hang just after "Enabling
swap space" as the .6 and .7 kernels do.
The hang comes from:
if LC_ALL=C fgrep -q 'Type: Sequential-Access' /proc/scsi/scsi
2>/dev/null ; then
within /etc/rc.d/rc.sysinit, which is within the SCSI tape section at
about line 741.
I have tried commmenting out the SCSI tape section and that results in
a later hang during the /etc/rc3.d/S??kudzu script.
FWIW, this occurs on an Athlon 800MHz, 320 MB ram.
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/