Giving up on Linux wireless with the Airlink 101 AWLL3028

> has been rejected from the kernel outright.

But what about the ones tossed out back?

Such as?

Oh you silly little Europeans....

>outright >out back

:-)

This whole topic tells me that any future computers for this family will have Linux installed from the vendor.

It's just so hard to figure out whether or not any given wireless adapter will work with a given Linux kernel. Since there are so many different kernels being used, it's maddening.

I'm no expert, and I've never compiled a kernel, but it seems to me that users can and should be able to add support for any device to any recent kernel.

And when identical-looking adapters (Airlink AWLL3026 and Airlink AWLL3028) have totally different chipsets, that doesn't make it any easier.

All this tells me is that my Orinoco WaveLAN Silver PCMCIA card -- recognized by every damn thing I've thrown at it -- is worth its weight in gold. .. or Gold, because I'm going to try to find an Orinoco WaveLAN Gold card to add to my arsenal of gear.

I know there are some chipset vendors who are very cooperative about writing drivers for Linux, but it would be very nice if one company -- say Netgear, D-Link, Linksys -- just one of them, would have a policy of writing drivers for Linux. I'd prefer they be open-source drivers, of course, but at this point anything would be better than nothing.

And if this would-be magical company would print on the box, in their documentation and on their Web site that the product was Linux-compatible, they'd sell more and, more importantly, have the entire FOSS community promoting their products as being the most Linux friendly. If they can write separate drives for Win 98, 2000, XP and Vista, they can do a little for the rest of us.

Don't forget WinCE, Windows Mobile, Windows Media Center (multiple editions), and how many home and pro versions of each one are there? Vista alone offers: Ultimate, Home Premium, Home Basic, Business, Enterprise, and don't forget the Windows Wizened and Crippled Edition that is being released in emerging markets.

Quoting:it would be very nice if one company -- say Netgear, D-Link, Linksys -- just one of them, would have a policy of writing drivers for Linux.

No need. Drivers should be written by the chipset manufacturers. Not the guys who put them in a bit of plastic and print their logo on it. What Netgear et. al. should do is clearly state on the box what chipset is used. Last time I went shopping for a wifi dongle I had to take it back 4 times because everytime I ended up with Broadcom crap. You simply can't find it on the box. Only on one vendors box did I happen to see the microscopic fine print that said the device contained some patented Broadcom technologies, so I assumed it was a broadcom chip. Can't they just print the chip model in the little table with tech specs?!

When Airlink 101 did that little switch with their dirt-cheap USB adapter, I was none too happy, since the "older" model used Ralink, while the newer used the not-supported Realtek 8187b ...

Good idea, but do not print it on the box please. I still want to be able to read what the chipset is after the one asking me to 'make it work in Linux' threw away the box.

Hans: It's it's on the spec sheet on the box it'll be on the spec sheet on the website and on ever webshop's site that sells it. Good enough for me :-)

FWIW, I have found the best way to find a wireless card that works with Linux is to go to http://customerproducts.atheros.com/customerproducts/default... and search. I have found that Atheros has yet to let me down, hopefully that will not change.

That's pretty cool.

I get this:

HTTP 403.9 - Access Forbidden: Too many users are connected Internet Information Services

Technical Information (for support personnel)

* Background: This error can occur if the Web server is busy and cannot process your request due to heavy traffic.

* More information: Microsoft Support

I got no problem with it. Perhaps everyone from LXer went there at one time? :) Hey, we crashed helios, now we've crashed Atheros!!!

Technically speaking, digg had a hand in crashing helios as well..... lol

It works for me though...

Hey, lets LXer /.

I did finally see the site -- very helpful.

So is there a list of which Atheros chipsets work nicely in linux?