Zoom PCMCIA Bluetooth and hciattach work only through a strange kludge
I have an IBM T23 running Slackware 10.1, with the following (relevant) items installed:
2.6.10 kernel, with Bluetooth section as follows:
# Bluetooth device drivers
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBFUSB is not set
# CONFIG_BT_HCIVHCI is not set
# CONFIG_DUMMY is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
# CONFIG_NET_SB1000 is not set
The card is recongnised on insertion as /dev/ttyS4, and cardmgr allocates a symlink /dev/bluetooth to it (instead of /dev/modem, as per my request).
* The following description is true whether hcid is running or not
I found (amongst the few references to this card on the net) that the command "hciattach /dev/bluetooth socket" would be the applicable one in my case, but on execution hciattach returns "BCSP initialization timed out". If, however, I try "hciattach /dev/bluetooth any" (or various others, including "ericsson"), it will succeed, but "hciconfig dev" shows it as "DOWN INITIALISING" or similar, IIRC. This does not change within several minutes at least.
"ps -A" shows that hciattach is still running in the background, and if I kill the process, I can then execute "hciattach /dev/bluetooth socket", and the card initialises happily, "hciconfig scan" finds my bluetooth mobile, and I can l2ping away to my hearts' content (this is the extent of my testing so far).
My questions are as follows:
1: How can I initialise the card correctly the first time round?
2: If I can't do that, would I be able to throw a script together that will do the hciattaching and killing for me?
3: Does anyone know anything about the innards of this card? Zoom doesn't acknowledge that Linux exists for this card, but knowing what the gubbons run on should help me even if you can't help with the above.
Many thanks in advance,