Dell bluetooth mouse won't connect at startup

Discussion in 'Installation/Configuration' started by TibetanTermite, Sep 26, 2008.

  1. TibetanTermite

    TibetanTermite New Member

    Hi all!
    I've managed to setup my bluetooth and I'm able to use it (I followed some internet guide).
    But, although the guide I followed explains how to activate the connection on every bootup, it doesn't work. I have to do it manually from the console every time.

    Some help please.
     
  2. falko

    falko Super Moderator

    Which distribution are you using, and what's the command that you have to run manually?
     
  3. TibetanTermite

    TibetanTermite New Member

    I'm sorry, I forgot add more detail.
    I'm using Debian (Lenny), kernel 2.6.25-2-686.

    The commands are:
    # hcitool scan
    # hidd --search

    It's really annoying to have to do this all the time since I've configured my /etc/default/bluetooth and /etc/bluetooth/hci.conf accordingly to detect and connect to my mouse's address at startup
     
  4. falko

    falko Super Moderator

    You can add those commands to /etc/rc.local. They will then be executed at the end of each boot process.
     
  5. TibetanTermite

    TibetanTermite New Member

    Yes, I thought about that option but, shouldn't it be enough just setting up the bluetooth 'conf' files?

    What's the point of having those files if in the end they don't do their job! Right?

    Here's an excerpt from my /etc/default/bluetooth file:

    # start bluetooth on boot?
    # compatibility note: If this variable is not found bluetooth will
    # start
    BLUETOOTH_ENABLED=1

    HID2HCI_ENABLED=1

    ############ HIDD
    #
    # HID daemon
    HIDD_ENABLED=1
    HIDD_OPTIONS="--server --search --connect MY_BLUETOOTH_ADDR"



    And my /etc/bluetooth/hci.conf :

    #
    # HCI daemon configuration file.

    # HCId options
    options {
    # Automatically initialize new devices
    autoinit yes;
    ...
    ...
    # Default PIN code for incoming connections
    passkey "0000";
    }

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

    # Local device class
    class 0x000100;

    # 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;
    }

    device MY_BLUETOOTH_ADDR {
    name“Dell BT Travel Mouse”;
    }


    I've checked services after booting and hcid is active, so I really don't know what I'm missing. Please help if possible.

    Thanks!
     
  6. falko

    falko Super Moderator

    Can you post the output of
    Code:
    ls -l /etc/init.d
    ?
     
  7. TibetanTermite

    TibetanTermite New Member

    Sure...

    $ ll /etc/init.d/
    total 456K
    -rwxr-xr-x 1 root root 3.2K 2008-06-20 14:56 acpid
    -rwxr-xr-x 1 root root 1.4K 2007-11-18 10:34 acpi-support
    -rwxr-xr-x 1 root root 8.7K 2008-06-25 10:24 alsa-utils
    -rwxr-xr-x 1 root root 1.3K 2008-03-09 20:58 anacron
    -rwxr-xr-x 1 root root 1.7K 2008-04-07 11:25 apmd
    -rwxr-xr-x 1 root root 946 2008-01-27 06:20 atd
    -rwxr-xr-x 1 root root 2.6K 2008-04-05 19:32 avahi-daemon
    -rwxr-xr-x 1 root root 1.1K 2005-10-27 14:15 binfmt-support
    -rwxr-xr-x 1 root root 2.4K 2007-12-05 14:06 bluemon
    -rwxr-xr-x 1 root root 6.6K 2008-07-20 18:34 bluetooth
    -rwxr-xr-x 1 root root 2.2K 2008-01-05 00:05 bootlogd
    -rwxr-xr-x 1 root root 2.0K 2008-07-16 19:45 bootmisc.sh
    -rwxr-xr-x 1 root root 3.0K 2008-08-12 14:50 checkfs.sh
    -rwxr-xr-x 1 root root 9.7K 2007-12-30 16:45 checkroot.sh
    -rwxr-xr-x 1 root root 7.0K 2008-09-05 18:30 clamav-daemon
    -rwxr-xr-x 1 root root 6.9K 2008-09-05 18:30 clamav-freshclam
    -rwxr-xr-x 1 root root 5.9K 2008-04-15 22:42 console-screen.sh
    -rwxr-xr-x 1 root root 2.5K 2008-07-19 10:20 cpufrequtils
    -rwxr-xr-x 1 root root 2.6K 2008-01-15 19:52 cron
    -rwxr-xr-x 1 root root 4.5K 2008-04-26 13:10 dbus
    -rwxr-xr-x 1 root root 1.5K 2008-04-06 15:56 dhcdbd
    -rwxr-xr-x 1 root root 6.5K 2008-07-19 20:22 exim4
    -rwxr-xr-x 1 root root 1.3K 2008-07-31 20:13 fancontrol
    -rwxr-xr-x 1 root root 1.5K 2008-07-18 23:10 firehol
    -rwxr-xr-x 1 root root 2.9K 2008-09-16 16:17 fuse
    -rwxr-xr-x 1 root root 2.3K 2008-09-02 12:12 gdm
    -rwxr-xr-x 1 root root 7.1K 2008-03-28 03:19 glibc.sh
    -rwxr-xr-x 1 root root 2.1K 2008-08-17 20:13 hal
    -rwxr-xr-x 1 root root 1.3K 2008-01-03 01:09 halt
    -rwxr-xr-x 1 root root 2.7K 2008-06-02 14:22 hddtemp
    -rwxr-xr-x 1 root root 11K 2008-06-03 01:36 hdparm
    -rwxr-xr-x 1 root root 2.7K 2008-05-17 00:33 hibernate
    -rwxr-xr-x 1 root root 1.3K 2006-09-12 23:31 hostname.sh
    -rwxr-xr-x 1 root root 4.2K 2008-06-27 09:21 hotkey-setup
    -rwxr-xr-x 1 root root 4.5K 2008-04-29 03:57 hwclockfirst.sh
    -rwxr-xr-x 1 root root 4.5K 2008-04-29 03:57 hwclock.sh
    -rwxr-xr-x 1 root root 2.5K 2006-09-15 20:03 ifupdown
    -rwxr-xr-x 1 root root 1.1K 2006-09-15 20:03 ifupdown-clean
    -rwxr-xr-x 1 root root 1.6K 2008-04-08 12:45 kerneloops
    -rwxr-xr-x 1 root root 3.7K 2008-07-05 21:59 keymap.sh
    -rwxr-xr-x 1 root root 1.5K 2008-01-05 00:11 killprocs
    -rwxr-xr-x 1 root root 2.0K 2008-07-15 15:44 laptop-mode
    -rwxr-xr-x 1 root root 837 2008-07-31 20:13 lm-sensors
    -rwxr-xr-x 1 root root 7.1K 2008-07-19 10:20 loadcpufreq
    -rwxr-xr-x 1 root root 1.8K 2008-04-05 01:10 module-init-tools
    -rwxr-xr-x 1 root root 620 2007-12-30 10:22 mountall-bootclean.sh
    -rwxr-xr-x 1 root root 2.0K 2008-06-06 09:03 mountall.sh
    -rwxr-xr-x 1 root root 2.2K 2008-01-01 10:24 mountdevsubfs.sh
    -rwxr-xr-x 1 root root 2.5K 2008-01-04 17:24 mountkernfs.sh
    -rwxr-xr-x 1 root root 618 2007-12-30 10:21 mountnfs-bootclean.sh
    -rwxr-xr-x 1 root root 2.3K 2008-02-29 21:27 mountnfs.sh
    -rwxr-xr-x 1 root root 1.3K 2008-01-06 11:14 mountoverflowtmp
    -rwxr-xr-x 1 root root 3.6K 2006-11-26 16:13 mtab.sh
    -rwxr-xr-x 1 root root 1.9K 2008-07-26 01:02 networking
    -rwxr-xr-x 1 root root 1.8K 2008-07-05 15:20 network-manager
    -rwxr-xr-x 1 root root 1.7K 2008-07-05 15:20 network-manager-dispatcher
    -rwxr-xr-x 1 root root 5.9K 2008-07-14 12:02 nfs-common
    -rwxr-xr-x 1 root root 1.1K 2008-07-23 11:19 nvidia-kernel
    -rwxr-xr-x 1 root root 2.3K 2008-04-20 15:30 openbsd-inetd
    -rwxr-xr-x 1 root root 2.4K 2007-08-19 15:20 pcmciautils
    -rwxr-xr-x 1 root root 2.5K 2008-08-01 13:48 policycoreutils
    -rwxr-xr-x 1 root root 2.0K 2008-06-12 12:53 portmap
    -rwxr-xr-x 1 root root 2.9K 2008-07-18 18:32 powersaved
    -rwxr-xr-x 1 root root 1.2K 2008-04-08 00:34 procps
    -rwxr-xr-x 1 root root 9.9K 2008-08-12 14:33 rc
    -rwxr-xr-x 1 root root 788 2007-12-29 22:59 rc.local
    -rwxr-xr-x 1 root root 117 2005-12-02 18:44 rcS
    -rw-r--r-- 1 root root 1.5K 2007-12-26 16:23 README
    -rwxr-xr-x 1 root root 639 2008-01-03 01:11 reboot
    -rwxr-xr-x 1 root root 941 2008-01-12 13:07 rmnologin
    -rwxr-xr-x 1 root root 5.0K 2008-07-25 12:07 rsync
    -rwxr-xr-x 1 root root 2.8K 2008-08-14 01:59 rsyslog
    -rwxr-xr-x 1 root root 2.3K 2008-05-20 09:13 sendsigs
    -rwxr-xr-x 1 root root 1.8K 2008-08-02 07:38 sensord
    -rwxr-xr-x 1 root root 590 2007-12-29 22:32 single
    -rw-r--r-- 1 root root 4.1K 2007-12-29 22:59 skeleton
    -rwxr-xr-x 1 root root 3.7K 2008-07-29 16:33 ssh
    -rwxr-xr-x 1 root root 525 2008-01-02 01:26 stop-bootlogd
    -rwxr-xr-x 1 root root 1.1K 2008-01-02 01:27 stop-bootlogd-single
    -rwxr-xr-x 1 root root 515 2008-07-06 09:17 sudo
    -rwxr-xr-x 1 root root 2.3K 2008-04-01 17:21 sysfsutils
    -rwxr-xr-x 1 root root 2.6K 2008-07-24 11:22 system-tools-backends
    -rwxr-xr-x 1 root root 7.3K 2008-08-07 01:35 udev
    -rwxr-xr-x 1 root root 1001 2008-07-31 00:55 udev-mtab
    -rwxr-xr-x 1 root root 3.2K 2008-03-02 00:14 umountfs
    -rwxr-xr-x 1 root root 2.1K 2007-12-30 10:19 umountnfs.sh
    -rwxr-xr-x 1 root root 1.5K 2008-05-29 19:50 umountroot
    -rwxr-xr-x 1 root root 1.8K 2006-09-12 23:30 urandom
    -rwxr-xr-x 1 root root 1.4K 2008-06-22 23:12 vbesave
    -rwxr-xr-x 1 root root 2.3K 2008-07-17 16:38 wpa-ifupdown
    -rwxr-xr-x 1 root root 1.8K 2008-03-24 00:26 x11-common
     
  8. falko

    falko Super Moderator

    Run
    Code:
    update-rc.d bluetooth defaults
     
  9. TibetanTermite

    TibetanTermite New Member

    Did it but I don't think anything has changed. Here's the output:

    # update-rc.d bluetooth defaults
    System startup links for /etc/init.d/bluetooth already exist.
     
  10. falko

    falko Super Moderator

    Do you see any errors when you run
    Code:
    /etc/init.d/bluetooth start
    manually?
     
  11. TibetanTermite

    TibetanTermite New Member

    Yep! I get this message:

    # /etc/init.d/bluetooth start
    Starting bluetooth: hcidSearching ...
    No devices in range or visible
    .
     
  12. TibetanTermite

    TibetanTermite New Member

    Yep! I do. Here's the message:

    # /etc/init.d/bluetooth start
    Starting bluetooth: hcidSearching ...
    No devices in range or visible
     
  13. falko

    falko Super Moderator

    Obviously it can't find your bluetooth devices. Are they switched on and close enough to the system when you boot it?
     
  14. TibetanTermite

    TibetanTermite New Member

    Hi!
    sorry, i haven't had time to post/read.

    Well, your conclusion would be correct if it weren't for the fact that my bluetooth device is inside my laptop and my mouse sits just 15-20cm away.

    I tried this sequence /etc/init.d/bluetooth restart because you suggested it, but I don't have any problems pairing my laptop and mouse when I do it manually with the commands I posted earlier.

    What I can tell you is that in my GNOME panel, i've got the Bluetooth icon which is the GNOME Bluetooth applet 0.27 and when i execute the command to restart bluetooth service, I get a bubble on screen telling me that my laptop bluetooth device has been made connectable.
    After that, I cannot connect my mouse through this applet (so it's really useless), I have to do it with hcitool and hidd commands.
     
  15. falko

    falko Super Moderator

    I don't know why this happens, so I'd add the commands to /etc/rc.local.
     
  16. TibetanTermite

    TibetanTermite New Member

    OK, I'll try the command in /etc/rc.local and post the results...
     
  17. TibetanTermite

    TibetanTermite New Member

    Well, I tried, but no luck.
    I used hcitool and hidd in /etc/rc.local but nothing... Is this the correct file to use for Debian distro? I'm not really sure.
     
  18. falko

    falko Super Moderator

    I'd try the full paths for hcitool and hidd in /etc/rc.local.
     
  19. TibetanTermite

    TibetanTermite New Member

    Ok, thanks! I'll try it that way...
     
  20. TibetanTermite

    TibetanTermite New Member

    Great! It worked.
    OK, thanks for the helpful hints and all assistance Falko.
    I'm still a bit unsatisfied, I must admit. I don't like to use rc.local to solve problems, considering Debian/Linux provides Bluetooth software and drivers to configure it all...
    Anyway, thanks a lot!
     

Share This Page