From: arjan@fenrus.demon.nl
To: ionut@moisil.cs.columbia.edu (Ion Badulescu)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Xircom RealPort versus 3COM 3C3FEM656C
Date: Tue, 22 May 2001 22:34:08 +0100 (BST) [thread overview]
Message-ID: <m152Jn6-000Oh3C@amadeus.home.nl> (raw)
In-Reply-To: <200105222118.f4MLISL01588@moisil.badula.org>
In article <200105222118.f4MLISL01588@moisil.badula.org> you wrote:
> On Tue, 22 May 2001 20:10:41 +0100 (BST), Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> Before you give up on the xircom thing, try the -ac kernel and set the box
>> up to use xircom_cb not xircom_tulip_cb
>>
>> That might help a lot
> It doesn't, it still performs poorly with any of the three available
> drivers -- xircom_cb, xircom_tulip_cb, and tulip_cb (from the pcmcia package):
> * Rx gets only about 1.8Mbit/s on a 100Base-TX network with any of the three
> * Tx gets 80+Mb/s with xircom_tulip_cb and tulip_cb, and less than 30Mb/s
> with xircom_cb.
This sounds like a bug I have heard before: some switches don't work with
the xircom card (well, our drivers for it) when doing full duplex.
Could you try the latest driver from
http://people.redhat.com/arjanv
which forces the card to half-duplex?
I manage to get 8Mbyte/sec with it without any problems.
Greetings,
Arjan van de Ven
next prev parent reply other threads:[~2001-05-22 21:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 18:33 Changes in Kernel Prasad
2001-05-22 18:20 ` Alan Cox
2001-05-22 18:28 ` H. Peter Anvin
2001-05-22 18:47 ` Vivek Dasmohapatra
2001-05-22 19:07 ` Xircom RealPort versus 3COM 3C3FEM656C Dax Kelson
2001-05-22 19:10 ` Alan Cox
2001-05-22 19:35 ` Jeff Garzik
2001-05-22 21:18 ` Ion Badulescu
2001-05-22 21:34 ` arjan [this message]
2001-05-22 22:13 ` Ion Badulescu
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=m152Jn6-000Oh3C@amadeus.home.nl \
--to=arjan@fenrus.demon.nl \
--cc=ionut@moisil.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
/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®