> -----Original Message----- > From: lccha-rhlist@xxxxxxxx [mailto:lccha-rhlist@xxxxxxxx] > Sent: Friday, May 07, 2004 4:11 PM > To: Discussion list about Kickstart > Subject: Re: NFS kickstart fails with e1000.ko drivers > > > Once upon a time (like on May 07, 2004), ccollier@xxxxxxxxxxx wrote: > > On Fri, 7 May 2004, Joe Cooper wrote: > > > Joe Robertson wrote: > > --snip-- > > > I'd be pleased as punch if someone would tell me what I > missed in my > > > modifications of the kickstart initrd image, that would make this > > > work...Even a simple list of files that must be changed > when adding a > > > new or modified driver to the kickstart image (so I could > spot the one I > > > didn't change) would be exceedingly useful. > > --snip-- > > > > I struggled with some similar issues with the e1000 and rh 7.3. > > Typically, for module insertion into the ramdisk you have > to edit these > > three files found inside the ramdisk: > > Hi - > > I too struggled with e1000 vs RH 7.3 in the past, and had > similar symptoms to what Joe described. I found it easier to > compile support for the e1000 into a new kernel image and use > that for kickstart instead of trying to add the e1000 module > into the ramdisk. > > We've had a few sets of machines with this card. When we > purchased our machines, the rev of the card was changing > pretty frequently, so we'd have to check for updated e1000 > drivers from Intel's website pretty often. Hopefully things > are more stable now. > > -L > I'm using Fedora Core 2 test 3 and the e1000 driver is already included in the ramdisk - /modules/modules.cgz I'm not familiar with compiling the kernel image. I assume that if it is in the ramdisk, then it probably isn't compiled into the kernel in the distribution? Joe > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickst> art-list >
