rt2500usb stopped working (vendor request error)

Ivo van Doorn · 2007-08-02 11:11 UTC

Hi,

Quoted 5 lines

I was using rt2x00 with hostapd to create a AP and it worked fine in FC6 with rt2x00-cvs-2007020803.
But after upgrading to F7 it stopped working. I am using kernel kernel-2.6.22.1-41.fc7 which have a recent wireless-dev copy of the driver but I just get this errors in dmesg:

<... snip...>

Quoted 5 lines

Any idea whats going on?
Can I provide more info to help finding a solution? I already reported it here before:
http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=4042
but got no usefull replies so I decided to try here.

Could you retry with a more recent version?

Ivo

dragoran · 2007-08-02 11:38 UTC

Quoted 10 lines · Ivo van Doorn

Hi,
Quoted 3 lines
I was using rt2x00 with hostapd to create a AP and it worked fine in FC6 with rt2x00-cvs-2007020803.
But after upgrading to F7 it stopped working. I am using kernel kernel-2.6.22.1-41.fc7 which have a recent wireless-dev copy of the driver but I just get this errors in dmesg:
<... snip...>

Quoted 10 lines

Quoted 6 lines
Any idea whats going on?
Can I provide more info to help finding a solution? I already reported it here before:
http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=4042
but got no usefull replies so I decided to try here.
Could you retry with a more recent version?

what do you mean by more recent?
its a some days old wireless-dev snapshot (31-07-2007). has something changed in the past 2 days that could fix it?

Ivo van Doorn · 2007-08-02 14:10 UTC

Hi,

Quoted 17 lines

Quoted 17 lines
Quoted 6 lines
I was using rt2x00 with hostapd to create a AP and it worked fine in FC6 with rt2x00-cvs-2007020803.
But after upgrading to F7 it stopped working. I am using kernel kernel-2.6.22.1-41.fc7 which have a recent wireless-dev copy of the driver but I just get this errors in dmesg:
<... snip...>
Quoted 6 lines
Any idea whats going on?
Can I provide more info to help finding a solution? I already reported it here before:
http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=4042
but got no usefull replies so I decided to try here.

Quoted 6 lines

Quoted 3 lines
Could you retry with a more recent version?
what do you mean by more recent?
its a some days old wireless-dev snapshot (31-07-2007). has something changed in the past 2 days that could fix it?

Well I don't know which rt2x00 version was shipped with 2.6.22.1-41-fc7, not do I know when it was released. Your last posted on the forum dated from July 13th.
And regarding the patches, last tuesday I have released rt2x00 2.0.5 which was then merged with wireless-dev, but the release itself contained quite a lot of patches...

Ivo

Ivo van Doorn · 2007-08-02 21:02 UTC

Hi,

Quoted 9 lines

I upgraded the kernel since than to to this version.
And regarding the patches, last tuesday I have released rt2x00 2.0.5 which
Quoted 2 lines
was then merged with wireless-dev, but the release itself contained quite a lot of patches...
ok I will compile a wireless-dev snapshot and when I get home and tell you if it worked or not.

Just an idea related to another bug report regarding vendor request errors, do you have the USB stick plugged into a USB 1.1 port?
If so, could you edit rt2x00usb.h and change the line:

#define REGISTER_TIMEOUT 20

And increase the value to something higher (up to 500) and see if that works better?

Thanks,

Ivo

dragoran · 2007-08-03 08:20 UTC

Quoted 8 lines · Ivo van Doorn

do you have the USB stick plugged into a USB 1.1 port? If so, could you edit rt2x00usb.h and change the line:
#define REGISTER_TIMEOUT 20
And increase the value to something higher (up to 500) and see if that works better?
Just an idea related to another bug report regarding vendor request errors,

1) tested todays snapshot:
same results.
2) increased the timeout didn't help.
"usb 2-2: new high speed USB device using ehci_hcd and address" so its a usb2 device.
any other ideas?

dragoran · 2007-08-03 09:07 UTC

Quoted 12 lines · Andy Green

Quoted 5 lines · Somebody in the thread at some point
2) increased the timeout didn't help.
"usb 2-2: new high speed USB device using ehci_hcd and address" so its a usb2 device.
any other ideas?
Are other USB devices working okay on that machine with that kernel?

mouse and usb-storage devices are working fine.

Ivo van Doorn · 2007-08-03 15:01 UTC

Quoted 8 lines · dragoran

Quoted 7 lines · Ivo van Doorn
do you have the USB stick plugged into a USB 1.1 port? If so, could you edit rt2x00usb.h and change the line:
#define REGISTER_TIMEOUT 20
And increase the value to something higher (up to 500) and see if that works better?

Quoted 8 lines

Quoted 2 lines
Just an idea related to another bug report regarding vendor request errors,
1) tested todays snapshot:
same results.
2) increased the timeout didn't help.
"usb 2-2: new high speed USB device using ehci_hcd and address" so its a usb2 device.
any other ideas?

Nope not at this time,
I'll look into the issue some more and see what might cause this.

Ivo

Ivo van Doorn · 2007-08-03 16:43 UTC

Quoted 8 lines · dragoran

Quoted 7 lines · Ivo van Doorn
do you have the USB stick plugged into a USB 1.1 port? If so, could you edit rt2x00usb.h and change the line:
#define REGISTER_TIMEOUT 20
And increase the value to something higher (up to 500) and see if that works better?

