[SOLVED] Logitech USB devices not functioning correctly

ShaneRoach · 01-31-2014, 11:02 PM

I love my logitech mouse, and it works just fine on the debian install I have on this laptop, but for some reason does not work on the new desktop installs I have done, both for SteamOS and Wheezy Debian. This seems to be a fairly cross-distro problem, as I seem to find similar issues reported on Ubuntu for example.

Basically, you have to keep plugging in the USB and unplugging it to get it to pick up. For me, this often takes far, far longer than is acceptable even as a work around. Is there not some linux command to just MAKE the box poll the usb and run?

It's an awfully odd bug. Once they finally DO get "detected" or whatever, they work great. (I also have a Logitech wireless keyboard).

fuorviato · 02-01-2014, 02:44 AM

This is a desktop install, isn't it. I was wondering if you had laptop-mode service running, but it is quite unlikely for a desktop.
Does your mouse autosuspend or just switches entirely off?

273 · 02-01-2014, 03:39 AM

Do you have another batch of USB ports (for example on the front of your case if you are using the ones on the back or vice-versa) that you could try to check it's not a hardware problem?

ShaneRoach · 02-01-2014, 08:48 AM

Quote:

Originally Posted by fuorviato

This is a desktop install, isn't it. I was wondering if you had laptop-mode service running, but it is quite unlikely for a desktop.
Does your mouse autosuspend or just switches entirely off?

I'm not sure if I understand the question. As I said, it simply does not work unless I plug it in and unplug it over and over. It is a known issue, but I just had hoped there was a better work around than this plugging and unplugging...

That's the best answer to that question I know how to give. =)

Quote:

Originally Posted by 273

Do you have another batch of USB ports (for example on the front of your case if you are using the ones on the back or vice-versa) that you could try to check it's not a hardware problem?

I have like 10 usb ports total, 4 of which are usb3, all of which function with everything but these logitech devices.

It behaves very similarly to this in that it DOES work when I am in my bios.

https://bbs.archlinux.org/viewtopic.php?pid=1107697

But that is an old bug and I would have thought long gone by now.

273 · 02-01-2014, 09:01 AM

Quote:

Originally Posted by ShaneRoach

I have like 10 usb ports total, 4 of which are usb3, all of which function with everything but these logitech devices.

Fair enough -- I thought it worth checking because I know some motherboards (mine included) have certain ports that are always "live" for charging and the like and some which switch off when the system does. It's not inconceivable that there's some sensing built into one of the controllers that would cut power when unused or something. I could well be wrong on that but, like I said, I think these things are worth checking.

ShaneRoach · 02-01-2014, 10:25 AM

Quote:

Originally Posted by 273

Fair enough -- I thought it worth checking because I know some motherboards (mine included) have certain ports that are always "live" for charging and the like and some which switch off when the system does. It's not inconceivable that there's some sensing built into one of the controllers that would cut power when unused or something. I could well be wrong on that but, like I said, I think these things are worth checking.

No doubt. I plugged em into at least 5 different ones, both usb3 and usb2. LOL! Just sayin', on this particular occasion, that's not it...

Always worth posting about checking the basics. I just wanted to update the thread is all.

I checked all of them in the process of troubleshooting wireless network usb... lol At least I got that working.

ShaneRoach · 02-01-2014, 10:56 AM

Little update.

I found this thread. My version is
3.2.0-4-amd64

I JUST got through with a thread where it was advised not to fiddle too much with Debian stable, but is updating a kernel considered such a risky update? (Sounds risky...)

273 · 02-01-2014, 11:01 AM

I run Sid so things are different but I've had good results following this to compile my own kernel (though I had to add some CD support and some crypto things using menuconfig to get everything working):
http://mapopa.blogspot.co.uk/2009/01/compiling-2.html
Or, you could perhaps use backports for a more supported and integrated approach?

ShaneRoach · 02-01-2014, 11:16 AM

Quote:

Originally Posted by 273

I run Sid so things are different but I've had good results following this to compile my own kernel (though I had to add some CD support and some crypto things using menuconfig to get everything working):
http://mapopa.blogspot.co.uk/2009/01/compiling-2.html
Or, you could perhaps use backports for a more supported and integrated approach?

Yeah, all of that looks crazier than just having Sid. I plan on having Sid on my second hard drive. (See other thread of mine where I screwed that pooch too).

I had hoped there was a simpler solution than updating the kernel for what appears to be a known driver issue. I am bemused because if you look at the interwebs in general, it appears that this bug has been detected and fixed at various stages of the kernel since 2011 at least.

Frustrating. Especially for Wheezy not to work with it. That's the whole point of stable to me. =(

ShaneRoach · 02-02-2014, 12:19 AM

Tried the Solaar software for pairing. It does not see the devices. I retested and they are both still working just fine in UEFI at bootup. \

Code:

root@debiansid:/home/shane# solaar-cli show
solaar-cli: error: Logitech receiver not found
root@debiansid:/home/shane# solaar-cli show
solaar-cli: error: Logitech receiver not found

You can see the two (stupid) unifying receivers here.

Code:

root@debiansid:/home/shane# lsusb
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 002: ID 8087:8008 Intel Corp. 
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 003 Device 002: ID 0781:5576 SanDisk Corp. 
Bus 003 Device 008: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 009: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 005: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 003 Device 006: ID 04f3:0103 Elan Microelectronics Corp. 
Bus 003 Device 007: ID 1740:9603 Senao

Theoretically, they come already paired with the devices they were sold with. I have plenty of usb ports. I just want the damnable things to work. Still searching for some explanation why a simple usb device is not working?

Incredibly frustrating. This is all over the web, so I can't imagine why it has not been caught and addressed, but what I am looking for here is anyone with some experience with USB, keyboards, mice, etc to know if there is a decent workaround.

ShaneRoach · 02-02-2014, 12:39 AM

Ok, here's the work around such as it is.

Root command line.

modprobe -r hid_logitech_dj && modprobe hid_logitech_dj

modprobe -r removes the module from the kernel, then modprobe adds it back in. It may take a few tries. There is bound to be a script to do this more effectively but for tonight I am done. Leaving the thread unsolved for now in hopes of someone better than me at this coming through with a better script.

Thanks to all of you who have read through this and given it a shot.

Or even just read through, scratched your heads collectively, and moved on. ;-)

ShaneRoach · 02-02-2014, 01:50 PM

The script (modprobe -r hid_logitech_dj && modprobe hid_logitech_dj) re-connects each Logitech unifying USB separately. In order to get both my Logitech devices on one USB, I went ahead and reinstalled Solaar. That software runs fine under Debian Linux and puts both mouse and keyboard on the same USB device. I still have to run the script a couple of times, but once it finally does pick up the USB, I get both devices up and running, which is better.

Now I need to figure out what to do to automate all of this detection stuff. There is also the possibility of there being software to help one program the mouse keys, but I am not as interested in this.

Just an update. Any help much appreciated.

I'd especially like to know who I contact to work on the driver for this with. I believe from reading around the web that it is all fixed in Sid, but why no backport yet I have no idea.

fuorviato · 02-02-2014, 04:34 PM

When it comes to automating the script so it is ran on each boot, you can put it in rc.local file.
You can find it under

Quote:

/etc/rc.local

presumably.

ShaneRoach · 02-05-2014, 10:28 PM

The real solution here is updating the kernel. No idea how to do that in Debian without moving up to Sid... I am not aware of any backport for this issue either.

I upgraded to Sid as I have been intending to do for some time now. Not only do the Logitech devices work, but there is even a handy little icon up in the tray (By your networking, volume, etc) to let you know if they are low on batteries....