Bug 42815
| Summary: | r8712u with RTL8191S WLAN Adapter: Connection lasts but no traffic for several seconds | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Adrian Batzill (linux) |
| Component: | network-wireless | Assignee: | Larry Finger (Larry.Finger) |
| Status: | RESOLVED CODE_FIX | ||
| Severity: | normal | CC: | florian, Larry.Finger, linux, linville |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 3.2.5 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
Patch to allow vendor driver v2.6.6.0.20110401 to compile and run
dmesg photo Patch to fix locking problem when using wicd Patch to fix formware load when using wicd |
||
|
Description
Adrian Batzill
2012-02-23 20:18:56 UTC
Not sure if Larry is interested in this or not -- let's ask... :-) Okay, I guess I was wrong on the Ping-thing. It just blocked again while the ping was running. I also tried to compile the driver from the realtek website directly (I only found a driver for RTL8191SU there, while lsusb says RTL8191S. But I think that's the same then...) However, that driver doesn't even compile and throws a lot of errors like event_tasklet and xmit_tasklet having an uncomplete type and a failing include to "linux/smp_lock.h". Maybe not compatible with recent Linux kernels(?). The driver on the Realtek Web site is not compatible with later kernels. If you want to try it, please post the version you downloaded, and the kernel you wish to use. I'll post the corresponding patch. The vendor driver uses features removed from the kernel, and most do not work with 64-bit systems. I have two different units with RTL8191SU chips, and neither shows this problem. Hey, 1: Can you confirm that my adapter is actually the same as the SU version? 2: Version 2.6.6.0.20110401 with kernel 3.2.5 3: Well, I would only try the realtek driver if it would help locating the probelm. Do you think it's even worth debugging this? If not, i will just give it back to the vendor as it doesn't work as advertised and go back to my old ralink adaptor (and write a bug report for that one as it only works correctly with patched vendor drivers and is buggy in the kernel, too). Created attachment 72471 [details]
Patch to allow vendor driver v2.6.6.0.20110401 to compile and run
Whether you want to use this patch is up to you. Your USB ID matches one the two different units that I have. As far as I know, all the chips with the same ID are the same.
Testing with the vendor driver would have some value for me. As I cannot duplicate your result, it would be useful to know if this is something that Realtek fixed. The kernel driver (kernel V3.2 and later) is based on the 8/31/10 version. I have not looked into what is different between 8/31/10 and 4/1/11 versions.
One other question - what is the Digitus model number? It's this little guy: http://www.digitus.info/en/products/network/300mbps-wireless-lan-series/wireless-300n-usb-adapter-dn-7053-2/ I will try the realtek driver tomorrow and report back. I will also do some tests on Windows to make sure it's not a hardware issue. Oh well, that diddn't quite work out :/ When I loaded the driver and looked at network manager, it found several networks, but all of them were displayed with a very low signal strength (0%?). When trying to connect, the driver crashed and the kernel hung up (had to SysRq to get out). Managed to get a dmesg right before the complete hangup. Created attachment 72477 [details]
dmesg photo
File was cleared during reboot. Photograph only :/
I think this was with the vendor driver. Is that correct? If so, I'm not that interested in fixing it. This morning, I found a bug that would affect kernel 3.2.5. A work-around will be posted. Created attachment 72478 [details]
Patch to fix locking problem when using wicd
The problem does not appear to affect NetworkManager, but it fails with wicd. This patch is needed for 3.2.0 and later.
Created attachment 72479 [details]
Patch to fix formware load when using wicd
This patch also fixes a problem that fails regularly with wicd and only infrequently with NetworkManager. It applies to kernel 3.2.6 and 3.3-rc4 and later.
Hey, The Crash only exists in the vendor driver. So don't mind fixing it, I'm not interested in using that driver anyway (it was just for testing). I will update to kernel version 3.2.7 now and apply your patches and see what happens. The new kernel with both of your patches is now running for approx. two hour and I had no problem for now (at least I couldn't see one). I hope that fixed it :) I'm now on 3.2.7 with both of your patches. I had to include the shorter one by myself as it conflicted with your other file (both do something at around the same line in the source). What also changed, is that I'm now getting a _lot_ more of the message from my first post in dmesg (sometimes 5 per minute, sometimes none for 5 minutes but a lot more on average). I will write again if the problem comes back. btw: I noticed that this driver is in staging for a long time already. Will this ever be moved to stable? Or will there be a replacement some day? Or will it just reside in staging until the devices are outdated enough so nobody uses them any more? Just curious... The driver is generally as stable as many drivers in the drivers/net/wireless tree, but is still in staging because it does not use mac80211. Doing that rewrite is on my TODO list, but with low priority. Is it OK if I add a Tested-by line for you in the official patch? Sure. Tested-by: Adrian Batzill <agib@gmx.de> A patch referencing this bug report has been merged in Linux v3.4-rc1: commit 9f4bc8cf3fe750ed093856a5f5d41c11cc12ad22 Author: Larry Finger <Larry.Finger@lwfinger.net> Date: Sat Feb 25 18:10:20 2012 -0600 staging: r8712u: Fix regression introduced by commit a5ee652 |