Un-Plugged Rant: GNU/Linux & Wireless

dcp's picture

Sometimes I just gotta wonder about GNU/Linux and wi-fi...Maybe you can help.

I don't get it. I had a BCM38xx wireless LAN card. I bought it because I saw decent reviews on getting it working under GNU/Linux. Well, let's just say it was fun, but not real fun, and leave it at that, eh? The odd thing was, I was using Ubuntu on the laptop at that point, and PCLinuxOS auto-detected and configured the wireless PCI version I bought for one of the desktops.Go figure.

So I went shopping. This time I set out to find a card with a libre driver that would work with GNU/Linux. So I got the Edimax card - it was advertised by Linux Emporium as working with Debian Etch "out of the box" (though now it just says "works reliably" with Etch). I did get it working, but nothing like out of the box. It worked fine at home, but I could never get it to detect the open wireless system at work, like my home LAN was the only thing in existence.

Recently, I've been toying with different distros on the laptop, playing with gNewSense-KDE and Debian Lenny. Turns out, gNewsense gets my wi-fi card (with the libre drivers) working, while Debian Lenny doesn't even see it (yeah, same card with libre drivers) at all. Bear in mind that gNewSense is based on Ubuntu, which, in turn, is based on Debian. I honestly don't get it.

If you get it, please help me understand, because I confess to being totally lost. The drivers are libre. They have been available for some time now. The standard line about GNU/Linux systems and hardware is that the drivers are not libre. Yet, here we have libre drivers, and the appropriate kernel devs, distro devs or whomever, still can't seem to make a networking card function properly.

I don't know where the problem lies. I don't know who is to blame. How does one distro get it right, but the parent distro (with the great reputation) get it wrong? That means it cannot be the kernel devs, because the device works, just not out of the box on certain distros. Bear in mind that networking has always been GNU/Linux' forté.

Look, all I'm saying is, I can just picture a suit, or just some regular Joe, trying out GNU/Linux, and running into this issue. I honestly don't think there is much excuse for not having something working properly and out of the box when you have the blooming drivers. Will someone please help me find a clue? And, no I really don't want to hear about how to compile the drivers from source. I want to know why something that should "just work" doesn't.

Note: I could have misread the Linux Emporium site way back then, but it appears to have changed since.


Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Debian Etch != Ubuntu FF

Ubuntu pulls from the Debian unstable tree. The most recent Debian stable kernel is 2.6.18-5. I run Kubuntu, but I expect Ubuntu is pretty close, and my kernel is 2.6.20-16. At http://git.kernel.org you can find the changes between those builds. I didn't spend much time looking, but there are about 100 changes to the single file, bcm43xx_main.c, in 2.6.22 (I don't know how far back that goes).

Something like SCSI should work pretty much the same in most 2.6 kernels. But wireless support is undergoing a lot of development, and even a few release levels will make a difference. Besides, Debian is the workhorse distro, while *buntu is a pony. If you are building a customized server, go with Debian. But if you want a fully functional desktop installed by default, go with *buntu.

Later . . . Jim

RenaissanceCore IDS, check it out at:
http://sourceforge.net/projects/renaissancecore


Same problem...

I had the same problem with the Ralink RT2500, the source code is even included in Debian's main repo.

When i asked Debian-devel about this that answer was simple, yet very enlightening.

Since those drivers aren't part of the mainstream Linux kernel, they'll never be part of the mainstream Debian installer.

From a developement perspective, that makes sense, since there's a lot involved in maintaining the installer. From the user perspective, however, it very well may make Debian unusable for many people.