Hi,
> I upgraded the kernel since than to to this version.
>
> 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...
>
>
> 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
On Friday 03 August 2007, dragoran wrote:
> Ivo van Doorn wrote:
> > 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?
Have you tried using the legacy driver?
I'm curious if the same problem exist in there are well...
Ivo
ok this makes sense.
is the legacy driver supported by hostapd?
On 8/3/07, Ivo van Doorn <[email protected]> wrote:
> On Friday 03 August 2007, dragoran wrote:
> > 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
>
On Friday 03 August 2007, dragoran wrote:
> Ivo van Doorn wrote:
> > 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?
Nope not at this time,
I'll look into the issue some more and see what might cause this.
Ivo
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....
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 <[email protected]> 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 [email protected]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
On Friday 03 August 2007, dragoran wrote:
> ok this makes sense.
> is the legacy driver supported by hostapd?
Nope, there is no master mode support in the legacy drivers.
Ivo
> On 8/3/07, Ivo van Doorn <[email protected]> wrote:
> > On Friday 03 August 2007, dragoran wrote:
> > > 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
> >
>
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
On 8/4/07, dragoran <[email protected]> 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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
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.
On 8/3/07, Ivo van Doorn <[email protected]> wrote:
> On Friday 03 August 2007, dragoran wrote:
> > Ivo van Doorn wrote:
> > > 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?
>
> Have you tried using the legacy driver?
> I'm curious if the same problem exist in there are well...
>
> Ivo
>
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.
On 8/3/07, Ivo van Doorn <[email protected]> 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.
>
> Ivo
>
Ivo van Doorn wrote:
> 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...
>
>
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.
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.
Ivo
Ivo van Doorn wrote:
> 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?
On Friday 03 August 2007, dragoran wrote:
> 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
thats what I am using it for....
On 8/3/07, Ivo van Doorn <[email protected]> wrote:
> On Friday 03 August 2007, dragoran wrote:
> > ok this makes sense.
> > is the legacy driver supported by hostapd?
>
> Nope, there is no master mode support in the legacy drivers.
>
> Ivo
>
> > On 8/3/07, Ivo van Doorn <[email protected]> wrote:
> > > On Friday 03 August 2007, dragoran wrote:
> > > > 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
> > >
> >
>
>
>