ubuntu 10.10 won't connect to wlan

[NexusN]

Sad to see it is ubuntu 10.10 to disable the n function, it is quite important to me who BT crazily.........

I felt strange to see the speed is limited to 2 MB/s........i see now.
Hope to see the fix soon

[Gyoja]

i have a broadcom 4311 wireless card on an HP pavillion dv9000. like many here i had some issues when upgrading to 10.10. wireless stopped working and i got a message that the password was incorrect when it wasn't. for me the solution was pretty simple. i use Wicd as my network manager. i opened Wicd -> preferences -> advanced settings. here there is a drop down to select WPA Supplicant (i use WPA-2 encryption on my router). i switched from the default Wext driver to the nl80211 driver and presto - connection problem solved. hopefully this helps

[cray0rb]

and for those of us using WEP, still no solution?

[scarleo]

I think 10.10 came with some power management features for the NIC which many NICs seem to have a lot of trouble with, at least my Broadcom did. I used to have a lot of the issues reported in this thread with slow internet or wouldn't connect to WLAN.

If your NIC is being power maneged doing 'iwconfig' would show 'PowerManagement:All packets accepted' or something similar. When in this state my network was really slow. However, if you turn this PowerManagement off all was back to normal. I'm not saying this is your problem, but might be worth a shot. To turn PowerManagement off just do:
'sudo iwconfig wlan0 power off', of course change wlan0 to whatever your actual connection is (like eth0, eth1 or whatever).

[cray0rb]

iwconfig is showing Power Management Off. Still no luck getting connected stably

[ionplay]

Similar to everyone else in this thread - minus a few tangential posts

I have installed 10.10 on my laptop and experiencing unexpected and uncommon wifi connection issues
lsb_release -d
Description: Ubuntu 10.10
uname -mr
2.6.35-24-generic-pae i686

I am using an ASUS X72D laptop
with a AR9285 Wireless Network Adapter

and basically as I read this thread, the solution is to downgrade to 10.04, and/or to downgrade just the kernel
but does anyone know if there is a way to isolate what changed in the kernel to cause this problem in the first place???
who is working to correct this problem and how do we help??

sudo lshw -C network

  *-network               
       description: Wireless interface
       product: AR9285 Wireless Network Adapter (PCI-Express)
       vendor: Atheros Communications Inc.
       physical id: 0
       bus info: pci@0000:04:00.0
       logical name: wlan0
       version: 01
       serial: 1c:4b:d6:fa:5e:a5
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath9k  driverversion=2.6.35-24-generic-pae firmware=N/A latency=0 link=no  multicast=yes wireless=IEEE 802.11bgn
       resources: irq:16 memory:fea00000-fea0ffff

iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:off/any  
          Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated   
          Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off

lspci | grep Wireless
04:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)

lsmod | grep ath
ath9k                  89076  0 
ath9k_common            5982  1 ath9k
ath9k_hw              292297  2 ath9k,ath9k_common
ath                     8153  2 ath9k,ath9k_hw
mac80211              231541  2 ath9k,ath9k_common
cfg80211              144470  4 ath9k,ath9k_common,ath,mac80211
led_class               2633  2 ath9k,asus_laptop

iwlist scan
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

wlan0     Scan completed :
          Cell 01 - Address: 00:1E:E5:44:0C:4B
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=44/70  Signal level=-66 dBm  
                    Encryption key:on
                    ESSID:"hemlockadventure"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=000006ba5bf4d183
                    Extra: Last beacon: 14760ms ago
                    IE: Unknown: 001068656D6C6F636B616476656E74757265
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 030106
                    IE: Unknown: 2A0104
                    IE: Unknown: 2F0104
                    IE: Unknown: 32040C121860
                    IE: Unknown: DD090010180203F4000000

rfkill list
0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

I have done a fresh install of 10.10, and I have only installed the default updates, The only additional package outside of default 10.10 I installed was the WICD packages.

Is it possible there is a driver conflict for wireless by default which would explain why so many users are experiencing the same problem. And I would wager that for each post in this thread there are a hundred more in the same boat but unable to find this thread.

