Anycom Bluetooth CF-2000 problems on cacko 1.21b, card is not being recognized Options

[phunkhy]

Hello Zaurus community,

I'm absolutely desperate about my Anycom CF-2000 bluetooth card (OXTLSE039). At first glance everything is fine. I insert it and then the led is turned on for a while. But then the card isn't working. I've read all threads about it I could find, but I didn't find any similar problem. It simply has no MAC address.

I have a Zaurus SL-C860, cacko 1.21b, 512MB SD. Please help!!!

Thanks

Some output:

# hciconfig -a
hci0: Type: PCCARD
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN INIT RUNNING
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:1 errors:0
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DH1 HV1
Link policy:
Link mode: SLAVE ACCEPT

# cat /var/lib/pcmcia/stab
Socket 0: LSE039 Bluetooth Compact Flash Card
0 bluetooth bluecard_cs 0 hci0
Socket 1: empty

# cardctl ident
Socket 0:
product info: "WSS", "LSE039"
manfid: 0x0264, 0x0008
function: 6 (network)
Socket 1:
no product info available

syslog output after inserting the card:
Aug 4 17:01:56 localhost cardmgr[157]: initializing socket 0
Aug 4 17:01:56 localhost cardmgr[157]: socket 0: LSE039 Bluetooth Compact Flash Card
Aug 4 17:01:57 localhost cardmgr[157]: executing: 'modprobe bluecard_cs'
Aug 4 17:01:58 localhost cardmgr[157]: executing: './bluetooth start hci0'
Aug 4 17:01:58 localhost /sbin/hotplug: no runnable /etc/hotplug/bluetooth.agent is installed
Aug 4 17:01:58 localhost kernel: BlueZ L2CAP ver 2.3 Copyright © 2000,2001 Qualcomm Inc
Aug 4 17:01:58 localhost kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Aug 4 17:01:58 localhost kernel: BlueZ RFCOMM ver 1.1
Aug 4 17:01:58 localhost kernel: Copyright © 2002 Maxim Krasnyansky <maxk@qualcomm.com>
Aug 4 17:01:58 localhost kernel: Copyright © 2002 Marcel Holtmann <marcel@holtmann.org>
Aug 4 17:01:59 localhost hcid[3675]: HCI daemon ver 2.4 started
Aug 4 17:01:59 localhost bluetooth: hcid startup succeeded
Aug 4 17:01:59 localhost bluetooth: sdpd startup succeeded
Aug 4 17:02:00 localhost cardmgr[157]: + Starting Bluetooth... Done.
Aug 4 17:02:09 localhost hcid[3680]: Can't init device hci0. Connection timed out(110)

[maslovsky]

I can't tell what's wrong. This card should be supported by the drivers. I'm currently trying to get one of these cards to be able to test with the ROM.

[phunkhy]

I can't tell what's wrong. This card should be supported by the drivers. I'm currently trying to get one of these cards to be able to test with the ROM.

Thanks for quick reply. Might be be also the card itself as I bought it second hand on ebay. I'll try it with an pcmcia adaptor with my friend's notebook and will post the result.

Anyway cacko is the best qtopia rom - thanks for this superb work.

[chyang]

It seems that my Billinton BT card also has this issue.
hci0: Type: PCCARD
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:3196 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DH1 HV1
Link policy:
Link mode: SLAVE ACCEPT

[maslovsky]

Billnton bluetooth cards are not supported:

http://www.bluez.org/hardware.html

[phunkhy]

So, yesterday I've tested my card with the notebook ofd my friend under Windows XP with the drivers from the anycom website and it doesn't work either. The hardware information shows 00:00:00:00:00:00 exactly as the Z. So it looks like the card is broken. Well, 32 € for nothing... Have to get another try.

Thanks for helping anyway.

[chyang]

Comfort.
Can your WinXP machine find it?
You can see whether you can upgrade the firmware or not. I have upgraded mine, but still result in failure.

[phunkhy]

The WinXP machine found it, reported it as Anycom LSE039 bluetooth adaptor. The Hardware was present in the device manager with a valid driver. I could even turn the card's power on and off with the driver's tray applet. It just got stuck during the initialization of the card and it showed the 00:00:00:00:00:00.

This is all pretty much the same behaviour as on the Z. So, I'm quite sure that my card is broken.