I am a metal monkey!
Administrator Community Supporter?
Jedai Sword Master
Gender:
Posts: 5659
45587 credits Members referred : 3
« on: Nov 18, 2008, 11:09:21 pm »
A few days ago I've installed Ubuntu 8.10 to my Toshiba Satellite A200-1M4 laptop. The first and only problem I got with this installation is that my wifi card (Atheros AR242x) were not working correctly.
As I see there are many solutions in the web regarding this problem, but none worked for me so here I am going to share it with anyone that still has troubles on using his/her Atheros AR242x wifi card. For my setup I wanted to be connected using WEP2 (128 bit encryption) with static IP address.
Here are the steps:
1) Install the linux-backports-modules-intrepid package. In a terminal window give this command :
2) Go to System -> Administration -> Hardware Drivers and deactivate the "Support for Atheros 802.11 wireless LAN cards" driver
3) We need to install WICD which can be configured in order to use the WEXT driver. Go to Settings > Repositories > Third Party Software > Add and add the following line :
Code:
deb http://apt.wicd.net intrepid extras
After that in the Terminal window execute the above commands :
And you are done Make sure to reboot your pc before using your new software, and use the WEXT WPA supplicant driver for connecting to your network (in wicd go to Preferences -> General settings)
Hope this mini tutorial will save some time from a few Ubuntu fans out there
« Last Edit: Dec 17, 2008, 10:54:37 am by Nikolas »
Google dot what?
Posts: 2
12 credits Members referred : 0
« Reply #5 on: Dec 18, 2008, 09:19:40 pm »
Hi ! Yet another one registering just to post in this thread (google find).
I have an Atheros AR242x in a Lifebook E-series E8310 (confirmed by lshw) and had the same problems. Card detected but no networks found.
When upon reading your instructions, I noticed your instructions require switching to WICD - a whole different network manager, extra repository etc. I started wondering whether it wouldn't be possible to tell the standard Ubuntu 8.10 network manager to load the correct driver. Turns out it will!
2) Go to System -> Administration -> Hardware Drivers and deactivate the "Support for Atheros 802.11 wireless LAN cards" driver
Note that installation of the backports modules adds a "Support for 5xxx series of Atheros 802.11 wireless LAN cards" (ath5k) driver to that menu, that you do NOT deactivate.
3) Reboot... done! Immediately connected. Gnome network manager will automatically use the other driver since the wrong one was manually disabled.
This simpler way may work for most as well! If it doesn't, you can always proceed with WICD.
I am a metal monkey!
Administrator Community Supporter?
Jedai Sword Master
Gender:
Posts: 5659
45587 credits Members referred : 3
« Reply #6 on: Dec 19, 2008, 10:39:54 am »
@web what kind of network are you using? I tried the solution you said and it was impossible to connect using WEP
Just another rainy day
Posts: 1
6 credits Members referred : 0
« Reply #7 on: Jan 08, 2009, 01:19:02 pm »
Thanks Nik for starting this tread (google), & web for simple instruction. I have this BenQ Joybook Lite U101 which I dual boot with ubuntu, until few minutes ago had to used wired to get to internet. web instruction can make my wifi (atheros AR242x) work on my home network (WPA2-PSK). Prev. this card registered on Hardware Testing, but no network found.
I am a metal monkey!
Administrator Community Supporter?
Jedai Sword Master
Gender:
Posts: 5659
45587 credits Members referred : 3
« Reply #8 on: Jan 08, 2009, 05:18:37 pm »
Hi Zaha, I am glad I've helped someone with this tutorial. At least I have contributed a penny to this great product/community
@web what kind of network are you using? I tried the solution you said and it was impossible to connect using WEP
Sorry about responding late. My post was a bit of hit and run I guess.
My network is WPA2-PSK as well, but it shouldn't matter - it was either "detect many networks and connect too" or "see nothing at all". IOW, things went wrong before even reaching the encryption phase, methinks.
Later I noticed my solution works (for me) only after cold boots. When I reboot Linux, or reboot from windows into linux (dual boot), my wireless still doesn't. So your solution may still be better, however I've left mine as is, because I like keeping things as "default" as possible, because upgradeability tends to be better then. A heavily customized install gets ugly when upgrading to a later release. Having to cold boot before using Linux wireless is a small price to pay - I generally cold boot into the OS I need that day anyway. However, while experimenting, you might have tried warm boots only and therefore found it non working?
I seem to remember that somewhere under the hood there's a firmware initialization thing about kicking a wireless adapter into action, that might have something to do with warm boots not working. The procedure might not be reboot-proof; not working on an already initialized adapter.
Where are my glasses?
Posts: 23
146 credits Members referred : 0
« Reply #10 on: Jan 21, 2009, 08:58:08 am »
After install of a.m. packages, a few steps below:
* rmmod ath5k + rmmod mac80211 + rmmod cfg80211 * in Network --- Networksetting ADD NEW device - as wireless, add the kernel module ath_pci * /etc/modprobe.d/blacklist enter at bottom a new blacklist entry blacklist ath5k, * reboot * after boot delete your earlier added new wireless device, then edit your NOW editable AR242x 802.11abg Wireless PCI Express Adapter, enter ath_pci as kernel module! * Your hardware now should become visible - if in range of an AP you should see the signal. You may however have to restart your network with rcnetwork restart. For unknown reason the NEW kernel modules do NOT autoconnect to the wireless network, even after a new system-start or reboot!
Trackback URI for this entry : http://www.webdigity.com/trackback.php?topic=8202