Bug 6031 - RTL8192CU wireless device doesn't connect using drakx tools
Summary: RTL8192CU wireless device doesn't connect using drakx tools
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Olivier Blin
QA Contact:
URL:
Whiteboard: MGA3TOO
Keywords: UPSTREAM
: 8754 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-05-23 03:34 CEST by Thomas Andrews
Modified: 2018-04-15 20:25 CEST (History)
8 users (show)

See Also:
Source RPM: kernel, drakx-net
CVE:
Status comment:


Attachments

Description Thomas Andrews 2012-05-23 03:34:09 CEST
My Encore USB wireless N adapter, model ENUWI-1XN45, uses the Realtec rtl8192CU chip, and will not connect most of the time when using the drakx tools on Mageia 2. It worked perfectly with Mageia 1. My computer is a stock Dell Dimension E310, with 2GB RAM. Mageia version is the RC, which after updates is now labeled simply Mageia 2.

The firmware has been installed, and drakconnect can see both the SSIDs in my area, including my router. I can configure a connection to my router, but it will not connect from drakconnect. On the first reboot, though, it connects just fine. But that is the last time it will do so. 

On subsequent boots, the connection fails. Checking the interface, I may see both SSIDs, or I may see just my router. If I "refresh," they may stay, one may disappear, or both may go. If I see both and attempt to connect to my router, it fails. If I then "refresh," all SSIDs disappear.

A workaround is to use the networkmanager plasma applet, with the network and network auth services not running at boot. While it's a little soon after trying that to be sure, so far that connection has come up every time with this device.
Manuel Hiebel 2012-05-24 19:25:11 CEST

Component: Release (media or process) => RPM Packages
Source RPM: (none) => drakx-net

Manuel Hiebel 2012-05-24 19:35:59 CEST

Assignee: bugsquad => mageia

Comment 1 Thomas Andrews 2012-06-03 22:22:21 CEST
Network Manager has proven to be not so reliable with this device, either. The connection has either "dropped" or failed to connect on boot three times in the last four days. A reboot seems to be the only way to get the connection back when this happens. I don't recall this happening even once with Mageia 1.

Next I will try using a USB extension so I can move the device around a little, and see if I can find a position where it's more stable.
Comment 2 Marja Van Waes 2012-07-06 15:04:49 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 3 Thomas Andrews 2012-07-06 16:08:07 CEST
Sorry I didn't get back with an update. But then, nobody asked for one before this. It seemed as if the bug was pretty much being ignored.

Using an extension to move the antenna to a better location seems to have eliminated the problems with using networkmanager to make the connection. Connections have been stable since I did this. 

However, it did nothing to help with the drakx tools. A new trial resulted in the same symptoms. 

Since getting a stable connection, I went on to other things. This is my secondary computer, and while I don't use it regularly I have used it several times over the last few months. 

But, I have not used the drakx tools with this computer since March. If there has been an update since then, I haven't tried it.
Comment 4 Samuel Iglesias Gonsálvez 2012-12-13 16:32:52 CET
There have been some similar problems with that driver:

https://bugzilla.redhat.com/show_bug.cgi?id=866786
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/869530
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/852190
https://bugs.launchpad.net/ubuntu/+source/linux-backports-modules-3.0.0/+bug/862684

Luckily, it is working for you :-)

Be aware of these problems if it happens to you again with a newer kernel. Instead of using the driver that it's in mainstream kernel, the driver from Realtek website fixes these problems.

CC: (none) => samuel_ig

Comment 5 René Lagoni Neukirch 2013-06-14 17:21:11 CEST
Pls. se my supplemnt under Bug 8754.

Forgot to state:

M3 is _x64, and the LAN card is an RTL8192cu labelled 802.11n WLAN adapter in Mageia Control Center.

CC: (none) => rene

Comment 6 Manuel Hiebel 2013-10-22 12:11:21 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 7 René Lagoni Neukirch 2013-10-22 12:23:29 CEST
Hi Manuel,

The problem is still present in M4 Cauldron _x64.
I still havn't got my 8192cu WLAN adapter connected ...
The fix may be to adapt the newest 8192cu (cu !) driver from RealTech ?

Can someone make sure, that the bugreport continues to the M4 platform also ?

Thx in advance/René
-------------------------------------------------------

