mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dominik Karall <dominik.karall@gmx.net>
To: Thomas Latzelsberger <tlatzelsberger@gmx.at>
Cc: webvenza@libero.it, linux-kernel@vger.kernel.org
Subject: Re: limited bandwidth with SiS900 onboard NIC
Date: Fri, 18 Jun 2004 18:57:58 +0200	[thread overview]
Message-ID: <200406181857.58759.dominik.karall@gmx.net> (raw)
In-Reply-To: <40D30FE4.1070900@gmx.at>

On Friday 18 June 2004 17:53, Thomas Latzelsberger wrote:
> Dear readers,
>
> As mentioned on http://teg.homeunix.org/sis900.html and
> http://www.latzinator.com/acer_aspire_1705SMi.html there is a problem
> with bandwidth for the SiS900 onboard NIC. I allways use vanilla kernels
> and I'm having had this problem from 2.4.22 to 2.4.24 and from 2.6.2 to
> 2.6.6.
> The symptom is easy to explain. I connect the PC to a 100MBit switch and
> no matter which method of transfer (ftp, scp, samba, nfs) I use, I get a
> maximum transfer rate of less than 400kB/s. By accident I found a dirty
> workaround that might be a hint for some tech savvy hackers: if I force
> the NIC to use halfduplex (allthough it's connected to a switch) it
> works like expected (7-8 MB/s).
>
> The only help I can be is that I can test new kernel drivers and send
> you feedback.
>
> Any help highly appreciated,
>
> Thomas Latzelsberger

Hi,
try the sis900-fix-phy-transceiver-detection.patch which you can find in -mm 
patches. It works fine for me, as I had the same problem.
A few days ago, I asked why that patch wasn't moved to stable tree. Here you 
can find the mail:
http://lkml.org/lkml/2004/6/16/182

greets dominik

  reply	other threads:[~2004-06-18 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 15:53 Thomas Latzelsberger
2004-06-18 16:57 ` Dominik Karall [this message]
2004-06-18 17:39 ` Jesper Juhl

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=200406181857.58759.dominik.karall@gmx.net \
    --to=dominik.karall@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tlatzelsberger@gmx.at \
    --cc=webvenza@libero.it \
    /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

all inboxes | Powered by JetHome®