Hmmm. Funny how writing out problems sometimes leeds to ideas... Just remembered that modules have to be compiled against a kernel in order to work.
Paul >Hi all, I have been looking at getting FDDI support for Bering, I have successfully compiled a Bering kernel (on a debian machine) that supports FDDI as a module. The problem is when I declare the FDDI driver in '/lib/modules' and reboot I get a lot of unresolved symbols and the driver installation is unsuccessful. In total there is 24 lines of problems, I am including the first 8 or so as an example: <SNIP> Insmod: Unresolved Symbol request_region Insmod: Unresolved Symbol bh_active Insmod: Unresolved Symbol release_region Insmod: Unresolved Symbol card_stop Insmod: Unresolved Symbol init_smt Insmod: Unresolved Symbol smt_reset_defaults Insmod: Unresolved Symbol mac_add_multicast Insmod: Unresolved Symbol mac_driver_check_space <SNIP> The FDDI card is a Syskonnect SK5544 DAS and I compiled the driver (skfddi.o) for it on a RedHat 7.1 machine. FDDI support is built into the 2.x kernel and I have tried using the FDDI module (skfp.o) that is loaded when I use the card in a full linux distro but get the error: 'Skfp not a valid ELF file' Can anyone help? Or let me know where to look.. Thanks Paul ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
