7392:7811 Edimax EW-7811Un USB dongle won't connect to networks (rtl8192cu module)

[mikewhatever]

The networks around are visible, but when trying to connect, the NM repeatedly asks for the password. Connecting to an open network fails as well.

lsusb
Bus 001 Device 002: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]

lsmod | grep 8192
rtl8192cu 103210 0
rtl8192c_common 75767 1 rtl8192cu
rtlwifi 110972 1 rtl8192cu
mac80211 310872 3 rtl8192cu,rtl8192c_common,rtlwifi

WORKAROUND: Use the drivers downloaded from Realtek's website.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-11-generic 3.0.0-11.18
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3937 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe978000 irq 43'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,1b352201,00100101'
   Controls : 20
   Simple ctrls : 12
CasperVersion: 1.284
Date: Fri Sep 16 20:53:04 2011
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110915.1)
MachineType: czc czc
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-11-generic N/A
 linux-backports-modules-3.0.0-11-generic N/A
 linux-firmware 1.60
RfKill:
 1: phy1: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: czc
dmi.board.vendor: czc
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: czc
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd03/16/2010:svnczc:pnczc:pvr1.0:rvnczc:rnczc:rvr1.0:cvnczc:ct3:cvr1.0:
dmi.product.name: czc
dmi.product.version: 1.0
dmi.sys.vendor: czc

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[mikewhatever (mikewhatever)]

Unfortunately, it still doesn't work with the 3.0.0-12 kernel from the daily ISO Oct 7.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[Alan Pater (alan-pater)]

Am wondering if these are all the same bug as they all involve RTL8192CU having trouble maintaining a connection.

   https://bugs.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.38/+bug/869530
   https://bugs.launchpad.net/ubuntu/+source/linux-backports-modules-3.0.0/+bug/862684

I'll be testing the 3.0.0-12.20 kernel once I get back to the "office" this afternoon. I wonder if it includes the latest (2011-10-07) changes from upstream? "The changes include: 1. Adding new chip revisions including new firmware."

  http://article.gmane.org/gmane.linux.kernel.wireless.general/78677/match=rtl8192cu

[Alan Pater (alan-pater)]

Ok. No luck with the latest kernel and linux-firmware package.

~$ 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

syslog attached to bug #869530.

   https://bugs.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.38/+bug/869530

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Alan Pater (alan-pater)]

See comment #6 in Bug #869530.

The kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-rc9-oneiric/ did not resolve our issue.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[Alan Pater (alan-pater)]

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3c', '/dev/snd/pcmC0D4p', '/dev/snd/by-path', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with AD1981B at irq 22'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 26
   Simple ctrls : 18
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 70HT28WW-1.05'
   Mixer name : 'ThinkPad EC 70HT28WW-1.05'
   Components : ''
   Controls : 2
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
   Playback channels: Mono
   Limits: Playback 0 - 14
   Mono: Playback 7 [50%] [on]
DistroRelease: Ubuntu 11.04
HibernationDevice: RESUME=UUID=1f935c28-d8ff-46ba-b9ff-ae5fc91286be
MachineType: IBM 1875M1U
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=es:en
 LANG=es_GT.UTF-8
 LC_MESSAGES=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=64033bba-f5e3-4e07-80a2-2db250a4fe6f ro splash quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-11-generic N/A
 linux-backports-modules-2.6.38-11-generic N/A
 linux-firmware 1.60
Tags: natty unity-2d
Uname: Linux 2.6.38-11-generic i686
UpgradeStatus: Upgraded to natty on 2011-09-10 (40 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/29/2007
dmi.bios.vendor: IBM
dmi.bios.version: 70ET69WW (1.29 )
dmi.board.name: 1875M1U
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr70ET69WW(1.29):bd05/29/2007:svnIBM:pn1875M1U:pvrThinkPadT43:rvnIBM:rn1875M1U:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 1875M1U
dmi.product.version: ThinkPad T43
dmi.sys.vendor: IBM

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

apport information

[Alan Pater (alan-pater)]

I've gotten in touch with upstream developers, they suggest running wireshark to isolate the issue. I don't have a lot of experience with wireshark, but I'll give it a try if i can find a bit of time.

http://comments.gmane.org/gmane.linux.kernel.wireless.general/79401

[Michael J Daniel (michael-j-daniel)]

I've messed around with this a bit and I think, at least,
the rtl8192cu driver needs to be rewritten to eliminate the BKL (big Kernel Lock).

Where is the documentation that explains the BKL and how to replace it in drivers?

The BKL calls are defined in smp_lock.h.
Is smp_lock.h included in any of the linux-firmware source code?

smp_lock.h is included twice in the manufacturer (realtek) sources for the driver.

My work around is to stay with 11.04,
and building my own version of rtl8192cu from the manufacturer sources.
It works great in my CQU-906.

[mikewhatever (mikewhatever)]

Just tested OpenSuse RC2 with the 3.1 kernel. Same problem, APs visible, won't connect. Looks like the driver needs to go back to the testing branch for another year or two.

[chicoff (chicoff)]

The proprietary driver RTL8188CUS works fine:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=48&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true#RTL8188CUS

To compile the driver for the 3.0 kernel you need to patch two files:
http://askubuntu.com/questions/68198/installing-realtek-8188-wireless-driver-fails

[Xavier López (xavilope)]

I confirm that the propietary RTL8192CU driver can be compiled successfully changing those linux/smp_lock.h includes to linux/smp.h. The propietary driver works fine.

Thanks a lot, chicoff, you've saved my 11.10 install :-)

[David Pérez (sanete)]

Steps I follow:

1) Download the driver
2) Unzip RTL819xCU_USB_linux_v3.3.0_2971.zip in a directory
3) cd directory
4) sudo ./install.sh
5) It compiles ok
6) But I don't know how to install it.

