> Will, > I was having a similar issue. If I correctly understand you (that you > want the boot disk to load e100 instead of eepro100), you need to edit the > pcitable in the modules directory of the initrd filesystem, and change the > occurances of "eepro100" to "e100." Of course, you need a working e100 > driver on the boot disk as well. I found that for 7.0 I needed to compile > it with the x-BOOT kernel config. I'm very nearly there. It's looking for the e100 module, I've cpio'ed it (figuring out the --format=crc bit too a while though grrr) all back up and now the module tries to load, but there are lots of resolved symbols. I take it this is because I"m not compiling it against the proper kernel config. How do you do that? In the configs dir, there is a boot config file, but moving that up a level and naming it .config did not seem to help matters. This file (the e100 1.6.6 driver from Intel's site) has it's own Makefile and is not inserted into the kernel tree like I'm used to. So how can I compile it against the x-BOOT kernel config? Thanks to everyone who has pitched in! Will > Cheers, > --Walker > > On Thu, 28 Jun 2001, Will Francis wrote: > > > > > > > name) works quite well. I'd like to have kickstart boot the > > > > RH e100 driver, > > > > then install a RPM which contains Intel's e100 driver and > > > > then have the > > > > post install script flip the kickstart boot floppy to a > > > > generic boot disk, > > > > reboot the machine with Intel's driver, and the put the floppy back to > > > > a kickstart floppy. > > > > > > This part loses me. Why do you want to flip the floppy to a generic boot > > > disk and then back? > > > > It's so I can do a completely monitor/keyboardless installation. My install > > process has a number in a file on each ks floppy. In the postinstall, I > > mount the floppy, and copy the file to the hard drive. Then, I do a > > mkbootdisk and make a generic boot floppy. The machine is rebooted off > > this floppy then. Once booted, a postinstall script of my own emails me > > the number from the file and the MAC address of the machine. another > > script then turns the now generic boot floppy back into a ks floppy and > > puts the file with the number back on it. This way I get an email that > > says something like "DISK 23 has installed on machine 0E:4C (which becomes the > > name of the machine), and I can take the boot floppy out > > and use it over and over again. I have just a few machines to do: > > > > http://www.anticlockwise.com/farm1.jpg > > http://www.anticlockwise.com/farm2.jpg > > > > (actually, these are less than a quarter of the machines now...) > > > > I'm trying to get all this GPL'ed so you may see it at some point. > > > > > What if you removed references to eepro100 in the boot disk, or better yet, > > > replaced it with e100? I assumed you were able to pull apart the > > > bootnet.img and place the e100 driver inside. > > > Thus if you replace the references to eepro100 with e100, it should probe > > > the card, and use the e100 driver instead. You could try using a driver > > > disk with the e100 on it, but it may give you similar results. > > > > Well, that's sort of what I'd like help with. I know how to tear apart a > > bootnet.img file, but there is already an e100 driver. I'd love to know > > how I can simply tell it to use the existing one. I'm a shell and perl geek > > and tracing through lots of python is lot so easy for me. How can I patch > > is so it says if you think you should use the eepro100 driver, use the e100 > > one instead?? > > > > Thanks > > > > Will > > > > > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list@xxxxxxxxxx > > https://listman.redhat.com/mailman/listinfo/kickstart-list > > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list >
