CentOS Plus Kernel – Moving It In And Back Out Again

Home » CentOS » CentOS Plus Kernel – Moving It In And Back Out Again
CentOS 5 Comments

I have been reading the bug reports about the problem with initializing Logitech wireless devices using the current stock CentOS 7 kernel. It’s my understanding that this issue will be fixed in the CentOS Plus kernel.

However, I suspect that the issue will also be fixed at some point when Red Hat get around to fixing their kernel as well.

My main computer has a Logitech wireless mouse that’s likely affected by the bug, though I haven’t tried it yet to verify that.

One of these days I intend to get around to installing CentOS 7 on this computer, and this will then become an issue.

If I install CentOS 7 and then the CentOS Plus kernel to get the Logitech bug fix, what happens when the stock CentOS 7 kernel also gets the bug fix applied? Will a standard “yum update” automatically find and download the new stock CentOS 7 kernel and set everything up to it instead of the CentOS Plus kernel?

I suppose I could go and hunt down a different mouse to use on this computer until the issue is resolved upstream, too.

5 thoughts on - CentOS Plus Kernel – Moving It In And Back Out Again

  • Look in /etc/sysconfig/kernel. There is a line:

    DEFAULTKERNEL=kernel

    For the default kernel, you can select between kernel and kernel-plus by adjusting that option.

    Akemi

  • My first mouse, many years ago with an AT plug, cost me GBP 56 (circa USD 90). These days I use on desktops, laptops, notebooks (all running CentOS of course) etc. mice costing circa GBP 3.00 including postage from China. These cheap mice simply plug into a spare USB socket.

    Get a cheap mouse from China – plug it into a USB socket then carry-on working normally.

  • My Logitech wireless mouse model M510 is NOT affected by this bug. I just plugged it into my laptop that I have CentOS 7 installed on, and it works perfectly.

  • M510 is as affected as anything else with the tiny unified receiver. It’s a race condition though, so sometimes it works, sometimes it doesn’t. It’s more likely to happen on boot, I think. From what I can recall of the Fedora days with the relevant kernels, un- and re-plugging the receiver or un- and re-loading the module would typically get things working again, though it could take a few attempts.