Here are the last lines of output of install.sh:

make[1]: Leaving directory `/usr/src/linux-headers-3.0.0-12-generic'
##################################################
Compile make driver ok!!
##################################################
Authentication requested [root] for remove driver:
ERROR: Module 8192cu does not exist in /proc/modules
Authentication requested [root] for insert driver:
insmod: error inserting '8192cu.ko': -1 Device or resource busy
Authentication requested [root] for install driver:
install -p -m 644 8192cu.ko /lib/modules/3.0.0-12-generic/kernel/drivers/net/wireless/
/sbin/depmod -a 3.0.0-12-generic
##################################################
The Setup Script is completed !
##################################################

I'm using Linux Mint 12, which is based in Ubuntu 11.10.
Any help by a Linux guru will be greatly appreciated.

[David Pérez (sanete)]

I think the old module interferes with the new compiled one.

[David Pérez (sanete)]

Solved!
Sorrry for the noise. I'm quite novice.

How to compile it:

1) Turn off wifi
2) Reboot computer
3) modprobe -rv rtl8192cu
4) cd directory
5) sudo ./install.sh

Hope it maybe useful to anyone else!.

[David Pérez (sanete)]

Strange. the above procedure works once for Linux Mint 12 (next time the computer reboots I experience the same problemas) and never for Ubuntu 11.10.

Any hint please?

I don't need to patch the source files, it compiles ok.

Am I doing something wrong?
Thanks in advance for any hint.

[Matthew Hancock (mahancock90)]

The following fixed this for me (link at the end):

to solve the "linux/smp_lock.h not found" error you need to edit this two files into the archive driver/rtl8192_8188CU_linux_v3.1.2590.20110922.tar.gz

file 1: include/rtw_io.h

Change osdep_service.h (line 49) linux/smp_lock.h to linux/smp.h

file 2: include/osdep_service.h

Change file rtw_io.h (line 36) linux/smp_lock.h to linux/smp.h

Then compile as normal

http://askubuntu.com/questions/68198/installing-realtek-8188-wireless-driver-fails

[Darío Piemonte (dpiemonte)]

I can compile and install the latest driver from realtek following comment #40 and blacklisting the original, but when I plug in the dongle it starts connecting to the network and inmediately after it connects everything freezes! and I mean EVERYTHING, the only way to restart the machine is to cut the power holding the power button, I can't even do a "raising skinny elephants is never utterly boring"

any ideas?

thanks!

[David Pérez (sanete)]

In response to comment #40, I was forgetting blacklisting the old driver, rtl8192cu.

Also, if the Wifi USB adaptor doesn't work, it is useful to unplug it and plug it again.

[David Pérez (sanete)]

In response to comment #42, Realtek has corrected the code, and there is no need anymore to patch source files.

[mikewhatever (mikewhatever)]

Just tested Precise daily of 30.12.2011, and the device still doesn't connect.

filename: /lib/modules/3.2.0-7-generic-pae/kernel/drivers/net/wireless/rtlwifi/rtl8192cu/rtl8192cu.ko
firmware: rtlwifi/rtl8192cufw.bin
description: Realtek 8192C/8188C 802.11n USB wireless
license: GPL
author: Larry Finger <email address hidden>
author: Ziv Huang <email address hidden>
author: Georgia <email address hidden>
srcversion: 785C46E6EA7B8B1A492066F
alias: usb:v7392p7822d*dc*dsc*dp*ic*isc*ip*
alias: usb:v2019pAB2Bd*dc*dsc*dp*ic*isc*ip*
alias: usb:v2001p330Ad*dc*dsc*dp*ic*isc*ip*
alias: usb:v2001p3309d*dc*dsc*dp*ic*isc*ip*
alias: usb:v2001p3307d*dc*dsc*dp*ic*isc*ip*
alias: usb:v07B8p8178d*dc*dsc*dp*ic*isc*ip*
alias: usb:v07AAp0056d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0586p341Fd*dc*dsc*dp*ic*isc*ip*
alias: usb:v9846p9041d*dc*dsc*dp*ic*isc*ip*
alias: usb:v4855p0091d*dc*dsc*dp*ic*isc*ip*
alias: usb:v4855p0090d*dc*dsc*dp*ic*isc*ip*
alias: usb:v13D3p3359d*dc*dsc*dp*ic*isc*ip*
alias: usb:v13D3p3358d*dc*dsc*dp*ic*isc*ip*
alias: usb:v7392p7811d*dc*dsc*dp*ic*isc*ip*
alias: usb:v20F4p648Bd*dc*dsc*dp*ic*isc*ip*
alias: usb:v2019pED17d*dc*dsc*dp*ic*isc*ip*
alias: usb:v2019pAB2Ad*dc*dsc*dp*ic*isc*ip*
alias: usb:v2001p3308d*dc*dsc*dp*ic*isc*ip*
alias: usb:v13D3p3357d*dc*dsc*dp*ic*isc*ip*
alias: usb:v103Cp1629d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0EB0p9071d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0DF6p0052d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0846p9041d*dc*dsc*dp*ic*isc*ip*
alias: usb:v07B8p8189d*dc*dsc*dp*ic*isc*ip*
alias: usb:v07B8p8188d*dc*dsc*dp*ic*isc*ip*
alias: usb:v06F8pE033d*dc*dsc*dp*ic*isc*ip*
alias: usb:v050Dp1102d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp817Cd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp817Bd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp8177d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp8754d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp817Fd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp817Ed*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp817Dd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp817Bd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp817Ad*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp8177d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp8176d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp8170d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp8191d*dc*dsc*dp*ic*isc*ip*
depends: rtlwifi,mac80211,rtl8192c-common
intree: Y
vermagic: 3.2.0-7-generic-pae SMP mod_unload modversions 686
parm: swenc:Set to 1 for software crypto (default 0)
 (bool)
parm: debug:Set debug level (0-5) (default 0) (int)

[ 104.774596] wlan0: authenticate with 94:0c:6d:ba:ba:5a (try 1)
[ 104.776400] wlan0: authenticated
[ 104.799482] wlan0: associate with 94:0c:6d:ba:ba:5a (try 1)
[ 104.803342] wlan0: RX AssocResp from 94:0c:6d:ba:ba:5a (capab=0x431 status=0 aid=11)
[ 104.803355] wlan0: associated
[ 104.805700] ADDRCONF(N...

[James E. LaBarre (jamesl-bestweb)]

Netgear WNA1000N uses the same chipset. This fails with Mint12, Mint LMDE, Fedora 16 as well. Doing another clean install to Ubuntu 11.10 to do more tests (fortunately this T23 isn't in use yet)

[Sander Jonkers (jonkers)]

FYI:

The driver from the realtek site works for me on Xubuntu 10.04 LTS with 2.6.32-38-generic after unzip and sudo /bin/sh install.sh

Details:

zip-file: RTL819xCU_USB_linux_ v3[1].3.2_3192.zip
name of unpacked directory: RTL8188C_8192C_8192D_USB_linux_v3.3.2_3192.20120103

$ lsmod | grep 8192
8192cu 482250 0

lsusb:
Bus 001 Device 002: ID 0bda:8176 Realtek Semiconductor Corp.

[mikewhatever (mikewhatever)]

Precise with the 3.2.0-17-generic, the driver still doesn't work.

[mikewhatever (mikewhatever)]

Precise beta2 gets connected to the AP (gets an IP), but still barely works. Does the built in rtl8192c work for anyone in any distro? I apologize for being thoroughly pissed, but how did it get into the stable kernel in the first place? The latest supported kernel at http://www.realtek.com.tw/ is 3.0.2.

http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=48&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true#RTL8192CU

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[James E. LaBarre (jamesl-bestweb)]

Have tried this yet again with 12.04, daily build, updated as of today (2012/04/09), still no connectivity (fresh install). Tried installing the Realtek version of the driver, still no connectivity.

[mikewhatever (mikewhatever)]

Simmilar issues are experienced with Fedora17 beta, kernel 3.3.1.

Bugzilla reports:

https://bugzilla.redhat.com/show_bug.cgi?id=806142
https://bugzilla.redhat.com/show_bug.cgi?id=789605

[candtalan (aeclist)]

Ubuntu 12.04 updated

I seem to have a version of this bug related to a wireless usb dongle

lsusb
Bus 001 Device 008: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN

lsmod | grep 8192
rtl8192cu 97722 0
rtl8192c_common 69519 1 rtl8192cu
rtlwifi 95804 1 rtl8192cu
mac80211 436455 3 rtl8192cu,rtl8192c_common,rtlwifi

I do not know which package to gather information about.
I will be happy to provide more informtaion if requested (lshw? attached)

Symptoms:
Wireless does not connect with open (unsecured) access points. For example, public cafe facility. This is very inconvenient!
However, it does connect ok to wpa secured network.

[mikewhatever (mikewhatever)]

No surprizes wtih Quantal Alpha2, kernel 3.5.0-2-generic. The device still doesn't work, same simptoms as before.

[Sidarth Dasari (sirsid)]

I believe the Asus N13 usb dongle uses the same chipset. It also has the same issues listed above

[mikewhatever (mikewhatever)]

https://bugzilla.kernel.org/show_bug.cgi?id=45241

[penalvch (penalvch)]

mikewhatever, 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 upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? 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

[mikewhatever (mikewhatever)]

Is this a joke? How many kernel versions do I need to test to get it fixed? The bug has been present since 2.6.38 (when rtl8192cu became stable, but apparently broken) through 3.5, which I've tested a month ago. It's an upstream but, and I've already posted a bug report. The link is up in #78. If that's not a joke, can you explain, what's the point of your request.

[penalvch (penalvch)]

mikewhatever, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/852190/comments/80 :

>"Is this a joke?"

This is Launchpad, not a comedy forum.

>"How many kernel versions do I need to test to get it fixed?"

The issue is not, how many kernels are you asked to test this to get if fixed. Your issue being fixed is depedent on a developer stepping in and fixing it. However, taking the time to provide requested information increases your chances of a developer stepping in and working on this for you, as it gives the developer more data points. This prevents a developer having to waste time asking you to test the very thing you were asked to test in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/852190/comments/79 .

>"The bug has been present since 2.6.38 (when rtl8192cu became stable, but apparently broken) through 3.5, which I've tested a month ago. It's an upstream but, and I've already posted a bug report. The link is up in #78."

We already knew all of this.

>"If that's not a joke, can you explain, what's the point of your request."

See above.

Thank you for your understanding.

[mikewhatever (mikewhatever)]

I apologize for the #80, it was inappropriate, and may have come across as a personal attack. I got a bit frustrated having noticed it's been almost a year since the bug got reported. I'll what I can do about the mainline kernel.

[mikewhatever (mikewhatever)]

I've tried testing "linux-image-3.6.0-030600rc1-generic_3.6.0-030600rc1.201208022056_i386", but the wireless device didn't work. Looking at dmesg, I got this:

dmesg | grep 8192
[ 1.127045] agpgart-intel 0000:00:00.0: detected 8192K stolen memory
[ 13.179009] rtl8192cu: Chip version 0x10
[ 13.521487] rtl8192cu: MAC address: 00:1f:1f:e4:4e:38
[ 13.521493] rtl8192cu: Board Type 0
[ 13.521900] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin
[ 13.522667] usbcore: registered new interface driver rtl8192cu
[ 13.563728] rtlwifi: Firmware rtlwifi/rtl8192cufw.bin not available

[penalvch (penalvch)]

mikewhatever, thank you for testing the mainline kernel.

Could you please provide the information following https://wiki.ubuntu.com/Kernel/LinuxWireless#Bug_Report_Minimum_Requirement_Information ?

[mikewhatever (mikewhatever)]

Right, here it comes:

    What is the wireless Access Point Manufacturer, Model, Firmware Version, and Settings (ex. encryption type, MAC filtering, QoS, Beacon Interval, etc.)?

It's an ISP provided Sagemcom F@st 3184. Here's some info it provides:

Standard Specification Compliant DOCSIS 3.0
Hardware Version 1.0
Software Version LxG_5.5.4_n_120103
Linux S/W Version 1.0.4-110517

The AP is wpa/wpa2 protected, MAC filtering and QoS not engaged, beacon interval unknown.

    Does another WiFi device tested with the AP have the same problem as the hardware you initially reported with?

No. All other devices connect properly.

    What is the distance of the WiFi device from AP? What is the number and type of obstructions between the two?

About four meters, a wall in between.

    Does the issue occur with different APs?

Yes, the device fails to connect to all APs when powered by the built in driver.

    Is it a regression (e.g. did the problem happen in a prior Ubuntu release)?

No. All releases since 11.04 (2.6.38) have had that problem.

    Does testing compat-wireless help?

No.

    Does testing the newest mainline kernel help?

No.

    Does ndiswrapper provide a WORKAROUND or solution?

Not tested.

    For Broadcom WiFi chipsets, does the proprietary Broadcom STA driver provide a WORKAROUND or solution?

No relevant.

    For Realtek WiFi chipsets, does the Realtek Backport PPA provide a WORKAROUND or solution?

Not relevant, the PPA has no rtl8192cu module.

[mikewhatever (mikewhatever)]

What follows is an update from Quantal daily (August 17 2012).

kernel version: Linux ubuntu 3.5.0-10-generic #10-Ubuntu SMP Mon Aug 13 15:25:53 UTC 2012 i686 i686 i686 GNU/Linux

I was trying to connect starting from about 22:40.

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

This is on Ubuntu 12.04.1 live USB, 32bit, kernel 3.2.0-29-generic-pae. I've reloaded the module with swenc=1 and debug=5 options (modprobe rtl8192cu swenc=1 debug=5), hopefully that will provide more usefull info.

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[mikewhatever (mikewhatever)]

apport information

[penalvch (penalvch)]

mikewhatever, could you please test the newest mainline kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc6-quantal/ ?

[mikewhatever (mikewhatever)]

I've tested the 3.6.2-030602 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6.2-quantal/. Bug confirmed, logs attached.

[penalvch (penalvch)]

Marking Triaged as newest mainline tested.

[David (nqk)]

Can anyone even confirm that the proprietary driver is running stable? Or even ndiswrapper?
Because I can't connect to a server anymore after a few minutes and have to reconnect or sometimes rmmod, tried both 8192cu and ndiswrapper.
Runs perfectly under Win7. Help!

[mikewhatever (mikewhatever)]

@David Sure, what do you think everyone has been using for the past 14 months or so? The driver from realtek.com works very well indeed - not even sure if it is proprietary or not. Anyway, this is a bug tracker here, if you need help and support, try the forum.

[Carterclan (carterclan)]

Can confirm bug still exists in latest stable kernel 3.7.0-7

[penalvch (penalvch)]

mikewhatever, 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 mainline kernels archive directory daily folder. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. 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. For example:
kernel-fixed-upstream-v3.8-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

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

As well, please remove the tag:
needs-upstream-testing

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

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[mikewhatever (mikewhatever)]

This bug is almost 16 months old, and has been tested and confirmed in kernels 3.0 - 3.7 across multiple distros, and, at least AFAIK, nothing has been done about it. I am not being bitter or demanding, this is life and kernel devs are busy and hard working people that have no time for little thing like this. Therefore, I suggest that from now on, we assume the bug is confirmed for all future kernel versions, untill stated otherwise.

I may (or may not) do more testing at my own leisure, and others affected are welcome to contribute. That said, it's pretty clear by now, that doing more testing doesn't help anyone.

Christopher, while your attention to this bug report has been remarkable, and I'd like to thank you for that, can you please stop copy/pasting those canned test requests. Their only goal is, apparently, to change the status to Incomplete, and hopefully, close it in 60 days.

[penalvch (penalvch)]

mikewhatever, regarding your comments :
>"This bug is almost 16 months old, and has been tested and confirmed in kernels 3.0 - 3.7"

While this is already known from reading the report, the newest mainline kernel available as noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/852190/comments/127 is v3.8-rc4. If the problem has not been tested in the newest mainline kernel available, as per Ubuntu Kernel Team policy, it would not be marked Status Triaged, or a point when a bug is in a state where a developer could begin working on it. For more on this, please see:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
https://wiki.ubuntu.com/Bugs/Status

As well, upstream will generally not be interested in your report, unless the newest mainline kernel has been tested with. If you would like to maximize the speed with which your bug is addressed, you are welcome to test the newest mainline kernel, as already requested. Could you please do this?

[mikewhatever (mikewhatever)]

Have tested the 32bit daily (Jan 18 2013) ISO of Raring. The kernel version it had was 3.8.0-1. Bug confirmed, as expected.

[TK (tkrishan)]

I can also confirm the bug still exists in kernel 3.8.0-2-generic.

The Realtek driver, 3.4.4_4749-2012/11/12 does not compile with this kernel either.

/tmp/rtl8192c$ sudo make
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/3.8.0-1-generic/build M=/tmp/rtl8192c modules
make[1]: Entering directory `/usr/src/linux-headers-3.8.0-1-generic'
  CC [M] /tmp/rtl8192c/core/rtw_cmd.o
