Skip to contentSkip to conversation

Bluetooth mouse on openSUSE 10.2 needs rootpassword on every reconnect

Bluez-users Håvar Nielsen 2 participants 4 messages Jan 22, 2007 – Jan 23, 2007 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear all,

I need some help with my bluetooth mouse.

I just went from ubuntu to openSuSE on my laptop. Everything except for the bluetooth mouse is working.

I have tried a lot of approaches really, but none seem to work. No matter what I do, I have to use the command sudo hidd --connect ... to make my mouse connect to the computer or vice versa (computer to mouse) every time I want to use the mouse. - That means I also have to type the root password each time I want to use the mouse.

On ubuntu this was really as simple as adding a line with 'hidd
- --server' in /etc/rc.local. Then after I had connected my mouse with the hidd --connect command once, it always reconnected by itself, even after restarts and such.

This approach doesn't seem to work in openSuSE however, even when using the ubuntu (default) /etc/bluetooth/hcid.conf file. Why is that?

In SuSE, I must go to a terminal, become root and do:
hidd --server
hidd --connect 00:07:61:4a:1b:ef
(press reset button on the mouse) -result-> Mouse connects and works. Now, if I turn my mouse off for five seconds and turn it back on again, I have to type another hidd --connect command as root for the mouse to reconnect.

I have attached the SuSE bluetooth init script and the bluetooth.conf file used by the bluetooth init script in hopes it can be of use to anyone who might answer this request.

Some more technical details is found below my signature.

With hopes of help...

Regards,
Håvar Nielsen

Installed bluez & bluetooth packages:
bluez-firmware 1.2-20
bluez-gnome 0.6-7
bluez-hcidump 1.33-8
bluez-libs 3.7-14.1
bluez-test 3.7-29
bluez-utils 3.7-29.2
gnome-bluetooth 0.8.0-26
yast2-bluetooth 2.14.0-33

/etc/init.d/bluetooth status
Checking service bluetooth (enabled) :

      hcid  (activated)      running
      hidd  (activated)      running
   hid2hci  (activated)
      sdpd  (activated)      running

opd unused
rfcomm (activated)
pand unused
dund unused

hcitool dev

	Devices:
        	hci0    00:10:C6:9E:0A:D7

hcitool inq
Inquiring ...

All init-parameters for these profiles can be found in the attached bluetooth.conf file.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFFtNIhurImHjOFF6oRAlpKAJ4iTVYRDheNU3MqGIRfiNXqMksrAwCcDBn5 TAw0jDaWK1e1pZX21rWS4hc=
=HTlD
-----END PGP SIGNATURE-----

#! /bin/sh
# Copyright (c) 1995-2003 SuSE Linux AG, Nuernberg, Germany. # All rights reserved.
#
# Author: Stefan Behlert <[email protected]>, based on
# proposals and templates from Marcel Holtmann
# and Stefan Reinauer <[email protected]>
#

# /etc/init.d/bluetooth
#   and its symbolic link
# /(usr/)sbin/rcbluetooth
#
### BEGIN INIT INFO
# Provides:          bluetooth
# Required-Start:    $syslog
# X-UnitedLinux-Should-Start: dbus
# Required-Stop:     $syslog
# X-UnitedLinux-Should-Stop:
# Default-Start:     3 5
# Default-Stop:      0 1 2 6
# Short-Description: Bluetooth protocol stack services
# Description:       Bluetooth protocol stack services
#	This services is needed to use bluetooth devices
### END INIT INFO
# 

# Check for existence of needed config file and read it BLUETOOTH_CONFIG=/etc/sysconfig/bluetooth
test -r $BLUETOOTH_CONFIG || exit 6
. $BLUETOOTH_CONFIG

. /etc/rc.status

# Reset status of this service
rc_reset

# check_service "hcid" "$HCI_START" "$HCI_DAEMON"
function check_service()

