I am using Cyperdrive CW058D, and yes i am burning at 16x to be sure it's working.


Edit : I just think it's wierd if it's the iso, since then it's both isos. I have never downloaded any game/os/programs before that came up with errors. And it's both Fedora core 2 and Suse 9.2

What CD-ROM device are you trying to run the install CD with?
Could you throw a different CD-ROM device into that PC and try to run the install again?

As said before, i have tried it on 3 different machines, same error.

On a Wintel box, can you copy all of the install CD-R file contents on to the harddrive?

There are many things that can affect burn quality of your CD-R writer.
General tips for CD-R writing:
Make sure your harddrive is defragged with at least 800MB of free space if possible.
Make sure DMA is enabled for your CD writer device.
Make sure buffer underrun protection is turned on.

Or, it could be that your Cyberdrive is starting to suck really bad at CD-R burning (eg failing / getting too old).

One way to determine whether or not the writer is at fault is to burn another install CD-R using a different writer.

Before you burn anymore CD's, verify that the ISO image that you downloaded is intact. You can do this by using the MD5SUM command
The output will be a long string of letters and numbers, which should match the published MD5SUM on the site from which you downloaded the images. If the numbers don't match, delete the file and download it again.

Once you have confirmed that the MD5SUM's match, then it's OK to burn them to a CD. Be sure to burn them as an Image file, rather than to just copy the image file to the CD.

Lastly, even though 16X should be a safe burn speed, I'd suggest dropping it down to 8X. Yes, it will take a few more minutes to burn, but so what, it's a one time "cost". If all goes well, this disk should be ready to go. Good luck with it -- J.W.

Just a quick thing maybe.

Check Bios, see if Block mode is enabled, or even if it's there.

Not a pro or anything but it's worth a shot I think.

I checked the md5sum and it's correct, so nothing to do with the iso, and yes i burned it with the option, burn image from nero. I looked for a block mode, but there is none on either of the three computers. I'll have to try a different burner some time then, that must be the fix then, only possibility left

I'm having the same issue. My Fedora Core 2 CDs pass the self test, but when I try to boot on them (using 4 different machine and player combos) it fails with a crc error. I'm going to the store to pick up some new CDRs and see if it is a problem with the media. I'll let you know how that turns out.
Jason.

Thanks for the reply, i used a different burner, and i got no problems at all! Thanks all, now my comp is running Suse 9.2 pro smoothly

I would recommend that you tried a different burner, as it worked for me.

After a long night of trial and error, swapping hardware, trying new media, re-downloading ISO's, and manipulating BIOS settings I thought I finally had my culprit.
It turned out to be my brand new Western Digital wd800 80G drive. When I removed it from my IDE chain and tried an old 8G Quantum BigFoot (and an old 40G Seagate), the CD tested and installed perfectly.
However...
On the final reboot, it will uncompress the kernel and at a point the kernel will panic. The process(kernel helper thread) that dies is probe_hwif a subprocess of ideprobe_init and the exit message is:
<0>Kernel Panic: Attempted to Kill init! and EIP is at disable_irq.

I have tested the memory with memtest86 but no issues exist there, except that the chipset banner is empty, I'm guessing without looking into it's code, that it doesn't recognize the memory controller.

A close friend suggested that it may have to do with BIOS SATA, special implementation on the hard drive, or a lack of new IDE driver in the Fedora Core 2 and Redhat 9 distributions so I'm currently downloading Knoppix and the new Fedora Core 3 to see if that helps.

I suspect that the memory or IDE controller is new and isn't supported by the distributions I have tried.

For any curious, the hardware I am having issues with:

ECS PM800-M2 motherboard with PhoenixBIOS 6.00PG
INTEL Celeron P4 2.0G processor
LITEONIT LTN 527T CDROM (also used a TOP-G BCD F560D)
FUJIFILM, and MEMOREX CDR media (not Read/Write).
Western Digital WD800 80G drive

I have the same problem. But I keep getting two different error messages (at random):
*****
RAMDISK: Compressed image found at block 0
crc error
VFS: Cannot open root device "<NULL>" or unknown-block(72,3)
Please append a coorect "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(72,3)
*****
Uncompressing Linux...

crc error

-- System halted
*****
Here's what I have tried:
-Ran a checksum test on the ISO files.. OK
-Stripped the PC for everything but the strictly necessary
-Tried different RAM chips
-Tried different CD-ROM players:
NEC CRD-1600A and LG DRD-8160B)
-Tried reburning ISO file at 4x in Nero instead of 40x
-Upgraded BIOS to latest version

My PC:
Motherboard: AOpen AX6BC with BIOS ver 2.59
CPU: PII 350MHz
RAM: 256MB PC100 CL2
HD: WD Caviar AC310200 10,2GB
Graphics: ASUS V8200 GeForce3
CD-Rom NEC 16x model: CDR-1600A
+ Floppy + PS/2 Keyboard & mouse

I get the (kind of) same error messages when I try to install Suse or Mandrake.
When I try the FC2 cd in another PII 350MHz machine, it works fine..
I think I have tried to start the installation at least 25times on my pc now, and only twice has it made it into the Anaconda installation program. (But I didn't want to run it with my PC stripped, so I aborted both times)
Could the AOpen motherboard cause the random, error-full beaviour?

Fixed it! It was the CD-ROM player(s)! Installed the player from the comp where the cd worked fine and suddenly it all worked! (and the loading started faster as well!)
The player that works is a Sony, model CDU701

Hi

What are the 5 md5sums for Suse 9.2 Professional btw ?

Swazi

I had this problem and found a solution (on my Dell Optiplex). First, some background:

I knew that I had good CD's and no hardware compatibility problems because I ran setup on an identical computer, I didn't get the error there, and the media test passed.

I fixed the problem by enabling "OS Install Mode" in my BIOS settings.