From: Jeff Chua <jeffchua@silk.corp.fedex.com>
To: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Cc: jchua@fedex.com
Subject: Re: Repeatable 2.4.0-test13-pre4 nfsd Oops rears it head again
Date: Sat, 30 Dec 2000 00:15:56 +0800 [thread overview]
Message-ID: <200012291615.eBTGFuq32091@silk.corp.fedex.com> (raw)
the only thing you've to be careful is to make sure you set
the correct options for the module (if you compiled it as module).
# options=0x30 100mbps full duplex
# options=0x20 100mbps half duplex
# options=0 10mbps half duplex
options eepro100 options=0
Otherwise, it'll cause a lot of unnecessary network traffic and
slow down your network!
These are not obvious unless you read the source code.
Jeff.
>From linux-kernel-owner@vger.kernel.org Fri Dec 29 14:14:55 2000
X-Authentication-Warning: palladium.transmeta.com: mail set sender to news@transmeta.com using -f
To: linux-kernel@vger.kernel.org
From: torvalds@transmeta.com (Linus Torvalds)
Subject: Re: Repeatable 2.4.0-test13-pre4 nfsd Oops rears it head again
Date: 28 Dec 2000 22:15:17 -0800
Organization: Transmeta Corporation
In-Reply-To: <20001228161126.A982@lingas.basement.bogus> <200012282159.NAA00929@pizda.ninka.net> <20001228212116.A968@lingas.basement.bogus>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
In article <20001228212116.A968@lingas.basement.bogus>,
Mike Elmore <mike@kre8tive.org> wrote:
>
>I really need to get rid of this 8139 card. Since
>yall are the oracle, which nice 100mbs card is fine
>hardware and is coupled with a well debugged driver?
There are always problems with some hardware, but my personal
recommendation for a card would definitely be the Intel Ethernet Pro 100
series (82557).
Unlike the tulip cards (which are pretty good too), there aren't a
million different versions of it. There's a few, but it's not a big
mess. It performs well, and is stable. It's pretty well documented
(apart from the magic extensions), and it's common.
That said, some people have trouble even with that card. Nobody knows
why, but at least the driver is actively maintained etc, so I still am
not nervous about recommending it.
I bet that others will have other recommendations, but so far I have at
least personally had good luck with the eepro100.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-29 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 16:15 Jeff Chua [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-29 8:51 Ray Strode
2000-12-28 22:11 Mike Elmore
2000-12-28 21:59 ` David S. Miller
2000-12-29 3:21 ` Mike Elmore
2000-12-29 3:47 ` Chris Wedgwood
2000-12-29 6:15 ` Linus Torvalds
2000-12-29 10:25 ` Chris Wedgwood
2000-12-30 10:42 ` Andrew Morton
2000-12-30 18:06 ` Francois Romieu
2000-12-29 8:14 ` David Ford
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=200012291615.eBTGFuq32091@silk.corp.fedex.com \
--to=jeffchua@silk.corp.fedex.com \
--cc=jchua@fedex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®