Description of problem:
OK first of all forget the selected components cause i have no idea which
component is causing the fault, all i know is i downloaded the FC4-DVD.iso
file and burned this to a DVD R disc. The dvd booted ok into the kernel and
the init rd image loaded fine. But the installer reported it could not find
the Fedora Core CD in any of its cd rom drives after i had selected the
language setting for the installation. This happened in both GUI and Text
Version-Release number of selected component (if applicable):
How reproducible: Always on both a dell precision M60 and Acer 4050
Steps to Reproduce:
2.boot system from dvd
cd/dvd drive is ejected awaiting disc with fedora
Should load the installer program
Why is the download size of the DVD iso approx 2 gb, when the reported size on
the uk mirror site is 2.56gb. Also why does Red Hat not put the DVD image on
their own server???
If i recall this has happened with FC3 as well???
I think your ISO is corrupt. Please re-download it and use sha1sum to calculate
the checksum. Other try could be using: ide=nodma as boot parameter.
I have had the same problem on a PIII 550Mhz and a LG DVDÂ±R/Â±RW/RAM (GSA
I have tried to use the same DVD on another machine equipped with a P4 2.66GHz
and a newer LG DVD (GSA) and it worked fine.
Could it be related to the DVD burner?
(This is a mass update of bugs which have been in the NEEDINFO state unmodified
for over a year and have not been confirmed for a still supported version of
Closing per lack of response to previous request for information.
This bug was originally filed against a much earlier version of Fedora
Core, and significant changes have taken place since the last version
for which this bug is confirmed.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.