I am a long time Eigerstein/Bering user who has been happily using a three-interface Bering box for some time.
I have a friend also using Bering, and he told me he could not get the ne.o module to work with his box when he attempted to migrate to the latest Bering uclib. So I thought I'd try to do the same thing on my three interface box. I downloaded Bering Uclib 2.1 and the corresponding modules and copied ne.o to /lib/modules, and configured the modules package the same way I did before: 8390 ne io=0x340,0x240,0x300 Upon boot, I did see a message saying those modules were being used, but I did not see the message I am used to seeing with Bering telling me the exact port and interrupt used with the ne2000 boards. I also saw error messages telling me that eth0 did not exist. Then I looked in /var/log/messages and saw these two lines: root: modutils module 8390 could not be loaded root: modutils module ne could not be loaded Does anyone have any idea why these two modules are not loading? (Note that the 8390.o is the one already on the Bering uclib disk. I supplied the ne.o module from the Bering Uclib 2.1 module tarball). I am assuming this is a real problem because my friend and I both attempted to migrate from Bering to Bering Uclib independently and neither one of us could get the ne.o module to work. Tim Wegner ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ------------------------------------------------------------------------ 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
