Ben, I thought that as well. I have changed both interfaces in the interfaces file. The built in NIC is a 10Mb and the new SBUS card is a 10/100Mb. When I bring up the interfaces I see the following messages:
eth1: Carrier Lost, trying AUI SIOCSIFNETMASK: Invalid argument eth0: Link is up using internal transceiver at 10Mb/s, Half Duplex. or SIOCSIFNETMASK: Invalid argument eth1: Carrier Lost, trying AUI eth0: Link is up using internal transceiver at 10Mb/s, Half Duplex. The messages are in different order depending on which is listed first in the interface file. The first set of messages are displayed when I list eth1 first in the interfaces file. The second is when I list eth0 first in the interfaces file. I thought that changing the order would change the NIC that the configuration was for. This is a wrong assumption? David -----Original Message----- From: Ben Collins [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Sunday, September 21, 2003 6:28 PM To: David Demland Cc: Debian-Sparc Subject: Re: SPARC 5 with a new SBUS NIC does not work now. On Sun, Sep 21, 2003 at 06:04:56PM -0700, David Demland wrote: > I have a SPARC 5. It has a built in NIC and I found a SBUS nic so I put in > into the SPARC 5. Before I put in the new NIC, the system would go out my > network just fine. I could ping all the machine inside and I could get to > the internet. Since I put in the second NIC the system will not ping > anything. I am running the 2.2 kernel. Does any one have any ideas of what > the problem might be? Probably just the ordering of the NIC's that Linux does. Perhaps the internal is now eth1, instead of eth0 as it was before. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
