Re: WUSB11 2.5 and Fedora problems

Thanks for the suggestions.

I installed the latest windows driver which may have flashed it, I'm
not so sure though. I'm reluctant to upload a specific driver that I
find on the net because I have no idea if it's correct.

I have made some progress under linux. I still get the same messages
but I tried the 1 second thing and I've poked and prodded with
prism2dl, prism2_srec and

wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable

the link light is now flashing and dmesg is full of

hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or
email [email protected]
hfa384x_ctlxout_callback(0): urb->status=0
prism2sta_mlmerequest(0): Received mibget request
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or
email [email protected]
hfa384x_ctlxout_callback(0): urb->status=0
prism2sta_mlmerequest(0): Received commsquality request

interesting messages :)

F


On 12/16/05, [email protected]
<[email protected]> wrote:
> Communication with your card seems to be breaking down, but
> it is not obvious why. There is a thread from previous
> months that suggests inserting a sleep 1 in one of the
> scripts which many have found to help.
>
> The other thing I notice is that the flash firmware on
> your card looks really old - you might want to consider
> flashing it to something newer (I would recommend doing
> this in Windows though if you can).
>
> Karl
>
>
> >
> > I'm trying without success to get this to work. I have 2 boxes one is
> > FC3, the other FC4, kernel versions
> >
> > 2.6.12-1.1381_FC3
> > 2.6.14-1.1644_FC4
> >
> > On the FC4 box, plugging in gives me
> > Dec 14 18:36:35 vivo kernel: usb 2-1: new full speed USB device using
> > ohci_hcd and address 7
> > Dec 14 18:36:35 vivo kernel: usb 2-1: config 1 has an invalid
> > interface number: 1 but max is 0
> > Dec 14 18:36:35 vivo kernel: usb 2-1: config 1 has no interface number 0
> > Dec 14 18:36:36 vivo kernel: prism2usb_init: prism2_usb.o: 0.2.3 Loaded
> > Dec 14 18:36:36 vivo kernel: prism2usb_init: dev_info is: prism2_usb
> > Dec 14 18:36:36 vivo kernel: usbcore: registered new driver prism2_usb
> > Dec 14 18:36:38 vivo kernel: hfa384x_usbctlx_complete_sync: CTLX[1]
> > error: state(Request failed)
> > Dec 14 18:36:38 vivo wlan.agent[26909]: Unknown prism2 hardware type
> > (), assuming SSF
> > Dec 14 18:36:38 vivo wlan.agent[26909]: Firmware failed to load for device wlan0
> > Dec 14 18:36:38 vivo wlan.agent[26909]: WLAN Could not bring up wlan0
> > Dec 14 18:36:38 vivo kernel: hfa384x_drvr_start: cmd_initialize()
> > failed, result=-5
> > Dec 14 18:36:38 vivo kernel: prism2sta_ifstate: hfa384x_drvr_start()
> > failed,result=-5
> >
> > then rmmod and modprobe with prism_doreset=1 gives me
> >
> > Dec 14 18:40:00 vivo kernel: prism2usb_init: prism2_usb.o: 0.2.3 Loaded
> > Dec 14 18:40:00 vivo kernel: prism2usb_init: dev_info is: prism2_usb
> > Dec 14 18:40:00 vivo kernel: usb 2-1: reset full speed USB device
> > using ohci_hcd and address 7
> > Dec 14 18:40:00 vivo kernel: usbcore: registered new driver prism2_usb
> > Dec 14 18:40:01 vivo crond(pam_unix)[27053]: session opened for user
> > root by (uid=0)
> > Dec 14 18:40:01 vivo kernel: PDA Read from 0x007f0000 in EXTDS space.
> > Dec 14 18:40:01 vivo kernel: PDA Read from 0x007f0000 in EXTDS space.
> > Dec 14 18:40:01 vivo crond(pam_unix)[27052]: session opened for user
> > root by (uid=0)
> > Dec 14 18:40:01 vivo kernel: Writing 4096 bytes to ram @0x7e2ffe
> > Dec 14 18:40:01 vivo kernel: Writing 4096 bytes to ram @0x7e3ffe
> > Dec 14 18:40:01 vivo crond(pam_unix)[27052]: session closed for user root
> > Dec 14 18:40:01 vivo kernel: Writing 4096 bytes to ram @0x7e4ffe
> > Dec 14 18:40:01 vivo kernel: Writing 4096 bytes to ram @0x7e5ffe
> > Dec 14 18:40:01 vivo kernel: Writing 4096 bytes to ram @0x7e6ffe
> > Dec 14 18:40:01 vivo kernel: Writing 4096 bytes to ram @0x7e7ffe
> > Dec 14 18:40:01 vivo kernel: Writing 4096 bytes to ram @0x7e8ffe
> > Dec 14 18:40:01 vivo kernel: Writing 4096 bytes to ram @0x7e9ffe
> > Dec 14 18:40:01 vivo kernel: Writing 4096 bytes to ram @0x7eaffe
> > Dec 14 18:40:01 vivo kernel: Writing 4096 bytes to ram @0x7ebffe
> > Dec 14 18:40:01 vivo kernel: Writing 4096 bytes to ram @0x7ecffe
> > Dec 14 18:40:01 vivo kernel: Writing 4096 bytes to ram @0x7edffe
> > Dec 14 18:40:01 vivo kernel: Writing 3010 bytes to ram @0x7eeffe
> > Dec 14 18:40:01 vivo kernel: Writing 416 bytes to ram @0x7efc20
> > Dec 14 18:40:01 vivo kernel: Writing 16 bytes to ram @0x7efdd0
> > Dec 14 18:40:01 vivo kernel: Writing 4044 bytes to ram @0x7f0800
> > Dec 14 18:40:01 vivo kernel: Writing 3288 bytes to ram @0x7fe000
> > Dec 14 18:40:01 vivo kernel: ident: nic h/w: id=0x8010 1.0.0
> > Dec 14 18:40:01 vivo crond(pam_unix)[27053]: session closed for user root
> > Dec 14 18:40:03 vivo kernel: hfa384x_usbctlx_complete_sync: CTLX[3]
> > error: state(Request failed)
> > Dec 14 18:40:03 vivo kernel: prism2sta_getcardinfo: Failed to retrieve
> > PRIIDENTITY
> > Dec 14 18:40:03 vivo kernel: prism2sta_getcardinfo: Failed, result=-5
> > Dec 14 18:40:03 vivo kernel: prism2sta_ifstate:
> > prism2sta_getcardinfo() failed,result=-5
> > Dec 14 18:40:05 vivo kernel: hfa384x_usbctlx_complete_sync: CTLX[1]
> > error: state(Request failed)
> > Dec 14 18:40:05 vivo wlan.agent[27022]: Failed to enable the device,
> > resultcode= implementation_failure .
> > Dec 14 18:40:05 vivo wlan.agent[27022]: WLAN Could not bring up wlan0
> >
> > Similar results for FC3.
> >
> > I got this device working a long time ago with maybe FC1 or something
> > so it is functional.
> >
> > Any ideas? Is there more info I can supply?
> >
>
>
> -----------------------------------------
> Email sent from www.ntlworld.com
> Virus-checked using McAfee(R) Software
> Visit www.ntlworld.com/security for more information
>
>