In file included from /tmp/rtl8192c/core/rtw_cmd.c:23:0:
/tmp/rtl8192c/include/osdep_service.h: In function ‘thread_enter’:
/tmp/rtl8192c/include/osdep_service.h:575:2: error: implicit declaration of function ‘daemonize’ [-Werror=implicit-function-declaration]
In file included from /tmp/rtl8192c/include/drv_types.h:69:0,
                 from /tmp/rtl8192c/core/rtw_cmd.c:24:
/tmp/rtl8192c/include/rtw_recv.h: In function ‘rxmem_to_recvframe’:
/tmp/rtl8192c/include/rtw_recv.h:626:30: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
/tmp/rtl8192c/include/rtw_recv.h:626:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
cc1: some warnings being treated as errors
make[2]: *** [/tmp/rtl8192c/core/rtw_cmd.o] Error 1
make[1]: *** [_module_/tmp/rtl8192c] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-1-generic'
make: *** [modules] Error 2

[penalvch (penalvch)]

TK, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[TK (tkrishan)]

I am not reporting a new bug. I am confirming that the rtl8192cu module does not work in the 3.8.0-2-generic kernel.

I am also reporting that the workaround, compiling the manufacturer's driver no longer works.

Why is this bug marked as "incomplete"?

[mikewhatever (mikewhatever)]

