Red Hat Bugzilla – Bug 115993
ks=cdrom:/ks.cfg still non-functoinal
Last modified: 2007-11-30 17:07:00 EST
Description of problem:
Customer reports that placing ks.cfg in the root of a boot.iso cdrom
and specifying 'linux ks=cdrom:/ks.cfg' still fails with Red Hat
Enterprise Linux 3 Quarterly Update 1.
Placing the ks.cfg in the initrd and specifying 'linux file:/ks.cfg'
does still work, but is inconvienient.
What type of CDROM? (ie, IDE vs SCSI, if scsi, what controller)?
Possible reasons for client's problem
1) Unusual cdrom driver
2) Incorrectly created custom boot.iso
3) Multiple cdrom devices?
The CD was made on a IDE burner (HP), and was atempted to be read
from another (Matsushita) IDE CDROM.
After describing the problem, Chris Kloiber (firstname.lastname@example.org) was
able to reproduce the error using CD-RW media.
However, I am able to use the 'linux ks=file:/ks.cfg' procedure with
the kickstart file embeded in the initrd.img file.
I am creating the '.iso' file with:
mkisofs -o file.iso -b isolinux.bin -c boot.cat -no-emul-boot -boot-
load-size 4 -boot-info-table -R -J -v -T isolinux/
And I make my CD with:
cdrecord dev=0,0,0 speed=2 -pad -v -eject file.iso
Matt's above comment answers Jeremy's question, so I am moving out of
Chris or Matt: Can you point me at one of these non-working kickstart
isos? (Don't attach it, just give me a url or something.)
Chris Vanhoof tried it for me, and it only worked with the ks.cfg in
the initrd, using file: rather then cdrom:. The CD-RW has been
refromatted and reused. I'm not in Raleigh at the moment, ask Chris
Vanhoof to duplicate it again please.
Are there any updates to this?
Ill be testing this over the weekend. Ill have some results late
I have tested this and not been able to reproduce the failure. Others
claim to have reproduced it though.
If someone can reproduce this bug, then *please* save your boot.iso
and contact me. (Do not attach it to the bug; just contact me and
we'll work out a way for me to get access to it.)
Closing due to inactivity. If someone can reproduce this bug, then
please reopen and provide the details requested above.