Kismet Problems "bus Error" Options

[StratoS]

Ok, i installed kismet and kismet-QT via de pki files.
but when i try to start kismet_server it gives me the error "bus error"

Now i searched google, and i got a few hints, but all are the same problem, yet no where a answer.

Is there anyone who knows what is going wrong?

I have a D-link air card with a prism2 chipset.
and offcourse a c860 zaurus, with the standard zaurus image on it.

[StratoS]

mmm after doing some tests with a AP i'm getting the feeling that zaurus isn't talking that well with my D-link.

netstumbler on another box saw me as another wlan machine, but i gave no signal at all.

[StratoS]

mmm I'm getting more and more the feeling thatthe zaurus doens't like my D-link card or something.

The following info was in the dmesg screen.

CODE

pxa_pcmcia_init(0)
init_module: prism2_cs.o: 0.1.12-shp Loaded
init_module: dev_info is: prism2_cs
prism2_cs: index 0x01: Vcc 3.3, irq 39, io 0xf6000000-00xf600003f
hfa384x_coreset: hfa384x_coreset not supported on pcmcia. Use driver services COR access function instead
ident: nic h/w: id=0800c 1.0.0
ident: pri f/w: id=0x15 1.1.1
ident: sta f/w: id=0x1f 1.7.4
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=4/4
STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/12
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-MFI:ACT:role=0x01:id=0x01:var=0x02:b/t=1/1
Prism2_card SN: serial nummber
pxa_pcmcia_suspend(0)

That is all when i put in the wifi card.

then when i try to connect.
the lights of the card blinks green. (like it's sending data)

CODE

hfa38x_coreset: hfa384x_coreset not supported on pcmcia. Use driver services COR access function instead.
hfa384x_docmd_wait: hfa384x_cmd timeout(1), reg=0x8888.
hfa384x_drvr_initialize: Initialize command failed.
hfa384x_drvr_initialize: Failed, result=-110
prism2sta_initmac: prism2sta_initmac: drvr_initialize() failed, result=-110
hfa384x_docmd_wait: hfa38x_cmd timeout(1), reg=0x8888.
hfa384x_drvr_shutdown: hfa384x_drvr_shutdown: cmd_initialize failed, result=-110
prism2sta_initmac: Failed, result=-110
prism2sta_open: initmac() failed, result=-110

Is there anyone who knows the answer to what is going wrong?
I've seen people with a c860 on the forums that said they have a working D-link, so please share how you got it to work.

[stars]

Hi!

Just wondering if anyone solve this bus error thing?
5600 with the latest arm binaries and Dlink ... same errors!


Thanks!

[speculatrix]

kismet_client dumps core with cacko1.22 on my sl-c860.
it used to work, but not any more, don't know why :-(

[ken]

Ok, i installed kismet and kismet-QT via de pki files.
but when i try to start kismet_server it gives me the error "bus error"

you will need to run uclx -d on /usr/local/bin/kismet_server and kismet_client

[speculatrix]

Ok, i installed kismet and kismet-QT via de pki files.
but when i try to start kismet_server it gives me the error "bus error"

you will need to run uclx -d on /usr/local/bin/kismet_server and kismet_client

uclx command doesn't exist on my Z (cacko 1.22 full).

[inode0]

uclx command doesn't exist on my Z (cacko 1.22 full).

google and you will find it ... or you probably can just set UCL to point to some other location for /tmp so there is enough unpacking room.

John

[ken]

... or you probably can just set UCL to point to some other location for /tmp so there is enough unpacking room.

I like that. That's an even more permanent solution.

[speculatrix]

when I use strace, I find that kismet_client actually starts up and runs normally (it's definitely not a uclx binary), but crashes soon after fiddling with the terminal. I can post the strace dump if it'd be useful.