Red Hat Bugzilla – Bug 131172
Installation fails: Fedora doesn't detect media change
Last modified: 2015-01-04 17:09:19 EST
Description of problem:
When I try to install FC2 I run in the same problem for 2 weeks now:
when it seems the CD has to be changed, no message is shown, and the
CD is not ejected so the installation fails.
I have tried to prevent the CD-change by using a DVD. This also fails,
since as soon as it seems the actual installation is done and the
reboot prompt should appear, no prompt appears.
The CD's have been tried on 2 different CD drives, with the same
In both cases the computer hangs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Insert the boot-CD/DVD and reboot
2. Follow the instructions
3. When the actual installation starts, at the point where the next
CD should be inserted or the installation from DVD is ready and the
computer should reboot, the computer hangs. No messages to change
the CD or to reboot.
FC2 cannot be installed
FC2 installation to continu (prompt for CD change or reboot (DVD)
I have downloaded a total CD-set from two different mirrors and burned
them. Further, I have tried CD's and DVD to try to install FC2. All
CD's pass the mediacheck and their MD5-sums are correct. All have the
Motherboard: Asus P4P800 (I use the patch CD)
Processor: Intel 2.8 GHz
Harddisks: 2 x Maxtor 120 Gb SATA
DVD/CD-drive: NEC DVD RW 2500A
RAM: 1 Gb
The installation on another computer (Dell Inspiron 8200) went
I have used both CD/DVD-drives in my previous computer to install
FC1. No problem there.
Are there any error messages listed on tty3 or tty4?
I'm sorry I wasn't able to react earlier.
I am not able to access any of the other consoles. It doesn't matter
whether I install via CD or DVD - the computer just hangs without any
other information, or at least without me being able to access that
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.