Anyone got the Socket Bluetooth 2.5G card working?

[Ethereal]

It should start logging on the next startup.

(shutdown -r now, or \"Reboot\" in QTopia)

[piggity]

i tried to restart and its still not creating a log.  Any other ideas on how to make sure this is being run?

[DrWowe]

DrWowe, still working on it. I\'ve got a contact at Ambicom now who has given me a few technical details. I just need to learn about UART stuff now and will start hacking hciattach. The hci_uart driver should be able to drive the card then.

Cool!  Thanks for the update.  It\'s hard to justify spending $90+ for the socket card, when I was able to buy the Ambicom for $30 at CompUSA.

[Ethereal]

It\'s hard to justify spending $90+ for the socket card, when I was able to buy the Ambicom for $30 at CompUSA.

You can buy the \"other\" Ambicom, which works with the bt950_cs module, for about $50 at Amazon.  (I\'m after the Socket card just b/c it doesn\'t dangle out of the CF slot...)

[Ethereal]

i tried to restart and its still not creating a log.  Any other ideas on how to make sure this is being run?

1.) Did you \"reboot,\" as opposed to \"restart qtopia\"?  The rc.d scripts only get run at startup (or when you change runlevel).

2.) Try /etc/rc.d/init.d/syslog start (as root).

3.) Does ls /var/log/message* return anything?  The syslog script (on my SL-5600) eventually archives eight levels of messages as var/log/messages.#

4.) Try ps ax | grep syslog  (It should find--in addition to itself--a running syslogd.)

[tumnus]

You also have to edit /etc/syslog.conf to get the system log going. You need to remove the \'#\' from the start of the line that also contains \'*.info;main.none....\' then reboot. But remember to disable all this afterwards as it will fill internal storage.

Can you confirm whether your Socket card is working on another computer? It could just be broken.

[piggity]

Etheral and Tumnus,

I will try this later today.  But yes I can use the socket card on a pocket PC. But I will retry to make sure something hasn\'t changed since I started to try to get it to work on the Z.  Thanks alot for your help and I\'ll be back.

[piggity]

ok, here is the info from /var/log/messages when i insert the card.  any ideas?

Apr  8 23:20:04 localhost cardmgr[173]: initializing socket 0
Apr  8 23:20:04 localhost cardmgr[173]: socket 0: Socket Bluetooth CF Card
Apr  8 23:20:04 localhost cardmgr[173]: executing: \'modprobe bm3_bcsp_cs\'
Apr  8 23:20:04 localhost cardmgr[173]: + modprobe: Can\'t locate module bm3_bcsp_cs
Apr  8 23:20:04 localhost cardmgr[173]: modprobe exited with status 255
Apr  8 23:20:04 localhost cardmgr[173]: module /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/bm3_bcsp_cs.o not available
Apr  8 23:20:05 localhost cardmgr[173]: get dev info on socket 0 failed: Resource temporarily unavailable

[tumnus]

Looks like they\'ve messed up the serial CF support to me, but I guess the missing module could be compiled once Sharp release the 6000 kernel source or maybe it could work compiled against the 5600 kernel.

[scarbone]

I\'m having the same issue with my new SL-6000, but here\'s another clue:  it seems to be trying
to load a module called: /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/bm3_bcsp_cs.o

This file doesn\'t exist, BUT
1. The compatibility list says this is the wrong driver for the Socket BT card anyway - it should be
using  hci_uart driver.
2. The hci_uart driver is on the system, but not in the /lib/modules directory

Does anyone know how to get things to point to the hci_uart driver? I tried to edit /etc/pcmcia/bluetooth.conf, but the changes were\'nt recognized.

[albertr]

Try the following:

grep bm3_bcsp_cs /etc/pcmcia/*.conf
grep bm3_bcsp_cs /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep

And see if you catch anything. This driver is probably for bluetooth 6000 model.

-albertr

[scarbone]

There were references in /etc/pcmcia/bm3.conf, but nothing in /lib/modules/.../modules.dep

I think I\'m getting the hci_uart driver now though, here\'s /var/log/mesages:

Apr 15 localhost cardmgr[6072]: socket 0: Socket Bluetooth CF Card
Apr 15 localhost cardmgr[6072]: executing: \'modprobe hci_uart\'
Apr 15 localhost cardmgr[6072]: get dev info on socket 0 failed: Resource temporarily unavailable

But \"hciconfig\" returns nothing and \"spdtool browse\" returns:
Inquiring ...
Inquiry failed

If I type: \"hciattach /dev/ttyS0 bcsp 230400\"
It sits there for a few seconds then prints:
BCSP initialization timed out

If the output to \"cardctl status\" says:

  Socket 0:
    3.3V 16-bit PC Card
     function 0: [ready]

mean that the card is at /dev/ttyS0?

[tumnus]

The card is probably still at /dev/ttyS3. It looks like the currently compiled BlueZ modules are not compatible with the 6000 kernel even though they load ok. That bm3_bcsp_cs.o kernel module may just be trying to be loaded automatically as part of the serial initialisation, which may or may not have anything to do with the problem. Until Sharp releases the kernel source, there may be nothing that we can do.

[Ethereal]

It looks like the currently compiled BlueZ modules are not compatible with the 6000 kernel even though they load ok.  Until Sharp releases the kernel source, there may be nothing that we can do.

tumnus,

What if one flashed the special kernel (v1.3, no cache workaround) onto a SL-6KL?  It\'s basically a 2.4.18 kernel for a PXA 255, no?  (Of course, if there are no modules available/compilable for Prism 3 support with this kernel, it just trades one problem for another...)  Since we know the bluez drivers work with the special kernel, this should solve the problem of module compatibility (and we\'d have a known, published source...)

[tumnus]

The 5600 kernel most probably will not work on the 6000 and I wouldn\'t advise trying it.

Although piggity seems to have got his card working as he posted in the other Socket Rev G thread. Don\'t know what\'s going on here then.