[SOLVED] Logitech MK520 Wireless Keyboard/Mouse Not Working on Slackware 14.1
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Logitech MK520 Wireless Keyboard/Mouse Not Working on Slackware 14.1
I have a new Slackware 14.1 system on which I'd like to use a Logitech MK520 wireless keyboard and mouse but I can't get it to work. The keyboard works fine while booting at the lilo prompt, but after the system starts the keyboard and mouse are ignored both in a terminal and KDE.
I have two MK520's, same symptoms with both.
Running Ubuntu 14.04 booted from a USB stick, they work fine.
They work fine on a Slackware 13.1 system, and a Win7 system.
Will it start working later if you unplug usb rf device and plug it back in? If so you may then be able to update your install. Slight chance this will fix it.
@jefro: Tried unplugging/replugging the USB RF module, no joy. Tried booting with it plugged in, no go. Tried booting without it plugged in and plugging it in later, no effect. Tried it with conventional USB keyboard & mouse with/without RF module with all above permutations, no effect. Conventional KB/mouse works no matter what, mk520 never does (neither of them).
@zrdc28: I have no idea if bluethooth is on or not, nor do I know how to find out. Note that although it uses a 2.4 GHz radio, it is not a bluetooth device. Assuming that perhaps bluetooth is relevant, the motherboard (Asus Z97 Deluxe) does have integrated bluetooth. Could this be a factor?
The MK520 is not a blue tooth device, but an 2.4 GHz RF device. Although not advertized, all the MKxxx kb/mouse combos work just spiffy with all Linux distros. Here are some steps to troubleshoot:
Does the kb work after boot but before you run "startx"? If so, then X.org is the culprit. (If you set your runlevel to go directly to a GUI login, don't!)
If needed plug in a std ps/2 or usb kb, run "lsusb" to see if your unifying receiver is detected. It should be, mine is.
Two separate devices (by which I mean two separate keyboard/mouse pairs) work flawlessly with Slackware 12.2, Slackware 13.1, and of course Windows 7. Neither works with vanilla 14.1 kernel 3.10.17 beyond the LILO prompt. When presented with the login prompt nothing happens when striking any keys on the keyboard(s). This is on tty1 (through 6 presumably but I can't switch ttys either). Using runlevel 3 so X isn't loaded; although it doesn't work when the GUI is booted either.
I don't recall the device ID but lsusb did list a "Logitech, Inc. Unifying Receiver".
However!
I installed the 3.14.12 kernel from -current after seeing a similar problem involving a Logitech wireless keyboard in this thread, and my keyboard & mouse now work fine. I now have a small display issue, but that's a matter for another thread. Accordingly, I'm marking this thread as [Solved]. Thanks for the suggestions, all!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.