Comment 47 for bug 550288

Revision history for this message
Yennix (yennix) wrote :

Wanted to kick in with this.

I'm using the Logitech Bluetooth Dongle to connect my MX1000 mouse (all from the MX5000 keyboard/mouse combo kit). I'm only connecting the mouse (ditched the keyboard long ago) so I'm running a really really simplified setup.

I applied the rule updates in comment 10 about 4 months ago. That fixed my mouse up until I applied the udev update last week.

Since then, none of the suggested rules have worked. Not even the combined KERNEL=="hidraw*|hiddev*" fix.

What has worked however, was purging the whole "KERNEL==<BLAH>," reference entirely. I followed the directions in this post (http://ubuntuforums.org/showthread.php?p=9574808) to do only the following:

1) sudo cp /lib/udev/rules.d/70-hid2hci.rules /etc/udev/rules.d/70-hid2hci.rules --- Contents of the /etc/udev/rules.d override the /lib/udev/rules.d and dont get overwritten on an update
2) Change <<KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]", \>> to <<ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]", \>>

I didn't do ANY OF THE OTHER STEPS in that document, only the two above. Your mileage may vary;)

So...all that said...I don't know the significance of removing "KERNEL==<BLAH>," from the rule. Presumably, it's there for a very good reason. But since my requirements are so trivial, this appears to work for me (though it should be noted that I haven't restarted my machine yet >.>)

Hopefully this helps rather than hurts.

$ uname -a
Linux sholan 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010 x86_64 GNU/Linux

$ cat /etc/*release*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu 10.04.1 LTS"

$ lsusb
Bus 002 Device 008: ID 046d:c709 Logitech, Inc. BT Mini-Receiver (HCI mode)
Bus 002 Device 007: ID 046d:0b02 Logitech, Inc. BT Mini-Receiver (HID proxy mode)
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ aptitude show bluez
Package: bluez
State: installed
Automatically installed: no
Version: 4.60-0ubuntu8
Priority: optional
Section: admin
Maintainer: Ubuntu Developers <email address hidden>
Uncompressed Size: 1,401k
Depends: libbluetooth3 (>= 4.60-0ubuntu8), libc6 (>= 2.7), libdbus-1-3 (>= 1.1.1), libglib2.0-0 (>= 2.23.5), libnl1 (>= 1.1), libusb-0.1-4
         (>= 2:0.1.12), module-init-tools, makedev | udev, lsb-base, dbus
Suggests: python-gobject, python-dbus
Conflicts: bluez-utils (<= 3.36-3)
Replaces: bluez-audio, bluez-input, bluez-network, bluez-serial, bluez-utils (<= 4.9)
Description: Bluetooth tools and daemons
 This package contains tools and system daemons for using Bluetooth devices.

 BlueZ is the official Linux Bluetooth protocol stack. It is an Open Source project distributed under GNU General Public License (GPL).
Homepage: http://www.bluez.org

$ aptitude show udev
Package: udev
State: installed
Automatically installed: no
Version: 151-12.1
Priority: required
Section: admin
Maintainer: Scott James Remnant <email address hidden>
Uncompressed Size: 1,626k
Depends: libacl1 (>= 2.2.11-1), libc6 (>= 2.9), libglib2.0-0 (>= 2.16.0), libselinux1 (>= 1.32), libusb-0.1-4 (>= 2:0.1.12), upstart-job,
         module-init-tools (>= 3.2.1-0ubuntu3), initramfs-tools (>= 0.92bubuntu63), procps, adduser, util-linux (> 2.15~rc2)
Suggests: watershed
Conflicts: hotplug, ifrename, libdevmapper1.02 (< 2:1.02.08-1ubuntu7), udev-extras (<= 20090618)
Breaks: casper (< 1.174), consolekit (<= 0.4.1), dmsetup (<= 2:1.02.27-4ubuntu5), initramfs-tools (< 0.92bubuntu30), lvm2 (<=
        2.02.39-0ubuntu9), mdadm (<= 2.6.7.1-1ubuntu8)
Replaces: hotplug, ifrename, initramfs-tools (< 0.040ubuntu1), udev-extras (<= 20090618)
Description: rule-based device node and kernel event manager
 udev is a collection of tools and a daemon to manage events received from the kernel and deal with them in user-space. Primarily this
 involves creating and removing device nodes in /dev when hardware is discovered or removed from the system.

 Events are received via kernel netlink messaged and processed according to rules in /etc/udev/rules.d and /lib/udev/rules.d, altering the
 name of the device node, creating additional symlinks or calling other tools and programs including those to load kernel modules and
 initialise the device.