Logitech Wireless M510 Does Not Work 12.10

Question

I' ve just installed Ubuntu 12.10 64 bits on my new laptop and my Logitech M510 mouse does not work. It worked perfectly on 11.04 but it stop woth the new version, I've read here that I need to install HID Point, but I'm having trouble with that too.

Here's my output of: lsusb

Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1bcf:2885 Sunplus Innovation Technology Inc.

As you can see it recognizes de unifying receiver, but the mouse does not respond.

When I try to install HID Point I get this:

libpng does not exist
libtiff does not exist
Gathering System information and generating a log
Launching HIDPoint Installer
./hidpointsetup: error while loading shared libraries: libpng.so.3: cannot open shared object file: No such file or directory

I've installed the 32-bit libraries just as it says in the installation instructions but nothing works.

Thank you in advanced!

EDIT

On this thread: Logitech M515 does not work after upgrade to 12.04 They suggest this line "modprobe -r hid_logitech_dj && modprobe hid_logitech_dj" should fix the problem but I get this error when I execute it:

WARNING: Error inserting usbhid (/lib/modules/3.5.0-17-generic/kernel/drivers/hid/usbhid/usbhid.ko): Operation not permitted
FATAL: Error inserting hid_logitech_dj (/lib/modules/3.5.0-17-generic/kernel/drivers/hid/hid-logitech-dj.ko): Operation not permitted

Solution

The problem with the Unifying Receiver is likely caused by this bug: https://bugs.launchpad.net/ubuntu/+bug/958174 which apparently has been fixed upstream. No fix as of yet in Ubuntu, but in the meantime running sudo modprobe -r hid_logitech_dj && sudo modprobe hid_logitech_dj a few times will probably fix it.

The message you're seeing (Operation not permitted) is because modprobe must be run as root (the most privileged user), which can be done using 'sudo' as above.

Comments

[Mr. Robot]

check out this link : askubuntu.com/questions/128345/…

[Adrian Matteo]

this: modprobe -r hid_logitech_dj && modprobe hid_logitech_dj doesn't work on my computer, I've added the output to my question.

[ThomasH]

I've the same problem using the M510 mouse and K750 keyboard. I'm using the modprobe script from this question and it usually gets one of the two working but both together seems to be a game of "connect the receivers until it's working", and sometimes even that doesn't work.

[Lekensteyn]

@AdrianMatteo You do not need HIDPoint to get your Unifying device to work, it works out of the box on Ubuntu/Linux.

[Adrian Matteo]

@Lekensteyn Mine does not work out of the box. I've just visited the link you provided and installed the library they mention and it recognizes the usb unifying receiver sometimes, if I run ltunify list sometimes it will say Mouse M510 and sometimes "No Logitech Unifying Receiver device found". Some how the receiver is turning itself on/off "randomly"

[Lekensteyn]

@AdrianMatteo That is correct, the wireless devices go standby after some inactivity. Move the mouse (or press a key on the keyboard in case of a wireless keyboard) to return it from standby, then you can continue working. If (as you say) you still have a mouse that does not re-act (and if ltunify also reports no files), please check of dmesg | tail shows some extra entries and insert it into your question if it is related to the HID/USB.

[Lekensteyn]

Another possibility is that you have USB runtime power management enabled (e.g. using powertop) and that your USB receiver got turned off after a while.

[Adrian Matteo]

@Lekensteyn I went to powertop and set the Ubs to never go off. Or at least that's what I think I did. I ran sudo powertop and set to bad the autosuspend feature fot the USBs.

[Adrian Matteo]

You were right about the error message the second command wasn't being run as root, I've run the command several times, it works sometimes but after a few seconds it stops working.