Problems with Logitech bluetooth mouse (M215) and keyboard (K360)
I bought the keyboard and mouse as a set a while ago. I just made the jump back into the Linux world by installing Arch on my Asus Q500A laptop after both getting fed up with Windows 10, and realizing that everything I kept Windows around for now runs on Linux!:D
I'm having an intermittent problem with my wireless keyboard and mouse. The touchpad and laptop keyboard are not affected. The mouse is unresponsive, moving just a little bit here and there, and the keyboard may recognize a key press, or may not, or it may input the key five or six times on one key press, command line or X makes no difference.The problem only manifests itself when I first power on the computer, but if I reboot it, they work flawlessly thereafter. This is dmesg | tail from when I first booted up this morning. Code:
[ 45.033512] logitech-hidpp-device 0003:046D:4004.0005: HID++ 2.0 device connected. |
Just thoughts.
Not sure what is going on. At one time Knoppix put in a wait state to let usb power up or as they called it "settle". Maybe you can replicate this issue by full power down and remove battery. Then press power button a few times to see if it fails on cold boot normally. It may be possible to put some wait state in this to give time for the usb. I know that it should normally work even in bios so I guess you could double check to see if it works correctly there. |
Well, I never did figure out the root cause of this issue, but I just recently installed updates with pacman -Syu, and the issue has not manifested itself since. I know one of the updates was to the Linux kernel, but I didn't really look at the rest of them that much, so I can't say for sure if maybe something in the kernel was patched, or if it was something else that fixed it.
|
logitech error after kernel update
Hi:
I have a similar error: logitech-hidpp-device 0003:046D:200D.0006 Unable to retrieve the name of the device. I'm running SuSE Tumbleweed and the error started after a kernel update that took me from 4.14.12.1 to 4.14.13.1. I used Snapper to go back to previous kernel. Same problem when 4.14.14.1 was pushed - Rolled back to 4.14.12.1. I have 4.14.15.1 lurking. Will try that later today. |
All times are GMT -5. The time now is 08:07 PM. |