Prev: scanning + OCR the monkey way ...
Next: netbook + Linux: please help
From: Vlad_Inhaler on 29 Nov 2009 06:32
On Nov 28, 7:18 pm, Lord Eldritch <lord_eldri...(a)yahoo.co.uk> 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).
>
> 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

I'd be very surprised if Fedora (not the distribution I use) got
something basic like that wrong. Have you thought of buying/borrowing
another card? You presumably have a PCI slot free. I'd deactivate
the card (Linux config or BIOS) and get something which uses a
different driver. Most cards have Linux drivers, I was really
surprised to find one recently which did not (an old Level One
FNC-0109TX).

Obviously, if the situation persists then something outside your PC is
wrong.
From: Lord Eldritch on 29 Nov 2009 12:21
Thank you all (Pascal, Vlad, Wannabe). I cannot tell when if did started; I
was out for more than one moth and when I came back I upgraded to Fedora 12
and show that thing (and I could say the network is kind of.. sluggish,
specially with very big files (FTPing, for instance).

When I started checking things, I've got puzzled by the Realtek/Via duality
and I thought i could be a driver thing, but you all helped me to establish
that was ok and I should probably look for the cause somewhere outside.

I trust linux but it is always easier to blame the software before start
checking the hardware..

I changed cable now and connection port to the router and it remains. Now I
am checking the router configuration...

Any diagnostic tool I could use to locate the failure?

I guess I'll try to find a network card and check it too...
--
Lord Eldritch
From: Bit Twister on 29 Nov 2009 13:03
On Sun, 29 Nov 2009 18:21:58 +0100, Lord Eldritch wrote:
>
> Any diagnostic tool I could use to locate the failure?

I use ifconfig to check for TX/RX errors. Other hardware tools of interest
might be ethtool or mii-tool. Then there is wireshark for looking
through the packet headers.

If speed tests look good, then blame the network to/from the ftp
site or your isp.

In no order of importance or checked url lately
http://www.speakeasy.net/speedtest/
http://homepage.eircom.net/~leslie/testpage.htm
http://support.midco.net/
http://reviews.cnet.com/7004-7254_7-0.html
http://www.broadbandreports.com/stest
http://www.browsertune.com/bt2kfast/
http://www.cable-modem.net/
http://www.dslreports.com/stest
http://www.dslreports.com/tweaks
http://www.testmy.net
http://www.toast.net/performance/
From: Wanna-Be Sys Admin on 1 Dec 2009 16:47
Lord Eldritch wrote:

> Thank you all (Pascal, Vlad, Wannabe). I cannot tell when if did
> started; I was out for more than one moth and when I came back I
> upgraded to Fedora 12 and show that thing (and I could say the network
> is kind of.. sluggish, specially with very big files (FTPing, for
> instance).
>
> When I started checking things, I've got puzzled by the Realtek/Via
> duality and I thought i could be a driver thing, but you all helped me
> to establish that was ok and I should probably look for the cause
> somewhere outside.
>
> I trust linux but it is always easier to blame the software before
> start checking the hardware..
>
> I changed cable now and connection port to the router and it remains.
> Now I am checking the router configuration...
>
> Any diagnostic tool I could use to locate the failure?
>
> I guess I'll try to find a network card and check it too...

It still might be a bug. I've not used Fedora in years, thankfully (my
own opinion). I just am glad you checked the simple things first
before taking more of your time. Others recommended swapping nic's and
see if that helps (onboard or another card, if you have either option)
and see if the issue remains. Also, you might try a change in the
settings:

ethtool -K eth0 tso off

This was a known issue that would cause it to drop (if tso is enabled).
See if that helps?
--
Not really a wanna-be, but I don't know everything.
From: Lord Eldritch on 2 Dec 2009 15:44
Wow. A lot of links to read... Thanks.. and thank you all.

So far I've tried changing cable and changing the router port. Also
installed a new network card I had (Zyxel -Realtek) and it is detected and a
Realtek driver is loaded but as soon as I plug the cable on it, the same
message appears (this time on eth1, of course). I guess this clears the
drivers of having bugs.

I'll go though all the suggestions this weekend.

I was also suggested by a friend that could also be just a router failure
(Zyxel 660 HW) and just the ports circuits are giving up. Can it be that
way?
--
Lord Eldritch
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: scanning + OCR the monkey way ...
Next: netbook + Linux: please help