From: Ivo van Doorn <ivdoorn@gmail.com>
To: "Luis Correia" <luis.f.correia@gmail.com>
Cc: dragoran <drago01@gmail.com>,
linux-wireless@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: rt2500usb stopped working (vendor request error)
Date: Sat, 4 Aug 2007 11:46:37 +0200 [thread overview]
Message-ID: <200708041146.37667.IvDoorn@gmail.com> (raw)
In-Reply-To: <efe7343f0708040134v30b7ffc1mcfc9b61e555897c3@mail.gmail.com>
On Saturday 04 August 2007, Luis Correia wrote:
> Well, it may be an hardware error you got on your stick.
Nope, very doubtfully.
When he is using the latest version there would be a big warning
"Not an rt2500usb device" and the driver would halt loading after that.
> That or it is one of those wrongly named sticks which are actually
> rt73... but i don't really know.
>
> One last test you could do, go to a friend that uses Windoze and see
> if it works as a client and if yes, which driver did it detect, rt73
> or rt2500usb.
Hmm checking if at least it works on windows would be an idea,
but I am really starting to suspect hardware problems...
Ivo
> On 8/4/07, dragoran <drago01@gmail.com> wrote:
> > Ivo van Doorn wrote:
> > > On Friday 03 August 2007, dragoran wrote:
> > >
> > >> thats what I am using it for....
> > >>
> > >
> > > I understand, but if you could test the legacy driver
> > > for any other mode to see if at least the hardware is
> > > all right.
> > > Managed and adhoc mode would already give a good
> > > idea about any possible hardware problems.
> > >
> > >
> > while testing the lagacy driver I got this messages:
> > usb 2-2: new high speed USB device using ehci_hcd and address 4
> > usb 2-2: unable to read config index 0 descriptor/start
> > usb 2-2: chopping to 0 config(s)
> > usb 2-2: string descriptor 0 read error: -71
> > usb 2-2: string descriptor 0 read error: -71
> > usb 2-2: string descriptor 0 read error: -71
> > usb 2-2: no configuration chosen from 0 choices
> > and nothing worked....
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
next prev parent reply other threads:[~2007-08-04 9:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 10:23 rt2500usb stopped working (vendor request error) dragoran
2007-08-02 11:15 ` Ivo van Doorn
2007-08-02 11:37 ` dragoran
2007-08-02 14:14 ` Ivo van Doorn
[not found] ` <f6ca9fed0708020756r7af012a0gd2a72009265a5000@mail.gmail.com>
2007-08-02 21:06 ` Ivo van Doorn
2007-08-03 8:20 ` dragoran
[not found] ` <46B2ED45.8020500@warmcat.com>
2007-08-03 9:07 ` dragoran
2007-08-03 15:05 ` Ivo van Doorn
2007-08-03 16:48 ` Ivo van Doorn
2007-08-03 17:46 ` dragoran
2007-08-03 18:07 ` Ivo van Doorn
2007-08-03 18:05 ` dragoran
2007-08-03 18:15 ` Ivo van Doorn
2007-08-03 18:14 ` dragoran
2007-08-03 18:31 ` Ivo van Doorn
2007-08-03 18:29 ` dragoran
2007-08-04 8:08 ` dragoran
2007-08-04 8:34 ` Luis Correia
2007-08-04 9:46 ` Ivo van Doorn [this message]
2007-08-04 9:46 ` dragoran
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=200708041146.37667.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=drago01@gmail.com \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luis.f.correia@gmail.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).