wlan0 Scan completed : Cell 01 - Address: 00:1A:70:79:2C:BF Channel:11 Frequency:2.462 GHz (Channel 11) Quality=40/70 Signal level=-70 dBm Encryption key:on ESSID:"linksys" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Any tips would be much appreciated. Thanks! affects: linux (Ubuntu Lucid) → linux-backports-modules-2.6.32 (Ubuntu Lucid) Changed in linux-backports-modules-2.6.32 (Ubuntu Lucid): importance: High → Medium Rolf Leggewie (r0lf) on 2010-02-24 Changed in linux-backports-modules-2.6.31 (Ubuntu Lucid): status: New → Triaged http://tbapplication.com/atheros-driver/atheros-driver-ubuntu-9-04.html
They work and play well in Ubuntu 12.04 (I reference Ubuntu 12.04 because its the other LTS still getting support.) They don't work and play well starting with 13.10 and up. Partners Support Community Ubuntu.com Ubuntu Documentation Official Documentation Community Help Wiki Contribute Page HistoryLogin to edit WifiDocs/Driver/Atheros Built-in drivers/modules, tested only on Intrepid Also works on Karmic - see below If Your time would be better spent pursuing legitimate avenues of promoting your websites. reply Log In or Register to post comments Eugene Markow (not verified) on Aug 28, 2009 I run Arch Linux on my Presario CQ50 laptop. https://help.ubuntu.com/community/WifiDocs/Driver/Atheros
This solution is based on this thread on the forums: http://ubuntuforums.org/showthread.php?p=6089169 If after all the above you see a network but cannot connect You might want to try changing the WPA But it does take some skill to resolve issues should they occur at compile time. Can anybody confirm that the bug is solved? When selecting a laptop for someone, I deliberately chose one that had an Intel WIFI card and it works great without any configuration or other changes at the sites we use
People should not expect this to hit in May and there is even a chance this will be left unfixed past June (OMG!) I may release patched kernel in my PPA It now worked another after a try of modprobe -v ath_pci, I have to load that module at start right ??? –zillion Jan 19 '10 at 18:05 Do I In the case of Windows, the hardware vendors are the ones who write the drivers, package them into stupid installers and make it available to the public for a price... Ichimonji10 (ichimonji10) wrote on 2009-11-23: #17 @afeet From what I remember, I was able to upgrade to the 2.6.28-16 kernel and use both eth0 and wlan0 with zero extra configuration.
I haven't done anything yet and have done some research and thinking about installing Madwifi, but the recent history is outdated and only goes up to hardy heron. To do that, edit (or create) the file /etc/modprobe.d/options.conf to include the line options ath_pci rfkill=0Your wireless should work after you reboot. (Edited 2010-05-15 to remove advertising spam links) WifiDocs/Driver/Atheros (last You do acknowledge that what you want will require more work. None, the status of the bug is updated manually.
Now type the following commands in the terminal window: sudo nano /etc/apt/sources.listNow uncomment anything in that file that starts with deb by changing it from #deb to deb or something along This doesn't require Canonical to be involved in upstream wireless development; it just requires modifying the Ubuntu kernel source to replace the wireless stack from upstream with better tested, slightly older ok. Just about any other type of wireless chipset will work "out of the box" well and reliably with Linux.
CaptSaltyJack (csjubuntu) wrote on 2010-05-05: #32 Haven't tried yet, too busy this week with work. her latest blog You may want to hang on to them rather than always running the latest lucid kernel. Jeremy, I have to wonder, what exactly are you expecting? And reply Log In or Register to post comments Volker Hett (not verified) on Aug 28, 2009 As an owner of an Asus EEE 901 I can feel your pain.
And the folks at canonical must do what it takes to make it happen.... Check This Out That said, the kernel package in my PPA is still waiting to be built. Do you think Canonical staffers are just sitting on their hands with nothing to do? But I think as far as this ticket is concerned all the 100x pinetrail netbooks from ASUS are the same.
And hardware developers actively support Windows. the fault lies with the wireless hardware makers who have refused to work with the kernel drivers, we are not even saying they should opensource their drivers or even write good Again, while ubuntu does tent to stick to the, lets say, more active end of the Wireless driver coding schedule, its definatly one of the better distros out there for getting Source Adv Reply October 31st, 2009 #7 Eric Lathrop View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Oct 2009 Beans 4 Re: Atheros WiFi Adapter not
Adv Reply October 30th, 2009 #6 GreatBunzinni View Profile View Forum Posts Private Message Just Give Me the Beans! It only makes it more difficult to actually fix this issue. Jugding from a quick glance at the changelog, I think my kernel is basically the latest lucid kernel (got it from git) plus the necessary patch. Your wireless connection should work now.
My card work with madwifi or ath5k cause it's a g card ... (7000 something I think) The big problem is to get the good driver and configure network-manager properly ... So try the following, but Be Extremely Careful - this next command opens nautilus with root privileges, which can change and/or damage any file on the system. 2) Hit "alt+f2" to In this thread you will find the instructions for installing the madwifi drivers for Atheros wireless cards. have a peek here After hours of searching many, many websites, I found a post that mentioned "blacklist-ath_pci.conf".
Not the answer you're looking for? tar -zxvf madwifi-hal-0.10.5.6-current.tar.gz 3. The problem with wireless on Fedora that I mentioned in the post you quote came down to Fedora pushing out the b43 driver to replace bcm43xx as soon as that change You don't seem to have an Atheros-based device.
Score yet another point for linux. Now if you were using Ubu 8.04 I'd say you'd have a real complaint b/c Wireless/Gnome NetworkManager was a complete horror to deal with and set-up.