Package Details: 8192cu-dkms v4.0.2_9000-24

Git Clone URL: https://aur.archlinux.org/8192cu-dkms.git (read-only, click to copy)
Package Base: 8192cu-dkms
Description: Driver for Realtek RTL8188CUS (8188C, 8192C) chipset wireless cards
Upstream URL: http://www.realtek.com.tw/
Licenses: GPL
Conflicts: 8192cu, dkms-8192cu, rt8192cu
Replaces: dkms-8192cu
Submitter: runnytu
Maintainer: runnytu
Last Packager: runnytu
Votes: 102
Popularity: 0.000024
First Submitted: 2014-05-07 21:01 (UTC)
Last Updated: 2024-06-01 21:12 (UTC)

Dependencies (2)

Required by (0)

Sources (3)

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 25 Next › Last »

mrueg commented on 2016-02-07 21:31 (UTC)

I updated to kernel 4.4 (specifically linux-4.4.1-2) today and the module stopped working. It works after downgrading to 4.3.3-2. I also tried to uninstall it, reboot, then reinstall it as sourc7 suggested, which didn't help. What should I do to get more information on what went wrong?

BorbMizzet commented on 2016-01-10 09:44 (UTC)

I'm running kernel 4.3.3-2 on an arch installation from the 1-1-2016 install iso. I installed this package due to frequent disconnects with the kernel drivers, and now I get three errors to either stdout or stderr (the same one thrice at once) either once I plug in the device or on the login terminal at boot if the device is connected. The errors go away when I uninstall the package and reappear when I reinstall the package. Also, unlike the kernel drivers, Network Manager no longer connects at boot nor will it work manually, not even sensing the SSID at all except like 1 out of 10 times when I re-plug in the dongle or boot, the errors dont appear and it works fine (noticeable improvements in connection speed when that happens though :-D). I have a TP-LINK TL-WN822N rev.3. Here is what happens when I boot. The errors also appear if I plug in the device post-login: [Terminal Text] Arch Linux 4.3.3-2-ARCH (tty1) My-PC login: [ 4.044568] xhci_hcd 0000:05:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 4.109525] xhci_hcd 0000:05:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 4.113901] xhci_hcd 0000:05:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 _ [/Terminal Text] any ideas?

mehine2 commented on 2016-01-04 18:15 (UTC)

Tnx. Works now.

sourc7 commented on 2016-01-04 13:30 (UTC) (edited on 2016-01-10 09:48 (UTC) by sourc7)

@mehine2 Look like it's dkms issue, so you can remove the 8192cu-dkms, reboot, install the latest version of GNU/Linux kernel, and/or re-install the 8192cu-dkms. You need to do it after you upgraded the GNU/Linux kernel (remove the 8192cu-dkms -> reboot -> re-install the 8192cu-dkms) or use DKMS to automatically load the modules after kernel upgrade.

mehine2 commented on 2016-01-03 14:11 (UTC)

Worked fine with linux 4.2.5. but after I install 4.3.3 didn't see the dongle. Downgrade fix. Still would like to see it work with latest linux. tnx

sourc7 commented on 2015-11-08 08:59 (UTC) (edited on 2015-11-08 09:39 (UTC) by sourc7)

This driver is stable, but I got lowest average "5ms" ping with very high signal (100%), with Linux 4.3.0-1-ARCH mainline driver the lowest average "1ms" ping.

mariusz84 commented on 2015-09-19 21:51 (UTC)

@pmattern I had similar issue. Interesting thing is that I have two usb tongles with the same 8188cus chipset. One is working without problem, but second one had problem exactly as you described. Just like you I tried few dkms drivers without success. Ended up with switching to wpa and tkip in my router. Now both dongles works. I know that this is just workaround, but works.

pmattern commented on 2015-09-16 17:16 (UTC)

Running the module provided by this package on a device featuring chipset RTL8188CUS (Edimax EW-7811Un) just gave me "nl80211: Driver does not support authentication/association or connect commands" here when wpa_supplicant was launched. Running the patched version from github.com/pvaret/rtl8192cu-fixes installed as depicted on the homepage it was the same except the message was preceded by another one "Could not read interface wlan flags: No such device". Actually this looks as if that elderly Realtek driver wouldn't play with this chipset and/or kernel 4.1.6 any longer. But I was wondering whether you eventually know something that can be done to get the module running nevertheless. (Module rtl8192cu from mainline was basically working but way too unstable.)