Bugzilla – Bug 256000
kbluetoothd and mouse not meeting
Last modified: 2007-09-24 16:48:00 UTC
I installed a brand new 10.2 with MaJ on my new Dell xps 1210 laptop and I try to connect my Kensington bluetooth mouse and things goes wrong. I installed Suse with my mouse activated. I activated Bluetooth in Yast2 (without security, activating all services, etc). I lauched kbluetoothd. But kbluetooth icon leaves an empty space in the task menu bar... I looked around Bug 228234 and made indicated MaJ but problem still appear. When I launch kbluetoothd in KDE Menu, It starts to launch for 10 seconds and disappear... I have no switch on my laptop to down and up bluetooth adapter (broadcom BCM2045). But I noticed that when I suspend (by s2ram), bluetooth adapter keeps sleeping after resume and then kbluetoothd icon appears !! (in black, certainly because adapter is off). If I restart X (Ctrl+Alt+Backspace), Bluetooth adapter awake and when I log in KDE, kbluetoothd icon has disapeared once again and an empty space is left instead (the application exists anyway because menu bar detects it). So what about my mouse ! Whatever I do with bluetooth config in kde, it is detected after.... 8 to 10 minutes (and roller does not work) !! I'd like to make linux search for it faster, or when I ask for but I couldn't find my mouse anywhere in the hidd or hcid daemons... It seems they have no devices connected... If I scan, they can't find anything... In the system jounal, Things seems not perfect : if I restart bluetooth services by /etc/init.d/bluetooth restart, things seems OK in xterm as it answers "done" but I get in /var/log/messages : Mar 20 11:37:09 xps su: (to root) marc on /dev/pts/1 Mar 20 11:37:16 xps hidd[2351]: Exit Mar 20 11:37:16 xps sdpd[2338]: terminating... Mar 20 11:37:16 xps hcid[2335]: Releasing agent :1.22, /org/bluez/kbluetoothd_4279 Mar 20 11:37:16 xps hcid[2335]: name_listener_remove(:1.22) Mar 20 11:37:16 xps hcid[2335]: Unregister path:/org/bluez/hci0 Mar 20 11:37:16 xps hcid[2335]: Unregister path:/org/bluez Mar 20 11:37:16 xps hcid[5752]: Bluetooth HCI daemon Mar 20 11:37:16 xps sdpd[5755]: Bluetooth SDP daemon Mar 20 11:37:16 xps hcid[5752]: syntax error line 24 Mar 20 11:37:16 xps hidd[5758]: Bluetooth HID daemon Mar 20 11:37:16 xps hcid[5752]: Register path:/org/bluez fallback:1 Mar 20 11:37:16 xps hcid[5752]: HCI dev 0 registered Mar 20 11:37:16 xps hcid[5752]: Register path:/org/bluez/hci0 fallback:0 Mar 20 11:37:16 xps hcid[5752]: HCI dev 0 already up Mar 20 11:37:16 xps hcid[5752]: Device hci0 has been added Mar 20 11:37:16 xps hcid[5760]: Can't set scan mode on hci0: Device or resource busy (16) Mar 20 11:37:16 xps hcid[5752]: Can't write inquiry mode for hci0: Input/output error (5) Mar 20 11:37:16 xps hcid[5752]: Getting scan enable failed with status 0x0c So I have no idea now to go ahead... I spent a week in forums to fixe that but I couldn't find that much tutorials about bluetooth. So I can't debug it. I tried a mouse test as explained somewhere : evtest /dev/input/event* but my linux doesn't knows this command and Yast can't find a rmp package about it... Hardware shouldn't have problems as my mouse works in vista. I saw a firmware for adapter BCM2033 in yast and I tried to install it but nothing changed. Thanks.
Could you please run as root the following command: hidd --search ? Some Readmes can be found in /usr/share/doc/packages/bluez-utils/
*** Bug 255996 has been marked as a duplicate of this bug. ***
*** Bug 256002 has been marked as a duplicate of this bug. ***
Hello, Thanks for your help. Here is the result : xps:/home/marc # xps:/home/marc # hidd --search Searching ... xps:/home/marc # I tested while the mouse was on and off : same result. Marc
Hello, I'm trying "reply" instead of "additionnal comment" (I'm not used to the list...) Here is the result : xps:/home/marc # xps:/home/marc # hidd --search Searching ... xps:/home/marc # I tested while the mouse was on and off : same result. Thanks
*** Bug 256013 has been marked as a duplicate of this bug. ***
I'm still trying to make bluetooth work on my suse 10.2. As I try to understand the problem, it seems that suse probably does not support my bluetooth adapter (BroadCom BCM 2045). I've been advice to list my computer components by lsusb and lspci. Here is the answer : xps:/home/marc # lsusb Bus 005 Device 004: ID 046d:08c6 Logitech, Inc. Bus 005 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 004: ID 413c:8126 Dell Computer Corp. Bus 002 Device 006: ID 0a5c:4503 Broadcom Corp. Bus 002 Device 005: ID 0a5c:4502 Broadcom Corp. Bus 002 Device 003: ID 0a5c:4500 Broadcom Corp. Bus 002 Device 001: ID 0000:0000 Bus 001 Device 003: ID 046d:c03d Logitech, Inc. Bus 001 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 xps:/home/marc # lspci 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01) 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 01) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 01) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01) 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 01) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01) 03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) 03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832 03:01.1 Generic system peripheral [Class 0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 03:01.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 01) 03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a) 03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05) 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) I can't find the bluetooth adapter. But Yast2-System-Hardware information show the bluetooth adapter.... If it can help, kbluetoothd lauched in a console doesn't work : xps:/home/marc # kbluetoothd kbuildsycoca running... KWrited - Écoute le périphérique « /dev/pts/2 » kbuildsycoca running... Reusing existing ksycoca kio (KSycoca): ERROR: No database available! DCOP aborting while waiting for answer from 'kbluetoothd' xps:/home/marc # After 2 min, I had to Ctrl-C to get the command line back... Thanks for any help...
sorry for lagging a bit on this report. The output of "hciconfig" will show you, if an adapter was found. Your bt adapter is the 413c:8126 device in your lsusb output, and those devices are even special cased in newer kernels, so it might be that they don't work well with the old kernel of 10.2. You do not need kbluetoothd to make your mouse work, so don't worry about it yet. The device is listed with two special settings in the newer kernels, so you could try the following as root: rcbluetooth stop rmmod hci_usb modprobe hci_usb reset=1 rcbluetooth start look at the output of "hciconfig -a" before and after those commands.
(In reply to comment #8) Hi Stefan, Thank for you advice. I've been trying your commands but that could not make my mouse work properly. I mean that it is detected after several minutes, without roller... Here is the responses to your commands : Little check before to try : xps:/home/marc # hciconfig -a hci0: Type: USB BD Address: 00:16:CF:D1:74:44 ACL MTU: 1017:8 SCO MTU: 64:1 UP RUNNING RX bytes:145 acl:0 sco:0 events:18 errors:0 TX bytes:318 acl:0 sco:0 commands:18 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Can't read local name on hci0: Input/output error (5) xps:/home/marc # This first check ends with an I/O error... Starts bad ! trying : xps:/home/marc # rcbluetooth stop Shutting down bluetooth ( hidd sdp hcid) done xps:/home/marc # rmmod hci_usb ERROR: Module hci_usb is in use xps:/home/marc # modprobe hci_usb reset=1 xps:/home/marc # rcbluetooth start Starting bluetooth: hcid sdpd hidd rfcomm done It seems that an error occures as hci_usb is still in use after rcbluetooth has been stopped. After that the mouse still not work. New check : xps:/home/marc # hciconfig -a hci0: Type: USB BD Address: 00:16:CF:D1:74:44 ACL MTU: 1017:8 SCO MTU: 64:1 UP RUNNING RX bytes:215 acl:0 sco:0 events:27 errors:0 TX bytes:598 acl:0 sco:0 commands:27 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Can't read local name on hci0: Input/output error (5) This doesn't seems much different from the first one... I wait for 4 minutes and my mouse is (at least) detected. I try a new check : xps:/home/marc # hciconfig -a hci0: Type: USB BD Address: 00:16:CF:D1:74:44 ACL MTU: 1017:8 SCO MTU: 64:1 UP RUNNING RX bytes:221 acl:0 sco:0 events:28 errors:0 TX bytes:601 acl:0 sco:0 commands:28 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Can't read local name on hci0: Input/output error (5) Still no change as far as I can see... Hope this can help ?? Thank for your help ! Do you know if new kernel would solve the problem ? I don't know if a new kernel change is shedduled for 10.2 but if 10.3 will take my hardware without pain, I can wait for it... I will use my usb mouse as I've been doing for years and keep my bluetooth mouse aside until next october ! Marc
In 10.3 we have at least done a major overhaul of the bluetooth system and at least my mice all work very well now. I of course cannot guarantee that it works better for you :-) If you have a spare partition left on your machine, you could try to install the latest openSUSE 10.3 beta version as a dual-boot setup, which would be interesting to see if things work better now.
Hi Stephan, Thanks to look forward bluetooth. I have a spare partition so that I can still work while making a new install. The only thing I miss is time... My work gives me only little rest... If you think that a test on my computer (dell xps 1210) can help for the developpement of the new 10.3, tell me : I will find time to make it. But if this test won't change anything, may be i'll wait until october and the last release to make the install. But if it can be usefull, I'll be very glad to give my little help ! I really look forward that brand new suse ! I hope it will solve the few missing items of the 10.2 (bluetooth, s2ram and my canon scaner and camera...) Enjoy your 10.3 ! Marc
(In reply to comment #11 from DERUMAUX Marc) > If you think that a test on my computer (dell xps 1210) can help for the > developpement of the new 10.3, tell me : I will find time to make it. But if > this test won't change anything, may be i'll wait until october and the last > release to make the install. I cannot promise anything and do not want to steal your time, so it is fine if you try it after the final 10.3 comes out. > I really look forward that brand new suse ! I hope it will solve the few > missing items of the 10.2 (bluetooth, s2ram and my canon scaner and camera...) If you have s2ram problems, make sure to try the procedure in http://en.opensuse.org/S2ram and report the success (just file a bug here), so that we can improve it for future versions. Actually, you could probably just install the suspend and libx86 package from 10.3 betas on your 10.2 system and maybe s2tam will just start working.
Stefan, I could install the brand new 10.3 RC1 for testing. First : it is a beautifull OS ! But a few things does not work : Wifi for example did work well on 10.2 but no longer works on 10.3. I hope this will be solved as I really need it !! Concerning bluetooth, Kbluetooth seems to work well as it detects neighbours phones and also my Kesington mouse (it is listed). But unfortunately, moving my mouse does not move my cursor on the screen... I tried to configure HCI in Yast->hardware->bluetooth but in the advanced settings menu, HCI daemon is not proposed... But I also have a good new : s2ram seems to work ! This is a very good news for me as for presentation, it is boring to wait for a 5 min boot... My machine is not recognized but a little s2ram -f does shut down my computer in 2 seconds and after another 2 seconds resume, everything seems to work well (on 10.2, nothing was working properly after resume, begining with the USB mouse). I'll wait to use this a few days to detect eventual problems with it before to declare my machine to the s2ram team. Best regards, Marc
(In reply to comment #13 from DERUMAUX Marc) > I could install the brand new 10.3 RC1 for testing. First : it is a beautifull > OS ! > > But a few things does not work : Wifi for example did work well on 10.2 but no > longer works on 10.3. I hope this will be solved as I really need it !! File a separate bugreport for this issue. I know almost nothing about Wifi, but somebody else might hopefully be able to help you. > Concerning bluetooth, Kbluetooth seems to work well as it detects neighbours > phones and also my Kesington mouse (it is listed). But unfortunately, moving my > mouse does not move my cursor on the screen... You do probably need to pair it again. I have written a short explanation on how this works in https://bugzilla.novell.com/show_bug.cgi?id=301780#c6 (note to myself: i need to put this up in the wiki :-) > I tried to configure HCI in Yast->hardware->bluetooth but in the advanced > settings menu, HCI daemon is not proposed... Basically, do not use the YaST module for bluetooth, it is of no real use anymore. If i had known how far we would get with the desktop applets (kdebluetooth and bluez-gnome), then it would probably no longer exist at all. The only thing that should be set in YaST (and it should be default already) is "Bluetooth enabled". Everything else, you better set from the desktop. > But I also have a good new : s2ram seems to work ! This is a very good news for > me as for presentation, it is boring to wait for a 5 min boot... My machine is > not recognized but a little s2ram -f does shut down my computer in 2 seconds > and after another 2 seconds resume, everything seems to work well (on 10.2, > nothing was working properly after resume, begining with the USB mouse). I'll > wait to use this a few days to detect eventual problems with it before to > declare my machine to the s2ram team. Nice :-) http://en.opensuse.org/S2ram contains some information on what is needed for a proper report. You can report it to the suspend-devel mailinglist or just open a bug here and we'll take it from there.
Thanks Stefan !! Thanks for your advice, it worked within 20 seconds in my 10.3 !! I make a copy of your message, and I added the path to find the right menu (not to confuse between input device, device, paired device kbluemon...) for people reading this bug... "The Yast bluetooth module needs to have bluetooth support enabled. This is the case here. Then you can connect the mouse with the inputwizard (either by clicking through kdebluetooth menu or by starting /opt/kde3/bin/kinputwizard) In the desktop applet, right click on Kbluetooth -> Configuration -> Input Device Once the window appears, you click on "Add new devices" and press the connect button on the mouse for a second or two. The mouse should now be found. Select it and then click "Setup". You should get a final confirmation window asking "Do you want to allow mouse $FOO to connect?", select "yes". After that it is "just working". At least for me (i tried it right now as i am typing this). :-)" Thanks for your help ! I can change this bug to "resolved". Marc
Last point : when I suspend and resume, of course bluetooth is disconnected. To reconnect my mouse, I have to go to "input device" and then select "connect". Is there a possibility of automatic reconnection ? Is there a command line way to do it within a script (to make it automatic after resume) ? Thanks, Marc
Normally, the mouse should reconnect to the host automatically. If it does not, it indicates a problem in the mouse firmware. There might be subtle bugs on our side here, so unplugging and replugging the dongle (or if it is built in, "rmmod hci_usb; sleep 1; modprobe hci_usb") after resume and then trying if the mouse reconnects by itself (which might take some seconds) is a good idea.
Ok, it does work in the end... I don't remember how but it asked me to reconnect automaticaly or not, so I just have now to clic on any button and wait 2 seconds and it works again. That's really nice ! Thanks for all. Marc