{
	if [ "$2" = "yes" ]; then
		printf "%10s  (%s)" "$1" "activated"
		/sbin/checkproc $3 || rc_failed 7
		rc_status -v
	else
		printf "%10s" "$1"
		/sbin/checkproc $3 || rc_failed 3
		rc_status -v
	fi
}
# we use '/var/lib/bluetooth/opd' as default-path for the opd. we make sure, the dir
# exists and we don't want to have the dir growing and growing
function check_opd_default_path()
{
	if [ ! -e /var/lib/bluetooth/opd ] && [ ! -d /var/lib/bluetooth/opd ]; then
		return
	fi
	# I don't like -exec
	# remove all files older than 3 days
	find /var/lib/bluetooth/opd/ -type f -a -mtime +3 |xargs -I{} /bin/rm {};
}

case "$1" in

    start)
	echo -n "Starting bluetooth: "

	# not generic, because that was to much overhead
	if [ $HID_START = "yes" ] && [ -x "$HID_DAEMON" ] ; then
		#/sbin/checkproc $HID_DAEMON || $HID_DAEMON $HID_DAEMON_ARGS
		$HID_DAEMON $HID_DAEMON_ARGS
		echo -n " hidd"
	fi
	if [ $HID2HCI_START = "yes" ] && [ -x "$HID2HCI_DAEMON" ] ; then
		$HID2HCI_DAEMON $HID2HCI_DAEMON_ARGS > /dev/null 2>&1
		echo -n " hid2hci"
	fi
	if [ $HCI_START = "yes" ] && [ -x "$HCI_DAEMON" ] ; then
		/sbin/checkproc $HCI_DAEMON || $HCI_DAEMON  $HCI_DAEMON_ARGS
		echo -n " hcid"
	fi
	if [ $SDP_START = "yes" ] && [ -x "$SDP_DAEMON" ] ; then
		/sbin/checkproc $SDP_DAEMON || $SDP_DAEMON $SDP_DAEMON_ARGS
		echo -n " sdpd"
	fi
	if [ $OPD_START = "yes" ] && [ -x "$OPD_DAEMON" ] ; then
		check_opd_default_path
		/sbin/checkproc $OPD_DAEMON || $OPD_DAEMON $OPD_DAEMON_ARGS
		echo -n " opd"
	fi
	if [ $RFCOMM_START = "yes" ] && [ -x "$RFCOMM_DAEMON" ] ; then
		$RFCOMM_DAEMON $RFCOMM_DAEMON_ARGS
		echo -n " rfcomm"
	fi
	if [ $PAND_START = "yes" ] && [ -x "$PAND_DAEMON" ] ; then
		/sbin/checkproc $PAND_DAEMON || $PAND_DAEMON $PAND_DAEMON_ARGS
		echo -n " pand"
	fi
	if [ $DUND_START = "yes" ] && [ -x "$DUND_DAEMON" ] ; then
		/sbin/checkproc $DUND_DAEMON || $DUND_DAEMON $DUND_DAEMON_ARGS
		echo -n " dund"
	fi

	rc_status -v
	;;
    stop)
	echo -n "Shutting down bluetooth ("

	if [ -x $DUND_DAEMON ]; then
		/sbin/killproc -TERM $DUND_DAEMON && echo -n " dund"
	fi
	if [ -x $PAND_DAEMON ]; then
		/sbin/killproc -TERM $PAND_DAEMON && echo -n " pand"
	fi
	if [ -x $RFCOMM_DAEMON ]; then
		/sbin/killproc -TERM $RFCOMM_DAEMON && echo -n " rfcomm"
	fi
	if [ -x $OPD_DAEMON ]; then
		/sbin/killproc -TERM $OPD_DAEMON && echo -n " opd"
	fi
	if [ -x $HID2HCI_DAEMON ]; then
		/sbin/killproc -TERM $HID2HCI_DAEMON && echo -n " hid2hci"
	fi
	if [ -x $HID_DAEMON ]; then
		/sbin/killproc -TERM $HID_DAEMON && echo -n " hidd"
	fi
	if [ -x $SDP_DAEMON ]; then
		/sbin/killproc -TERM $SDP_DAEMON && echo -n " sdp"
	fi
	if [ -x $HCI_DAEMON ]; then
		/sbin/killproc -TERM $HCI_DAEMON && echo -n " hcid"
	fi
	echo -n ")"
	rc_status -v
	;;
    try-restart)
	$0 status >/dev/null &&  $0 restart
	rc_status
	;;
    restart)
	$0 stop
	$0 start
	rc_status
	;;
    force-reload)
	echo -n "Reload service BLUETOOTH "
	$0 stop  &&  $0 start
	rc_status
	;;
    reload)
	rc_failed 3
	rc_status -v
	;;
    status)
	echo -n "Checking service bluetooth "
	if [ $START_SERVICES = 'no' ] ; then
		echo "(disabled) :"
	else
		echo "(enabled) :"
	fi;
	check_service "hcid"	"$HCI_START"	"$HCI_DAEMON"
	check_service "hidd"	"$HID_START"	"$HID_DAEMON"
	check_service "hid2hci"	"$HID2HCI_START"	"$HID2HCI_DAEMON"
	check_service "sdpd"	"$SDP_START"	"$SDP_DAEMON"
	check_service "opd"	"$OPD_START"	"$OPD_DAEMON"
	check_service "rfcomm"	"$RFCOMM_START"	"$RFCOMM_DAEMON"
	check_service "pand"	"$PAND_START"	"$PAND_DAEMON"
	check_service "dund"	"$DUND_START"	"$DUND_DAEMON"
	if [ $START_SERVICES = 'no' ] ; then
		rc_failed 3
	else
		rc_failed 0
	fi;

	;;
    probe)
	## Optional: Probe for the necessity of a reload, print out the
	## argument to this init script which is required for a reload.
	## Note: probe is not (yet) part of LSB (as of 1.2)
	# test /etc/FOO/FOO.conf -nt /var/run/FOO.pid && echo reload
	;;
    *)
	echo "Usage: $0 {start|stop|status|try-restart|restart|force-reload|reload|probe}"
	exit 1
	;;

