** Reply to message from Vidiot <[EMAIL PROTECTED]> on Mon, 5 Feb 2001 00:58:57
-0600 (CST)
> >> OK. I know this has been batted around before but
> >> I can't go looking through the archives right
> >> now. Does anybody know how to get the second eth1
> >> NIC configured if it is identical to eth0? I have
> >> tried all day and am not getting anywhere. I have
> >> set up the modules.conf as such for the two
> >> Linksys LNE100 cards:
> >>
> >> alias eth0 tulip
> >> alias eth1 tulip
> >>
> >> and it is still not being recognized. Both the
> >> ACT and power LEDs are lit up on the NIC. An
> >> "sbin/ifconfig eth1 up" gives "eth1: unknown
> >> interface: No such device". It is possible that
> >> both cards are trying to use the same interrupt
> >> although I have "PNP OS" set to no in the BIOS
> >> and it should be picking them both up.
> >> "sbin/lspci" shows it being recognized as a
> >> separate network controller.
> >> Jack Bowling
>
> These cards will work just fine. As proof, I have two of the recent
> models running in my box right now. One handles the DSL web serving
> traffic and the other handles the internal LAN traffic.
>
> eth0 Link encap:Ethernet HWaddr 00:20:78:1E:F6:FD
> inet addr:208.171.49.43 Bcast:208.171.49.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:52357744 errors:0 dropped:36 overruns:0 frame:0
> TX packets:75914304 errors:0 dropped:0 overruns:0 carrier:0
> collisions:14079622 txqueuelen:100
> Interrupt:10 Base address:0xbc00
>
> eth1 Link encap:Ethernet HWaddr 00:03:6D:11:1C:E4
> inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:22099345 errors:0 dropped:0 overruns:0 frame:0
> TX packets:20611594 errors:3 dropped:0 overruns:3 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:9 Base address:0xd800
>
> Something tells me you never configured the card. Did you run netcfg and
> enable it?
Ummm...yes, I did. And it gives me the "Delaying eth1 initialization." output when
activated from netcfg. Could be wonky PNP capability in the BIOS. I note that the
onboard chipset of the failing card is an ADMtek AL985 Centaur-P rather than a Lite-On
PNIC-II of my other working Linksys card. The box proudly displays "Tested with Linux"
and the readme on the floppy says to use the tulip driver so I will rip the working
card out and see if the failing one comes to life when it is by itself.
--
Jack Bowling
Prince George, BC
mailto:[EMAIL PROTECTED]
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
