From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: speakup@braille.uwo.ca
Subject: Re: I need a new Ethernet card
Date: Sat, 19 Jul 2003 00:58:00 -0600 (Mountain Daylight Time) [thread overview]
Message-ID: <Pine.WNT.4.56.0307190054060.928@merlin> (raw)
In-Reply-To: <001b01c34d9c$ed026560$be00a8c0@vicki>
Hello,
There are quite a few that will work just fine with Linux. Matter of fact, I've found that most will. The problem your going to run in to is that the kernel may not refur to the card specifically by name, but rather the chip set it is using. For example, most linksys cards work well under Linux. However, there is not any option to select a Linksys card. Instead, there is a tulip option and that is the one you need because the cards I'm refurring to use the tulip chip.
As far as cards that will definitely work, any of the 3com 3c90x type will work using the 3c59x option. Most Linksys cards will work with the tulip option. I'm not really sure about others.
--
Joseph C. Lininger
jbahm@pcdesk.net
On Fri, 18 Jul 2003, Glenn Ervin wrote:
> Can anyone recommend a good PCI Ethernet Card for my desktop computer?
> I am looking for one that will work in both Windows mE, and Linux.
> The ones I looked at on the dLink site stated nothing about working with
> Linux.
> Thanks.
>
> >From Glenn Ervin
> This message originated from a computer which I do not usually use, and when
> you reply, you may not be replying to my e-mail address, so my e-mail
> address is:
> GlennErvin@cableONE.net
> .
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Glenn Ervin
` Luke Davis
` Glenn Ervin
` Luke Davis
` Adam Myrow
` Thomas D. Ward
` Joseph C. Lininger [this message]
` Toby Fisher
Gregory Nowak
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=Pine.WNT.4.56.0307190054060.928@merlin \
--to=jbahm@pcdesk.net \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).