From: Larry Finger <Larry.Finger@lwfinger.net>
To: v4mp <gaigo88@hotmail.it>
Cc: linux-wireless@vger.kernel.org,
'George0505' <george0505@realtek.com>,
'georgia' <georgia@realtek.com>
Subject: Re: Alfa AWUS036NHR with RTL8188RU chipset
Date: Fri, 30 Sep 2011 10:18:01 -0500 [thread overview]
Message-ID: <4E85DDA9.3090300@lwfinger.net> (raw)
In-Reply-To: <loom.20110930T160704-310@post.gmane.org>
On 09/30/2011 09:20 AM, v4mp wrote:
> hello larry,
>
> i've an ALFA AWUS036NHR and i tried latest compat-wireless-2011-09-27 on ubuntu
> natty 3.0.4-030004-generic,
> the adapter is recognized as rtl8192cu but is not
> responding, no network is detected.
>
> Then if i try to "modprobe -r rtl8192cu" results
> FATAL: Error removing rtl8192cu
> (/lib/modules/3.0.4-030004-generic/updates/drivers/net/wireless/rtlwifi
> /rtl8192cu/rtl8192cu.ko):
> Device or resource busy
>
> seems that remains blocked..i can't do anything
You are the second person that has reported a problem with this device.
Unfortunately, I do not have a sample of the device, but I have just ordered one
that will be delivered in about one week. I would guess that there is some
difference between the RTL8192CU and the RTL8188RU chips.
I Cc'd the Realtek group that works on USB devices. Perhaps they have some info
that will be useful. Given the difference in time between the US and Taiwan, I
would not expect any answer until Monday.
There are some changes that affect connection with an 802.11n network that are
found in the latest kernels. I'm not sure they are in the one you are using. You
can get the very latest by downloading and building the "bleeding edge" version
of compat-wireless.
Larry
next prev parent reply other threads:[~2011-09-30 15:18 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 2:10 Alfa AWUS036NHR with RTL8188RU chipset Chiefdome
2011-09-20 2:27 ` Chiefdome
2011-09-20 3:05 ` Larry Finger
2011-09-20 9:32 ` Chiefdome
2011-09-20 21:38 ` Chiefdome
2011-09-20 22:32 ` Larry Finger
2011-09-21 0:02 ` Larry Finger
2011-09-21 9:43 ` Chiefdome
2011-09-21 14:45 ` Larry Finger
2011-09-21 19:19 ` Chiefdome
2011-09-21 20:03 ` Larry Finger
2011-09-21 20:28 ` Chiefdome
2011-09-21 20:37 ` Larry Finger
2011-09-21 20:39 ` Chiefdome
2011-09-21 20:41 ` Chiefdome
2011-09-21 21:09 ` Larry Finger
2011-09-30 14:20 ` v4mp
2011-09-30 15:18 ` Larry Finger [this message]
2011-09-30 18:14 ` v4mp
2011-10-06 16:25 ` Toddy
2011-10-06 22:06 ` Larry Finger
2011-10-08 16:24 ` Toddy
2011-10-08 16:52 ` Larry Finger
2011-10-08 23:29 ` Gábor Stefanik
2011-10-09 14:21 ` v4mp
2011-10-09 14:47 ` Larry Finger
2011-10-15 14:22 ` v4mp
2011-10-16 2:49 ` Larry Finger
2011-10-17 10:07 ` v4mp
2011-10-17 14:59 ` Larry Finger
2011-10-17 17:09 ` v4mp
2011-10-17 18:38 ` Larry Finger
2011-10-18 3:23 ` Larry Finger
2011-10-18 12:44 ` v4mp
2011-10-18 13:07 ` v4mp
2011-10-18 15:20 ` Larry Finger
2011-10-18 21:50 ` v4mp
2011-10-18 23:01 ` Larry Finger
2011-10-19 8:17 ` v4mp
2011-10-19 12:08 ` Larry Finger
2011-10-19 14:37 ` v4mp
2011-10-20 3:38 ` Larry Finger
2011-10-20 9:47 ` v4mp
2011-10-20 13:35 ` Larry Finger
2011-10-26 15:49 ` Chiefdome
2011-10-26 16:12 ` Larry Finger
2011-10-26 19:39 ` Chiefdome
2011-10-26 21:20 ` Larry Finger
2011-10-26 21:31 ` Larry Finger
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=4E85DDA9.3090300@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=gaigo88@hotmail.it \
--cc=george0505@realtek.com \
--cc=georgia@realtek.com \
--cc=linux-wireless@vger.kernel.org \
/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).