From: <esp@pyroshells.com>
To: <linux-kernel@vger.kernel.org>
Subject: usb problems with wireless device..
Date: Fri, 30 May 2003 10:26:45 -0700 (PDT) [thread overview]
Message-ID: <33268.65.122.196.250.1054315605.squirrel@mail.webhaste.com> (raw)
argh.. lets try this again..
I've got a wusb v2.1 wireless connection device, which I'm trying to use
with linux 2.4.20-4GB (standard suse linux 8.2), and have been getting the
following errors inside of dmesg:
----
hub.c: new USB device 00:02.0-2, assigned address 3
usbdfu.c: USB Device Fimware Uploader (DFU) v0.8
usb.c: registered new driver usbdfu
at76c503.c: Atmel at76c503 Wireless LAN Driver v0.8
usbdfu.c: get_op_mode() failed: -32
usbdfu.c: downloading firmware
usbdfu.c: remap
usb.c: registered new driver at76c503
at76c503.c: driver registered
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 18 ret -110
<repeats about 1000 times>
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 18 ret -110
usbdfu.c: resetting device
usbdfu.c: scanning unclaimed devices
usbdfu.c: op_mode = 4
usbdfu.c: firmware already loaded
at76c503.c: downloading external firmware
at76c503.c: firmware version 0.100.2 #16
at76c503.c: using MAC 00:06:25:0d:55:bd
at76c503.c: using net device eth0
at76c503.c: using BSSID 02:00:ce:1c:07:00
eth0: no IPv6 routers present
---
It looks like eth0 exists with the right MAC address, but when I
try running dhcpcd on eth0 it basically hangs the dhcpcd call, and when I
try to plug in the linksys unit into the usb slot with KDE
running, KDE hangs..
This is very annoying. I'm not sure what's causing the get_op_mode call to
fail, nor what's causing the usbdevfs call to fail.
Any help would be appreciated - let me know what diagnostic info people
would need in order to file a fixable bug report, too..
Thanks,
Ed
Thanks much,
Ed
next reply other threads:[~2003-05-30 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 17:26 esp [this message]
2003-05-30 18:29 ` Greg KH
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=33268.65.122.196.250.1054315605.squirrel@mail.webhaste.com \
--to=esp@pyroshells.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®