From: Larry Finger <Larry.Finger@lwfinger.net>
To: v4mp <gaigo88@hotmail.it>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Alfa AWUS036NHR with RTL8188RU chipset
Date: Wed, 19 Oct 2011 07:08:51 -0500 [thread overview]
Message-ID: <4E9EBDD3.6060907@lwfinger.net> (raw)
In-Reply-To: <loom.20111019T101621-921@post.gmane.org>
On 10/19/2011 03:17 AM, v4mp wrote:
>
> i don't know why you are saying this, i was just kidding....
> you take me too seriously...
> i think i'm doing a favour to you too debugging this..
>
> however with the rtl8192cu the hardware doesn't work with
> the ep error related to xhci_hcd..
> it is the point that we are now
>
> there is something more can i do now?
> i don't have any other usb port that works with other controller like ehci..
You can set up usbmon and dump the starting USB traffic for rtl8192cu and for
the Alfa driver, but please do not let it run for a long time. Those dumps get
very long. Load the driver you want with the device unplugged, then plug in the
device, and dump the buffer 3-4 seconds later. The instructions for using usbmon
are at http://www.mjmwired.net/kernel/Documentation/usb/usbmon.txt or in
Documentation/usb/usbmon.txt in the source tree.
The other thing you could do is to plug in the device with rtl8192cu as the
driver and after 1 second dump the dmesg log with 'dmesg > dmesg.out'. In your
previous attempt, you let the buffer wrap around and important info was lost.
These logs should be posted at Pastebin.
I sent a request for info regarding this to the Chinese group that wrote the
driver, but I have not heard back.
Larry
next prev parent reply other threads:[~2011-10-19 12:08 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
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 [this message]
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=4E9EBDD3.6060907@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=gaigo88@hotmail.it \
--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).