That sucks! I guess the driver from realtek.com is too old for the 3.8 kernel.

Chistopher likes to mark my bug reports as "Incomplete", I am also unsure why.

[penalvch (penalvch)]

mikewhatever, regarding your comments :
>"Chistopher likes to mark my bug reports as "Incomplete", I am also unsure why."

For more on Status please see https://wiki.ubuntu.com/Bugs/Status . Despite this, could you please test http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc5-raring/ ?

[TK (tkrishan)]

I have tested Edimax EW-7811UN with v3.8-rc5-raring and the bug still exists as originally submitted.

The Realtek driver for the RTL8192 chip does not compile correctly so there is no workaround.

According to https://wiki.ubuntu.com/Bugs/Status this bug is confirmed.

Please do not ask for additional testing unless you have reason to believe the bug has been addressed and a fix submitted.

[mikewhatever (mikewhatever)]

Well, Christopher, this is just stupid. You ask to test v3.8-rc5-raring, TK does that and confirms that the bug exists, then you come back and change the status to Incomplete. What do you want now!? A jig dance!?

[penalvch (penalvch)]

mikewhatever, regarding your comments :
>"Well, Christopher, this is just stupid. You ask to test v3.8-rc5-raring, TK does that"

You were asked to test it, not TK.

>" and confirms that the bug exists, then you come back and change the status to Incomplete. What do you want now!? A jig dance!?"

