Created attachment 100041 [details] Output from a manual attempt without network-manager hi. I bought an RTL8192CU USB Wireless Network Adaptor about 6 month ago, at which time I was running Ubuntu 12.10 (Kernel 3.4.x). When I plugged in this USB Adaptor, the driver (rtl8192cu) was loaded successfully and I was able to find and start connecting to my wireless router. However, I was not able to actually connect to it. It just kept popping up with the password dialog. The funny thing is that when I plugged the USB Adaptor into my 32bit laptop, it was working just fine. The issue seamed to be related to the 64bit kernel version. I was able to get around this by downloading the driver source from Realtek's website and compile it myself. But now that I have upgraded the OS to the latest Ubuntu (Kernel 3.8.0 by default) the kernel source is no longer compatible. Also I had hoped that the issue had been resolved in the kernel source at this time as I found that a lot of people have had this issue. Then I read somewhere that the issue should be resolved in kernel 3.8.6, so I compiled a version myself, but same result. I then tried the same with 3.8.10 and 3.9.0-rc8 but still no go. For now I have USB Tethering running from my smartphone which is connected to the wireless router. This is not optimal and I would really like to get this driver working. I have attached dmesg and output from a manual attempt without the usage of any network managers. I have also tried this on two different 64bit machines to eliminate any issues on the hardware side, just since it seams to be working on 32bit versions.
Created attachment 100051 [details] Output from dmesg after connection attempt
Created attachment 100141 [details] Trial patch for rtl8192cu With the changes made in 3.8.6, the driver connected OK to WPA2-encrypted networks. With this patch applied, it should work OK will all networks.
I am using WPA2 on my router, but I will try this patch on the 3.8.10 version and see what happens.
patching file drivers/net/wireless/rtlwifi/rtl8192cu/hw.c patching file drivers/net/wireless/rtlwifi/rtl8192cu/hw.h patching file drivers/net/wireless/rtlwifi/rtl8192cu/mac.c patching file drivers/net/wireless/rtlwifi/rtl8192cu/sw.c patching file drivers/net/wireless/rtlwifi/rtl8192cu/sw.h patching file drivers/net/wireless/rtlwifi/usb.c Hunk #1 succeeded at 740 (offset -84 lines). Hunk #2 succeeded at 947 (offset -80 lines). Hunk #3 succeeded at 988 (offset -80 lines). patching file drivers/net/wireless/rtlwifi/wifi.h Hunk #1 succeeded at 1572 (offset -164 lines). Hunk #2 FAILED at 1871. Hunk #3 FAILED at 2050. 2 out of 3 hunks FAILED -- saving rejects to file drivers/net/wireless/rtlwifi/wifi.h.rej
Created attachment 100151 [details] Revised Proposed patch to fix problems in connecting to WEP and WPA networks Sorry, I sent the version for wireless-testing. This one will apply to mainline 3.9-rc8.
Thanks, I will report back once it has finished building :)
Well now it is better than before, but it is still not working. It finally connects, but I cannot use the connection. For some reason when using dhcp then both Bcast and inet are assigned the same address. And when trying with static address setup, I can get a connection for a few seconds and then nothing. The connection to the router seams to be persistent, but there is no connection out.
Created attachment 100161 [details] Connection Attempt after applying the patch file
So I thought about what you said, that kernel 3.8.6 fixed connection issue with WPA2. So I changed my router configs from WPA2/WPA to simply WPA2 and TKIP/CCMP to simply TKIP and started testing with 3.8.6, 3.8.10 and 3.9-rc8 (Unpatched). Using these router configs I can connect using all 3 kernels, but I still get the same issue as with the patched 3.9-rc8 where I can only stay connected for a little while. So the patch you provided does work as it should, letting other security methods connect. But there is still a general issue in the wifi driver which makes the connection unstable. However, as this is the same whether the kernel is patched or not, the issue is not in the patch you provided. This should help you NOT looking in the wrong place :) I have now 6 different custom kernel builds installed, if you want me to build and test more, I still have plenty of space on my /boot partition ;) At least this is getting closer to a working solution
I have no idea what is wrong with your setup. On my system, using the kernel from the wireless-testing git repo, the driver stays connected for days. There are some changes in rtlwifi that cannot be backported to older kernels. Perhaps they are the difference. You can get these patches from wireless-testing, linux-next, or the mainline 3.10-rc1 in about 3 weeks.
Tried with the wireless-testing branch, same issue. * Normal state: It connects fine, and I have an outgoing connection for about 10 seconds. It does not disconnect from the router, but there is no connection between the router and the computer. * Prope the driver with Software Encoding (modprobe rtl8192cu swenc=1): It connects fine, and I have an outgoing connection for about one minute. From here, the connection comes and goes, which means that it almost works, but a couple of times a minute the connection is lost but comes back on. This makes the driver okay for browsing, but not good for anything with a direct connection like SSH, Downloading etc.
Created attachment 100191 [details] Version of patch for wireless-testing kernel Use this patch for wireless testing tree.
One other suggestion - use NetworkManager to make the connection. Your scripts are using a lot of WEXT commands that are not implemented.
I do use NetworkManager. I just used the terminal for output purposes. And the wireless testing patch helped, but it did not fix anything. Now I can use hardware encoding, but with the same results as with software encoding before. It connects just fine, but the connection is very unstable. I did however manage to fine someone who have fixed the Realtek source to work with 3.8+ and 3.9+ kernel versions. This driver is working fine, so that did give me a chance to rule out any hardware issues or other software related once. And it has provided a working WiFi until the native driver is working. If you need me to test anything else, just let me know. But for now, nothing in the git's are working, patched or not. I have tried every branch in every tree.
Please try this bug with latest kernel image.