To make my system recognize this card, I had to modify my /etc/pcmcia/config file to add the following entries:
device "dtl1_cs" module "dtl1_cs" card "Socket Bluetooth CF Card" version "Socket", "CF+ Personal Network Card" bind "dtl1_cs"After the above change, my PCMCIA card services automatically load the dtl1_cs module when the card is inserted, and I have a new "hci0" device available. Running hciconfig hci0 up brings the device up, and then I can do things like hcitool scan to look for other bluetooth devices in the area.
Note: You may have to run mknod /dev/rfcomm0 c 216 0 to make an rfcomm0 device.
Warning: Although the socket card "worked" I had a problem using it with my T610 phone. I could not get data to transfer faster than 2-3KB/sec (which is annoying when GPRS supports 5.6KB/sec). After a bit of complaining, Socket was nice enough to replace my card with a "revision H" card, which uses a completely different chipset.
Perhaps around kernel 2.6.12 it will be fixed, but as of 2.6.11 it has not. If you are able to recompile your kernel, you can fix the bug yourself by using this patch, helpfully provided by Mathias Adam on the BlueZ mailing list, against the /usr/src/linux/drivers/serial/8250.c file and recompiling.
Once you have done this, the CF card is reported as a serial port (ttyS4 for me) and a simple "hciattach ttyS4 socket" command will make it work! In Mandrake, you simply put "/dev/ttyS4 socket" in your /etc/bluetooth/uart file.
During the six months between getting my socket CF card and actually getting it to work, I had been using a Zoom Bluetooth PCMCIA card which works great. I really recommend that you use that card if you just want things to work out of the box without having to patch your kernel and don't mind giving up a PCMCIA slot. I'm using the Socket card now because I like the smaller form factor and I have the CF slot on the X31.