<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Thanks to both Forrest Taylor and Brad Doctor for the quick response. Since sending my original email I have been playing around with the anaconda-ks.cfg file generated from a normal install, and learned a bit more. <blockquote cite="mid1082491817.12707.69.camel@bad.jf.intel.com" type="cite"> <blockquote type="cite"> <pre wrap=""> When I try to install with: linux ks=cdrom:/ks.cfg I get a "No driver found" window with the message "Unable to find any devices of the type needed for this installation type." </pre> </blockquote> <pre wrap=""> This looks like it is telling you that it cannot find the media for the installation. </pre> </blockquote> At the moment, I'm leaning more towards a problem accessing the hard disk. The anaconda-ks.cfg file works as is, but since the part and clearpart options are commented out, it takes you through an interactive install. When I uncomment the part and clearpart options, it generates the "No driver found" window. I also tried Brad's suggestion of adding allowcddma to the boot line, but without effect. <blockquote cite="mid1082491817.12707.69.camel@bad.jf.intel.com" type="cite"> <blockquote type="cite"> <pre wrap="">- the disk 1 ISO image for test 2 is not bootable. Technically, when I tested with the standard install CDs, I initially booted with the FC2 test 1 disk 1 and then swapped to FC2 test 2. </pre> </blockquote> <pre wrap=""> This has been discussed many times on the fedora-list and the fedora-test-list. I haven't had a problem yet booting from test2, but you are certainly not alone. I have successfully used kickstart, but I don't have the non-booting CD-ROM problem, so that may be the difference. </pre> </blockquote> Interesting. I tried both the FC2t2 disk 1 and my install CD on a Proliant, the only alternative hardware I have readily available. The FC2t2 disk 1 does boot. Both disks starve on a "Loading SCSI driver" window with the message "Loading CCISS" driver. That is at least a different message. Actually the Proliant platform is my desired target, but I've had a good deal of trouble getting it to work with anything beyond RHL 7.x. <blockquote cite="mid1082491817.12707.69.camel@bad.jf.intel.com" type="cite"> <blockquote type="cite"> <pre wrap="">- The current anaconda genhdlist program wants to write to RedHat/base rather than Fedora/base. I've been getting around this by symbolically linking Fedora to RedHat before calling genhdlist, then removing the link before creating the ISO file. </pre> </blockquote> <pre wrap=""> Use --productpath Fedora (or patch anaconda). </pre> </blockquote> Thanks to both Forrest and Brad for this suggestion. The --productpath option worked nicely. <blockquote cite="mid1082491817.12707.69.camel@bad.jf.intel.com" type="cite"> <blockquote type="cite"> <pre wrap="">- It appears to me that we will need an "selinux" option similar to the "firewall" option in the ks.cfg file, with options to disable, warn or enable. </pre> </blockquote> <pre wrap=""> Agreed. I thought I filed a bugzilla report, but I cannot find it. Test3 should be out soon, so I'll put this in bugzilla if it is not in test3. </pre> </blockquote> It appears your bugzilla report was successful. Once I looked in anaconda-ks.cfg I found the line: selinux --disabled (I'm currently disabling selinux because of problems with useradd even in non-enforcing mode -- which also has a bugzilla report out). I'm not sure where to take it from here, except to try and scrounge up some hardware that will install flawlessly from FC2t2 disk 1 and see if it handles my install disk also. Does anyone think this is worth escalating to bugzilla? Thanks, Marty </body> </html>