Unfortunately, it appears neither you or TK read https://bugs.launchpad.net/ubuntu/+source/linux/+bug/852190/comments/132 . Nobody can verify anything about TK's hardware, because the instructions previously requested of TK have not been followed. Until this is done, what TK posts is not helpful, and is disregarded.

Despite this, could you please test http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc6-raring/ ?

[mIRROR (mirror-ftw)]

ApportVersion: 2.8-0ubuntu4
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lord-tyrant 2799 F.... rhythmbox
 /dev/snd/pcmC0D0p: lord-tyrant 2799 F...m rhythmbox
 /dev/snd/timer: lord-tyrant 2799 f.... rhythmbox
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=96ef24d4-4093-4fae-bdf2-9b7c0af4b6b0
InstallationDate: Installed on 2013-01-18 (24 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MachineType: MSI MS-7592
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-5-generic root=UUID=5e70f1cc-2559-4763-b726-7905964cff7c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-5-generic N/A
 linux-backports-modules-3.8.0-5-generic N/A
 linux-firmware 1.100
RfKill:

StagingDrivers: r8712u
Tags: raring running-unity staging
Uname: Linux 3.8.0-5-generic i686
UpgradeStatus: Upgraded to raring on 2013-02-11 (0 days ago)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V28.9
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G41M-P25 (MS-7592)
dmi.board.vendor: MSI
dmi.board.version: 6.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 6.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV28.9:bd02/23/2011:svnMSI:pnMS-7592:pvr6.0:rvnMSI:rnG41M-P25(MS-7592):rvr6.0:cvnMSI:ct3:cvr6.0:
dmi.product.name: MS-7592
dmi.product.version: 6.0
dmi.sys.vendor: MSI

[mIRROR (mirror-ftw)]

apport information

[mIRROR (mirror-ftw)]

apport information

[mIRROR (mirror-ftw)]

apport information

[mIRROR (mirror-ftw)]

apport information

[mIRROR (mirror-ftw)]

apport information

[mIRROR (mirror-ftw)]

apport information

[mIRROR (mirror-ftw)]

apport information

[mIRROR (mirror-ftw)]

apport information

[mIRROR (mirror-ftw)]

apport information

[mIRROR (mirror-ftw)]

apport information

[mIRROR (mirror-ftw)]

apport information

[mIRROR (mirror-ftw)]

apport information

[mIRROR (mirror-ftw)]

I'm a noob to this, I did my best
the first lines in wifisyslog repeat like forever
hope this helps

[mikewhatever (mikewhatever)]

I've switched to the development release to test - currently on Raring 32bit, kernel 3.8.0-12-generic.

The device is the same as before:

Bus 001 Device 002: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]

