Keyboard and Mouse Issues with Linux Mint

VitrasSlade

Reputable
Aug 23, 2015
103
0
4,690
Linux Mint 17.2 kernel 3.19.0-30

I have a Corsair K70 (keyboard) and Sabre (mouse). Even after updating Linux Mint my keyboard/mouse do not respond at the login screen until about 20-30 seconds later. My keyboard also doesn't have working indicators (numlock/caplock) after logging in. (Tried plugging in a regular old Dell keyboard and that had the same issues on startup.)

The utility software provided by Corsair is for Windows and Wine gives me an error message when I open the installer.

When booting up there is a USB error message (which I can't read properly since it goes too fast) repeated about 4 times with the code -71 at the end. Can't find anywhere that elaborates on that.

I'm still new to using Linux, so I don't know everything that I probably should.

Any help is appreciated.
 
Solution
I remember having similar problems with my K70 keyboard.. but it's been a while. I had plug it into the back of the computer rather than using a usb extension hub, and use the usb2 ports rather than usb3. My caps-lock indicator works, but not the num-lock light. Also, sometimes keyboard lag can be solved by installing the proprietary driver for your graphics card. That is especially true for the Cinnamon desktop on Mint. I don't think there's any Corsair software for the K70 on Linux. If you change the usb ports while the computer is on, be sure to plug the power cable in before the data cable or you could mess up the keyboard.
I remember having similar problems with my K70 keyboard.. but it's been a while. I had plug it into the back of the computer rather than using a usb extension hub, and use the usb2 ports rather than usb3. My caps-lock indicator works, but not the num-lock light. Also, sometimes keyboard lag can be solved by installing the proprietary driver for your graphics card. That is especially true for the Cinnamon desktop on Mint. I don't think there's any Corsair software for the K70 on Linux. If you change the usb ports while the computer is on, be sure to plug the power cable in before the data cable or you could mess up the keyboard.
 
Solution


(It's perfectly fine and understandable that you can't read the text at boot time -- I have a MBP and when I boot to Linux the text is too tiny and goes too fast for one of my best friends who, like me, is a super nerd. The only reason why I can read the text is because I've become accustomed to it.) ← Personal anecdote (skip if you don't care)

Aside from the personal anecdote, I suggest you post your logs so that I/we may read them and find the problem(s). The following is a list of log files which will help me/us:

  • /var/log/boot.log
    /var/log/daemon.log
    /var/log/dmesg
    /var/log/kern.log
    /var/log/messages
    /var/log/Xorg.x.log

I suggest using the cat command to get the information so that you may copy it. I encourage you to redact any information you believe to be sensitive. The following website provides a modest explanation of what's contained in each log file: http://www.thegeekstuff.com/2011/08/linux-var-log-files/
 


I found the line that I see repeated a few times when it's booting up in the dmesg log:

usb 1-2: device descriptor read/64, error -71

And there's different serial numbers for each, but otherwise exactly the same. What does it mean?
 


That was it. It's almost sad how simple that was, haha. Thanks a bunch! Saves me a huge headache. :)