Re: associate, then "prism2sta_commsqual_defer: error fetching commsqual"

Josh Wyatt wrote:
> Josh Wyatt wrote:
> 
>>Chris Rankin wrote:
>>
>>
>>>--- Josh Wyatt <Josh.Wyatthcssystems.com> wrote:
>>>
>>>
>>>
>>>>Any ideas?  I have a suspicion that the
hardware is faulty.  For example, after the above, the
>>>>device disappears from the USB tree, and
does not reappear after a reboot.  Only removing and
>>>>replacing the device "revives" it.
 But, the silly thing actually works for a few seconds!
>>>>
>>>>Any help would be appreciated.
>>>
>>>
>>>Did you notice a lot of compiler warnings in
hfa384x_usb.c? The prototype to one of the kernel's
>>>callback functions changed in 2.6.19, and I'm
not sure that vanilla 0.2.7 has the fix. (Or even if
>>>it matters...) You can grab the fix from the SVN
repository.
> 
> 
>><lots snipped>
>>
>>I will try the SVN repo version and get back to
you.
> 
> 
> Same problem with this morning's svn (reports 0.2.8). 
Although I do note that it took almost a minute (59 seconds)
to fail this time, instead of 7-15 seconds from previous
attempts.

Another datapoint.  I also tried this on a completely
different machine which has 0.2.0 running, with kernel
2.4.29 (Does that make me a luddite?).  This machine is a
compaq evo N600C with builtin wireless, which is an internal
version of a prism2.5 USB card.  It has been nice and stable
for me for quite awhile.

I tested by disabling the internal wireless, then booting
the machine and trying to bring up this external one.

Net result is the interface is initialized and configured
successfully, but after a minute or two, the machine
completely locks.

I'm starting to think this hardware is somehow broken.  It
was second-hand, after all.  Any other thoughts?  I tell
you, getting wireless going happily on Linux is getting
harder and harder.

Thanks,
Josh

_______________________________________________
Linux-wlan-devel mailing list
Linux-wlan-devellists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-
wlan-devel

--- Josh Wyatt <Josh.Wyatthcssystems.com> wrote:

> Another datapoint.  I also tried this on a completely
different machine which has 0.2.0 running,
> with kernel 2.4.29 (Does that make me a luddite?). 
This machine is a compaq evo N600C with
> builtin wireless, which is an internal version of a
prism2.5 USB card.  It has been nice and
> stable for me for quite awhile.
...
> Net result is the interface is initialized and
configured successfully, but after a minute or
> two, the machine completely locks.

I wouldn't conclude that yet; the driver has changed
considerably between 0.2.0 and 0.2.8, as has
the Linux USB stack between 2.4.x and 2.6.x. The fact that
the *entire machine* locks with 0.2.0
suggests that you hit a nasty driver bug. Can you compile
0.2.8 on Linux 2.4.29?

Ideally, you would need to try a second "known
good" Prism2 USB device in your existing machine to
prove that your current device is broken. Plugging your
device into a Windows machine wouldn't
*necessarily* prove anything, although it would be a good
indication of a broken device if it
failed under Windows too.

Cheers,
Chris



	
	
		
___________________________________________________________

New Yahoo! Mail is the ultimate force in competitive
emailing. Find out more at the Yahoo! Mail Championships.
Plus: play games and win prizes. 
http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.ne
t/uk 
_______________________________________________
Linux-wlan-devel mailing list
Linux-wlan-devellists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-
wlan-devel