latest Etch update broke my wifi...
 

The latest Etch update broke my wifi...

I have an Atheros based card and am running the MadWifi drivers (at least I WAS running the MadWifi drivers).

Since the latest kernel update, my MadWifi drivers no longer work...

I've forgotten how to build the drivers from my source files...

And even if I rebuild the package,... I don't know if that will solve my problem. Has anyone heard of Etch using some other mechanism to detect and/or launch the pci detection and/or wifi drivers???

Don't blame Etch. Any kernel update will disable your wifi. The module needs to be recompiled to match the new kernel. Don't forget to delete the old module (.ko file) first.

I find it pretty amazing that you can do a kernel upgrade in Ubuntu with everything still working after a reboot.

In Debian, I have a particular affinity for module-assistant for stuff like fglrx modules for ati drivers.

I'm seriously thinking of abandoning Etch for Ubunto...

One of the main reasons I went to Etch in the first place was configurability... and it just seems so freakin' pointless that they won't maintain compatibility with madwifi because of the licensing issues (this goes for all distros, actually). Now I have togo back and re-figure out what I did in the first place to get everything working...

I'm really getting sick of the whole GPL "holier than thou" deal with allowing distribution of proprietary drivers... Just let distros release the stinkin drivers already... Let `em put in a disclaimer or something...

That said, my girlfriend's computer is a laptop running XPee... and believe me, setting up wireless or bluetooth on that machine is NO EASIER than on Linux... It's just that there is more commercial support... for what it's worth... since most of the time that stuff doesn't work right either... and, like I said, is no easier to install.

That "deal" is what keeps Linux free. You had best develop a different attitude about it if you enjoy having an alternative to MS.

Restarting the wireless should be as simple as deleting the old module, and typing #m-a a-i madwifi" or whatever the module is named.

Don't forget how frustrating it is next time you're buying hardware. Insist on native Linux compatibility, and these issues are much less difficult.

Excuse me?!?!?!?! I'm a lawyer my friend... Licensed in 2 US states,... So I understand the GPL probably much better than you do... What I also understand is that the GPL is structured rather arbitrarily and that a license closer to the BSD license would have benefited Linux much more...

Hardware manufacturers follow the almighty buck. Right now Linux compatibility is a combination of altruism and sucking up to developers... M$'s market share is what hardware makers cow-tow to... That will only change when Linux's market share builds beyond a fringe element...

In addition,... try to find a piece of hardare that adequately describes what chipset the thing is designed with or the extent of its Linux compatibility on the box... If I gave you a $1 for every hardware manufacturer that published its Linux compatibility on its packaging (or even detailed specs that would lend themselves to figuring it out for yourself) I would still be able to buy an average bar a round of drinks with the change left over from a $100 bill...