esac
rc_exit

############ general
## Path: Hardware/Bluetooth
## Description: General settings for the Bluetooth device, if set to 'yes' bluetooth is started when hotplug reports 'added bluetooth device'
## Type: yesno
## Default: no
## ServiceRestart: bluetooth

START_SERVICES="yes"

## Path: Hardware/Bluetooth
## Description: General settings for the Bluetooth system, if set to 'yes' bluetooth is stopped when a hotplug records 'removed bluetooth device', no matter if there are still active devices left
## Type: yesno
## Default: no
## ServiceRestart: bluetooth

ALWAYS_STOP_SERVICES="no"

############ HCID

## Path: Hardware/Bluetooth
## Description: Start responsible demon for managing Bluetooth hciX-devices
## Type: yesno
## Default: yes
## ServiceRestart: bluetooth
HCI_START="yes"

## Path: Hardware/Bluetooth
## Description: Set responsible demon for managing Bluetooth hciX-devices
## Type: list("/usr/sbin/hcid","")
## Default: "/usr/sbin/hcid"
## ServiceRestart: bluetooth
HCI_DAEMON="/usr/sbin/hcid"

## Path: Hardware/Bluetooth
## Description: Arguments for hci-demon
## Type: string("-f /etc/bluetooth/hcid.conf")
## Default: "-f /etc/bluetooth/hcid.conf"
## ServiceRestart: bluetooth

HCI_DAEMON_ARGS=" -f /etc/bluetooth/hcid.conf"

############ SDP

## Path: Hardware/Bluetooth
## Description: Start responsible demon for incoming service queries
## Type: yesno
## Default: yes
## ServiceRestart: bluetooth
SDP_START="yes"

## Path: Hardware/Bluetooth
## Description: Set responsible demon for incoming service queries
## Type: list("/usr/sbin/sdpd","")
## Default: "/usr/sbin/sdpd"
## ServiceRestart: bluetooth SDP_DAEMON="/usr/sbin/sdpd"

