linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Christian Clauss <cclauss@bluewin.ch>
Cc: ziv_huang@realtek.com, georgia@realtek.com,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: rtl8192cu NOT working on Raspberry Pi
Date: Sat, 16 Mar 2013 18:22:52 -0500	[thread overview]
Message-ID: <5144FECC.6050504@lwfinger.net> (raw)
In-Reply-To: <041DFAF5-BEDE-4C1A-9863-A04F2DD3049A@bluewin.ch>

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	<Larry.Finger@lwfinger.net>
> author:         Ziv Huang	<ziv_huang@realtek.com>
> author:         Georgia		<georgia@realtek.com>
>
> # ========
>
> $ 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



       reply	other threads:[~2013-03-16 23:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <041DFAF5-BEDE-4C1A-9863-A04F2DD3049A@bluewin.ch>
2013-03-16 23:22 ` Larry Finger [this message]
2013-03-17  9:12   ` rtl8192cu NOT working on Raspberry Pi Jussi Kivilinna
2013-03-17 15:06     ` Adrian Chadd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5144FECC.6050504@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=cclauss@bluewin.ch \
    --cc=georgia@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ziv_huang@realtek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).