(In reply to Manuel Hiebel from comment #6)
> This message is a reminder that Mageia 2 is nearing its end of life.
> Approximately one month from now Mageia will stop maintaining and issuing
> updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL)
> if it remains open with a Mageia 'version' of '2'.
> 
> Package Maintainer: If you wish for this bug to remain open because you plan
> to fix it in a currently maintained version, simply change the 'version' to
> a later Mageia version prior to Mageia 2's end of life.
> 
> Bug Reporter: Thank you for reporting this issue and we are sorry that we
> may not be able to fix it before Mageia 2 is end of life.  If you would
> still like to see this bug fixed and are able to reproduce it against a
> later version of Mageia, you are encouraged to click on "Version" and change
> it against that version of Mageia.
> 
> Although we aim to fix as many bugs as possible during every release's
> lifetime, sometimes those efforts are overtaken by events. Often a more
> recent Mageia release includes newer upstream software that fixes bugs or
> makes them obsolete.
> 
> -- 
> The Mageia Bugsquad

Hardware: i586 => x86_64
Version: 2 => Cauldron

Comment 8 Atilla ÖNTAŞ 2013-11-29 15:33:24 CET
*** Bug 8754 has been marked as a duplicate of this bug. ***
Atilla ÖNTAŞ 2013-11-29 15:35:51 CET

Keywords: (none) => UPSTREAM
CC: (none) => tarakbumba
Whiteboard: (none) => MGA3TOO

Comment 9 Thierry Vignaud 2013-12-09 11:18:12 CET
Reported fixed in Cauldron in bug #11929

CC: (none) => thierry.vignaud

