Prev: scanning + OCR the monkey way ...
Next: netbook + Linux: please help
From: Lord Eldritch on 28 Nov 2009 13:18
Hi, I've been surfing the net to find the solution to this, but the only
clear thing I've got was that it was a driver problem.

The situation is that I have a Fedora 12 and I get this messages:
dmesg
eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: link down

that it i caused by the a buggy/bad driver (I read).

Digging into the system, I saw I have a MSI K9VGM-V motherboard who has a
Realtek 8201CL LAN card but the drive I have running is the via-rhine:

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev
7c)

So my question here is:

Am I using the right driver? Fedora picked it during installation. Is it
possible the manufacturer has changed the network card form the Realtek to
the VIA and Linux is detection properly?
Or autodetection is not working and I should change it to a Realtek driver
and then my problem would go away? How should I do that then?

Any hint would be appreciated. Thanks in advance.
--
Lord Eldritch
From: Pascal Hambourg on 28 Nov 2009 14:36
Hello,

Lord Eldritch a �crit :
>
> Digging into the system, I saw I have a MSI K9VGM-V motherboard who has a
> Realtek 8201CL LAN card but the drive I have running is the via-rhine:
>
> 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev
> 7c)

This is only the device identification, not the running driver.

> So my question here is:
>
> Am I using the right driver?

Probably.

> Fedora picked it during installation. Is it
> possible the manufacturer has changed the network card form the Realtek to
> the VIA and Linux is detection properly?

Maybe the motherboard documentation is wrong, because in the driver list
the LAN driver is for a VIA VT6103/VT6105 controller. Can you see the
Realtek 8201CL chip on the motherboard ?

> Or autodetection is not working

This is highly unlikely, or the motherboard is horribly broken.

> and I should change it to a Realtek driver
> and then my problem would go away?

This won't work because a driver has a built-in list of identifiers it
can handle.
From: Lord Eldritch on 28 Nov 2009 15:50
Pascal Hambourg wrote:

>> Fedora picked it during installation. Is it
>> possible the manufacturer has changed the network card form the Realtek
>> to the VIA and Linux is detection properly?
>
> Maybe the motherboard documentation is wrong, because in the driver list
> the LAN driver is for a VIA VT6103/VT6105 controller. Can you see the
> Realtek 8201CL chip on the motherboard ?
>
>> Or autodetection is not working
>
> This is highly unlikely, or the motherboard is horribly broken.
>
Well. I went for the brute force approach and I opened the case. The place
for the network chip shows a very small one (0.5�0.5cm maybe) showing
Realtek on it and RLT8201CL (I cannot swear on it because they are very
tiny). The chips around are all with "crab" and branded as Realtek. The only
Via chips are the (covered by dissipator) *bridges.


--
Lord Eldritch
From: Wanna-Be Sys Admin on 28 Nov 2009 16:56
Lord Eldritch wrote:

> Hi, I've been surfing the net to find the solution to this, but the
> only clear thing I've got was that it was a driver problem.
>
> The situation is that I have a Fedora 12 and I get this messages:
> dmesg
> eth0: link down
> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> eth0: link down
> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> eth0: link down
>
> that it i caused by the a buggy/bad driver (I read).
>

Could be a bad driver, or a bug anyway, but you appear to be using the
right driver. Anyway, the above can be caused by a bad/loose
connection, a bad cable, bad port on a router/switch, etc. as well.
--
Not really a wanna-be, but I don't know everything.
From: Pascal Hambourg on 28 Nov 2009 17:14
Lord Eldritch a �crit :
>
> Well. I went for the brute force approach and I opened the case. The place
> for the network chip shows a very small one (0.5�0.5cm maybe) showing
> Realtek on it and RLT8201CL (I cannot swear on it because they are very
> tiny). The chips around are all with "crab" and branded as Realtek. The only
> Via chips are the (covered by dissipator) *bridges.

I'm so stupid. I should have remembered that the RTL8201CL is not a
controller but only a PHYceiver between the link and the controller
which must be the VT6102 integrated in the VIA chipset.
 |  Next  |  Last
Pages: 1 2 3
Prev: scanning + OCR the monkey way ...
Next: netbook + Linux: please help