[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-wlan-user
Subject:    Re: [lwlan-user] Linksys WUSB11 problems
From:       "Mark S. Mathews" <mark () linux-wlan ! com>
Date:       2002-01-29 14:38:56
[Download RAW message or body]

These are the classic symptoms of the WLAN adapter firmware problems I
talk about in the readme.

Try playing with the prism2_usb module argument prism2_doreset.  It
_might_ help, it might make things worse.

The basic problem is that some sequences of "enumeration" control
endpoint exchanges (which are done by the core USB code, not the driver)
will leave the prism MAC chip in an unresponsive state.  There is
nothing that the driver can do except attempt a USB hub-port-reset. 
Unfortunately, with some hardware and with some versions of the core USB
code, the hub-port-reset makes things worse. In those cases, the USB
core code detects the hub-port-reset as a new device connection and the
sequence of events that led to our attempt of the reset starts all over
again.

You can try different kernel versions to see if a different version of
the USB core code will help.

Beyond that, we are stuck with things as they are until Intersil
releases the new primary firmware.

-Mark

Simon Pollitt wrote:
> 
> Inspired by the number of people on this list who have had success
> with the WUSB11 (v2.5) I got hold of one recently - folding antenna
> and all!  Unfortunately I've had very limited success.
> 
> My machine for testing is as follows:
> 
> - A bastard version of RedHat 6.2
> - Kernel 2.4.17 on a single processor machine
> - UHCI USB
> - wlan-ng-0.1.13-pre1
> 
> I have made the mods to prism2sta.c that recognise the device and it
> seems to be detected OK.
> 
> Upon modprobing prism2_usb I get:
> 
> Jan 29 17:08:05 fb kernel: init_module: prism2_usb.o: 0.1.13-devel1 Loaded
> Jan 29 17:08:05 fb kernel: init_module: dev_info is: prism2_usb
> Jan 29 17:08:05 fb kernel: usb.c: registered new driver prism2_usb
> Jan 29 17:08:05 fb kernel: prism2_usb: Attempting to claim device Linksys WUSB11 \
> v2.5 with devnum 2 
> and ifconfig -a shows wlan0.
> 
> When I try to run "ifconfig wlan0 up", I get:
> 
> Jan 29 17:19:18 fb kernel: hfa384x_docmd: hfa384x_docmd:ctlx failure=REQ_TIMEOUT
> Jan 29 17:19:18 fb kernel: hfa384x_drvr_initialize: \
>                 hfa384x_drvr_initializecmd_initialize() failed, result=-5
> Jan 29 17:19:18 fb kernel: prism2sta_initmac: prism2sta_initmac: drvr_initialize() \
>                 failed, result=-5
> Jan 29 17:19:20 fb kernel: hfa384x_docmd: hfa384x_docmd:ctlx failure=RESP_TIMEOUT
> Jan 29 17:19:20 fb kernel: hfa384x_drvr_shutdown: hfa384x_drvr_shutdown: \
>                 cmd_initialize() failed, result=-5.
> Jan 29 17:19:20 fb kernel: prism2sta_initmac: Failed, result=-5
> Jan 29 17:19:20 fb kernel: prism2sta_open: initmac() failed, result=-5.
> 
> I no longer get kernel hangs with 0.1.13 as I did with 0.1.12 and earlier, but I \
> never get any further result. 
> I've tried on another machine (which has two processors) and OHCI USB.
> I've tried in both SMP and non-SMP mode with exactly the same results
> as above...
> 
> Does anyone have any suggestions as to where things are going wrong?
> I'm going crazy here!
> 
> Thanks,
> 
> Simon
> 
> --
> Simon Pollitt
> Maptek Pty. Ltd.
> 
> _______________________________________________
> Linux-wlan-user mailing list
> Linux-wlan-user@lists.linux-wlan.com
> http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-user

-- 

Mark S. Mathews

AbsoluteValue Systems      Web:    http://www.linux-wlan.com
715-D North Drive          e-mail: mark@linux-wlan.com
Melbourne, FL 32934        Phone:  321.259.0737
USA                        Fax:    321.259.0286


[prev in list] [next in list] [prev in thread] [next in thread]