Comment 10 Atilla ÖNTAŞ 2013-12-09 11:42:51 CET
(In reply to Thierry Vignaud from comment #9)
Then should we push a update for Mga3 and see if it is fixed?
Comment 11 René Lagoni Neukirch 2013-12-11 14:32:43 CET
Unfortunately, I am back to square one.
My 8192cu will (agin) not connect whatsoever.
Albeit it has been working for a short while - pls see bug 11929

My humble guess is, that something(s) must have changed with the updates of the drakx-xxx-tools ???

Status: NEW => REOPENED

Comment 12 René Lagoni Neukirch 2013-12-11 15:41:59 CET
(In reply to René Lagoni Neukirch from comment #11)
> Unfortunately, I am back to square one.
> My 8192cu will (agin) not connect whatsoever.
> Albeit it has been working for a short while - pls see bug 11929
> 
> My humble guess is, that something(s) must have changed with the updates of
> the drakx-xxx-tools ???

This is really very, very strange - I rebooted for the 10'th time or so - and now the wireless connection works again.
I havn't touched anything at all, be it router, SW updates, configuring or anything else.

What on earth is going on ???
Comment 13 Thierry Vignaud 2013-12-12 09:55:07 CET
You should look at your logs (journalctl), there might be differences in kernel outputs

CC: (none) => tmb
Source RPM: drakx-net => kernel, drakx-net

Comment 14 René Lagoni Neukirch 2013-12-16 12:40:14 CET
Programmet "drakroam" er gået ned med den følgende fejl: 

  undefined value for mandatory argument 'is_active' encountered at /usr/lib/libDrakX/interactive/gtk.pm line 400. 
  Perl's trace: 
  standalone::bug_handler() called from /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm:304 
  Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1500 
  mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:748 
  ugtk3::main() called from /usr/lib/libDrakX/network/drakroam.pm:133 
  network::drakroam::main() called from /usr/libexec/drakroam:30 

Used theme: oxygen-gtk 

For at indsende en fejlrapport klik da på rapport-knappen. 
Dette vil åbne et vindue i en netlæser på Bugzilla 
 hvor du vil finde en formular der kan udfyldes. Informationen vist ovenfor vil blive overført til den server. 
I din rapport ville det være meget nyttigt at medtage uddata fra den følgende kommando: 'lspcidrake -v'


Tried to connect my wireless 8192CU after having lost connection. 
Maybe somehow connected to bug 6031 ??? 



bash-4.2$ lspcidrake -v
r8169           : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:10ec device:8168 subv:1462 subd:7797) (rev: 06)
snd_hda_intel   : NVIDIA Corporation|GK107 HDMI Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:10de device:0e1b subv:1462 subd:2802) (rev: a1)
Card:NVIDIA GeForce 400 series and later: NVIDIA Corporation|GK107 [GeForce GTX 650] [DISPLAY_VGA] (vendor:10de device:0fc6 subv:1462 subd:2802) (rev: a1)
i2c_i801        : Intel Corporation|7 Series/C210 Series Chipset Family SMBus Controller [SERIAL_SMBUS] (vendor:8086 device:1e22 subv:1462 subd:7797) (rev: 04)
unknown         : Intel Corporation|7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] [STORAGE_SATA] (vendor:8086 device:1e02 subv:1462 subd:7797) (rev: 04)
lpc_ich         : Intel Corporation|B75 Express Chipset LPC Controller [BRIDGE_ISA] (vendor:8086 device:1e49 subv:1462 subd:7797) (rev: 04)
unknown         : Intel Corporation|82801 PCI Bridge [BRIDGE_PCI] (vendor:8086 device:244e) (rev: a4)
ehci_pci        : Intel Corporation|7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [SERIAL_USB] (vendor:8086 device:1e26 subv:1462 subd:7797) (rev: 04)
shpchp          : Intel Corporation|7 Series/C210 Series Chipset Family PCI Express Root Port 5 [BRIDGE_PCI] (vendor:8086 device:1e18) (rev: c4)
shpchp          : Intel Corporation|7 Series/C210 Series Chipset Family PCI Express Root Port 1 [BRIDGE_PCI] (vendor:8086 device:1e10) (rev: c4)
snd_hda_intel   : Intel Corporation|7 Series/C210 Series Chipset Family High Definition Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:8086 device:1e20 subv:1462 subd:7797) (rev: 04)
ehci_pci        : Intel Corporation|7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [SERIAL_USB] (vendor:8086 device:1e2d subv:1462 subd:7797) (rev: 04)
unknown         : Intel Corporation|7 Series/C210 Series Chipset Family MEI Controller #1 [COMMUNICATION_OTHER] (vendor:8086 device:1e3a subv:1462 subd:7797) (rev: 04)
xhci_hcd        : Intel Corporation|7 Series/C210 Series Chipset Family USB xHCI Host Controller [SERIAL_USB] (vendor:8086 device:1e31 subv:1462 subd:7797) (rev: 04)
shpchp          : Intel Corporation|Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [BRIDGE_PCI] (vendor:8086 device:0151) (rev: 09)
unknown         : Intel Corporation|Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [BRIDGE_HOST] (vendor:8086 device:0150 subv:1462 subd:7797) (rev: 09)
hub             : Linux 3.12.5-server-1.mga4 xhci_hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0003)
hub             : Linux 3.12.5-server-1.mga4 xhci_hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub             : Linux 3.12.5-server-1.mga4 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub             : Intel Corp.|Integrated Rate Matching Hub [Hub|Unused|Full speed (or root) hub] (vendor:8087 device:0024)
hub             : Linux 3.12.5-server-1.mga4 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub             : Intel Corp.|Integrated Rate Matching Hub [Hub|Unused|Full speed (or root) hub] (vendor:8087 device:0024)
rtl8192cu       : Realtek|802.11n WLAN Adapter (vendor:0bda device:8176)
uvcvideo        : Logitech, Inc.|Webcam Pro 9000 [Video|Video Control] (vendor:046d device:0809)
usbhid          : Logitech|USB Receiver [Human Interface Device|Boot Interface Subclass|Mouse] (vendor:046d device:c52f)
usb_storage     : Generic|USB2.0-CRW [Mass Storage|SCSI|Bulk-Only] (vendor:0bda device:0184)
usbhid          : Logitech|Logitech USB Keyboard [Human Interface Device|Boot Interface Subclass|Keyboard] (vendor:046d device:c315)
hid_generic     : Logitech Logitech USB Keyboard
hid_generic     : Logitech USB Receiver
hid_generic     : Logitech USB Receiver
bash-4.2$
Comment 15 Mageia Robot 2013-12-16 13:36:38 CET
commit 6cc2bcd4cf9910461409a57f1429aabeddf51676
Author: Thierry Vignaud <thierry.vignaud@...>
Date:   Mon Dec 16 13:21:11 2013 +0100

    fix a drakx crash (mga#6031)
---
 Commit Link:
   http://gitweb.mageia.org/software/drakx/commit/?id=6cc2bcd4cf9910461409a57f1429aabeddf51676
Comment 16 Sébastien GUERIN 2015-01-12 23:26:36 CET
rtl8192cu firmware provided by default is buggy. Same problem as Ubuntu, see here :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1365844

A fix has been developed for Ubuntu : 
https://github.com/pvaret/rtl8192cu-fixes


This is how to install it in Mageia 4 : 

- Install following packages : kernel-desktop-devel-latest, dkms, git.
- Reboot to enable dkms (mandatory).

- Login as root and change directory to /usr/src :
# cd /usr/src/

- Download latest version of driver fix :
# git clone https://github.com/pvaret/rtl8192cu-fixes.git

- Retrieve driver version in dkms.conf (1.9 for me) :
# cat ./rtl8192cu-fixes/dkms.conf

- Rename driver folder with appending version number :
# mv rtl8192cu-fixes/ rtl8192cu-fixes-1.9/

- Add, build and install new driver :
# dkms add -m rtl8192cu-fixes -v 1.9
# dkms build -m rtl8192cu-fixes -v 1.9
# dkms install -m rtl8192cu-fixes -v 1.9
# depmod -a
# cp ./rtl8192cu-fixes-1.9/blacklist-native-rtl8192.conf /etc/modprobe.d/

- Reboot

Warning: the first boot with USB wifi key plugged-in can be very very long (several minutes), so please be patient ;-)

