K70 RGB core troubleshooting for RGB control

Ask Fedora
,
1

Having an unfun time trying to turn this lame seizure inducing pointless c*ap off. Openrgb, ckb-next, and icue using crossover or base wine are failing me.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 003 Device 003: ID 1058:25ea Western Digital Technologies, Inc. My Passport 25EA
Bus 003 Device 005: ID 1b1c:0a63 Corsair CORSAIR VIRTUOSO XT Wireless Gaming Headset
Bus 003 Device 009: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 003 Device 010: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 003 Device 012: ID 1b1c:0a64 Corsair CORSAIR VIRTUOSO XT Wireless Gaming Receiver
Bus 003 Device 013: ID 1b1c:1bff Corsair CORSAIR K70 CORE RGB Mechanical Gaming Keyboard
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 004 Device 003: ID 0781:5588 SanDisk Corp. Extreme Pro
Bus 004 Device 006: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub
Bus 004 Device 007: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 1b1c:1b5c Corsair CORSAIR NIGHTSWORD RGB Gaming Mouse
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

The keyboard shows up fine above, but refuses to show up in either openrgb or ckb-next.
I have quite a few “RGB” devices since they’re impossible to get away from now, including memory, asus motherboard, I think even the headset which is ludicrous, but whatever. The mouse and keyboard I just bought are the issue, mouse works fine for openrgb and ckb-next. Icue is just bombing on install:

noone@fedora:~/Downloads$ wine Install\ iCUE.exe
002c:fixme:winediag:loader_init wine-staging 9.15 is a testing version containing experimental patches.
002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org.
0088:fixme:wineusb:query_id Unhandled ID query type 0x5.
0088:fixme:wineusb:query_id Unhandled ID query type 0x5.
0088:fixme:wineusb:query_id Unhandled ID query type 0x5.
0088:fixme:wineusb:query_id Unhandled ID query type 0x5.
0088:fixme:wineusb:query_id Unhandled ID query type 0x5.
0088:fixme:wineusb:query_id Unhandled ID query type 0x5.
0130:fixme:combase:RoGetActivationFactory (L"Windows.UI.ColorHelper", {8504dbea-fb6a-4144-a6c2-33499c9284f5}, 000000000011FE00): semi-stub
0130:err:ole:ensure_mta Failed, hr 0x800401f0.
0130:fixme:combase:RoGetActivationFactory (L"Windows.UI.ColorHelper", {8504dbea-fb6a-4144-a6c2-33499c9284f5}, 000000000011FE00): semi-stub
0130:err:combase:RoGetActivationFactory Failed to find library for L"Windows.UI.ColorHelper"
0130:fixme:combase:RoOriginateLanguageException 0x80040154, L"", 0000000000000000: stub
0130:err:seh:NtRaiseException Unhandled exception code c0000409 flags 1 addr 0x140111085

Any insight on either appreciated, as in resolving them not showing up in the interfaces, or getting iCUE to install with wine to see if that would at least let me disable the grand mall seizure aspect of the keyboard.

misc info, unlikely necessary but just in case:
Linux fedora 6.12.6-100.fc40.x86_64
KDE spin
all packages updated with no errors: “sudo dnf update --refresh”

2

I had a 1b1c:1b38 Corsair Corsair Gaming K70 RGB RAPIDFIRE Keyboard that worked fine with ckb-next immediately after installing it on Fedora, but it’s been over a year since I last tried.

I only used OpenRGB on Windows but it worked fine and detected.

A quick search on ckb-next’s GitHub didn’t show any results for 1b1c:1bff, so I’m not too sure if it’d support that keyboard out-the-box. Depending on how different it is, maybe support could be made easily from an existing device on ckb-next’s end.

iCUE through Wine I wouldn’t expect to work, but it’ll likely need to access the keyboard through USB (possible hid/raw with Wine permissions allowed). Depending on how new that keyboard is, I’d recommend either V2 CUE or the last V3 version (iCUE 4+ are bloated).

If the keyboard saves lighting states to its own hardware, it’d probably be easiest to do it from a different computer with Windows real quick (I preferred iCUE on a different Windows PC for my HARPOON mouse Hz/DPI config vs ckb-next on Linux).

3

Meh, tried openrgb’s experimental, couldn’t find it either (OpenRGB - Supported devices). That at least let me know what to search for, as I wasn’t sure before (1B1C:1BFF).

Added it to openRGB’s ticketing system to hopefully be added. Did the same for ckb-next now.

Thanks Espionage724, not a “solution” per say, but should lead to one for others down the line, and hopefully soon for my sore eyes. Have I mentioned I loathe RGB?

1 Like
4

I have managed to avoid rgb for mouse and mechanical keyboard.
Might have some inside the case, but the case does not have glass sides, deliberately.