Page 1 of 1
AR5008 , AR5416 , AR5418 chipsets driver open suse 11.1
Posted: Tue Jul 21, 2009 5:39 am
by rssb
I have a AR5008 card, with kernel 2.6.27.23 ( on x_64, a T60 with T7200 ). The card comes up with Ath9k driver in open suse 11.1. It works, but keeps disconnecting from the wirless routers which uses wpa2-psk.
Tired to compile the madwifi drivers, everything goes well with the compile and install, however modprobe ath_pci never loads the driver.
Is there a way to get this working. The ath9k comes up with wlan0 name.
Tried black listing ath9k, then nothing shows up for the wireless in ifconfig -a.
Is there a problem with Ar5008 chipset and are AR5416 etc.. better ?
Re: AR5008 , AR5416 , AR5418 chipsets driver open suse 11.1
Posted: Wed Jul 22, 2009 2:41 pm
by Kaervak
Try adding the madwifi repo,
http://madwifi-project.org/suse/11.1/ and install the drivers from there instead of compiling from source. That might work better for you. I've only ever used an AR5001X based card in OS 11.1 with the included ath5k driver and it's worked perfectly. Maybe some lingering issue in an older driver version?
Re: AR5008 , AR5416 , AR5418 chipsets driver open suse 11.1
Posted: Thu Jul 23, 2009 3:44 am
by tylerwylie
I'd try the latest ath9k drivers from
http://www.linuxwireless.org
I had similar issues, and usually updating to the latest release helped me. madwifi works like crap for my AR5418ABGN.
You can also join the ath9k mailing lists and seek help there, the developers(Atheros Employees!) and the community are very helpful, and you bringing your issue to their attention could result in a better product overall
Tyler.
Re: AR5008 , AR5416 , AR5418 chipsets driver open suse 11.1
Posted: Mon Jul 27, 2009 9:40 am
by rssb
Ath9k worked great, but I had to upgrade the kernel to 2.6.30 from 2.6.27. Thanks tyler
Re: AR5008 , AR5416 , AR5418 chipsets driver open suse 11.1
Posted: Mon Jul 27, 2009 1:51 pm
by tylerwylie
rssb wrote:Ath9k worked great, but I had to upgrade the kernel to 2.6.30 from 2.6.27. Thanks tyler
You shouldn't have to, I'm using the 2.6.30 compat wireless tarball on a 2.6.29 kernel....the numbering is there to let you know which kernel contains that release...oh well I'm glad to see everything's working out!