|
Bluetooth mouse connects, but not recognized
Hi,
I'm running Debian squeeze on a Fujitsu Lifebook AH550 under kernel revision 2.6.37. For the most part, everything is good, but I can't get my Verbatim Bluetooth mouse (model 96991) to work. It's fine with the Debian 2.6.32 kernel, so I know that the hardware is recognized and any required configuration files are in place. I've evidently missed some kernel configuration parameter, unless perhaps some driver has changed since 2.6.32 which renders my mouse incompatible. If I run bluetooth-properties, I can see that a mouse is configured. I've tried removing that device and adding a new device. The mouse is found immediately, and, according to the dialog, is configured successfully. This message is displayed in the command shell from which bluetooth-properties was launched: ** Message: has_config_widget 00:16:90:00:18:8C HumanInterfaceDeviceService I also see this message, however: ** (bluetooth-wizard:3973): DEBUG: Unhandled UUID 0000111b 0000-1000-8000-00805f9b34fb (0x111b) In "/sys/class/bluetooth", a new entry appears each time the mouse is connected, so it's pretty certain the mouse is connecting, however the events from the mouse are not being recognized. Comparing the entries in "/var/log/syslog" shows virtually no differences: 2.6.32 ------ Feb 19 09:06:49 simak bluetoothd[2397]: Bluetooth daemon 4.63 Feb 19 09:06:49 simak bluetoothd[2397]: Starting SDP server Feb 19 09:06:50 simak bluetoothd[2397]: Starting experimental netlink support Feb 19 09:06:50 simak bluetoothd[2397]: Failed to find Bluetooth netlink family Feb 19 09:06:50 simak bluetoothd[2397]: Failed to init netlink plugin Feb 19 09:06:50 simak bluetoothd[2397]: bridge pan0 created Feb 19 09:06:50 simak bluetoothd[2397]: HCI dev 0 registered Feb 19 09:06:51 simak bluetoothd[2397]: HCI dev 0 up Feb 19 09:06:51 simak bluetoothd[2397]: Starting security manager 0 Feb 19 09:06:51 simak bluetoothd[2397]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory Feb 19 09:06:51 simak bluetoothd[2397]: probe failed with driver input-headset for device /org/bluez/2397/hci0/dev_00_1C_C1_DC_1C_69 Feb 19 09:06:51 simak bluetoothd[2397]: Adapter /org/bluez/2397/hci0 has been enabled Feb 19 09:06:54 simak bluetoothd[2397]: Failed to access HAL 2.6.37 ------ Feb 19 09:15:12 simak bluetoothd[1650]: Bluetooth daemon 4.63 Feb 19 09:15:12 simak bluetoothd[1650]: Starting SDP server Feb 19 09:15:12 simak bluetoothd[1650]: Starting experimental netlink support Feb 19 09:15:12 simak bluetoothd[1650]: Failed to find Bluetooth netlink family Feb 19 09:15:12 simak bluetoothd[1650]: Failed to init netlink plugin Feb 19 09:15:12 simak bluetoothd[1650]: bridge pan0 created Feb 19 09:15:12 simak bluetoothd[1650]: HCI dev 0 registered Feb 19 09:15:13 simak bluetoothd[1650]: HCI dev 0 up Feb 19 09:15:13 simak bluetoothd[1650]: Starting security manager 0 Feb 19 09:15:13 simak bluetoothd[1650]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory Feb 19 09:15:13 simak bluetoothd[1650]: probe failed with driver input-headset for device /org/bluez/1650/hci0/dev_00_1C_C1_DC_1C_69 Feb 19 09:15:13 simak bluetoothd[1650]: Adapter /org/bluez/1650/hci0 has been enabled Note that the message regarding HAL is not present with the 2.6.37 kernel. Here is a list of kernel modules which are loaded when I boot 2.6.32 vs. 2.6.37: < ahci < cpufreq_stats < crc16 < crc_t10dif < ext3 < i2c_core < jbd < led_class < libata < lp < mbcache < nls_base < parport < parport_pc < ppdev < rsrc_nonstatic < scsi_mod < sd_mod < snd_hda_codec_intelhdmi < thermal Some of those modules are directly linked into the 2.6.37 kernel, e.g. ext3, since they are always required. I can't find anything in that list which appears to be related to Bluetooth HID hardware. The full list of differences between loaded modules for the two kernels, is appended. My kernel configuration file is available at <http://members.cox.net/f7j9jwirjsljejic/kernel_config-2.6.37>. If anyone has any ideas as to what I've missed or done wrong, I'd appreciate the information. A related question: where are the files which contain information regarding previously configured devices stored (in other words, where does bluetooth-properties store its data when you set up a new device)? Thanks, -- Mike -- -------------------------------------------------------------------- Loaded modules: Key: < 2.6.32 > 2.6.37 -------------------------------------------------------------------- > acpiphp < ahci > ath9k_common > ath9k_hw > broadcom < cpufreq_stats < crc16 < crc_t10dif < ext3 < i2c_core < jbd > intel_gtt > intel_ips < led_class < libata > libphy > llc < lp < mbcache < nls_base > mperf < parport < parport_pc > pci_hotplug > pcmcia_rsrc < ppdev < rsrc_nonstatic < scsi_mod < sd_mod > shpchp < snd_hda_codec_intelhdmi > snd_hda_codec_hdmi < thermal |
That's odd...I've never had a problem using bluetooth mice/keyboards at all. For HID, I've got these modules loaded:
Code:
lsmod | grep hid |
Those are all loaded. I provided diffs between the two kernels, but neglected to include the full list of modules loaded under 2.6.37. That list is shown below. Any other ideas?
-- Mike -- uhci_hcd 19120 0 hidp 10178 1 hid 62000 1 hidp aes_i586 6844 1 aes_generic 25830 1 aes_i586 acpi_cpufreq 4945 1 mperf 931 1 acpi_cpufreq cpufreq_userspace 1480 0 cpufreq_powersave 610 0 cpufreq_conservative 7636 0 i915 327651 7 sco 6954 2 bridge 61371 0 stp 1104 1 bridge llc 2901 2 bridge,stp bnep 7126 2 rfcomm 28895 4 drm_kms_helper 25219 1 i915 l2cap 37056 21 hidp,bnep,rfcomm drm 133256 3 i915,drm_kms_helper i2c_algo_bit 4055 1 i915 uinput 6004 1 binfmt_misc 5818 1 fuse 55823 1 acpiphp 14242 0 loop 13880 0 snd_hda_codec_hdmi 19079 1 snd_hda_codec_realtek 221470 1 snd_hda_intel 18333 0 snd_hda_codec 57672 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel snd_hwdep 4778 1 snd_hda_codec snd_pcm_oss 32701 0 snd_mixer_oss 12781 1 snd_pcm_oss snd_pcm 57633 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss arc4 1022 2 ecb 1509 2 snd_seq_midi 3880 0 ath9k 73750 0 btusb 9540 4 snd_rawmidi 15079 1 snd_seq_midi snd_seq_midi_event 4352 1 snd_seq_midi bluetooth 44505 10 hidp,sco,bnep,rfcomm,l2cap,btusb mac80211 153566 1 ath9k ath9k_common 1377 1 ath9k ath9k_hw 248684 2 ath9k,ath9k_common uvcvideo 54506 0 ath 11166 2 ath9k,ath9k_hw pcmcia 29957 0 snd_seq 41195 3 snd_seq_midi,snd_seq_midi_event cfg80211 118899 3 ath9k,mac80211,ath snd_timer 15263 2 snd_pcm,snd_seq snd_seq_device 4149 3 snd_seq_midi,snd_rawmidi,snd_seq snd 40894 13 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer _oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device yenta_socket 18874 0 rfkill 12260 4 bluetooth,cfg80211 pcmcia_rsrc 7111 1 yenta_socket soundcore 4111 1 snd videodev 55287 1 uvcvideo intel_agp 8777 1 i915 intel_gtt 11451 3 i915,intel_agp video 9601 1 i915 agpgart 21711 3 drm,intel_agp,intel_gtt intel_ips 9437 0 i2c_i801 6914 0 snd_page_alloc 5549 2 snd_hda_intel,snd_pcm v4l1_compat 12514 2 uvcvideo,videodev shpchp 22003 0 pcmcia_core 9889 3 pcmcia,yenta_socket,pcmcia_rsrc pci_hotplug 9014 2 acpiphp,shpchp processor 20524 1 acpi_cpufreq psmouse 44508 0 thermal_sys 11274 2 video,processor ac 1604 0 button 3506 1 i915 output 1208 1 video fujitsu_laptop 12124 0 evdev 7303 27 serio_raw 3328 0 pcspkr 1311 0 battery 4178 0 broadcom 5122 0 sdhci_pci 5675 0 sg 18269 0 sdhci 14663 1 sdhci_pci mmc_core 54789 1 sdhci ehci_hcd 33705 0 usbcore 115488 5 uhci_hcd,btusb,uvcvideo,ehci_hcd tg3 116182 0 sr_mod 13033 0 cdrom 30786 1 sr_mod libphy 13453 2 broadcom,tg3 |
Quote:
There's an article on the Debian wiki: http://wiki.debian.org/HOWTO/BluetoothMouse that may help. Also, some mice I've seen like the one-click mobile, don't actually pair (or even HAVE pairing codes), but just 'announce' themselves as HID devices. I've still had to go and do a one-time connect, but sometimes I've got to press the CONNECT button on the mouse to make it come alive. |
Pairing appears to be working. I'm using gnome, and if I run bluetooth-properties and remove the existing mouse entry, then re-attach using "add new device", the mouse is recognized immediately. Kernel messages (see earlier logs) confirm this. I took a look at the Debian Bluetooth Mouse HOWTO, but there are discrepancies. The most glaring occurs when the daemon is launched. According to the HOWTO, I should see:
# /etc/init.d/bluetooth restart Restarting bluetooth: hidd hcid sdpd hidd rfcomm. Instead, I get the following message: # /etc/init.d/bluetooth restart Stopping bluetooth: bluetoothd. Starting bluetooth: bluetoothd compatibily daemons not started, see bluez-compat package. Looking at the script, I don't think there's a problem with the "compatibily" daemons -- this appears to be an informational message, and in any case, the same occurs if I restart the daemon when 2.6.32 is running and the mouse works fine with that kernel. I'm not clear what "hidd", "hcid", etc. following the "Restarting bluetooth:" message mean. Are these daemons, references to other start scripts, kernel modules or something else? If they're kernel modules, I suspect they may refer to older revisions of Bluetooth support, since they're not present on my machine when 2.6.32 is running and the mouse works. So in general, I'm not sure the HOWTO is applicable. The only new clue I've found since yesterday is this one, and I don't know how to interpret it: Kernel 2.6.32 running: $ ps aux | grep blue root 749 0.0 0.0 0 0 ? S 00:39 0:00 [bluetooth] root 1738 0.0 0.0 4016 2000 ? Ss 00:39 0:00 /usr/sbin/bluetoothd wilson 2867 0.0 0.2 79272 7900 ? S 00:40 0:00 bluetooth-applet Kernel 2.6.37 running: $ ps aux | grep blue root 1749 0.0 0.0 4064 1992 ? Ss 09:23 0:00 /usr/sbin/bluetoothd mcollins 3015 0.0 0.2 79972 7724 ? S 09:32 0:00 bluetooth-applet Note the first entry in the 2.6.32 log. What is "[bluetooth]" telling me? It's a process, obviously, but there's no executable that I can find by that name, and if there's a kernel configuration parameter which enables it, I haven't been able to determine which one. Still stuck, but perhaps getting closer. -- Mike -- |
Not sure, but I think you need the bluez-compat package loaded for Debian, before the HID stuff will work, which is where the mouse comes in. In openSUSE the HID stuff is in the 'standard' bluez package, but from what I've read of Debian, I think you may need that other package loaded.
Sorry I can't be more specific, but I don't have Debian loaded here, but do have experience with Linux and bluetooth. Try to load that package, and then run back through the web page I linked to earlier...that was from November of last year, so it's fairly current.... |
I installed bluez-compat yesterday, but it hasn't made any difference. I also downloaded and installed bluez-4.88, but that didn't help either. For now, I've reverted back to bluez-4.66 from the Debian repository.
If you've got a working Bluetooth mouse on your system, could you provide the response to "$ps aux | grep blue". You can see in my previous message that there is a difference between kernels on my machine when I run this command. What I've not been able to determine is what the PID 749 is or was doing when my machine was running 2.6.32. The assistance is appreciated, despite the lack of resolution. -- Mike -- |
Quote:
Code:
root 1074 0.0 0.0 0 0 ? S 19:29 0:00 [bluetooth] |
| All times are GMT -5. The time now is 02:42 PM. |