I D/Led FC3 all the discs are good (md5sum is ok)
db8c7254beeb4f6b891d1ed3f689b412 FC3-i386-disc1.iso
2c11674cf429fe570445afd9d5ff564e FC3-i386-disc2.iso
f88f6ab5947ca41f3cf31db04487279b FC3-i386-disc3.iso
6331c00aa3e8c088cc365eeb7ef230ea FC3-i386-disc4.iso
07bb34ce97b62b99f84d32812a2eec75 FC3-i386-rescuecd.iso

[joe@localhost joe]$ md5sum FC3-i386-disc1.iso
db8c7254beeb4f6b891d1ed3f689b412 FC3-i386-disc1.iso
[joe@localhost joe]$ md5sum FC3-i386-disc2.iso
2c11674cf429fe570445afd9d5ff564e FC3-i386-disc2.iso
[joe@localhost joe]$ md5sum FC3-i386-disc3.iso
f88f6ab5947ca41f3cf31db04487279b FC3-i386-disc3.iso
[joe@localhost joe]$ md5sum FC3-i386-disc4.iso
6331c00aa3e8c088cc365eeb7ef230ea FC3-i386-disc4.iso
[joe@localhost joe]$ md5sum FC3-i386-rescuecd.iso
07bb34ce97b62b99f84d32812a2eec75 FC3-i386-rescuecd.iso
[joe@localhost joe]$

The 1st one in each case is the correct md5sum , the 2nd one is generated
from the file
db8c7254beeb4f6b891d1ed3f689b412 FC3-i386-disc1.iso
db8c7254beeb4f6b891d1ed3f689b412 FC3-i386-disc1.iso

2c11674cf429fe570445afd9d5ff564e FC3-i386-disc2.iso
2c11674cf429fe570445afd9d5ff564e FC3-i386-disc2.iso

f88f6ab5947ca41f3cf31db04487279b FC3-i386-disc3.iso
f88f6ab5947ca41f3cf31db04487279b FC3-i386-disc3.iso

6331c00aa3e8c088cc365eeb7ef230ea FC3-i386-disc4.iso
6331c00aa3e8c088cc365eeb7ef230ea FC3-i386-disc4.iso

07bb34ce97b62b99f84d32812a2eec75 FC3-i386-rescuecd.iso
07bb34ce97b62b99f84d32812a2eec75 FC3-i386-rescuecd.iso
Any ideas on how I might get a good set of discs (disc 1 is ok) it's the only disc to pass the
integerty test.

I had failures with the integrity tests too, Someone here told me, During boot, when lilo gives you 2 options "enter" or F1. Hit F1, on the command line enter "ide=nodma", and it passed the tasts.

Apparently, anaconda, the install kernel has a problem with some CDROMs. (cdrom modules)

Hope I'm on the right track

Hi,

I had a similar issue. Downloaded ISOs and they MD5'd fine. Bunt the disks and the first one failed the integrity check. - all others passed. Then I retested the first one again and it passed ... Maybe it was a read error due to burning at high speed??? Not sure, but retest the disks a few times.

oops, double post.

see below

If it was a burn error, it would still be there.

I thinks it's a dma error, trying to read at high speed.

The cdrom module is broken, and some cdrom's like my sony 40x, don't work.

BTW I disabled the same feature in grub after it was all setup. It was soooo sloooow.

Yep you are rihgt, I meant a read error due to reading a disk at high speed,

Although, i have to say that I have found it more reliable to read disks that were recorded at lower speed ... or am I just imagining this???

Remember to remove ide=nodma from grub and/or lilo after you're setup.

to be safe use the boot configurator in "configure my computer" or

/etc/lilo.conf (run lilo after editing.)
and/or
/boot/grub/menu.lst

Why do you want to remove this setting after installing? Is it only an anaconda problem and not something in the actual Fedora core? It was difficult enough for me to find this setting to get my burnt CD's to pass mediacheck, and now I'm supposed to remove it? I'm confused...

Thanks!

sorry for taking so long to reply, I've been away.

That's right, it's just an anaconda driver/module problem.

To realise your ide speed again, find /etc/lilo.conf and delete the mention of "ide=nodma".

you must run "lilo" in a console after editing, to make the settings permanent.

Grub is easier to do, just edit /etc/grub/menu.lst in the same manner as above. No need to run anything after.

Not the whole line but just the phrase. "ide=nodma"

You can also do this in the configurator for boot-up.

Reboot to see the effect.

Hope this helps.

As far as I know, (I found this solution in these posts) it is not a fedora kernel problem. Just the setup app (anaconda).

Some entries that you put on the command line are integrated into the boot-loader for future booting.

Once you have the OS installed you can safely remove this entry.

The benifits will be realised by the speed of boot and any accessing of hard-drives and cdroms.

Cheers.

Gotcha. Thanks! I am not currently using either grub or lilo, chosing to boot from a CD for now while I'm just getting a feel for things. I can see where grub.conf changes need to be made, once I move on to that. My current boot CD was created with --kernelargs "ide=nodma", but I think I can probably override that when it comes to the boot prompt by entering ide=dma or something like that. If not, it's trivial to create a new boot CD without that nodma option (which I specifically requested via mkbootdisk!) Well, I'm learning. Slowly ... but I AM learning!

Thanks again.

OK, Good luck, and happy holiday season.

Thanks, Glenn

If you can burn from linux - try burning with -pad and -dao

IE if your burner is /dev/hdd

cdrecord -dev=/dev/hdd -speed=16 -pad -dao -v FC3-i386-disc1.iso

That satisfies some ( SOME ) of the cdrom drives that have issues with the ide cd driver.

To burn bootable FC3 discs, you must use the -dao option (disc at once) because cdrecord's default writing mode is tao (track at once).

On my Compaq Presario with a 48x Samsung SW-252S CD-R/RW drive, I used the following command to burn the FC3 discs:

# cdrecord -v -eject -dao -speed=16 dev=/dev/hdc FC3-i386-disc1.iso

I included the "-speed=16" to slow the drive down a bit. Also, make sure you're not running any other programs at the same time so there's no chance to overflow the buffers.

Which works perfectly well to create a bootable working cd.
Using dao and pad helps it pass the media check on some atapi cdrom drives, but is not required to make a good cd that boots and installs fedora core, and the only reason that disks burned tao fail the media check is because of a bug in the 2.6 kernel ide-cd driver. They still install just fine.