On Sun, 2006-01-01 at 16:29 -0800, Noah Roberts wrote:
> On 1/1/06, Alberto Botti <alberto.botti@email-addr-hidden> wrote:
>
> > Don't forget that Ralink cards are some of the better supported wireless
> > interfaces available for Linux, having a completely GPL driver which
> > doesn't need external binary firmware.
> >
> >
>
> A while back I managed to get a DLink working within a few hours.
> Took a LOT of searching and scrambling through convoluted (even for
> unix) docs, websites, and forums to get there but once I found out
> everything I needed it was pretty easy...it just worked. So anyway, I
> know there is better even if you sometimes need that HAL component.
>
> Setting up a wireless connection in Linux seems a lot harder than it
> needs to be. Certainly the documentation on it could be much better.
> If I knew what the hell I was doing with it maybe I could figure out
> more about why it is breaking but I can't find any really good docs on
> this stuff. The HOWTO kinda sucks... and people complain about audio
> being hard to figure out :P
I think it does not much attention because wireless on Linux right now
has much bigger problems that poor documentation.
> At any rate, its off topic now I think because the interrupt problem
> is not what is at issue anymore now that I realized I was still
> loading an old driver. That older driver actually says not to use SMP
> or PREEMPT so...
>
> Thanks for the help guys. I might try a few more things but I'm
> pretty close to giving up on this card and trying a different
> one...maybe I can get a DLink like the one I already got working once
> before.
>
Of course you'll have the easiest time if you get a device that the
kernel supports OOTB.
Check drivers/net/wireless/Kconfig in your kernel source for some
examples of devices that should Just Work.
Lee
Received on Mon Jan 2 04:15:06 2006
This archive was generated by hypermail 2.1.8 : Mon Jan 02 2006 - 04:15:06 EET