Help please Corsair SCIMITAR PRO RGB Mouse doesn't work at all in Suse

I have the Corsair SCIMITAR RGB mouse (which works), and the most recent Corsair Gaming SCIMITAR PRO, I got this last one because it has onboard memory, so I could set macros or whatever bindings in windows, and have it working in Suse.

The surprise is that it doesn’t work at all in Suse, works perfectly at boot (BIOS), and in Windows.

It doesn’t get any output in
cat /dev/input/mice

Relevant output from:

hwinfo --mouse

35: USB 00.0: 10503 USB Mouse
[Created at usb.122]
Unique ID: VBUu.+GZlG+AMzX5
Parent ID: ADDn.4Nx_qoDfSd7
SysFS ID: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0
SysFS BusID: 1-1.5:1.0
Hardware Class: mouse
Model: “Corsair Gaming SCIMITAR PRO RGB Mouse”
Hotplug: USB
Vendor: usb 0x1b1c “Corsair”
Device: usb 0x1b3e “Corsair Gaming SCIMITAR PRO RGB Mouse”
Revision: “1.09”
Serial ID: “0603F027AEBD1500562C2173F5001941”
Compatible to: int 0x0210 0x0015
Driver: “usbhid”
Driver Modules: “usbhid”
Device File: /dev/input/mice (/dev/input/mouse0)
Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event6, /dev/input/by-id/usb-Corsair_Corsair_Gaming_SCIMITAR_PRO_RGB_Mouse_0603F027AEBD1500562C2173F5001941-event-mouse, /dev/input/by-path/pci-0000:00:1a.0-usb-0:1.5:1.0-event-mouse, /dev/input/by-id/usb-Corsair_Corsair_Gaming_SCIMITAR_PRO_RGB_Mouse_0603F027AEBD1500562C2173F5001941-mouse, /dev/input/by-path/pci-0000:00:1a.0-usb-0:1.5:1.0-mouse
Device Number: char 13:63 (char 13:32)
Speed: 12 Mbps
Module Alias: “usb:v1B1Cp1B3Ed0109dc00dsc00dp00ic03isc01ip02in00”
Driver Info #0:
Buttons: 5
Wheels: 1
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #51 (Hub)

evtest

Select the device event number [0-18]: 6
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x1b1c product 0x1b3e version 0x111
Input device name: “Corsair Corsair Gaming SCIMITAR PRO RGB Mouse”
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 272 (BTN_LEFT)
Event code 273 (BTN_RIGHT)
Event code 274 (BTN_MIDDLE)
Event code 275 (BTN_SIDE)
Event code 276 (BTN_EXTRA)
Event type 2 (EV_REL)
Event code 0 (REL_X)
Event code 1 (REL_Y)
Event code 8 (REL_WHEEL)
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Testing … (interrupt to exit)

You’ll see three enties for Corsair here, I have a Corsair keyboard, plus both models of mice mentioned:

lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 1b1c:1b3e Corsair
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 05e3:0612 Genesys Logic, Inc.
Bus 004 Device 002: ID 05e3:0612 Genesys Logic, Inc.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 006: ID 1b1c:1b1e Corsair
Bus 003 Device 034: ID 1b1c:1b07 Corsair
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Of course I tried to boot just with the SCIMITAR PRO, tried all USB ports, updated every system that could help… Nothing.

Any ideas? :confused:

Unfortunately I have some bad news for you and some good news at the same time, according to this thread; https://www.spinics.net/lists/kernel/msg2442348.html it requires kernel level supports because Corsair has done some naughty stuff.

Bad news is it’ll either require manual kernel patching and compilation or waiting for someone else to do it for you.

Thank you for your prompt answer, back at 2006 I used Gentoo, and routinely compiled the kernel manually. Will check how it is done here – otherwise how long do you think will take for us to get the patched kernel?

Thank you.