eth problem in Suse 9.1

Greetings,

I just installed Suse 9.1 on my desktop. Everything is well except for
the network card: it won't establish an connection at all; I have to use
YAST2 to re-detect the ethernet card (and to restart the network service)
before I can get any connection.

The ethernet card is been detected as:

Lite-On LNE100TX [rev 2.0]

which uses Tulib driver. The error message I get (from dmesg) is:


eth0: Autonegotiation failed, using 10baseT, link beat status 10ce.

I'm using Suse 9.1 with updated kernel (2.6.5-7.75-default).

Any help is very much appreciated!

ECC

On Tue, 22 Jun 2004 20:06:24 -0400, Elvis Chen <(E-Mail Removed)> wrote:
>
> Greetings,
>
> I just installed Suse 9.1 on my desktop. Everything is well except for
> the network card: it won't establish an connection at all; I have to use
> YAST2 to re-detect the ethernet card (and to restart the network service)
> before I can get any connection.
>
> The ethernet card is been detected as:
>
> Lite-On LNE100TX [rev 2.0]
>
> which uses Tulib driver. The error message I get (from dmesg) is:
>
> eth0: Autonegotiation failed, using 10baseT, link beat status 10ce.
>
> I'm using Suse 9.1 with updated kernel (2.6.5-7.75-default).

What specific card is it or what does "lspci -v" show for it? That info
might allow someone to recognize any problems with it.

I had an LNE100TX card (Netgear FA310TX?) that would not work reliably
with latest tulip module in 2.2.x kernels (had to ping it from network
before it would work) or 2.4.x (stopped responding overnight, requiring
down/up of interface or network restart). Since it was headless and
needed reliable networking, I ran Mandrake 7.0 using latest 2.2.x kernel
with "old_tulip" module until that PC died. That nic lives on in a United
Parcel Service owned NT box at work, and the drive is in my SuSE 8.2 Pro
pppoe router.

I am running SuSE 9.1, but it is ftp installed x86_64 version using
integrated Nvidea force3 nic.

--
David Efflandt - All spam ignored http://www.de-srv.com/