From: Oleksij Rempel <linux@rempel-privat.de>
To: "Alan Stern" <stern@rowland.harvard.edu>,
"Yannik Völker" <yannikv@yahoo.de>
Cc: Pontus Fuchs <pontus.fuchs@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: ar5523 Gigaset USB Adapter 108 issue
Date: Fri, 18 Oct 2013 17:07:07 +0200 [thread overview]
Message-ID: <52614E9B.6040400@rempel-privat.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1310181041080.1164-100000@iolanthe.rowland.org>
Am 18.10.2013 16:49, schrieb Alan Stern:
> Yannik, you should always use Reply-To-All so that your messages get
> sent to the mailing list and not just to me.
>
> On Thu, 17 Oct 2013, Yannik Völker wrote:
>
>> Am 07.08.2013 19:34, schrieb Alan Stern:
>>> Please post two usbmon traces, one showing the failure on your
>>> current system and the other showing the adapter running correctly
>>> under a 32-bit kernel. Instructions for usbmon are in the kernel
>>> source file Documentation/usb/usbmon.txt.
>> I never got it to work under a 32-bit kernel, i was just able to utilize
>> a windows32 driver using ndiswrapper.
>>
>> Now i got it to "work". I randomly found out that the ar5523 driver
>> actually works when you load it after you unload ndiswrapper so the
>> following steps make it work:
>> 1. modprobe ndiswrapper
>> 2. plug in device
>> 3. connect to wlan using ndiswrapper and disconnect again (might be
>> optional)
>> 4. modprobe -r ndiswrapper
>> 5. modprobe ar5523
>> 6. connect to wlan
>> log for that is attatched as wlanthennative2.log
It sounds like linux driver didn't recognised usb id and didn't uploaded
firmware, or there was no firmware to upload.
>>
>> This works but is unreliable and sometimes the connection breaks down with
>>
>> Oct 17 19:26:46 yannik-desktop wpa_supplicant[2153]: wlan0:
>> CTRL-EVENT-DISCONNECTED bssid=01:23:45:67:89:ab reason=3
>> Oct 17 19:26:46 yannik-desktop kernel: [ 633.005591] usb 3-14:
>> ar5523_data_rx_cb: USB err: -71
>> Oct 17 19:26:46 yannik-desktop kernel: [ 633.005703] usb 3-14: RX USB
>> error -71.
>> Oct 17 19:26:46 yannik-desktop kernel: [ 633.005718] usb 3-14:
>> ar5523_data_rx_cb: USB err: -71
>> Oct 17 19:26:46 yannik-desktop kernel: [ 633.005779] usb 3-14: RX USB
>> error -71.
>> Oct 17 19:26:46 yannik-desktop kernel: [ 633.005788] usb 3-14:
>> ar5523_data_rx_cb: USB err: -71
>> Oct 17 19:26:46 yannik-desktop kernel: [ 633.005846] usb 3-14: USB
>> disconnect, device number 7
>> Oct 17 19:26:46 yannik-desktop kernel: [ 633.006080] wlan0:
>> deauthenticating from 01:23:45:67:89:ab by local choice (reason=3)
>>
>> unloading ar5523 and then refollowing the steps beginning with step 3
>> usually makes it work again
>>
thas is probably other issue. Let's start with thirst issue.
>> directload.log contains what happens when you just load ar5523 after
>> the device was plugged in.
>>
>> plug_ndis.log contains what sometimes happens when i have loaded and
>> unloaded the modules some times and then try to load ndiswrapper.
>>
>> pluginout.log contains syslog for plugging the device in and out.
>>
>> Do you still need the usbmon traces?
>
> In fact, I'm not the best person to work on this, since I know nothing
> about the ar5523. Problems with a particular driver should be brought
> to the attention of the driver's maintainer (CC'ed). Maybe he can
> help.
>
> It might be a good idea to post two usbmon traces: One showing what
> happens during steps 1-3, and another showing what happens if you
> modprobe ar5523 without loading ndiswrapper first.
>
--
Regards,
Oleksij
next prev parent reply other threads:[~2013-10-18 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <526020B6.7080601@yahoo.de>
2013-10-18 14:49 ` ar5523 Gigaset USB Adapter 108 issue Alan Stern
2013-10-18 15:07 ` Oleksij Rempel [this message]
2013-10-18 15:38 ` Yannik Völker
2013-10-18 16:16 ` Oleksij Rempel
2013-10-18 16:33 ` Yannik Völker
2013-10-18 17:16 ` Oleksij Rempel
2013-10-19 12:18 ` Yannik Völker
2013-10-19 15:30 ` Oleksij Rempel
2013-10-19 23:53 ` Stefan Lippers-Hollmann
[not found] ` <5262BA7A.2050803@rempel-privat.de>
[not found] ` <5266C4C1.80408@yahoo.de>
2013-10-22 18:45 ` Oleksij Rempel
2013-10-24 12:46 ` Yannik Völker
2013-10-25 10:31 ` Pontus Fuchs
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=52614E9B.6040400@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=linux-wireless@vger.kernel.org \
--cc=pontus.fuchs@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=yannikv@yahoo.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.