[ionplay]

the other thing I would add that I have seen in my logfiles and in the logs others have posted on this matter from
syslog
and
messages

kernel: [31926.193065] ADDRCONF(NETDEV_UP): wlan0: link is not ready

and I am not sure how to make it ready when all the commands above appear correctly

[oddious]

It will find it, but it won't connect.this has happened to every wireless network i've tried to join. ethernet rj-45 works fine(wired)

Had a quite similar problem on ubuntu 9.10

this:

sudo aptitude install wpasupplicant

worked

[ionplay]

I am on 10.10
still no wlan love - using external D-Link wifi adapter until I figure out how to use built-in wifi on laptop

K72Dr:~$ sudo aptitude install wpasupplicant
sudo: aptitude: command not found

K72Dr:~$ sudo apt-get install aptitude
Reading package lists... Done

K72Dr:~$ sudo aptitude install wpasupplicant
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.                                         
K72Dr:~$

no fireworks
no love
still using D-Link

[richwales]

I'm seeing a similar (?) problem with 10.10 on a Dell Latitude D620. This machine has a builtin Intel 3945ABG wireless adapter, and Ubuntu is using the iwl3945 driver.

I can connect just fine to 802.11g access points (at work, or at my mother's home). And I can connect just fine (in 802.11a mode) to my Netgear WNDR3300 access point (with DD-WRT firmware) at home, provided I configure the access point's 5-GHz radio to "A-only" mode.

However, in hopes of enabling 802.11n capability at home, I tried last night to reconfigure my Netgear's 5-GHz radio to "AN-only" mode (using a wide, 40-MHz channel) — without making any configuration changes on my Ubuntu laptop — and after I did that, the laptop was unable to connect at all. The logs showed an endless repetition of messages like the following:

Apr 9 00:20:44 rde-richw-2 NetworkManager[1321]: <info> (wlan0): supplicant connection state: scanning -> associating
Apr 9 00:20:44 rde-richw-2 kernel: [168861.354918] wlan0: authenticate with 00:1f:33:b6:cd:82 (try 1)
Apr 9 00:20:44 rde-richw-2 kernel: [168861.355625] wlan0: authenticated
Apr 9 00:20:44 rde-richw-2 kernel: [168861.355669] wlan0: associate with 00:1f:33:b6:cd:82 (try 1)
Apr 9 00:20:44 rde-richw-2 kernel: [168861.357320] wlan0: RX AssocResp from 00:1f:33:b6:cd:82 (capab=0x11 status=18 aid=0)
Apr 9 00:20:44 rde-richw-2 kernel: [168861.357328] wlan0: 00:1f:33:b6:cd:82 denied association (code=18)
Apr 9 00:20:44 rde-richw-2 kernel: [168861.357359] wlan0: deauthenticating from 00:1f:33:b6:cd:82 by local choice (reason=3)
Apr 9 00:20:54 rde-richw-2 NetworkManager[1321]: <info> (wlan0): supplicant connection state: associating -> disconnected
Apr 9 00:20:54 rde-richw-2 NetworkManager[1321]: <info> (wlan0): supplicant connection state: disconnected -> scanning

Note the denied association (code=18) error, similar to what other people have reported seeing.

My wife's Windows 7 machine, with a Linksys AE1000 dual-band wireless-N adapter, can connect to the AP without difficulty while it's in either "A-only" or "AN-only" mode. And when I reconfigured my AP back to "A-only" mode, my laptop was once again able to connect to it.

Since my wife's computer was able to connect just fine in all cases, I'm assuming the problem is most likely a bug in the Ubuntu code (or possibly a failing in the laptop's Intel wireless adapter), and not a problem in the Netgear WNDR3300 access point or the DD-WRT firmware.

This isn't a horrible showstopper problem for me, since I can connect — but I'd like to find a fix if possible, since the problem is preventing me from upgrading my home network for possible future 802.11n capability.

As I said, this problem appears at first glance to be similar, but please accept my apologies if it turns out to be something completely different that belongs in a new thread.