bluetooth issue again

ssl6 · 2008-01-26 01:40:28

i noticed the since the updates i just did, or something i just did broke my bluetooth mouse, i have to connect manually now again. which is fine, i just have to open a terminal once i login and connect the mouse

but i checked my config, and nothings changed there, am i the only one having this problem???

ssl6 · 2008-01-28 19:23:15

am i the only one having issues since the last update? my mouse was working fine before after rebooting, sometimes i had to turn it off and on again, but it reconnected everytime.

i had this happen before, and was skeptical for a while everytime the bluetooth stuff updated and now it broke again. i guess it forced me to fix my touchpad, but i'd like to have my mouse connect automatically again. i guess ill wait for another update. amsn did just get fixed at least

ssjlegendx · 2008-01-29 00:11:36

Hello,

I have experienced the same problem on multiple occasions. For me, at least, the fix was quite simple:

Check out the file /etc/rc.d/bluetooth in Vim or whatever text editor your prefer. Somewhere in the file (line 28 for me) you will probably see the following:

HIDD_ENABLE="false"

If so, change this to:

HIDD_ENABLE="true"

Then, for the change to take effect, you must restart your computer or -- at least -- the Bluetooth subsystem (as root or using su[do]):

/etc/rc.d/bluetooth restart

If it goes as well for you as it has for me in the past, then your mouse should automatically connect at startup once more. I'm not quite certain why Bluetooth-related updates tend to overwrite the settings stored in this file....

Last edited by ssjlegendx (2008-02-01 01:38:22)

ssl6 · 2008-01-29 01:22:14

it is set to enabled already, i checked that first

ssjlegendx · 2008-01-29 03:13:03

Hmm... Would you mind posting the contents of /etc/rc.d/bluetooth and /etc/bluetooth/hcid.conf?

I don't have extensive knowledge on this subject, but I do have a Bluetooth mouse that -- even after recent updates -- connects at startup.... Maybe I can be of some assistance.

Last edited by ssjlegendx (2008-02-01 01:40:08)

ssl6 · 2008-01-29 03:41:44

heres the /etc/rc.d/bluetooth contents

#!/bin/sh
#
# Start/stop the Bluetooth daemons
#

. /etc/rc.conf
. /etc/rc.d/functions

DAEMON_NAME="hcid"
HID2HCI_NAME="hid2hci"
SDPD_NAME="sdpd"
HIDD_NAME="hidd"
RFCOMM_NAME="rfcomm"
PAND_NAME="pand"
DUND_NAME="dund"

DAEMON_EXEC="/usr/sbin/hcid"
HID2HCI_EXEC="/usr/sbin/hid2hci"
SDPD_EXEC="/usr/sbin/sdpd"
HIDD_EXEC="/usr/bin/hidd"
RFCOMM_EXEC="/usr/bin/rfcomm"
PAND_EXEC="/usr/bin/pand"
DUND_EXEC="/usr/bin/dund"

DAEMON_ENABLE="true"
HID2HCI_ENABLE="false"
SDPD_ENABLE="false"
HIDD_ENABLE="false"
RFCOMM_ENABLE="false"
DUND_ENABLE="false"
PAND_ENABLE="false"

DAEMON_CONFIG="/etc/bluetooth/hcid.conf"
RFCOMM_CONFIG="/etc/bluetooth/rfcomm.conf"

HIDD_OPTIONS=""
DUND_OPTIONS=""
PAND_OPTIONS=""

[ -f /etc/conf.d/bluetooth ] && . /etc/conf.d/bluetooth