The same module:

rtl8192cu 66659 0
rtlwifi 69015 1 rtl8192cu
rtl8192c_common 47075 1 rtl8192cu
mac80211 526481 3 rtlwifi,rtl8192c_common,rtl8192cu
cfg80211 436177 2 mac80211,rtlwifi

...and as before, wireless doesn't work with the same sympthoms, as 18 months ago.

The only difference, I've added '-dd' to wpa_supplicant for higher verbosity:

~$ ps aux | grep wpa
root 896 0.0 0.1 6276 2288 ? Ss 07:39 0:00 /sbin/wpa_supplicant -B -P -dd /run/sendsigs.omit.d/wpasupplicant.pid -u -s -O /var/run/wpa_supplicant

 Tried connecting with 'rtl8192cu swenc=0' (the defalt), and 'rtl8192cu swenc=1'. Syslog attached.

PS: Not bothering to change the status, as Chistopher will change it back to Incomplete anyway.

[Casey Greene (casey-s-greene)]

I observe the exact same issue with the latest amd64 raring kernel.

[Olcay Korkmaz (olci)]

patch has been posted on bugzilla

https://bugzilla.kernel.org/show_bug.cgi?id=45241#c13

[mmalmeida (mmalmeida)]

This bug also affects me. I just bought a TP-Link Nano USB Adapter (TL-WN725N), which has the following chipset:

Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN

Same behaviour as described in original poster: after supplying a password, it will never be able to successfully connect.

Strangest thing is: sometimes when I disconnect the dongle from the USB slot and attach it again, it will successfully connect to the wifi network. However, if I then disconnect from that wifi (from the network-manager tray), it won't be able to connect again to any network (until I physically detach and attach the USB dongle again).

[mmalmeida (mmalmeida)]

Given Olcay's comment (#155), does this mean we can expect a working kernel in a near future?

What would an ETA be for this? Is 1 week viable?
Please let me know how I can help. I can test a patched kernel to confirm if the fix works. Just let me know how.

[Olcay Korkmaz (olci)]

The attached patch fixes the realtek (vendor) driver 3.4.4.4749-20121105 for the kernel v3.7 and v3.8 series but didn't test on 3.9 kernel

[mikewhatever (mikewhatever)]

@ocli Thanks for the heads up. I really hope the patch fixes the kernel tree driver, cause I am tired of building one from realtek.com.

@mmalmedia Two months sounds like a more reasonable time frame for a stable Ubuntu release.

[mikewhatever (mikewhatever)]

Building the patched 3.4.4.4749-20121105 driver on 13.04 (kernel 3.8) didn't work for me. It failed with error 2.

[Seth Forshee (sforshee)]

The patch from the Linux bugzilla is currently working its way to Ubuntu through the stable kernel releases. If that patch really does fix the issues then it should be fixed in the official Ubuntu kernels in 3-6 weeks, and sooner than that in raring.

For now I've done a test build of the raring kernel with that patch. Please give it a try let me know whether or not it fixes the issues.

http://people.canonical.com/~sforshee/lp852190/linux-3.8.0-15.25~lp852190v201303291747/

[mmalmeida (mmalmeida)]

Seth - with your kernel I've successfully turned wireless on and off, connected and disconnected to a network successfully, so it seems to be ok.

I do have another problem - I have 2 wifi networks and, even though I can connect to both, in one of them I don't have internet or access to the LAN; I can ping my machine (192.168.1.115) but not the router (192.168.1.1). I don't have problems with any other device connected to it. Could this be related?

I have tried with both automatic DHCP and manual (with router as DNS address).

[mmalmeida (mmalmeida)]

Attached is the syslog, ifconfig and a ping test on the troublesome wifi network.

[mikewhatever (mikewhatever)]

@Seth Thanks for the patched kernel. It seems to work ok here.

[Seth Forshee (sforshee)]