## Path: Hardware/Bluetooth
## Description: Arguments for sdp-demon start
## Type: list("","-n")
## Default: ""
## ServiceRestart: bluetooth
SDP_DAEMON_ARGS=""

############ OPD

## Path: Hardware/Bluetooth
## Description: Start responsible demon for obex push queries
## Type: yesno
## Default: no
## ServiceRestart: bluetooth
OPD_START="no"

## Path: Hardware/Bluetooth
## Description: Set responsible demon for obex push queries
## Type: list("/usr/bin/opd","")
## Default: "/usr/bin/opd"
## ServiceRestart: bluetooth OPD_DAEMON="/usr/bin/opd"

## Path: Hardware/Bluetooth
## Description: Arguments for opd-demon start
## Type: list("--mode OBEX --channel 10 --sdp --daemonize --path /var/lib/bluetooth/opd","--sdp")
## Default: "--mode OBEX --channel 10 --sdp --daemonize --path /var/lib/bluetooth/opd"
## ServiceRestart: bluetooth
OPD_DAEMON_ARGS="--mode OBEX --channel 10 --sdp --daemonize --path /var/lib/bluetooth/opd"

############ RFCOMM

## Path: Hardware/Bluetooth
## Description: Start responsible service for rfcomm
## Type: yesno
## Default: no
## ServiceRestart: bluetooth RFCOMM_START="yes"

## Path: Hardware/Bluetooth
## Description: Set responsible service for rfcomm
## Type: list("/usr/bin/rfcomm","")
## Default: "/usr/bin/rfcomm"
## ServiceRestart: bluetooth RFCOMM_DAEMON="/usr/bin/rfcomm"

## Path: Hardware/Bluetooth
## Description: Arguments for rfcomm-service start
## Type: list("-f /etc/bluetooth/rfcomm.conf bind all","")
## Default: "-f /etc/bluetooth/rfcomm.conf bind all"
## ServiceRestart: bluetooth RFCOMM_DAEMON_ARGS="-f /etc/bluetooth/rfcomm.conf bind all"

############ PAND

## Path: Hardware/Bluetooth
## Description: Start responsible demon for Personal Area Network
## Type: yesno
## Default: no
## ServiceRestart: bluetooth
PAND_START="no"

## Path: Hardware/Bluetooth
## Description: Set responsible demon for Personal Area Network
## Type: list("/usr/bin/pand","")
## Default: "/usr/bin/pand"
## ServiceRestart: bluetooth PAND_DAEMON="/usr/bin/pand"

## Path: Hardware/Bluetooth
## Description: Arguments for pan-demon start
## Type: list("--listen --role NAP")
## Default: "--listen --role NAP"
## ServiceRestart: bluetooth
PAND_DAEMON_ARGS="--listen --role NAP"

############ DUND

## Path: Hardware/Bluetooth
## Description: Start responsible demon for LAN Access over PPP
## Type: yesno
## Default: no
## ServiceRestart: bluetooth
DUND_START="no"

## Path: Hardware/Bluetooth
## Description: Set responsible demon for LAN Access over PPP
## Type: list("/usr/bin/dund","")
## Default: "/usr/bin/dund"
## ServiceRestart: bluetooth DUND_DAEMON="/usr/bin/dund"

## Path: Hardware/Bluetooth
## Description: Arguments for dun-demon start
## Type: list("--listen --persist")
## Default: "--listen --persist"
## ServiceRestart: bluetooth
DUND_DAEMON_ARGS="--listen --persist"

############ HIDD

## Path: Hardware/Bluetooth
## Description: Start responsible demon for HID Daemon
## Type: yesno
## Default: no
## ServiceRestart: bluetooth
HID_START="yes"

## Path: Hardware/Bluetooth
## Description: Set responsible demon for HID
## Type: list("/usr/bin/hidd","")
## Default: "/usr/bin/hidd"
## ServiceRestart: bluetooth
HID_DAEMON="/usr/bin/hidd"