case "$1" in
  start)
    stat_busy "Starting bluetooth subsystem:"
    if [ "$DAEMON_ENABLE" = "true" -a -x "$DAEMON_EXEC" -a -f "$DAEMON_CONFIG" ] ; then
      stat_append " $DAEMON_NAME"
      if [ "$SDPD_ENABLE" = "true" ]; then
        $DAEMON_EXEC -f $DAEMON_CONFIG
      else
        $DAEMON_EXEC -s -f $DAEMON_CONFIG
      fi
    fi
    if [ "$HID2HCI_ENABLE" = "true" -a -x "$HID2HCI_EXEC" ] ; then
      stat_append " $HID2HCI_NAME"
      $HID2HCI_EXEC --tohci > /dev/null 2>&1 || true
    fi
    if [ "$SDPD_ENABLE" = "true" -a -x "$SDPD_EXEC" ] ; then
      stat_append " $SDPD_NAME"
      $SDPD_EXEC
    fi
    if [ "$HIDD_ENABLE" = "true" -a -x "$HIDD_EXEC" ]; then
      stat_append " $HIDD_NAME"
      $HIDD_EXEC $HIDD_OPTIONS --server
    fi
    if [ "$RFCOMM_ENABLE" = "true" -a -x "$RFCOMM_EXEC" -a -f "$RFCOMM_CONFIG" ]; then
      stat_append " $RFCOMM_NAME"
      $RFCOMM_EXEC -f $RFCOMM_CONFIG bind all
    fi
    if [ "$DUND_ENABLE" = "true" -a -x "$DUND_EXEC" -a -n "$DUND_OPTIONS" ]; then
      stat_append " $DUND_NAME"
      $DUND_EXEC $DUND_OPTIONS
    fi
    if [ "$PAND_ENABLE" = "true" -a -x "$PAND_EXEC" -a -n "$PAND_OPTIONS" ]; then
      stat_append " $PAND_NAME"
      $PAND_EXEC $PAND_OPTIONS
    fi
    add_daemon bluetooth
    stat_done
    ;;
  stop)
    stat_busy "Stopping bluetooth subsystem:"

    stat_append " $PAND_NAME"
    killall $PAND_NAME >/dev/null 2>&1

    stat_append " $DUND_NAME"
    killall $DUND_NAME >/dev/null 2>&1

    if [ -x "$RFCOMM_EXEC" ]; then
      stat_append " $RFCOMM_NAME"
      $RFCOMM_EXEC release all >/dev/null 2>&1
    fi

    stat_append " $HIDD_NAME"
    killall $HIDD_NAME >/dev/null 2>&1

    stat_append " $SDPD_NAME"
    killall $SDPD_NAME >/dev/null 2>&1

    stat_append " $DAEMON_NAME"
    killall $DAEMON_NAME >/dev/null 2>&1

    rm_daemon bluetooth
    stat_done
    ;;
  restart)
    $0 stop
    sleep 1
    $0 start
    ;;
  *)
    echo "usage: $0 {start|stop|restart}"  
esac
exit 0

and here's the /etc/bluetooth/hcid.conf content

#
# HCI daemon configuration file.
#

# HCId options
options {
    # Automatically initialize new devices
    autoinit yes;

    # Security Manager mode
    #   none - Security manager disabled
    #   auto - Use local PIN for incoming connections
    #   user - Always ask user for a PIN
    #
    security none;

    # Pairing mode
    #   none  - Pairing disabled
    #   multi - Allow pairing with already paired devices
    #   once  - Pair once and deny successive attempts
    pairing multi;

    # Default PIN code for incoming connections
    passkey "xxxx"; #seems not to be used for my mouse, after all
}

# Default settings for HCI devices
device {
    # Local device name
    #   %d - device id
    #   %h - host name
    name "BlueZ (%d)";

    # Local device class
    class 0x000100;

    # Default packet type
    #pkt_type DH1,DM1,HV1;

    # Inquiry and Page scan
    iscan enable; pscan enable;

    # Default link mode
    #   none   - no specific policy 
    #   accept - always accept incoming connections
    #   master - become master on incoming connections,
    #            deny role switch on outgoing connections
    lm accept;

    # Default link policy
    #   none    - no specific policy
    #   rswitch - allow role switch
    #   hold    - allow hold mode
    #   sniff   - allow sniff mode
    #   park    - allow park mode
    lp rswitch,hold,sniff,park;
        discovto 0;
}

FFS, i thought i checked it before, but it is set off here.

edit, just checked /etc/conf.d/bluetooth, its set on there, maybe thats what i looked at

i just corrected it to show this

