On 03/16/2013 05:03 PM, Christian Clauss wrote:
> Hi Larry, Ziv, and Georgia,
>
> These rtl8192cu drivers seem to be very flakey / non-functional on Raspberry Pi.
>
> https://github.com/hexameron/rtlwifi
>
> http://www.raspberrypi.org/phpBB3/viewtopic.php?f=71&t=24951
Sorry, but I only support the drivers in the current Linux kernel, and as
backported with compat-drivers.
>
> # ========
>
> $ uname -a
> Linux raspberrypi 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l GNU/Linux
>
> # ========
>
> $ modinfo rtl8192cu # Only after following hexameron's instructions above.
> filename: /lib/modules/3.6.11+/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 protected]>
> author: Ziv Huang <[email protected]>
> author: Georgia <[email protected]>
>
> # ========
>
> $ modinfo 8192cu
> filename: /lib/modules/3.6.11+/kernel/drivers/net/wireless/rtl8192cu/8192cu.ko
> version: v3.4.3_4369.20120622
> author: Realtek Semiconductor Corp.
> description: Realtek Wireless Lan Driver
> license: GPL
>
> # ========
>
> $ ifup wlan0
> ioctl[SIOCSIWAP]: Operation not permitted
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
No mac80211 driver will support *ALL* of the ioctl commands. You should use iw;
however, these should not be critical.
>
> # ========
>
> $ ip addr
> 4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
> link/ether e0:91:53:62:9e:d9 brd ff:ff:ff:ff:ff:ff
>
> # ========
>
> $ ifconfig wlan0
> wlan0 Link encap:Ethernet HWaddr e0:91:53:62:9e:d9
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
There is a major bug in rtl8192cu that was just fixed this past week. See
http://marc.info/?l=linux-wireless&m=136319807619280&w=2 for the patch.
Larry
On 17.03.2013 01:22, Larry Finger wrote:
> On 03/16/2013 05:03 PM, Christian Clauss wrote:
>> Hi Larry, Ziv, and Georgia,
>>
>> These rtl8192cu drivers seem to be very flakey / non-functional on Raspberry Pi.
>>
>> https://github.com/hexameron/rtlwifi
>>
>> http://www.raspberrypi.org/phpBB3/viewtopic.php?f=71&t=24951
>
> Sorry, but I only support the drivers in the current Linux kernel, and as backported with compat-drivers.
>
Problems I had with rtl8192cu on arm/sunxi, were mostly related to USB host driver not handling unaligned and/or overlapping URB buffers correctly which lead to memory corruption and random crashes. So if you get problematic behavior with latest compat-drivers (+ with the patch Larry pointed out), I'd say look at USB host driver of raspberry.
You can check the workarounds for sunxi-ehci/ohci and tegra-ehci at:
https://github.com/linux-sunxi/linux-sunxi/blob/stage/sunxi-3.4/drivers/usb/host/ehci-tegra.c#L386
https://github.com/linux-sunxi/linux-sunxi/blob/stage/sunxi-3.4/drivers/usb/host/sw_hci_sunxi.c#L633
-Jussi
<snip>
>
> There is a major bug in rtl8192cu that was just fixed this past week. See http://marc.info/?l=linux-wireless&m=136319807619280&w=2 for the patch.
>
> Larry
>
On 17 March 2013 02:12, Jussi Kivilinna <[email protected]> wrote:
> Problems I had with rtl8192cu on arm/sunxi, were mostly related to USB host driver not handling unaligned and/or overlapping URB buffers correctly which lead to memory corruption and random crashes. So if you get problematic behavior with latest compat-drivers (+ with the patch Larry pointed out), I'd say look at USB host driver of raspberry.
>
> You can check the workarounds for sunxi-ehci/ohci and tegra-ehci at:
> https://github.com/linux-sunxi/linux-sunxi/blob/stage/sunxi-3.4/drivers/usb/host/ehci-tegra.c#L386
> https://github.com/linux-sunxi/linux-sunxi/blob/stage/sunxi-3.4/drivers/usb/host/sw_hci_sunxi.c#L633
FreeBSD just went through this same problem with the USB stack. Please
work with the USB host driver team and eliminate all of the issues
there before blaming the USB wifi driver. :)
Adrian