public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Which wireless cardbus?
Date: Tue, 20 Feb 2007 14:21:34 +0000	[thread overview]
Message-ID: <01D78D09-AF9E-4D7C-8116-8D6D89FB17DD@stellar.eclipse.co.uk> (raw)
In-Reply-To: <200702192317.35690.michaelkintzios@gmail.com>


On 19 Feb 2007, at 23:15, Mick wrote:
>> ...
>> You don't state which model of Belkin you tried, but I can assure you
>> that they do a "set" (USB, cardbus, PCI) of 802.11g cards that are
>> excellently supported by the rt2500 drivers. These are excellent, are
>> OSS & you can get them with `emerge rt2500`.
>
> Well, I didn't want to bore you - I think I may have already posted  
> about my
> troubles with it in the past.  It is a Belkin USB WiFi adaptor,  
> Model No.
> K7SF5D7050A, which seems to have a RaLink chipset ...
>
> However, if you have any ideas to make my Belkin USB work again  
> then I'll use
> that voucher for something else.  :)

I can't comment on that, although it doesn't particularly surprise  
me. I know the drivers for the USB RaLink chipsets are less mature  
than those for the PCI & Cardbus cards - when I first started using  
those (100% success on the Belkin cards under Gentoo, very easy to  
get going) work on the BSD USB drivers was only just beginning.

>> I recommend this card, but if you're outside the UK contact in
>> advance regarding shipping:
>> <http://networkned.co.uk/Belkin_Cardbus.php>
>> FULL DISCLOSURE: I am involved with this supplier.
>
> Having been burned once I would rather go for something which has  
> matured
> enough to be in the kernel, if possible, but thank you for the  
> suggestion all
> the same.

I don't think you're going to be terribly lucky with that. I'm only  
familiar with the 3 drivers I mentioned - and I know there's an OSS  
driver available for an Intel chipset, too - but of those 3 only the  
prism54 was in the main kernel last time I checked, and cards with  
that chipset that are getting quite hard to get hold of. I have never  
seen a  prism54 cardbus card.

I appreciate your concerns, but honestly a rt2500 cardbus (or PCI)  
card is a safe bet - these drivers are very mature. I'm guessing that  
driver design for USB devices is more complicated &/or widely less  
well-understood than for devices using the "more traditional" PCI or  
cardbus busses (in fact, I think PCI & cardbus are substantially the  
same from the computer's point-of-view). I'd be very surprised if you  
were to plug on of these cards into your machine and `emerge rt2500  
&& modprobe rt2500 & iwconfig` failed to show it.

Stroller.

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-02-20 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18 23:19 [gentoo-user] Which wireless cardbus? Mick
2007-02-19  6:08 ` Ali Polatel
2007-02-19 11:43 ` Stroller
2007-02-19 23:15   ` Mick
2007-02-20 14:21     ` Stroller [this message]
2007-02-21 14:43       ` Nelson, David (ED, PAR&D)

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=01D78D09-AF9E-4D7C-8116-8D6D89FB17DD@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=gentoo-user@lists.gentoo.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