1
Sharp ROMs / Anycom Cf-300 Bluetooth On Cacko 1.21b
« on: November 25, 2004, 01:18:42 am »
I'm having problems getting an AnyCom CF-300 bluetooth card to be recognized by Cacko 1.21b, on an 860. I did a fresh install of the ROM (with the hotfix applied) just in case. At first I was getting nothing at all when I inserted the card, but a related ZUG post (with no resolution, sadly) suggested adding the following lines to /etc/pcmcia/bluetooth.conf:
card "LSE139 Bluetooth Compact Flash Card"
manfid 0x0264, 0x000b
bind "bluecard_cs"
That improved things, and the card is recognized as a new CF Bluetooth card upon insertion, and the card light goes on (though it goes back off after a few seconds). I thought I was homefree, but no dice. Running hciconfig shows:
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
So the address is all zeros. That seems to be the stumbling block.
cardctl ident gives:
product info: "BTCFCARD", "LSE139"
manfid: 0x0264, 0x000b
when I do an "sdptool browse" I get:
Inquiring...
Inquiry failed
But I assume that's because the address for the card is showing up as 0's, which is the root of the problem.
BlueZ compatibility page says this card is supported. Any ideas?
card "LSE139 Bluetooth Compact Flash Card"
manfid 0x0264, 0x000b
bind "bluecard_cs"
That improved things, and the card is recognized as a new CF Bluetooth card upon insertion, and the card light goes on (though it goes back off after a few seconds). I thought I was homefree, but no dice. Running hciconfig shows:
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
So the address is all zeros. That seems to be the stumbling block.
cardctl ident gives:
product info: "BTCFCARD", "LSE139"
manfid: 0x0264, 0x000b
when I do an "sdptool browse" I get:
Inquiring...
Inquiry failed
But I assume that's because the address for the card is showing up as 0's, which is the root of the problem.
BlueZ compatibility page says this card is supported. Any ideas?