Slashdot Mirror
Atheros Releases Free Linux Driver For Its 802.11n Devices
mcgrof writes "Atheros has released a shiny new Atheros driver for all their 11n devices aimed for inclusion in the Linux kernel. This new driver has no proprietary HAL and is licensed under the ISC license, so the BSD community should be able to benefit as well. Note: no firmware required!"
for my AR5212
Geology - it's not rocket science; it's rock science
Now... if we can just get Broadcomm to do the same.....
THANK YOU, Edward Snowden!! Americans owe you a debt of gratitude (whether they know it or not..)
No blob, ISC license, and supporting .11n? That only leaves one question: is there a miniPCI card available containing this chipset that I can plug into a little router board?
I am TheRaven on Soylent News
No more weighing the lesser of two evils, I can cross off all the laptops with Broadcom chips and narrow the playing field.
I wasted untold hours with the b43 driver and routinely get bitten when I upgrade kernels and madwifi falls apart and I can't load the new source because it fell apart. Wireless hardware that just works will be a relief.
Does anybody know the HW capabilities of the Atheros chipset?
Thinking of Software Radio...
thegodmovie.com - watch it
That's why I bought the Dell Inspiron 1420n. I KNEW that everything would work under Linux.
When I finally upgrade my home's network, you can bet I'll be going with Atheros.
ath9k - Atheros unveils free Linux driver for its 802.11n devices Â
We are pleased to announce Atheros has released ath9k to the community. This driver is aimed at inclusion to the Linux kernel and supports all Atheros IEEE 802.11n devices. This represents a major shift in terms of support from Atheros with respect to Linux. The ath9k driver comes shortly after Atheros hired two key Linux wireless developers -- Luis Rodriguez and Jouni Malinen.
We have been informed Atheros does plan to add access point support to ath9k and to work with the community to enhance and complete access point support in the Linux kernel. It is understood there is plenty of work required on the wireless stack to complete full access point support. Jouni Malinen will help drive this process within the community while Luis helps enhance regulatory compliance in the Linux kernel.
We are eager to work with Atheros with ath9k and applaud their efforts for properly supporting Linux.
The ath9k driver includes supports for the following chipsets:
* AR5418+AR5133
* AR5416+AR5133
* AR5416+AR2133
* AR9160
* AR9280
* AR9281
How does this affect 802.11 B and G devices? Can I expect greater stability in those products, or does this only help out 802.11n hardware?
Pretend I said something meaningful or insightful here.
And it's been in the kernel for at least one major release. ath5k is the name
I have a few of these devices and they work pretty well with the driver. They don't do access point mode yet, but that will come soon.
Atheros hired Luis R. Rodriguez, the developer of the Linux kernel Atheros driver, back in April with the intention of doing just this. Congratulations!
Help stamp out iliturcy.
The driver itself is open source but depends on the proprietary Hardware Abstraction Layer (HAL) that is available in binary form only.
Breakfast served all day!
This is great!
I applaud Atheros for taking this step, and I will be buying Atheros hardware in the future due to this move.
May other companies learn from this initiative.
After struggling with Zydas ZD1211, various Broadcrap cards and two TI ACX cards, I tried using atheros. After that, I ordered 10 minipci cards to use in my various devices (NAS, Laptop, routers etc.). And by the look of things, I'm never going back ;)
I just get Intel laptops with Centrino...works perfectly.
"You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
I have a dv5030us of the dv5000 series. But this applies to nearly all Pavilion models. If you take out the Broadcom card and replace it with something that is not Broadcom (or does not have its ID in the BIOS), then the BIOS will boot and say "Unsupported hardware detected. Remove and reboot." I wanted official support for wireless. I bought an Atheros card off eBay, installed it, got exactly what everyone was saying it would do. Then, I found this web site: http://www.richud.com/HP-Pavilion-104-Bios-Fix/ . And, I had to hex edit my BIOS and reflash as well. Quite something, HP, doing a hardware lock-in with a vendor who refuses to release specs on their hardware.
From the MadWifi homepage:
The driver itself is open source but depends on the proprietary Hardware Abstraction Layer (HAL) that is available in binary form only.
That's for the madwifi driver.
...yes, they're all written by the madwifi group...
We're talking about the ath9k driver.
There's also ath5k, that does not uses HAL.
"I was gratified to be able to answer promptly, and I did. I said I didn't know." -- Mark Twain
Please don't take this as an insult, I actually congratulate you for don't giving up and learning about your OS while solving an actual issue.
Anyway, my point is: If you know Unix, and have at least some specific knowledge of GNU/Linux, the atheros cards work out of the box. There are two drivers, one proprietary, the other free, both of them work like a charm if you are connecting as a client (I Haven't tried them in other modes since I have an ath chipset in the built-in wlan of my Toshiba laptop, which being a laptop is allmost allways used as a station) I know there are limitations in other modes, specially access point mode, but that's beyond the normal use of a cheap wireless card.
I think you can even try to load the windows driver with ndiswrapper to get certain functionality that might not be available in the GNU/Linux drivers ( I haven't tried ath with ndiswrapper, but most drivers work with it anyway ).
So, this is the beauty of Unix: If you understand the paradigm behind the design of the system, you can use any Unix application. Even if you haven't used it before, all it takes is a quick man page read to get the specifics, the rest, you already know it all.
If to this you add certain specific knowledge about the particular implementation you are going to use, add practice and if you have a general common sense and are a logical person, with at least a normal IQ, you will feel like a fish in the water and be able to do virtually anything with your system after a year or so of using it.
If you don't have this two prerequisites, and try to start using it expecting to get things actually done the first time you try, you will be very dissapointed. If OTOH, you accept you are learning and try harder, again and again, until you get it right, you will learn A LOT, and become skilled on this stuff very quickly, like you did.
If you pretend to use the system as an end-user without learning ANYTHING about it, You can do that too, and have a great user experience, if you follow the rules that would apply in this situation to any other system.
This means:
- An end user of windows or mac buys a computer with the OS preinstalled and configured or get some tech guy to do it for them.
- An end user of windows or mac uses the functionality that is officially supported by the OS, doesn't download and install beta or experimental software, doesn't try to add complex hardware himself, and calls a tech guy to fix the computer once in a while.
The problem with this kind of endusers that refuse to learn (which is ok) is that they don't apply this rules to GNU/Linux, and so they install themselves, add beta and experimental stuff, try to get not supported hardware working, and essentially do a lot of things they don't have the lesser idea how to do properly, and then complain that things doesn't work.
I'm not saying this is your case, I'm just making a point about how something that starts with a user trying GNU/Linux and doing things beyond their current knowledge and beyond what's safe for a beginner can go the right way, proving the power of Unix and it's not so steppy learning curve (like your experience) or can end up with an asshole bitching arround in forums about things not working and then calling his son to get windows loaded on the machine again.
WTF am I doing replying to an AC at 5 A.M on a Friday night?