Re: Z-COM ZB-1725 problem with 0.2.2 driver

I am sorry forgeting to add the linux mailiing list.
 I used the 1.8.3 secondary firmware until the card start to work.
 When I stop the card using "/etc/init.d/wlan stop", sometimes system 
informs me that p80211 module is in use.
 It is strange to unable to delete "prsim2_usb" and "p80211" moudles after 
executing "/etc/init.d/wlan stop"

 On 9/5/05, Chris Rankin <[email protected]> wrote: 
> 
> --- hua law <[email protected]> wrote:
> > OK, anyway, I got the card work at the Ad-hoc mode though it is not 
> stable.
> >
> > I made no change about the firmware except just keeping trying
> > "/etc/init.d/wlan start" ,"/etc/init.d/wlan stop", "/etc/init.d/wlan
> > restart"
> >
> > two times, after the "stop" command, the light begin to stay on. It's 
> really
> > strange.
> >
> > when failed,Debug output is following:
> >
> > m2sta_mlmerequest(0): Received mlme ifstate request
> > prism2sta_ifstate(0): Current MSD state(5), requesting(2)
> > hfa384x_usbin_callback(0): status=-2, urb explicitly unlinked.
> > hfa384x_ctlxout_callback(0): urb->status=0
> > hfa384x_usbctlx_complete_sync: CTLX[1] error: state(Request failed)
> > hfa384x_cmd_initialize(0): cmdresp.init: status=0xa000, resp0=0xc1a9,
> > resp1=0x2000, resp2=0xc44c
> > hfa384x_usbin_callback(0): status=-2, urb explicitly unlinked.
> > hfa384x_drvr_start: cmd_initialize() failed, result=-5
> > prism2sta_ifstate: hfa384x_drvr_start() failed,result=-5
> >
> > more detail:
> > prism2sta_mlmerequest(0): Received mlme ifstate request
> > prism2sta_ifstate(0): ---->
> > prism2sta_ifstate(0): Current MSD state(5), requesting(2)
> > hfa384x_drvr_start(0): ---->
> > hfa384x_usbin_callback(0): ---->
> > hfa384x_usbin_callback(0): status=-2, urb explicitly unlinked.
> > hfa384x_usbin_ctlx(0): ---->
> > hfa384x_usbin_ctlx(0): <----
> > hfa384x_usbin_callback(0): <----
> > submit_rx_urb(0): ---->
> > submit_rx_urb(0): <----
> > hfa384x_cmd_initialize(0): ---->
> > hfa384x_docmd(0): ---->
> > hfa384x_docmd(0): cmdreq: cmd=0x0000 parm0=0x0000 parm1=0x0000 
> parm2=0x0000
> > hfa384x_usbctlx_submit(0): ---->
> > hfa384x_usbctlxq_run(0): ---->
> > hfa384x_usbctlxq_run(0): <----
> > hfa384x_usbctlx_submit(0): <----
> > hfa384x_usbctlx_complete_sync(0): ---->
> > hfa384x_ctlxout_callback(0): ---->
> > hfa384x_ctlxout_callback(0): urb->status=0
> > hfa384x_ctlxout_callback(0): <----
> > hfa384x_usbin_callback(0): ---->
> > submit_rx_urb(0): ---->
> > submit_rx_urb(0): <----
> > hfa384x_usbin_ctlx(0): ---->
> > unlocked_usbctlx_complete(0): ---->
> > unlocked_usbctlx_complete(0): <----
> > hfa384x_usbctlxq_run(0): ---->
> > hfa384x_usbctlxq_run(0): <----
> > hfa384x_usbin_ctlx(0): <----
> > hfa384x_usbin_callback(0): <----
> > hfa384x_usbctlx_completion_task(0): ---->
> > hfa384x_usbctlx_completion_task(0): <----
> > usbctlx_get_status(0): ---->
> > usbctlx_get_status(0): cmdresult:status=0x0000 resp0=0x0000 resp1=0x0000
> > resp2=0x0000
> > usbctlx_get_status(0): <----
> > hfa384x_usbctlx_complete_sync(0): <----
> > hfa384x_docmd(0): <----
> > hfa384x_cmd_initialize(0): cmdresp.init: status=0x0000, resp0=0x0000,
> > resp1=0x0000, resp2=0x0000
> > hfa384x_cmd_initialize(0): <----
> > hfa384x_drvr_start(0): <----
> >
> >
> > After success, issue command "wlanctl-ng wlan0 lnxreq_ifstate
> > ifstate=enable" ,get:
> >
> > prism2sta_mlmerequest(0): Received mlme ifstate request
> > prism2sta_ifstate(0): Current MSD state(7), requesting(2)
> > p80211knetdev_do_ioctl(0): rx'd ioctl, cmd=35142, len=0
> > hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or 
> email
> > [email protected]
> > hfa384x_ctlxout_callback(0): urb->status=0
> > prism2sta_commsqual_defer(0): commsqual 0 65463 65463
> > p80211knetdev_do_ioctl(0): rx'd ioctl, cmd=35142, len=0
> > hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or 
> email
> > [email protected]
> > hfa384x_ctlxout_callback(0): urb->status=0
> > prism2sta_commsqual_defer(0): commsqual 0 65463 65463
> > p80211knetdev_do_ioctl(0): rx'd ioctl, cmd=35142, len=0
> > hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or 
> email
> > [email protected]
> > hfa384x_ctlxout_callback(0): urb->status=0
> > prism2sta_commsqual_defer(0): commsqual 0 65463 65463
> > p80211knetdev_do_ioctl(0): rx'd ioctl, cmd=35142, len=0
> > hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or 
> email
> > [email protected]
> > hfa384x_ctlxout_callback(0): urb->status=0
> > prism2sta_commsqual_defer(0): commsqual 0 65463 65463
> > p80211knetdev_do_ioctl(0): rx'd ioctl, cmd=35142, len=0
> > hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or 
> email
> > [email protected]
> > hfa384x_ctlxout_callback(0): urb->status=0
> > prism2sta_commsqual_defer(0): commsqual 0 65463 65463
> > p80211knetdev_do_ioctl(0): rx'd ioctl, cmd=35142, len=0
> > hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or 
> email
> > [email protected]
> > hfa384x_ctlxout_callback(0): urb->status=0
> > prism2sta_commsqual_defer(0): commsqual 0 65463 65463
> > p80211knetdev_do_ioctl(0): rx'd ioctl, cmd=35142, len=0
> > hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or 
> email
> > [email protected]
> > hfa384x_ctlxout_callback(0): urb->status=0
> > prism2sta_commsqual_defer(0): commsqual 0 65463 65463
> > p80211knetdev_do_ioctl(0): rx'd ioctl, cmd=35142, len=0
> > hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or 
> email
> > [email protected]
> > hfa384x_ctlxout_callback(0): urb->status=0
> > prism2sta_commsqual_defer(0): commsqual 0 65463 65463
> > p80211knetdev_do_ioctl(0): rx'd ioctl, cmd=35142, len=0
> > hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or 
> email
> > [email protected]
> > hfa384x_ctlxout_callback(0): urb->status=0
> > prism2sta_commsqual_defer(0): commsqual 0 65463 65463
> > p80211knetdev_do_ioctl(0): rx'd ioctl, cmd=35142, len=0
> > hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or 
> email
> > [email protected]
> > hfa384x_ctlxout_callback(0): urb->status=0
> > prism2sta_commsqual_defer(0): commsqual 0 65463 65463
> > p80211knetdev_do_ioctl(0): rx'd ioctl, cmd=35142, len=0
> > hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or 
> email
> > [email protected]
> > hfa384x_ctlxout_callback(0): urb->status=0
> > prism2sta_commsqual_defer(0): commsqual 0 65463 65463
> > p80211knetdev_do_ioctl(0): rx'd ioctl, cmd=35142, len=0
> > hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or 
> email
> > [email protected]
> > hfa384x_ctlxout_callback(0): urb->status=0
> > prism2sta_commsqual_defer(0): commsqual 0 65463 65463
> > p80211knetdev_do_ioctl(0): rx'd ioctl, cmd=35142, len=0
> 
> Can we keep this conversation on the linux-wlan mailing lists, please? 
> Other people may be
> interested, and might even be able to help too.
> 
> You can ignore the "please reboot Universe" messages. That message was 
> only put there to confirm
> whether or not an "impossible" scenario could happen in the Real World, 
> and it obviously can. To
> get rid of them completely, just recompile without debugging. And the 
> "comms-quality" polling is
> part of normal operation, and looks fine (usb->status = 0).
> 
> As for the flakiness in bringing the adapter up, it could still be a race 
> condition while enabling
> the adapter in the init scripts. Does the adapter start up and shut down 
> correctly if you run
> wlanctl-ng from the command line, once the kernel modules are safely 
> loaded?
> 
> Also, you say that you're not loading firmware any more. In which case, 
> can you tell which
> firmware versions you are currently using?
> 
> Cheers,
> Chris
> 
> Send instant messages to your online friends http://uk.messenger.yahoo.com
>

_______________________________________________
Linux-wlan-devel mailing list
[email protected]
http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-devel