CC: (none) => sebastien.guerin.news

Comment 17 René Lagoni Neukirch 2015-01-13 05:47:13 CET
Interesing News - thanks a lot, also for The install guide. Do you think it will work for the kernel-server-devel-latest as well ?
Anyway I'll give it at try soon ...
Thanks again !
/René
Comment 18 René Lagoni Neukirch 2015-01-13 17:32:31 CET
CONFIRMED - it works just fine for me.

bash-4.2$ uname -a
Linux rln 3.14.27-server-1.mga4 #1 SMP Sun Dec 21 22:58:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

GREAT - my speed has doubled (approx).
------------------------------------------------------------------------------
(In reply to René Lagoni Neukirch from comment #17)
> Interesing News - thanks a lot, also for The install guide. Do you think it
> will work for the kernel-server-devel-latest as well ?
> Anyway I'll give it at try soon ...
> Thanks again !
> /René
Comment 19 René Lagoni Neukirch 2016-01-03 08:52:04 CET
REGRESSION - 8192cu

As before I unfortunately experience yet another regression when using kernel 4.1.13-server-2.mga5 #1 SMP.

I have several times cleaned all I could think of, an I have then done the following:

# cd /usr/src/
# git clone https://github.com/pvaret/rtl8192cu-fixes.git
# cat ./rtl8192cu-fixes/dkms.conf
# mv rtl8192cu-fixes/ rtl8192cu-fixes-1.10
# dkms add -m rtl8192cu-fixes -v 1.10
# dkms build -m rtl8192cu-fixes -v 1.10
# dkms install -m rtl8192cu-fixes -v 1.10
# depmod -a
# cp ./rtl8192cu-fixes-1.10/blacklist-native-rtl8192.conf /etc/modprobe.d/

then reboot - but to no avail every time.
The connection simply won't operate.

I use now utilize a fallback on my WGT111 dongle - any help ?

/René
Comment 20 René Lagoni Neukirch 2016-01-03 09:13:13 CET
Sorry, I forgot to add:

There are severe problems in connecting to the network.
When it sometimes happens the upload is around 15 KB !) per minute, and the downlaod is around 1 KB (!) - yes, KILO not MEGA - PER MINUTE.
I have tried to configure with(out) static IP - no difference.
Before changing to the current kernel, and some generations back it has been working fine.

(In reply to René Lagoni Neukirch from comment #19)
> REGRESSION - 8192cu
> 
> As before I unfortunately experience yet another regression when using
> kernel 4.1.13-server-2.mga5 #1 SMP.
> 
> I have several times cleaned all I could think of, an I have then done the
> following:
> 
> # cd /usr/src/
> # git clone https://github.com/pvaret/rtl8192cu-fixes.git
> # cat ./rtl8192cu-fixes/dkms.conf
> # mv rtl8192cu-fixes/ rtl8192cu-fixes-1.10
> # dkms add -m rtl8192cu-fixes -v 1.10
> # dkms build -m rtl8192cu-fixes -v 1.10
> # dkms install -m rtl8192cu-fixes -v 1.10
> # depmod -a
> # cp ./rtl8192cu-fixes-1.10/blacklist-native-rtl8192.conf /etc/modprobe.d/
> 
> then reboot - but to no avail every time.
> The connection simply won't operate.
> 
> I use now utilize a fallback on my WGT111 dongle - any help ?
> 
> /René

Version: Cauldron => 5

Comment 21 Marja Van Waes 2018-04-15 19:00:02 CEST
@ all who were affected by this bug,

Thank you for having taken the needed time to report this issue and add comments!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Comment 22 Thomas Andrews 2018-04-15 20:25:14 CEST
Sometime in the life of MGA5, I tried this device again, and it was working perfectly, what little I used it. 

Later, the machine began to be used all the time by a relative. The device would still work the vast majority of the time, but once in a while would fail to work at all on boot, as if the firmware hadn't been loaded. I could work with it and get it started again, after which it would again work for 2-3 weeks or so.

Since upgrading that computer to 64-bit Mageia 6 Plasma, there have been no more failures of this device.

So, I am marking this as resolved.

Resolution: (none) => FIXED
Status: REOPENED => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.