Author Topic: Bluetooth Problem On Henntges Oz 3.5.3  (Read 7274 times)

Marty

  • Newbie
  • *
  • Posts: 44
    • View Profile
Bluetooth Problem On Henntges Oz 3.5.3
« Reply #15 on: September 14, 2005, 06:05:07 pm »
The only thing I altered in /etc/initid/bluetoth was that I commented out the references to HIDD which was causing the same sort of error message that you saw appeared on my  z when I ran  "/etc/init.d/bluetooth start".
Once I did that the error message went away.

I then found that when I came out of a suspend and ran "/etc/etc/init.d/bluetooth start" the light on the card flashed but... my dial up script would'nt work.
However if I ran  "/etc/init.d/bluetooth stop" then "/etc/init.d/bluetooth start" then everything would work just fine.

I've tried modprobeing the bluecard_cs driver in the past but didnt see much happening. I found the rmmod insmod of the driver to do something (at least it told me the bluecard_cs driver was already loaded.)
I know your card uses a different driver than mine but it looks like its not being loaded properly
Maybe you should try that approach instead of modprobe. (see script)
Sorry I wish I could be more help but I'am not an expert on bluetooth.

HeavyWeaponDude

  • Newbie
  • *
  • Posts: 37
    • View Profile
Bluetooth Problem On Henntges Oz 3.5.3
« Reply #16 on: September 18, 2005, 07:51:20 pm »
Uhm...
Following your suggestions I'm going somewhere.  
It is not much pratical right now, but still it works, more or less.

I've wrote a little script:

Code: [Select]
#!/bin/sh
modprobe hci_uart
sleep 1
setserial /dev/ttyS3 baud_base 921600
hciattach /dev/ttyS3 billionton
hciconfig hci0 up
/etc/init.d/bluetooth start

It basically does what /etc/init.d/bluetooth alone didn't do: setup my card and then startup the bluetooth services. Of course I too have commented out the references to HIDD in /etc/init.d/bluetooth.

However, even if when i run it everything seems to work well ("hciconfig -a" shows the device, and "hcitool -scan" gives the proper results), I get the following message just after running it:

      BCSP initialization time out

Making some test, I found that is due to the "hciconfig hci0 up" being in the script.
If I remove it from there and run it manually, I don't get the message.
I've tried also to put some sleep time between "hciattach" and "hciconfig" in the script, but still I get the message. Any hint on this?

I can remove the card running /etc/init.d/bluetooth stop. When I re-insert it I should re-run my script. When I suspend, I have to resume the card manually, by "cardctl resume 0".

At least this way, I've to run just one command upon starting/stopping the bluetooth.
Thanks for any help so far.


***little update***

The card is somewhat unreliable. Sometimes, upon insertion, the led doesn't blink.
Even if "cardctl status" shows the card as being active, it is not.
Doing "cardctl suspend 0", waiting a couple of seconds, and then "cardctl resume 0",
makes it up. Then the script works well, and doesn't give that "BCSP initialization time out" error message.
« Last Edit: September 18, 2005, 08:18:11 pm by HeavyWeaponDude »
Zaurus SL-5500
OpenZaurus 3.5.3 + Opie 1.2 (Hentges ROM T3)