[eepro100] second ethernet card dropped?
hsiao-yu chen
notificationserver@hotmail.com
Thu, 24 Aug 2000 23:27:52 GMT
I have one eepro card,(eth0) which has been working good for a few years. I
want to use another ethernet interface, using the last generation management
plus adapter.
What I have done: insert the card, edit /etc/modules.conf to have two lines,
alias eth1 eepro100
alias eth0 eepro100
then, I rebooted the computer and eth0 is working but eth1 is not there.
Here are some diagnosis that I have done,
>dmesg
th0: Intel EtherExpress Pro 10/100 at 0xe800, 00:D0:B7:6C:47:7B, IRQ 5.
Receiver lock-up bug exists -- enabling work-around.
Board assembly 721383-008, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
eth1: Intel EtherExpress Pro 10/100 at 0xec00, 00:90:27:8C:44:86, IRQ 11.
Receiver lock-up bug exists -- enabling work-around.
Board assembly 721383-006, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
So I guess the kernel saw it, but
>ifconfig
eth0 Link encap:Ethernet HWaddr 00:D0:B7:6C:47:7B
inet addr:128.211.202.61 Bcast:128.211.202.255
Mask:255.255.255.0
inet6 addr: fe80::2d0:b7ff:fe6c:477b/10 Scope:Link
inet6 addr: fe80::d0:b76c:477b/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3550 errors:0 dropped:0 overruns:0 frame:0
TX packets:1610 errors:0 dropped:0 overruns:0 carrier:0
collisions:153 txqueuelen:100
Interrupt:5 Base address:0xe800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:684 errors:0 dropped:0 overruns:0 frame:0
TX packets:684 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
As you can see, ifconfig shows no sign of eth1.
>cat /proc/interrupts
CPU0
0: 216787 XT-PIC timer
1: 6071 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 5178 XT-PIC Intel EtherExpress Pro 10/100 Ethernet
8: 2 XT-PIC rtc
10: 0 XT-PIC Ensoniq AudioPCI
12: 120447 XT-PIC PS/2 Mouse
13: 1 XT-PIC fpu
14: 107159 XT-PIC ide0
15: 63 XT-PIC ide1
NMI: 0
So the interrupts are not a problem, it seems.
lastly, I compiled eepro100-diag.c and it shows
>./eeprotest -a
eepro100-diag.c:v2.02 7/19/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a Intel i82557 (or i82558) EtherExpressPro100B adapter at
0xe800.
A potential i82557 chip has been found, but it appears to be active.
Either shutdown the network, or use the '-f' flag.
Index #2: Found a Intel i82557 (or i82558) EtherExpressPro100B adapter at
0xec00.
i82557 chip registers at 0xec00:
00000000 00000000 00000000 00080002 10000000 00000000
No interrupt sources are pending.
The transmit unit state is 'Idle'.
The receive unit state is 'Idle'.
This status is unusual for an activated interface.
Any help?
thanks,
carol
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com