Re: Unresolved symbols when using custom bootnet.img that has net driver added

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry, my whole posting didn't come through the first time.  Here it is
again.



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



[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux