> >0.2.1-pre23 is very old. Compiling 0.2.2 for yourself
> >should not be hard, and contains many many fixes.
> >
>
> Sure, but I used 0.2.1-pre21, because this was simple available on my
> gentoo installation. I'wasn't seeking for the newest. ;-) (and I don't
> know if version 0.2.2 will handle my problem in a better way? see below)
>
You really will be much better off with the newest - alot
of the sensitivity to different types of hub chip etc.
probably dissappear when you upgrade.
> I think, my crash is connected with the fact, that I use an
> Intel-USB-controller, I read, that such make trouble sometimes,
> especially with the reset-feature on loading the module.
I think the mention of the reset feature is probably
old and no longer applicable if you are in a 2.6 kernel
with the latest driver.
>
> Here are the content from /proc/net/p80211/wlan0/nsd resp. wlandev:
>
> nsd:
> # prism2_prism2_usb version 0.2.1-pre23 (Tue Sep 13 19:56:45 CEST 2005)
> '$Id: prism2sta.c,v 1.3 2004/04/20 14:55:47 solomon Exp $'
>
> # nic h/w: id=0x00 0.0.0
> # pri f/w: id=0x00 0.0.0
> # ap f/w: id=0x00 0.0.0
>
Yep this doesn't look good, but may not be the flash -
it could be that the driver failed to talk to the card
properly and so this information hasn't made it into
the driver data structures.
> It looks so , as at least on area in flash is erased and so the stick
> can't work. The next is a piece of syslog o plug in the stick and trying
> 'wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable':
> Sep 16 15:34:59 camstation usb 1-1: new full speed USB device using
> uhci_hcd and address 2
> Sep 16 15:35:03 camstation prism2usb_init: prism2_usb.o: 0.2.1-pre23 Loaded
> Sep 16 15:35:03 camstation prism2usb_init: dev_info is: prism2_usb
> Sep 16 15:35:03 camstation usbcore: registered new driver prism2_usb
> Sep 16 15:35:04 camstation net.agent[5575]: add event not handled
> Sep 16 15:37:37 camstation ident: nic h/w: id=0x8026 1.0.0
> Sep 16 15:37:37 camstation ident: pri f/w: id=0x15 1.1.2
> Sep 16 15:37:37 camstation hfa384x_dorrid: RID len mismatch, rid=0xfd20
> hlen=8 fwlen=-2
> Sep 16 15:37:37 camstation prism2sta_getcardinfo: Failed to retrieve
> STAIDENTITY
> Sep 16 15:37:37 camstation prism2sta_getcardinfo: Failed, result=-61
> Sep 16 15:37:37 camstation prism2sta_ifstate: prism2sta_getcardinfo()
> failed,result=-61
>
> Intresting in syslog is, that there nic id and fw id is found, but not
> in nsd file!
>
Communication is breaking down here, at an unusual time.
Again the latest driver may help as the handling of this
kind of communication is more robust in the latest version.
> I think, it can be only the content of flash, which is destroyed. On
> windows box this stick works with the normal dlink drivers! It knows his
> MAC, but, I think it forgots his serial id (but this is, I think not
> really necessary and I can set it from this, what's written on the stick)
>
If it works on Windows, I would imagine that the card is
basically okay and the flash not totally messed up (can't
see how it would work even on Windows if flash was corrupted).
> Maybe it's to repair, if I can find the right files for flashing the
> stick again, but I can't find a right pda file for this stick and maybe
> it's necessary to have init software hex file (CIS-hex?) and the right
> pairing of primary and station software (for station software I have
> only a ram hex file, maybe anewer ones as flash hex file will help, but
> then I must know, what's the right primary software and also the pda
> file) Maybe sombody will have this informations for me and where I get
> such files.
>
Again, if it works on windows then you should be able
to easily re-flash on windows. The websites previously
quoted give info on how to do that, and the windows flash
program is very good at vetting your proposed flash file
first. I can't see you need to worry about pda etc etc.
>From the websites you can download what you need, and use
the windows flash program. There is no need to merge
files first or anything.
Karl
-----------------------------------------
Email sent from www.ntlworld.com
Virus-checked using McAfee(R) Software
Visit www.ntlworld.com/security for more information
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.