## Path: Hardware/Bluetooth
## Description: Arguments for hid-demon start
## Type: list("--server", "")
## Default: "--server"
## ServiceRestart: bluetooth
HID_DAEMON_ARGS="--server"

############ HID2HCI

## Path: Hardware/Bluetooth
## Description: Start HID to HCI mode switching utility
## Type: yesno
## Default: no
## ServiceRestart: bluetooth HID2HCI_START="yes"

## Path: Hardware/Bluetooth
## Description: Set responsible utility for HID to HCI mode switching
## Type: list("/usr/bin/hidd","")
## Default: "/usr/sbin/hid2hci"
## ServiceRestart: bluetooth HID2HCI_DAEMON="/usr/sbin/hid2hci"

## Path: Hardware/Bluetooth
## Description: Arguments for RHID to HCI mode switching utility
## Type: list("--tohci", "")
## Default: "--tohci"
## ServiceRestart: bluetooth HID2HCI_DAEMON_ARGS="--tohid "

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

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

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

# Local device class
class 0x3e0100;

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

# Inquiry and Page scan
iscan disable;

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

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

#1 lore raw

Hi H=E5var,

Quoted 17 lines · On Mon, Jan 22, 2007 at 04:02:57PM +0100, H=E5var Nielsen wrote:

Dear all,
=

I need some help with my bluetooth mouse.
=

I just went from ubuntu to openSuSE on my laptop. Everything except for the bluetooth mouse is working.
=

I have tried a lot of approaches really, but none seem to work. No matter what I do, I have to use the command sudo hidd --connect ... to make my mouse connect to the computer or vice versa (computer to mouse) every time I want to use the mouse. - That means I also have to type the root password each time I want to use the mouse.
=

Quoted 8 lines

On ubuntu this was really as simple as adding a line with 'hidd
- --server' in /etc/rc.local. Then after I had connected my mouse with the hidd --connect command once, it always reconnected by itself, even after restarts and such.
=

This approach doesn't seem to work in openSuSE however, even when using the ubuntu (default) /etc/bluetooth/hcid.conf file. Why is that?

