Socket Cf Bluetooth Ersion F Works In 6k?

[Nexus7]

I've used the following package, per the instructions in the HOWTO.
   bluez-zaurus_2.3-2.4.18d_arm.ipk

Actually, I also tried with packages downloaded from the BlueZ site. So far, the Socket CF Bluetooth version F card is identified correctly by "cardctl ident". However the dtl1_cs kernel module is not loaded automatically when the card is inserted. When I modprobe dtl1_cs, it remains unused. There is no diagnostic info in dmesg. So seeking reports of using this card successfully on a 6k, and the environment you're using.

Also, how do I increase the logging level? Seems like dmesg doesn't record most of the interesting activity that would be useful for diagnosing these things.

[Nexus7]

Fixed. Folllowing is the post which helped.
"
DrWowe     
Posted: May 8 2004, 12:49 AM
I've found the problem with the bluez drivers. There is a file /etc/pcmcia/bm3.conf that already contains driver mappings for various bluetooth cards. This file conflicts with the bluez driver mappings, and to make matters worse, the kernel modules refered to by bm3.conf don't seem to exist on the 6000L.

The fix is simple: Just delete the file, or move it out of the way.
"

I searched in the pcmcia directory for the device IDs (0x0104, 0x009f) and didn't find the conflict; because they used the names (Socket, CF+ Personal Network Card).

Thanks DrWowe.