For what it's worth, I am running one of these cards with the driver compiled into 2.2.16, rather than as a module.
Here's a snippet from dmesg: ne2k-pci.c:vpre-1.00e 5/27/99 D. Becker/P. Gortmaker http://cesdis.gsfc.nasa.gov/linux/drivers/ne2k-pci.html ne2k-pci.c: PCI NE2000 clone 'RealTek RTL-8029' at I/O 0xe800, IRQ 10. eth0: RealTek RTL-8029 found at 0xe800, IRQ 10, 52:54:00:E6:65:FB. Bob On Tue, Aug 22, 2000 at 09:33:45PM +0200, Vitux wrote: > Trying to build a tiny lan here... > Recompile fresh 2.2.16 with the ne2k-pci driver as module. > No signs of nic when booting, insmod ne2k-pci.o gives me "unresolved > symbols"-error, and ifconfig -yadayada gives me error to the effect > that there's no hardware to configure. > > So the question is: to nic or not to nic? > > I've determined that the kmod-bit works (all the other modules are > inserted automagically on request), and little lights are shining > from nic and hub. > > Is there any other voodoo I have to do to get the card recognised/ > installed/ configured/ whatever? > It said in a howto somewhere (I forget which, I've pored over so > many of'em lately;-), that the Realtek RTL8029 is a NE2000-clone, > and so should use the driver for same... Right?! > > Thanks > Vitux > > -- > "I'm not a crook" > Richard Nixon > > Debian GNU/Linux > Micro$loth-free Zone > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- Bob Nielsen, N7XY [EMAIL PROTECTED] Bainbridge Island, WA http://www.oz.net/~nielsen