mmalmeida: Being able to ping the machine's own IP address doesn't prove anything. You're obviously able to communicate with the AP, to some degree at least, since you can associate and DHCP works. I'd suggest trying again when an official kernel with the fix is released, and if you see problems there then open a new bug.

[Omega (atrauzzi)]

Running Raring at kernel version 3.8.0-19-generic, 64bit. Still not working. When can we expect this to be fixed?

[mikewhatever (mikewhatever)]

@Omega Hopefully sooner then later, but keep your expectations reasonable. With only 40 affected users, I can imagine, this bug is not too high on the developers' priority list.

[Omega (atrauzzi)]

@Mikewhatever - There are only 40 people who have logged onto Launchpad and complained about it.

I can guarantee you far more than 40 people are actually affected by this. Most of which just throw their hands up and go on to speak ill of Ubuntu and Linux.

Your response - while seemingly rational - abandons all intuition.

[mikewhatever (mikewhatever)]

There is a slew of the 8192cu related changes with the 3.2.0-48-generic update for Precise, and that seems to provide a fix, and a happy end for this bug report. I've un-blacklisted the module, rebooted, and was glad to find the wireless connection established.

Here is the info summary, as shown by the update manager:

  * rtlwifi: rtl8192cu: Fix schedule while atomic bug splat
    - LP: #1164646
--
  * rtlwifi: rtl8192cu: Fix problem that prevents reassociation
    - LP: #1164646
--
  * rtlwifi: rtl8192cu: Fix NULL dereference BUG when using new_id
    - LP: #1150557
  * rtlwifi: rtl8192cu: Add new USB ID
    - LP: #1150557
--
  * rtlwifi: rtl8192cu: Add new USB ID
    - LP: #1087865
--
  * rtlwifi: rtl8192cu: Change buffer allocation for synchronous reads
    - LP: #1039087
--
  * rtlwifi: rtl8192cu: New USB IDs
    - LP: #1024020
--
  * rtlwifi: rtl8192ce: rtl8192cu: rtl8192de: Fix low-gain setting when
    scanning

Thanks everyone for participating.

[Ming Lei (tom-leiming)]

On Fri, Jun 14, 2013 at 2:49 PM, mikewhatever <email address hidden> wrote:
> There is a slew of the 8192cu related changes with the 3.2.0-48-generic
> update for Precise, and that seems to provide a fix, and a happy end for
> this bug report. I've un-blacklisted the module, rebooted, and was glad
> to find the wireless connection established.
>
> Here is the info summary, as shown by the update manager:

In fact, from the below upstream discussion, 8192cu driver should have
some bug about transfer buffer:

       http://marc.info/?t=137121757300006&r=1&w=2

Thanks,

[Antti Haapala (ztane)]

So when is the fix landing to raring, or is it supposed to be there already? Because I have a fresh Edimax EW-7811Un, 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux, and I certainly couldn't connect into any kind of pw protected net; open wifi seemed to work for like 3 minutes, after which the connection was severed and reconnection not possible anymore.

I also tried the workaround (compiling the 8192cu driver by realtec), and managed to get them compile with the latest patch provided in the comments modprobed it in, but while it seemed to work for a while, then it dropped connection too and had dmesg full of strange stuff, so I disconnected the adapter and *boom* got a kernel panic...

[Jedna Dvatři (spiro-multimax+launchpad)]

It seems fixed in raring, kernel 3.8.0-26-generic. I'm writing from a WPA-protected network, using the rtl8192cu driver for this dongle.

[Balinares (balinares)]

It doesn't work here in Saucy, kernel 3.11.0-12-generic. The hardware (Belkin N300 USB dongle, id F7D2102, using chipset Realtek RTL8192CU) is recognized properly and the rtl8192cu module loads fine. However, the hardware fails to see any nearby AP. It worked fine in Raring with Timothy Phillips' patched driver (https://code.google.com/p/realtek-8188cus-wireless-drivers-3444749-ubuntu-1304/), which unfortunately isn't compatible with the 3.11 kernel used in Saucy.

[penalvch (penalvch)]

Antti Haapala / Balinares, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[Aaron Peromsik (aperomsik)]

With the recent kernel update this started working for me. Looks like it is using the packaged firmware, not the updated one, which might mean the updated one is not needed for this device.

$ uname -a
Linux kermit 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
$ lsusb
Bus 001 Device 008: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]

[ 65.908605] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin

-rw-r--r-- 1 root root 16014 Apr 25 2013 rtl8192cufw.bin
-rw-r--r-- 1 root root 16116 Oct 27 15:56 rtl8192cufw_TMSC.bin

[senpaji (senthil300794)]

i am not able to use tp link 723 usb wifi adapter driver for linux

[mikewhatever (mikewhatever)]

Unfortunately, despite the fixes, it doesn't work very well at all. If you have time to wait a couple of more years, may be the driver will get there, and may be not.
Meanwhile, Realtek has an updated driver for us, good for kernel 3.9:
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=48&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true#RTL8192CU
There is also a pached driver to install on 3.8:
https://code.google.com/p/realtek-8188cus-wireless-drivers-3444749-ubuntu-1304/

[penalvch (penalvch)]

mikewhatever, thank you for your comment. Could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please just make a comment to this.

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. 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. For example:
kernel-fixed-upstream-v3.13-rc7

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

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

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[mikewhatever (mikewhatever)]

