- I just got an Ambicom BT2000CF, the one with the yellow label, which everyone says is supposed to work. It doesn't! (pout)
- I've spent the last three hours scouring the forum for information about resolving BlueZ problems, and found nothing that seems to fit my particular issue. I did install the packages listed in this thread:
https://www.oesf.org/forums/index.php?showt...837&hl=bt950_cswhich indicated I wasn't using the right ones. I had ver e, and he specifically says to use d, so I am now. (grin)
- But that avails me not. I finally found a post that reminded me I *could* run ipkg from the command line, which was done. Here's the result:
#ipkg install bluez-zaurus_arm.ipk
Unpacking bluez-zaurus_arm.ipk
Configuring bluez-zaurus...Starting Bluetooth... modprobe: Can't locate module rfcomm
modprobe: Can't locate module 12cap
Can't get port settings: Input/output error
Can't initialize device: Input/output error
Can't open RFCOMM control socket: Address faimily not support by protocol
Done.
Done.
- So I look for and find: /home/root/modules/2.4.18-rmk7-pxa3-embedix/kernal/net/buetooth/rfcomm/rfcomm.o
- So I look for and DO NOT FIND 12cap.o.
- The only reference to this module I found on the entire OESF Forum list referred to OpenZaurus. So I'm right good and stumped.
- All of my cardctl, settings, etc are the same as those listed on the above thread EXCEPT my /etc/bluetooth/uart file contains:
"Socket", "CF+ Personal Network Card Rev 2.5":/dev/ttyS3 bcsp 23400
THAT's not right!! However, updating to read what the above link contains, for the AmbiCom card, has no effect. When I "sudo /etc/rc.d/init.d/bluetooth restart", it still can't find module 12cap, or rfcomm.
- I am using and have verified using the "18d" version of BlueZ, plus sudo, susp_resume, and susp_resume_bluez.
- Any ideas all?? I'm LOST!...