Quoted 8 lines

Quoted 2 lines
Just an idea related to another bug report regarding vendor request errors,
1) tested todays snapshot:
same results.
2) increased the timeout didn't help.
"usb 2-2: new high speed USB device using ehci_hcd and address" so its a usb2 device.
any other ideas?

Have you tried using the legacy driver?
I'm curious if the same problem exist in there are well...

Ivo

dragoran · 2007-08-03 17:46 UTC

no I havn't I will try it tomorrow and tell you if it worked. but as I said before a earilier version of the driver worked before on fc6 without any problems.

Quoted 24 lines · Ivo van Doorn

Quoted 7 lines · dragoran
Quoted 6 lines · Ivo van Doorn
do you have the USB stick plugged into a USB 1.1 port? If so, could you edit rt2x00usb.h and change the line:
#define REGISTER_TIMEOUT 20
And increase the value to something higher (up to 500) and see if that
works better?
Quoted 9 lines
Quoted 3 lines
Just an idea related to another bug report regarding vendor request errors,
1) tested todays snapshot:
same results.
2) increased the timeout didn't help.
"usb 2-2: new high speed USB device using ehci_hcd and address" so its a usb2 device.
any other ideas?
Have you tried using the legacy driver?
I'm curious if the same problem exist in there are well...
Ivo

Ivo van Doorn · 2007-08-03 18:03 UTC

Quoted 3 lines · dragoran

no I havn't I will try it tomorrow and tell you if it worked. but as I said before a earilier version of the driver worked before on fc6 without any problems.

Yes, but I want to rule out hardware problems completely.
If legacy still works then there is nothing with the hardware, but indeed a driver problem.
If the legacy driver shows the same problem, it might be a hardware problem.

Ivo

dragoran · 2007-08-03 18:05 UTC

ok this makes sense.
is the legacy driver supported by hostapd?

Quoted 12 lines · Ivo van Doorn

Quoted 3 lines · dragoran
no I havn't I will try it tomorrow and tell you if it worked. but as I said before a earilier version of the driver worked before on fc6 without any problems.
Yes, but I want to rule out hardware problems completely.
If legacy still works then there is nothing with the hardware, but indeed a driver problem.
If the legacy driver shows the same problem, it might be a hardware problem.
Ivo

Ivo van Doorn · 2007-08-03 18:11 UTC

Quoted 2 lines · dragoran

ok this makes sense.
is the legacy driver supported by hostapd?

Nope, there is no master mode support in the legacy drivers.

Ivo

Quoted 14 lines · Ivo van Doorn

Quoted 12 lines · dragoran
Quoted 3 lines
no I havn't I will try it tomorrow and tell you if it worked. but as I said before a earilier version of the driver worked before on fc6 without any problems.
Yes, but I want to rule out hardware problems completely.
If legacy still works then there is nothing with the hardware, but indeed a driver problem.
If the legacy driver shows the same problem, it might be a hardware problem.
Ivo

dragoran · 2007-08-03 18:14 UTC

thats what I am using it for....

Quoted 26 lines · Ivo van Doorn

Quoted 2 lines · dragoran
ok this makes sense.
is the legacy driver supported by hostapd?
Nope, there is no master mode support in the legacy drivers.
Ivo
Quoted 10 lines · Ivo van Doorn
Quoted 9 lines · dragoran
Quoted 3 lines
no I havn't I will try it tomorrow and tell you if it worked. but as I said before a earilier version of the driver worked before on fc6 without any problems.
Yes, but I want to rule out hardware problems completely. If legacy still works then there is nothing with the hardware, but indeed a driver problem.
If the legacy driver shows the same problem, it might be a hardware
problem.
Quoted 4 lines
Quoted 3 lines
Ivo

Ivo van Doorn · 2007-08-03 18:26 UTC

Quoted 1 line · dragoran

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.

Ivo

dragoran · 2007-08-03 18:29 UTC

ok will test a connection to my laptop via ad-hoc to see if it works. but I can't do anything today so tomorrow ;)
thx for your help.

Quoted 11 lines · Ivo van Doorn

Quoted 1 line · dragoran
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.
Ivo

dragoran · 2007-08-04 08:09 UTC

Quoted 12 lines · Ivo van Doorn

Quoted 2 lines · dragoran
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....

Luis Correia · 2007-08-04 08:34 UTC

Well, it may be an hardware error you got on your stick.

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.

Luis

Quoted 27 lines · dragoran

Quoted 12 lines · Ivo van Doorn
Quoted 2 lines · dragoran
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Ivo van Doorn · 2007-08-04 09:42 UTC

Quoted 1 line · Luis Correia

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.

Quoted 6 lines

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

Quoted 29 lines · dragoran

Quoted 27 lines
Quoted 12 lines · Ivo van Doorn
Quoted 2 lines · dragoran
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

dragoran · 2007-08-04 09:46 UTC

Quoted 13 lines · Ivo van Doorn

Quoted 2 lines · Luis Correia
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.
Quoted 3 lines
That or it is one of those wrongly named sticks which are actually rt73... but i don't really know.

Quoted 9 lines

Quoted 4 lines
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...

ok will test in on my fc6 server (where the last working driver still builds) and see if this one works. if this does not work too I will test on windows to make sure thats a hw problem.