lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <582d04385829105911e6152cf33268e9@mailserv.regfish.com>
Date:	Sat, 09 Mar 2013 17:41:29 +0100
From:	Benjamin Pabst <os@...iox.com>
To:	<linux-kernel@...r.kernel.org>
Subject: PROBLEM: rtl8192cu driver issue

[1.] rtl8192cu driver issue with Kernel version 3.7.5 and 3.7.10
(archlinux)
[2.] Since last update (Kernel 3.7.5) the rtl8192cu driver does not work
properly (only tested with Kernel 3.7.5 and 3.7.10).
     Although the hardware is correctly recognized and modules are load
(rtlwifi, rtl8192cu, rtl8192c_common), the corresponding
     device is either not created (checked with "ip link") or the device
is not able to scan or connect to any networks.
     An additional problem is a broken shutdown when the modules are load
(shutdown process stops at something like "All DMs unload",
     sorry, cannot remember the exact words).
[3.] networking, wireless, drivers, rtl8192cu
[4.] Linux version 3.7.10-1-ARCH (tobias@...OWA-LX) (gcc version 4.7.2
(GCC) ) #1 SMP PREEMPT Thu Feb 28 09:50:17 CET 2013
[5.] 
[6.] Plugging the a usb device with rtl8192cu chipset should trigger the
problem
[7.1.] Archlinux x64, connection and scanning tested with "Wicd"
[7.2.] model name	: AMD Phenom(tm) II X4 965 Processor
[8.] I have checked Openelec sources, where the usb device works fine.
They have applied a patch to replace "thread" with "kthread" to
     the driver. I also installed the following package
"https://aur.archlinux.org/packages/dkms-8192cu/" from Archlinux AUR which
     seems to do the same (applying the "kthread" patch). Using the
patched driver everything seems to work fine (further testing
     may be necessary).

Hope that might help (its my first report).

Greetings from Germany
Ben
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