Mailinglist Archive: opensuse (4053 mails)

< Previous Next >
Re: [SLE] NIC trouble...quickly reaching the last straw with Suse
  • From: Alexandr Malusek <Alexandr.Malusek@xxxxxxxxxx>
  • Date: 01 Aug 2001 18:16:01 +0200
  • Message-id: <86snfb4uym.fsf@xxxxxxxxxxxxxxxxxxxxx>
"Ron Sinclair" <sinclair@xxxxxxxxxxxxxxxx> writes:

> ... Japanese card that supposedly uses the VIA Rhine module.

Use /sbin/lspci to identify the card. For instance:

$ /sbin/lspci
...
00:0d.0 Ethernet controller: 3Com Corporation 3c900B-TPC [Etherlink XL TPC]
(rev 04)
00:0e.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100]
(rev 08)

> Aug 1 17:03:32 500mhz kernel: PCI: Found IRQ 9 for device 00:0a.0
> Aug 1 17:03:48 500mhz kernel: eth0: Transmit timed out, status 0000, PHY
> status 0000, resetting...

It seems the driver doesn't work well.

> root@500mhz:/home/ron > ifconfig
> eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00

The HWaddr (MAC address) is wrong. It confirms that the driver doesn't
work.

> root@500mhz:/home/ron > ping 400mhz
> PING 400mhz.zama.com (192.168.2.20): 56 data bytes

It's wasting of time. If the driver doesn't work, then the networking
won't work.

My suggestion is to identify the card via the lspci command. Then you
can search for a proper driver. (Or buy a Linux-friendly card if you
don't want to waste your time.)

--
Alexandr.Malusek@xxxxxxxxxx

< Previous Next >
Follow Ups
References