The hcid.conf is mostly obsolete (IMO) in bluez-3.x since all the settings are now remembered for every adapter in /var/lib/bluetooth/* and can be set via the DBus API..

Quoted 2 lines

In SuSE, I must go to a terminal, become root and do:
hidd --server

Don't do that. Rather investigate why the bluetooth init script does not start hidd for you.

Check if HID is enabled in /etc/sysconfig/bluetooth:

root@strolchi:~# grep ^HID_ /etc/sysconfig/bluetooth
HID_START=3D"yes"
HID_DAEMON=3D"/usr/bin/hidd"
HID_DAEMON_ARGS=3D"--server"

I then just connected my keyboard and mouse once after installation with "hidd --search", then pressed the connect button on the keyboard and on the mouse ant it is working happily ever after.

We had a bug which started the bluetooth service too early (before DBus), so you needed to unplug and replug your adapter or restart the service after booting, but this is fixed since some days with an online update

Quoted 28 lines

hidd --connect 00:07:61:4a:1b:ef
(press reset button on the mouse) -result-> Mouse connects and works. Now, if I turn my mouse off for five seconds and turn it back on again, I have to type another hidd --connect command as root for the mouse to reconnect.
=

I have attached the SuSE bluetooth init script and the bluetooth.conf file used by the bluetooth init script in hopes it can be of use to anyone who might answer this request.

## Path: Hardware/Bluetooth
## Description: Start responsible demon for HID Daemon
## Type: yesno
## Default: no
## ServiceRestart: bluetooth HID_START=3D"yes"
=

## Path: Hardware/Bluetooth
## Description: Set responsible demon for HID =

## Type: list("/usr/bin/hidd","")
## Default: "/usr/bin/hidd"
## ServiceRestart: bluetooth
HID_DAEMON=3D"/usr/bin/hidd"
=

Quoted 6 lines

## Path: Hardware/Bluetooth
## Description: Arguments for hid-demon start
## Type: list("--server", "")
## Default: "--server"
## ServiceRestart: bluetooth
HID_DAEMON_ARGS=3D"--server"

This is strange since it is exactly the same as my config. So is the bluetooth service started after bootup? Check with "service bluetooth status":

root@strolchi:~# service bluetooth status
Checking service bluetooth (enabled) :
      hcid  (activated)                                               runni=
ng
      hidd  (activated)                                               runni=
ng
   hid2hci                                                            unused
      sdpd  (activated)                                               runni=
ng
       opd                                                            unused
    rfcomm  (activated)
      pand                                                            unused
      dund                                                            unused

The "hcid" and the "hidd" line should show "running".

Please also check with "ps aux|grep hidd" if there really is no hidd runnin= g.

If not, does it help if you unplug and replug the adapter or restart the service with "service bluetooth restart"?

Next try would be to pair the device with "hidd --search", then pressing the connect button on the mouse (i usually click around on the mouse and move it until it is connected, but this might be just voodoo :-):

root@strolchi:~# hidd --search
Searching ...
        Connecting to device 00:07:61:3F:1B:6D
root@strolchi:~#
Quoted 1 line
Quoted 1 line

From now on, the mouse reconnects automatically to my machine if i activate

it (depending on the mouse, you might need to press a mouse button or simply move it around).

This works for me in 10.2, so it looks as if it is not generally broken :-)

HTH,

Stefan

-- =

Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

#2 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Stefan,

Thanks for the answer. I've tried what you suggested, checked that both hidd and dbus are running just after boot-up. They are:

Quoted 1 line

ps aux | grep hidd

	root      1922  0.0  0.0   1820   456 ?        S<s  21:56   0:00
/usr/bin/hidd --server
	havar     4087  0.0  0.0   2860   716 pts/0    R+   22:07   0:00 grep hidd
Quoted 1 line

ps aux | grep dbus

	100       2700  0.0  0.0   3628  1060 ?        Ss   21:56   0:00
/usr/bin/dbus-daemon --system
	havar     3821  0.0  0.0   3724   884 ?        Ss   21:59   0:00
/usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
	havar     4091  0.0  0.0   2856   712 pts/0    R+   22:07   0:00 grep dbus

Since you said that dbus needs to start before bluetooth, I opened YaST and saw to it that dbus starts at run levels: 1,2,3,5,6,S and bluetooth now starts at runlevels 6 and S. What puzzles me is that bluetooth actually was disabled (originally set to not start during boot), but it started during boot anyways. - I have no idea on which boot-script or how it got started.

Still the mouse won't work properly and I still have to use the sudo hidd --search or --connect commands to connect the mouse. Don't have to run hidd --server though, cause it is already running.

And even though the hidd --server is running, the mouse doesn't reconnect when I turn it off and on again nor when it comes out of power-saving.

Disabling and re-enabling the internal bluetooth dongle didn't work either.

My hardware is a Dell Latitude X1 laptop and a Logitech V270 mouse.

Quoted 1 line

lsusb

Bus 003 Device 002: ID 413c:8103 Dell Computer Corp. Wireless 350 Bluetooth

Quoted 1 line

hidd --show

00:07:61:4A:1B:EF Bluetooth HID Boot Protocol Device [046d:b002] connected [boot-protocol]

I just got the mouse connected without using sudo =3D)

Quoted 1 line

hidd --connect 00:07:61:4a:1b:ef

HID create error 13 (Permission denied)
But the mouse started working (had to press the reset button on the mouse though). At least some progress.

Anyhow, I appreciate the answer.

(A bit tired from reading SuSE boot-scripts for many hours today and yesterday).

With thanks,
H=E5var

Quoted 21 lines · Stefan Seyfried

Hi H=E5var,
=

On Mon, Jan 22, 2007 at 04:02:57PM +0100, H=E5var Nielsen wrote:
=

Quoted 15 lines

Dear all,

I need some help with my bluetooth mouse.

I just went from ubuntu to openSuSE on my laptop. Everything except for the bluetooth mouse is working.

I have tried a lot of approaches really, but none seem to work. No matter what I do, I have to use the command sudo hidd --connect ... to make my mouse connect to the computer or vice versa (computer to mouse) every time I want to use the mouse. - That means I also have to type the root password each time I want to use the mouse.

On ubuntu this was really as simple as adding a line with 'hidd
- --server' in /etc/rc.local. Then after I had connected my mouse with t=

he

Quoted 22 lines
Quoted 5 lines

hidd --connect command once, it always reconnected by itself, even after restarts and such.

This approach doesn't seem to work in openSuSE however, even when using the ubuntu (default) /etc/bluetooth/hcid.conf file. Why is that?

=

The hcid.conf is mostly obsolete (IMO) in bluez-3.x since all the settings are now remembered for every adapter in /var/lib/bluetooth/* and can be set via the DBus API..
=

Quoted 2 lines

In SuSE, I must go to a terminal, become root and do:
hidd --server

=

Don't do that. Rather investigate why the bluetooth init script does not start hidd for you.
=

Check if HID is enabled in /etc/sysconfig/bluetooth:

Quoted 8 lines
root@strolchi:~# grep ^HID_ /etc/sysconfig/bluetooth
HID_START=3D"yes"
HID_DAEMON=3D"/usr/bin/hidd"
HID_DAEMON_ARGS=3D"--server"
=

I then just connected my keyboard and mouse once after installation with "hidd --search", then pressed the connect button on the keyboard and on t=

he

Quoted 42 lines

mouse ant it is working happily ever after.
=

We had a bug which started the bluetooth service too early (before DBus), so you needed to unplug and replug your adapter or restart the service after booting, but this is fixed since some days with an online update =

Quoted 9 lines

hidd --connect 00:07:61:4a:1b:ef
(press reset button on the mouse) -result-> Mouse connects and works. Now, if I turn my mouse off for five seconds and turn it back on again, I have to type another hidd --connect command as root for the mouse to reconnect.

I have attached the SuSE bluetooth init script and the bluetooth.conf file used by the bluetooth init script in hopes it can be of use to anyone who might answer this request.

=

Quoted 15 lines

## Path: Hardware/Bluetooth
## Description: Start responsible demon for HID Daemon
## Type: yesno
## Default: no
## ServiceRestart: bluetooth HID_START=3D"yes"

## Path: Hardware/Bluetooth
## Description: Set responsible demon for HID =

## Type: list("/usr/bin/hidd","")
## Default: "/usr/bin/hidd"
## ServiceRestart: bluetooth
HID_DAEMON=3D"/usr/bin/hidd"

Quoted 6 lines

## Path: Hardware/Bluetooth
## Description: Arguments for hid-demon start
## Type: list("--server", "")
## Default: "--server"
## ServiceRestart: bluetooth
HID_DAEMON_ARGS=3D"--server"

=

Quoted 8 lines

This is strange since it is exactly the same as my config. So is the bluetooth service started after bootup? Check with "service bluetooth status":
=

root@strolchi:~# service bluetooth status
Checking service bluetooth (enabled) :
      hcid  (activated)                                               run=

ning

Quoted 1 line

hidd (activated) run=

ning

Quoted 1 line

hid2hci unu=

sed

Quoted 1 line

sdpd (activated) run=

ning

Quoted 1 line

opd unu=

sed

Quoted 2 lines

rfcomm (activated)
pand unu=

sed

Quoted 1 line

dund unu=

sed

Quoted 6 lines

=

The "hcid" and the "hidd" line should show "running". =

Please also check with "ps aux|grep hidd" if there really is no hidd runn=

ing.

Quoted 7 lines

=

If not, does it help if you unplug and replug the adapter or restart the service with "service bluetooth restart"?
=

Next try would be to pair the device with "hidd --search", then pressing =

the

Quoted 1 line

connect button on the mouse (i usually click around on the mouse and move=

it

Quoted 10 lines

until it is connected, but this might be just voodoo :-):
=

root@strolchi:~# hidd --search
Searching ...
        Connecting to device 00:07:61:3F:1B:6D
root@strolchi:~#
=
Quoted 1 line
Quoted 1 line

From now on, the mouse reconnects automatically to my machine if i activa=

te

Quoted 1 line

it (depending on the mouse, you might need to press a mouse button or sim=

ply

Quoted 4 lines

move it around).
=

This works for me in 10.2, so it looks as if it is not generally broken :=

-)

Quoted 6 lines

=

HTH,
=

Stefan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFFtTF5urImHjOFF6oRAhwSAJ9v1qBB1d7XMbPIus08FlHKY5fmbwCaAiW+ mSwSfsmlYagRAQ6eiV2Tchk=3D
=3DjxNs
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

#3 lore raw

Hi H=E5var,

Quoted 9 lines · On Mon, Jan 22, 2007 at 10:49:45PM +0100, H=E5var Nielsen wrote:

Hi Stefan,
=

Thanks for the answer. I've tried what you suggested, checked that both hidd and dbus are running just after boot-up. They are:

Quoted 1 line

ps aux | grep hidd

	root      1922  0.0  0.0   1820   456 ?        S<s  21:56   0:00
/usr/bin/hidd --server
	havar     4087  0.0  0.0   2860   716 pts/0    R+   22:07   0:00 grep hi=

dd

Quoted 8 lines

=

Quoted 1 line

ps aux | grep dbus

	100       2700  0.0  0.0   3628  1060 ?        Ss   21:56   0:00
/usr/bin/dbus-daemon --system
	havar     3821  0.0  0.0   3724   884 ?        Ss   21:59   0:00
/usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
	havar     4091  0.0  0.0   2856   712 pts/0    R+   22:07   0:00 grep db=

us

Quoted 8 lines

=

Since you said that dbus needs to start before bluetooth, I opened YaST and saw to it that dbus starts at run levels: 1,2,3,5,6,S and bluetooth now starts at runlevels 6 and S. What puzzles me is that bluetooth actually was disabled (originally set to not start during boot), but it started during boot anyways. - I have no idea on which boot-script or how it got started.

It gets started by udev when the adapter is plugged in. On a regular boot this is before DBus is started, though, so it won't work. We fixed this with an update to the bluez packages.
Just enabling the bluetooth service to always start on every boot is also an option, you can do this in YaST or simply with "insserv bluetooth".

Quoted 8 lines

Still the mouse won't work properly and I still have to use the sudo hidd --search or --connect commands to connect the mouse. Don't have to run hidd --server though, cause it is already running.
=

And even though the hidd --server is running, the mouse doesn't reconnect when I turn it off and on again nor when it comes out of power-saving.

This is strange and does not sound like a SUSE-specific bug (to me :-) It works fine for me with a Logitech MX1000 and a CSR based Epox mouse. It might still be a service-start-ordering problem.
Try restarting the bluez daemons with "service bluetooth restart" and check if the mouse will reconnect afterwards. If it does not, i have no real idea what could be the problem.

Quoted 1 line

Disabling and re-enabling the internal bluetooth dongle didn't work eithe=

r.

Quoted 5 lines

=

My hardware is a Dell Latitude X1 laptop and a Logitech V270 mouse.

Quoted 1 line

lsusb

Bus 003 Device 002: ID 413c:8103 Dell Computer Corp. Wireless 350 Bluetoo=

th

Quoted 12 lines
Quoted 1 line

hidd --show

00:07:61:4A:1B:EF Bluetooth HID Boot Protocol Device [046d:b002] connected [boot-protocol]
=

I just got the mouse connected without using sudo =3D)

Quoted 1 line

hidd --connect 00:07:61:4a:1b:ef

HID create error 13 (Permission denied)
But the mouse started working (had to press the reset button on the mouse though). At least some progress.
=

Quoted 5 lines

Anyhow, I appreciate the answer.
=

(A bit tired from reading SuSE boot-scripts for many hours today and yesterday).

I can understand that :-)

Good Luck,
-- =

Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users