[Bug 12394] Madwifi module out of date

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Tue Aug 9 20:56:41 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=12394
Ubuntu | linux-restricted-modules





------- Additional Comments From mail at theantix.org  2005-08-09 21:56 UTC -------
(In reply to comment #0)
> Atheros has reved the 5212 chip set preventing the shipping MADWIFI module
from working with newer cards using the Atheros product. I 
> tried picking up an independently prepared source package and building it but
the resulting module does not load. Would it be possible 
> to 
> update this package in the near future? 
> 
> The package and build procedure I used came from
http://www.marlow.dk/site.php/tech/madwifi.
> 
> The WIFI card in question is a D-Link DWL-G650 D-Link part bwlg650na.b5
hardware version B5 firmware version 2.54
> 
> The stock driver provides ath_hal 0.9.12.14 (ar5210, ar5211, ar5212)
> 
> The newer hal is identified as ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212,
RF5111, RF5112, RF2413)     

Is this a bug in Hoary or Breezy?  I had the same problem in Hoary, dmesg
indicated that the ath_hal failed with status code 13, which means that my newly
purchased PCMCIA card with an Atheros chip did not work (despite being listed on
the ubuntu hardware chart as fully supported).  Some investigation revealed the
same as you, a new madwifi driver was required.  To resolve, I removed the
linux-restricted module in hoary and compiled the latest drivers from madwifi. 
I tested the latest liveCD of Breezy, and that detected the ath_hal fine and I
could configure it with ifconfig and iwconfig to get full networking.

I'm not sure if I should make this as confirmed, resolved, or leave it be.  In
some ways it is both, so I'll leave the status alone for now.

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the kernel-bugs mailing list