BarbulaM1

I burned the 4 CD set of Fedora Core 3 and check them all. Disk 1 boots up perfectly fine. But when selecting the CD-Rom as the location of Fedora Core 3 I get:

CD Not Found
--
The Fedora Core CD was not found in any of your CDROM drives. Please insert the Fedora Core CD and press OK to retry.

and when pressing Crl+Alt+F4 I get

<6> ide-cd: cmd 0x28 timeout
<4> hdc: DMA timeout retry
<3> hdc: timeout waiting for DMA
<4> hdc: Status timeout: status=0xd0 {Busy}
<4> hdc: Status timeout: status=0x00
<3> hdc: Drive not ready for command
<4> hdc: ATAPI reset complete
<4> hdc: command error: status=0x51 {DriveReady SeakComplete error}
<4> hdc: command error: error=0x54
<4> ide: failed to opcode was 100
<4> isof_file_super: bread failed, dev=hdc, is_blknum=16, block=16

I have installed many OS's before but never a version of Linux. I have checked all of my IDE connections and my CD-Rom is secondary primary. I have no clue what the problem is please help.

kode

Boot with the 'Boot Disc' (Disc 1), then when you get to that screen, take out Disc 1 and put in Disc 2 before you select 'CD ROM'...

It's yet another item on Fedora's very long list of f*ups.

__________________
Blog - KB5UMQ - Linux User #272983
3 Rules:
1) "It doesn't work..." is simply not useful information.
2) Don't cross post!
3) If you are asking for help, start by telling us your distro/os and version.

BarbulaM1

Im still getting the same error, with the occasional <6> hdc: cdrom not found. I can also set it up fine in a virtual machine, but the virtual machine Im using is just a trial version . Could it be some type of bios problem.

HP XE783
Celeron 700 Mhz
256MB Ram
GeForce MX4000 64MB
IBM 40GB 7,200 RPM
Lite-On CDRW 40x12x48

kjax

^^^^^^^^^^^^^^^^^^^^^^^^

That's probably the problem right there. Some of the earlier LITE-ON drives pretty well sucked. Could try ide=nodma. I'd suggest starting cold, too- not warm reboots... I recall some of the older LITE-ON's (I think it was LITE-ON) that seemed to have problems with warm reboots... I don't recall if it was a driver problem or a hardware problem.