>From: treed@xxxxxxxxxxxxxxx >>>Building initrd.img >>>Module 3c501 not found in kernel rpm >>>Module 3c503 not found in kernel rpm >>>Module 3c505 not found in kernel rpm >> Is your build system the same kernel and architecture as the release >you're trying to build? > >Yes. 2.6.18-92.1.6.el5 x86_64 for both. Are those 3c501, 3c503, 3c505 and the other modules supposed to be part of the standard kernel, or did you get them from somewhere else? Hmm, you'll probably get a better answer from someone who actually knows the relationship between modules in the running kernel and modules in initrd.img on x86_64 architecture. >Ah-hah...Well that seems rather silly. Maybe I shouldn't be using >buildinstall at all for what I'm trying to do (customize the CD)? If you're doing it this way, you're supposed to need buildinstall to provide the images your CD needs to boot. There is at least one hidden file, /.discinfo, that needs to be present and usually gets missed if you just copy the contents of a CD. I don't know what other manual steps would be necessary. There is a tool called Revisor (http://revisor.fedoraunity.org/) which may help you if you are running a graphical environment. I'm told it can handle CentOS. > To perform a CD-ROM-based kickstart installation, the kickstart file >must > be named ks.cfg and must be located in the boot CD-ROM's top-level > directory. You're right, that does sound weird. I think I see the problem, though: you need an extra slash in the URI for your kickstart file. At least, what works for me is a kickstart file /isolinux/install.cfg referred to using ks=cdrom://isolinux/install.cfg. I know, that's not what it says on http://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-kickstart2-startinginstall.html. Moray. "To err is human. To purr, feline" http://members.aol.com/edgwddirk _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