I may (or may not) do more testing at my own leisure, and others affected are welcome to contribute. That said, it's pretty clear by now, that doing more testing doesn't help anyone.

Christopher, while your attention to this bug report has been remarkable, and I'd like to thank you for that, can you please stop copy/pasting those canned test requests. Their only goal is, apparently, to change the status to Incomplete, and hopefully, close it in 60 days.

[mmalmeida (mmalmeida)]

I "solved" it by buying another usb wifi dongle. I got tired of the hassle and time taken to test, compile, etc.

[penalvch (penalvch)]

mikewhatever, thank you for your comment.

>"...it's pretty clear by now, that doing more testing doesn't help anyone."

This would be anything but clear as a developer has worked on addressing your issue before, as per your now closed bug report https://bugzilla.kernel.org/show_bug.cgi?id=45241 . Unfortunately, it wasn't a fix all.

>"...can you please stop copy/pasting those canned test requests."

Please review carefully https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

>"Their only goal is, apparently, to change the status to Incomplete, and hopefully, close it in 60 days."

In order to mark this Triaged, the latest upstream kernel would need to be tested -> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/ . If the problem is reproducible, then upstream would be re-engaged (as they will immediately ask you have you tested upstream 3.13+ if you do otherwise).

Thank you for your understanding.

[Peter Schüller (schueller-p)]

I have the same issue with a WN8200ND adapter (same driver): i cannot connect to access points with the kernel module shipped in the newest 14.4 build

I didn't find any reference to the following repository which I used to fix the issue partially:
https://github.com/pvaret/rtl8192cu-fixes

Status is as follows:
* before using the above modified driver, my 14.4 kernel (3.13.0-19-generic 64 bit) could not connect to any accesspoint i tried
* after using this driver i can connect to my cellphone's access point but not to another accesspoint where i can connect with my laptop nicely.

If I compare both accesspoints - the one i can connect and the one I cannot - the differences start after

"link to Broadcom AP"

the accesspoint that works:
"OnAuthCclient
network.SupportedRates[0] = ......
...
many more such lines

the accesspoints that does not work:
"link_timer_hdl: auth timeout and try again
(4 times)
report_join_res(-1)
"

[Peter Schüller (schueller-p)]

Here is another guy having the same problem
http://tinymicros.com/wiki/TP-Link_WN8200ND_On_BeagleBone_Black

and I noticed an additional differing line that could be relevant:

"issue_deauth_ex(wlan0) to <mac address>, ch:13, 5/5 in 496 ms"

i did not find anything useful while googling this line

[penalvch (penalvch)]

Peter Schüller, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Luke (lukebenes)]

I have the same hardware as described in the first comment, Edimax EW-7811Un.

With 3.11.0-12 kernel in Saucy, I cannot connect to my WRT54G access point.

If I use the drivers from: https://github.com/pvaret/rtl8192cu-fixes
my Wireless card works perfectly

With Linux kernel 3.13 in a Trusty Tahr beta install, I can sometimes connect to my network, but the network frequently disappears. The only way to connect is to remove the USB device or reboot the computer.

kernel.org Bug 45241 was closed, but the kernel 3.13's driver does not work as well as pvaret's fixes with 3.11. Does Ubuntu's 3.13 contain Larry Finger's patch? If so, more work still needs to be done to fix the driver in the kernel. Should I create a new bug report or reopen 45241?

Please let me know if there is anything else I can provide to be of assistance.

[penalvch (penalvch)]

Luke, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[mikewhatever (mikewhatever)]

Oh dear, how many bug reports do we need?
Christopher, you are being a real PITA with constant canned copy/paste statements. I am sure your energy is urgently required elsewhere. Can you just go away.

[penalvch (penalvch)]

mikewhatever, this is still pending https://bugs.launchpad.net/ubuntu/+source/linux/+bug/852190/comments/183 . For your convenience, the latest kernel is now http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc7-utopic/ .

Despite this, you acting rude and obnoxious, and actively choosing not to read or understanding anything regarding how triaging works in Ubuntu despite being provided a plethora of information it on multiple occasions, doesn't get your bug fixed any faster. If anything, it, and the fact you actively choose not to do the minimum requirement testing to get developers interested in your bug report, strongly delays this being resolved for you.

The better question you would want to ask is, why did I file a bug report when I'm not willing to do the bare minimum to get it resolved? And to top it off, then mouth off to the very people who advise you on what it takes to get it resolved?

[Rolf Leggewie (r0lf)]

After three years, I think people can judge for themselves who is being rude and especially who is being obnoxious.

Personally, I consider it pretty rude to make people do silly busywork and jump through hoops simply for the sake of protocol without EVER making any real progress. Being rude in words is not OK. Being rude in action is much worse in my book.

That being said, I think it is clear that this ticket needs to be addressed upstream. It should be pretty clear by now that Canonical won't expend any effort to fix this and kernel work seems not to be an area of Ubuntu community effort.

[Rolf Leggewie (r0lf)]

upstream work best sponsored by the hardware maker

[ppjdee (cheesecake-monsta)]

i had hopes this would be fixed by 13.10. still an issue though on 14.04.

[penalvch (penalvch)]

mikewhatever, as per https://bugzilla.kernel.org/show_bug.cgi?id=45241#c14 this is resolved for you in Precise. Is this also the case in Trusty+?

[mikewhatever (mikewhatever)]

Well, I am done here. Hope it gets fixed some day, but this bug report has outlived itself.