Friends:
I am running Red Hat 6.1 on an Aptiva 572 system.
I installed a RealTek RTL8029(AS) ethernet PCI network NIC card into my Aptiva,
but can't seem to get it to be recognized as "eth0" device. No ethernet
messages show up during startup.
I went to the RealTek website and they indicated that the ne2k-pci.o driver
should work for this model. I found that I already have ne2k-pci.o in my
/lib/modules/2.2.12-20/net directory.
When I do an 'insmod ne2k-pci.o' I get the following messages:
ne2k-pci.o: unresolved symbol ei_open
ne2k-pci.o: unresolved symbol ethdev_init
ne2k-pci.o: unresolved symbol ei_interrupt
ne2k-pci.o: unresolved symbol NS8390_init
ne2k-pci.o: unresolved symbol ei_close
This is what my /etc/conf.modules file looks like:
alias eth0 ne2k-pci
alias parport_lowlevel parport_pc
I ran Donald Beckers's diagnostic program ne2k-pci-diag, here is what I got:
ne2k-pci-diag.c:v1.08 10/15/99 Donald Becker ([EMAIL PROTECTED])
Index #1: Found a RealTek RTL8029 adapter at 0xff80.
The 8390 core appears to be active, so some registers will not be read.
To see all register values use the '-f' flag.
Initial window 0, registers values by window:
Window 0: 20 08 4c 7f 03 00 00 42 6e 48 50 43 21 00 00 00.
Window 1: 60 00 54 05 f7 a8 a4 4c 00 41 00 80 00 00 00 00.
Window 2: a0 00 00 ff 43 ff ff ff ff ff ff ff c0 e0 cd 80.
Window 3: e0 30 ff 00 ff 00 30 ff ff ff ff ff ff ff 29 80.
Interrupt sources are pending (42).
Tx done indication.
Transfer done indication.
Parsing the EEPROM of a RTL8029:
Station Address 52:54:05:F7:A8:A4 (used as the ethernet address).
Configuration is 30 00:
0K boot ROM, half duplex
Transceiver: 10baseT/coax (autoselected on 10baseT link beat).
PCI Vendor ID 0x10ec Device ID 0x8029
Subsystem ID: vendor 0000 device 0000
Use '-a' or '-aa' to show device registers,
'-e' to show EEPROM contents,
or '-m' or '-mm' to show MII management registers.
I tried to recompile from the source in /usr/src/linux/drivers/net/ne2k-pci.c
using the compile statements at the bottom of the source file, it compiled just
fine, no messages, but I got the same error with insmod as before.
Is there any way to activate this driver without going through a full re-install
from the Red Hat 6.1 CD-rom?
--
Tony Pearson
My diary of Linux experiences at ...
http://www.users.uswest.net/~tonypearson/index.html
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