DAEMON_NAME="hcid"
HID2HCI_NAME="hid2hci"
SDPD_NAME="sdpd"
HIDD_NAME="hidd"
RFCOMM_NAME="rfcomm"
PAND_NAME="pand"
DUND_NAME="dund"

DAEMON_EXEC="/usr/sbin/hcid"
HID2HCI_EXEC="/usr/sbin/hid2hci"
SDPD_EXEC="/usr/sbin/sdpd"
HIDD_EXEC="/usr/bin/hidd"
RFCOMM_EXEC="/usr/bin/rfcomm"
PAND_EXEC="/usr/bin/pand"
DUND_EXEC="/usr/bin/dund"

DAEMON_ENABLE="true"
HID2HCI_ENABLE="truec"
SDPD_ENABLE="false"
HIDD_ENABLE="true"
RFCOMM_ENABLE="false"
DUND_ENABLE="false"
PAND_ENABLE="false"

DAEMON_CONFIG="/etc/bluetooth/hcid.conf"
RFCOMM_CONFIG="/etc/bluetooth/rfcomm.conf"

HIDD_OPTIONS="--connect 00:07:61:6c:03:bb --server"
DUND_OPTIONS=""
PAND_OPTIONS=""

hoping it works

Last edited by ssl6 (2008-01-29 03:52:07)

ssjlegendx · 2008-01-29 05:14:22

Your edit looks correct to me, but -- in my case -- my mouse functions without specifying any HIDD_OPTIONS (though it seems that I first had to pair it manually for automatic connection to work later). I seem to recall many posts/guides instructing users to include such options, though, so it might be necessary in some cases.

I assume that I also enabled HIDD in /etc/conf.d/bluetooth at some point in time, but I had forgotten about it.... In my experience, Bluetooth-related updates only seem to mess with the settings in /etc/rc.d/bluetooth. When you do get this working properly, it might be a good idea to keep copies of your Bluetooth configuration files in your home directory so that you can check all the settings after any future updates.

Last edited by ssjlegendx (2008-02-01 01:44:23)

Grenshad · 2008-01-29 12:55:00

lasts updates around bluetooth now comes with a new file /etc/bluetooth/input.service, which seems to be in charge for input device, there is an autostart line in this file, maybe it could be the line you need to fix.

ssl6 · 2008-01-30 03:15:52

the autostart line is set to true in that input.service file

ssjlegendx · 2008-01-30 05:25:13

Hmm... Still not working?

Though I've been optimistic in my other posts, I'm not quite sure what else to tell you at this point. As long as HIDD_ENABLE is set to "true" in both /etc/rc.d/bluetooth and /etc/conf.d/bluetooth, it seems to me that -- given the configuration files you posted and the fact that you have manually paired the mouse at some point -- things should be connecting properly.

My final suggestion is to read over this wiki page (which you have likely done already) and follow the instructions there step-by-step -- even if you've done them before. Perhaps the update wiped out something else, too....

Last edited by ssjlegendx (2008-02-01 01:47:13)

Mr Green · 2008-01-30 06:30:19

recently the only way I can get bluetooth working is to restart it after logging in, been like that for many months now...

does hcitool scan work? at least can you see your device?

ssl6 · 2008-02-01 19:22:29

issue is that it doesnt connect automatically. i can connect manually after login no problem. it just doesnt automatically restore the connection anymore, again

Arch Linux

#1 2008-01-26 01:40:28

bluetooth issue again

#2 2008-01-28 19:23:15

Re: bluetooth issue again

#3 2008-01-29 00:11:36

Re: bluetooth issue again

#4 2008-01-29 01:22:14

Re: bluetooth issue again

#5 2008-01-29 03:13:03

Re: bluetooth issue again

#6 2008-01-29 03:41:44

Re: bluetooth issue again

#7 2008-01-29 05:14:22

Re: bluetooth issue again

#8 2008-01-29 12:55:00

Re: bluetooth issue again

#9 2008-01-30 03:15:52

Re: bluetooth issue again

#10 2008-01-30 05:25:13

Re: bluetooth issue again

#11 2008-01-30 06:30:19

Re: bluetooth issue again

#12 2008-02-01 19:22:29

Re: bluetooth issue again

Board footer