Logitech unifying receiver drops out of lsusb

English Hardware
#1

I’ve been using this K270 mouse+keyboard combo for almost two years without problems when suddenly it stopped working (batteries are new).

I’ve tried different ports and different machines, with and without usb extension cable, this is what I have found so far:

Works on new Asus Chromebit but not on older Acer Chromebook. Works on SOME usb ports in one notebook (Tumbleweed) but doesn’t work with any usb ports in another (Leap). USB3 ports are luckier, usb cable is not, even though it worked fine until now.

On this desktop it sometimes appears briefly in lsusb output but then disappears again. When it comes up Xorg logs it normally and then cleanly unloads it when it drops off lsusb list, I can post Xorg.0.log file if necessary.

Sometimes, if run right after plugging it in, lsusb needs a few seconds to show the output, sometimes it registers immediately. It always goes away, though.

I have another Logitech wireless keyboard+mouse set which works fine so far, this is how they are shown in lsusb when it works:

stan@linux-pwfe:~> lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.  
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.  
Bus 001 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 003 Device 002: ID 048d:1336 Integrated Technology Express, Inc. SD/MMC Cardreader
Bus 003 Device 021: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 011: ID 046d:c534 Logitech, Inc.  
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
stan@linux-pwfe:~> lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.  
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.  
Bus 001 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 003 Device 002: ID 048d:1336 Integrated Technology Express, Inc. SD/MMC Cardreader
Bus 003 Device 011: ID 046d:c534 Logitech, Inc.  
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
stan@linux-pwfe:~>

“Unifying Receiver” is the troublesome one.

So, is this a faulty device or some other problem? I see there was a kernel bug with these things a few years ago:

Logitech K350 (Unifying) doesn’t work after update to linux 3.10

It might have been developing this problem slowly over time and caused garbage output that woke up the monitor in this thread from last month. That problem disappeared after disabling KDE power management, however. On this machine it’s still turned off.

#2

I would guess that it’s a hardware issue.

I have a logitech mouse with unifying receiver, and it is working fine.

This is on my desktop. I plug the receiver into a front port on desktop. If I plug into a rear port, then it keeps dropping out. There’s probably too much metal (conductive material) between mouse and receiver when I use a rear port.

I also using a similar mouse on my laptop, with receiver on a rear port. And I am not having problems with that.

#3

Right, I just want to make sure it’s the mouse hardware issue rather than anything else. I use the usb cable to connect the receiver to the rear port and then tape it to the top of the monitor. That’s another hardware component that might interfere but no, it fails even when plugged in directly. And it drops from lsusb list even when the mouse and keyboard are switched off. I thought that another Logitech wireless mouse might interfere with it but no, it fails even when I use the wired mouse and keyboard.

What’s there in the receiver to fail, though?

Otherwise it’s a perfectly good keyboard and a flawless mouse. Should they be thrown away now?

#4

I think you can replace the receiver. But then you have to configure the receiver to accept that mouse and keyboard. I’m not sure how to do that. Hopefully, someone who has already done that will pop into the thread.

#5

On Mon 14 Mar 2016 01:06:01 PM CDT, nrickert wrote:

Stan_Ice;2758696 Wrote:
> Otherwise it’s a perfectly good keyboard and a flawless mouse. Should
> they be thrown away now?

I think you can replace the receiver. But then you have to configure
the receiver to accept that mouse and keyboard. I’m not sure how to do
that. Hopefully, someone who has already done that will pop into the
thread.

Hi
Install the solaar package to configure the receiver.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.4|3.12.53-60.30-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!