rtl8192cu module fails to connect to some access points

I tried the newer kernel and backports, but get the same result.

Pluging in the USB wifi adaptor results in the module being loaded, but it does not connect to any access point. Manually selecting the access point results in an apparent connection, but it does not really connect to the Internet.

The package just installed is: linux-backports-modules-cw-3.0.0-2.6.38-12-generic

Tried a newer kernel from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-rc9-oneiric/

Same difference, module loads but fails to connect to Meraki access point.

Comments on Bug # 548992 suggests turning off power management for the wlan adaptor.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/548992

However, on the rtl8192cu, power management seems to be disabled and is already off.

~$ sudo iwconfig wlan2 power off
Error for wireless request "Set Power Management" (8B2C) :
    SET failed on device wlan2 ; Invalid argument.

~$ iwlist wlan2 power
wlan2 Current mode:off

~$ iwconfig wlan2
wlan2 IEEE 802.11bgn ESSID:"xobilyol"
          Mode:Ad-Hoc Frequency:2.412 GHz Cell: 5A:BD:E0:FF:BD:55
          Tx-Power=20 dBm
          Retry long limit:7 RTS thr=2347 B Fragment thr:off
          Power Management:off

Note: It also does not appear to work in ad-hoc mode, unless I am setting that up wrong ...

Note that the AP is a Meraki MESH, made up of 2 Meraki mini AP's. I contacted Meraki, they say their AP's follow all known standards. They did push out an updated firmware, but it did not help our case.

Enabled debugging out for Network Manager. I've added notes indicating when I plugged in, unplugged, connected, and disconnected.

# Unplugged RTL8192CU USB WiFi adaptor
15:55:07

# Plugged in RTL8192CU USB WiFi adaptor
15:55:11

# Disconnected via Network-Manager
15:57:25

# Re-connected via Network-Manager
Oct 10 15:57:54

Tried the latest 3.0 kernel and linux-firmware 1.60 from oneiric, but it fails to connect.

~$ uname -a
Linux crow 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:50:42 UTC 2011 i686 i686 i386 GNU/Linux

~$ ls -l /lib/firmware/rtlwifi
total 272
-rw-r--r-- 1 root root 13540 2011-08-23 07:22 rtl8192cfw.bin
-rw-r--r-- 1 root root 16014 2011-08-23 07:23 rtl8192cufw.bin
-rw-r--r-- 1 root root 20526 2011-08-23 07:23 rtl8192defw.bin
-rw-r--r-- 1 root root 88856 2011-08-23 07:23 rtl8192sefw.bin
-rw-r--r-- 1 root root 129304 2011-08-23 07:25 rtl8712u.bin

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 869530

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Alan Pater, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]