From: Richard Dawe <rich@phekda.gotadsl.co.uk>
To: netdev@oss.sgi.com
Cc: Richard Dawe <rich@phekda.gotadsl.co.uk>
Subject: Re: Acer Aspire 1524WLMi and RealTek 8169 - very slow
Date: Sun, 21 Nov 2004 13:24:52 +0000 [thread overview]
Message-ID: <41A09724.4050905@phekda.gotadsl.co.uk> (raw)
In-Reply-To: <41A09541.5040405@phekda.gotadsl.co.uk>
Helo.
Richard Dawe wrote:
> Hello.
>
> I recently bought an Acer Aspire 1524WLMi, which is a laptop with an AMD
> Athlon64 3400, a RealTek 8169 GigE chip and a bunch of other stuff.
>
> I'm currently not able to get more than about 30KB/sec throughput out of
> the RealTek built-in network adapter. I get a lot of packet loss. The
> packet loss seems to increase with packet size. Using ping I see that
> around 1500 bytes packets very little data passes at all.
>
> I'm running Fedora Core 3. Here are the different kernels I've tried:
[snip]
> Sadly these all had the same terrible performance.
[snip]
Sorry, I forgot to mention the other networking hardware and what I'd
tried there.
* Draytek Vigor 2600 ADSL modem, which has a built-in 100Mbs switch. I
can get reasonably close to 100Mbs throughput with this switch. I've had
no problems with Netgear cards using the "tulip" driver with this switch.
* I tried various bits of cable, including ones that I know work. No
difference.
* I tried a Netgear 100Mbs hub. No difference.
I would try a cross-over cable to do point-to-point with my desktop PC,
but I don't have any right now.
I tried to flip the 8169 into half duplex using:
ethtool -s eth0 duplex half
but that segfaults and leaves the computer at 100% CPU and unresponsive.
That's with ethtool-2 and ethtool-1.8-4 from FC3. The only choice then
is to turn the computer off and leave it off for about 10 seconds. If
you power it up too quickly, then eth0 will not come back up - perhaps
the 8169 is still wedged?
Bye, Rich =]
--
Richard Dawe [ http://homepages.nildram.co.uk/~phekda/richdawe/ ]
"You can't evaluate a man by logic alone."
-- McCoy, "I, Mudd", Star Trek
next prev parent reply other threads:[~2004-11-21 13:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 13:16 Acer Aspire 1524WLMi and RealTek 8169 - very slow Richard Dawe
2004-11-21 13:24 ` Richard Dawe [this message]
2004-11-21 19:47 ` Richard Dawe
2004-11-21 20:58 ` Francois Romieu
2004-11-22 20:42 ` Richard Dawe
2004-11-22 21:30 ` Francois Romieu
2004-11-22 22:07 ` Richard Dawe
2004-11-24 19:36 ` Richard Dawe
2004-11-30 19:52 ` Jon Mason
2004-12-29 10:17 ` Richard Dawe
2004-12-29 23:52 ` Francois Romieu
2005-01-02 13:51 ` Richard Dawe
2005-01-02 15:23 ` Richard Dawe
2005-01-22 13:10 ` Richard Dawe
2005-01-22 15:22 ` Richard Dawe
2005-01-22 23:01 ` Francois Romieu
2005-01-23 19:08 ` Richard Dawe
2005-01-25 21:47 ` Francois Romieu
2005-02-05 13:26 ` Richard Dawe
2005-02-05 20:41 ` Francois Romieu
2005-02-06 10:54 ` Richard Dawe
2005-02-08 23:00 ` Richard Dawe
2005-02-12 0:07 ` Francois Romieu
2004-11-21 23:28 ` [patch] ethtool (was Re: Acer Aspire 1524WLMi and RealTek 8169 - very slow) Francois Romieu
2005-01-27 20:27 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-01-26 22:00 Acer Aspire 1524WLMi and RealTek 8169 - very slow Brandeburg, Jesse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41A09724.4050905@phekda.gotadsl.co.uk \
--to=rich@phekda.gotadsl.co.uk \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).