On Thu, 13 Mar 2003, Karri Puumanen wrote: Hi Karri. Where I gre up, a Karri is a rather large tree;-) > Hi, > > I'am building a custom bootable Red Hat 7.3 installation CD. My problem is that kickstart/anaconda does not seem to recognize the onboard Intel PRO/1000 (e1000.o) chipset and add the alias entries to modules.conf file. I have modified the initrrd image to include the module and updated related information like pcitable etc. So, my questions are: > > 1. If the setup process identifies the network chips correctly, should it also update the modules.conf file? > 2. How can I troubleshoot the identification of PCI devices in setup process? > 3. What actually updates the modules.conf file in setup process? anaconda, kudzu ... ? My guess is it's recognised (or not) by Kudzu, based in what's in its hwdata file. Check the contents of /usr/share/hwdata/pcitable against the information lspci provides. A quick fix would be to add the relevant statements to modules.conf yourself in the %post section: echo >>/etc/modules.conf 'alias eth0 e1000' and if necessary, built the ifcfg-eth0 script too. Note that the echo statement is based on the assumption you run the %post script chroot (the default) to the target system. -- Please, reply only to the list.
