Is the kernel you compiled it with the same version as the kernel image on the bootnet disk? -----Original Message----- From: Rebecca.R.Hepper@xxxxxxxxxxx [mailto:Rebecca.R.Hepper@xxxxxxxxxxx] Sent: Tuesday, October 08, 2002 10:22 AM To: kickstart-list@xxxxxxxxxx Subject: Unresolved symbols when using custom bootnet.img that has net driver added Hello All, I am trying to add a more recent e100.o module to the initrd.img in place of the e100.o module that is standard with RedHat 7.1. This new module is needed by my motherboard. I have been following the instructions for adding modules from a previous post --> http://www.redhat.com/mailing-lists/kickstart-list/msg02393.html I downloaded a tar file from the Intel site and compiled to create my new e100.o module. I added this module to the bootnet.img and added (I did not copy & paste) information to the pcitable file. I did not edit modules.dep or module-info(already had information for e100.o). When I kickstart, I see the following on the alt-F3 screen: going to insmod e100.o (path is NULL) /tmp/e100.o: unresolved symbol __kfree_skb_R047ef26a /tmp/e100.o: unresolved symbol __netdev_watchdog_up_R1bbf5ccf /tmp/e100.o: unresolved symbol skb_over_panic_R11ebe673 _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/kickstart-list
