From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Panagiotis Issaris <takis.issaris@uhasselt.be>
Cc: linux-kernel@vger.kernel.org, linux-netdev@vger.kernel.org
Subject: Re: WLAN drivers
Date: Fri, 3 Feb 2006 12:35:30 +0000 [thread overview]
Message-ID: <200602031235.31098.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <1138969138.8434.26.camel@localhost.localdomain>
On Friday 03 February 2006 12:18, Panagiotis Issaris wrote:
[snip]
> And, finally, it seems a lot of cards that get recommendations, are
> based on rather old chipsets, which are unlikely to be still sold today.
This is especially true of the once ubiquitous prism chipsets.
> And now the reason I'm sending this to this mailing list: Which wireless
> network cards are you all using and which ones would you recommend? Is
> anyone using USB wireless network cards (without using ndiswrapper)?
In my experience, you're simply best going to either http://prism54.org/ (if
you can find one still) or http://madwifi.org/ (modern cards, likely to be
purchasable), and then buying one of the cards on the "known to work" lists.
If you buy the wrong revision, return it.
There's really nothing Linux can do about vendors who annoyingly change their
entire product description (and chipset) between revisions.
Personally I've successfully used a 3Com OfficeConnect 11g 1.0 (probably
discontinued) which uses the prism54 driver, Intel's Centrino IPW2200BG and
Proxim's new Orinoco Gold cardbus card (with the madwifi.org drivers).
Keywords for _modern_ Linux supported wireless chipsets are still (to my
knowledge) atheros, atmel, prism54, and most recently broadcom, though that
support is currently immature.
Also possibly the Ralink chipsets are worth considering, they seem to have
been pretty open with respect to drivers, and the cards are dirt cheap.
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-02-03 14:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 12:18 Panagiotis Issaris
2006-02-03 12:35 ` Alistair John Strachan [this message]
2006-02-03 18:06 ` Lee Revell
2006-02-03 18:18 ` Stephen Clark
2006-02-03 18:33 ` Lee Revell
2006-02-05 3:46 ` Luke-Jr
2006-02-03 19:14 ` Alistair John Strachan
2006-02-03 19:19 ` Joel Jaeggli
2006-02-03 19:35 ` Lee Revell
2006-02-03 18:44 ` Lee Revell
2006-02-03 14:24 ` Denis Vlasenko
2006-02-03 18:49 ` Jan Kiszka
[not found] ` <mailman.1138977902.23981.linux-kernel2news@redhat.com>
2006-02-03 19:14 ` Pete Zaitcev
2006-02-03 19:22 ` Alistair John Strachan
2006-02-03 19:38 ` Lee Revell
2006-02-14 16:07 ` David Gómez
2006-02-03 19:32 ` Alessandro Suardi
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=200602031235.31098.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-netdev@vger.kernel.org \
--cc=takis.issaris@uhasselt.be \
/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®