orinoco and prism2

[gen2]

I used some other rom (cacko i think) a few days back and it bound prism2 to my card. Pdaxrom seems to use orinoco instead (using wcf12). Should I be using prism2? Is one better for kismet than the other? How do I install prism2 driver?

thanks!

[rgrep]

I also have a Linksys WCF12 and I have modified my pdaXrom config to use the hostap driver.  I find that it works better with kismet (although I am restricted to only using the US channels, otherwise iwconfig gives an error).  I explain how to change the config in this post:

https://www.oesf.org/forums/inde...indpost&p=44759

BTW, pdaXrom doesn't include the prism2 module so you'd need to compile this yourself if you want to use it.  HostAP is, in my opinion, the best Prism2-chipset driver anyway, and it should also allow you to setup your Zaurus as a wireless Access Point.

[gen2]

https://www.oesf.org/forums/inde...indpost&p=44759

BTW, pdaXrom doesn't include the prism2 module so you'd need to compile this yourself if you want to use it.  HostAP is, in my opinion, the best Prism2-chipset driver anyway, and it should also allow you to setup your Zaurus as a wireless Access Point.

Sounds good to me!

I've done the switch to hostap as per the link instructions, but now kismet fails with: "FATAL: Failed to set channel 11 22:Invalid argument", which is weird, cause it worked fine with orinoco, and weirder, cause I can
"iwconfig wlan0 channel 11"
and it works fine. Confused...
Any ideas? Thanks!!!

[Laze]

Im beginning to suspect thats because of settings written to default profile. :-( Try setting cardctl scheme resume and try running - or making a new profile in lan & wireless config tool and set it up total open networking and then try kismet.

[gen2]

Im beginning to suspect thats because of settings written to default profile. :-( Try setting cardctl scheme resume and try running - or making a new profile in lan & wireless config tool and set it up total open networking and then try kismet.

# cardctl scheme resume

produces same symptoms, subsequent run of kismet gives same error. I deleted channel 11 from the kismet.conf channel list, and it threw the same error, but with the next available channel. Seems to implicate channel-hopping in general...

Also set up a new profile -- I think what you mean by "total open networking" is to leave every entry blank (?)...I did that, loaded it, and still no change...

# kismet -X

does work

thx