From: "William L. Thomson Jr." <support@obsidian-studios.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] NIC recommendations
Date: Tue, 20 May 2003 20:59:54 +0000 [thread overview]
Message-ID: <marc-lartc-105346451924938@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105345672815485@msgid-missing>
On Tue, 2003-05-20 at 15:38, Nickola Kolev wrote:
>
> With such a "high" ammount you can take almost any off-the-shelf NIC, eg. even
> Realtek 8139 based cards. But I'd recommend 3Com - EtherLink XL 3c900 or 3c905,
> 3c540/3c900/3c905/3c980/3c575/3c656, 3c905, or Intel EtherExpressPro/100, if
> you can afford'em, of course. They are pretty stable and I'm quite happy with
> their performance.
I am not a fan of 3com cards any more. I used to have many of them until
I noticed under certain circumstances if a cable came unplugged my nic
would not be available again until a reboot. Which is very odd, since
normally you can do many things without having to reboot.
Stop start the interface.
Load unload the driver.
I had problems with them so I avoid them now. Not to mention I never got
the type of through put with 3com nics as I do with Intel Pro 100 nics.
Especially when using the e100 driver directly from Intel. They are
always updating it and releasing new versions. The e100 that comes with
most kernels, is not always the most up2date version of the driver.
--
Sincerely,
William L. Thomson Jr.
Support Group
Obsidian-Studios, Inc.
3548 Jamestown Ln.
Jacksonville, FL 32223
Phone/Fax 904.260.2445
http://www.obsidian-studios.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-05-20 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 18:50 [LARTC] NIC recommendations Harkisoon Sharan (CCI-Gainesville)
2003-05-20 19:38 ` Nickola Kolev
2003-05-20 20:56 ` William L. Thomson Jr.
2003-05-20 20:59 ` William L. Thomson Jr. [this message]
2003-05-22 14:10 ` Anton Tinchev
2003-05-22 14:22 ` Blagoy Genadiev
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=marc-lartc-105346451924938@msgid-missing \
--to=support@obsidian-studios.com \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.