Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GE66 Raider - No compatible keyboard #42

Open
emanueleghedini opened this issue Aug 26, 2021 · 8 comments
Open

GE66 Raider - No compatible keyboard #42

emanueleghedini opened this issue Aug 26, 2021 · 8 comments

Comments

@emanueleghedini
Copy link

emanueleghedini commented Aug 26, 2021

Thanks for the tool! However, it seems not to recognize the GE66 Raider device (Ubuntu 21.04).

Here is the output of ./msiklm list

Device: SteelSeries KLC
Device Vendor ID: 4152
Device Product ID: 4386
Device Serial Number: (null)
Device Manufacturer: SteelSeries
Device Path: 0001:0003:00
Device Interface Number: 0
Device Release Number: 567

Device: SteelSeries KLC
Device Vendor ID: 4152
Device Product ID: 4386
Device Serial Number: (null)
Device Manufacturer: SteelSeries
Device Path: 0001:0003:01
Device Interface Number: 1
Device Release Number: 567

Device: SteelSeries ALC
Device Vendor ID: 4152
Device Product ID: 4402
Device Serial Number: (null)
Device Manufacturer: SteelSeries
Device Path: 0001:0004:00
Device Interface Number: 0
Device Release Number: 550

Device: SteelSeries ALC
Device Vendor ID: 4152
Device Product ID: 4402
Device Serial Number: (null)
Device Manufacturer: SteelSeries
Device Path: 0001:0004:01
Device Interface Number: 1
Device Release Number: 550

@Gibtnix
Copy link
Owner

Gibtnix commented Aug 26, 2021

I don't know whether this keyboard is compatible or not. It might be worth a try to replace the IDs in open_keyboard() function with the vendor and product IDs of your keyboard, cf. line 324 in msiklm.c. If you replace the IDs accordingly and recompile the program, running sudo msiklm test should find the keyboard. If this holds, you can try to use either of the two modes (i.e. with or without explicitly setting the brightness which results in different command structures; explained in full detail in the readme). Maybe one of them works, but if not, your keyboard might simply be not supported.

@emanueleghedini
Copy link
Author

Thanks for the suggestion. I've tried to replace the IDs in the code with the IDs of both listed devices. In both cases the execution, after recompile, led to no effect. Probably it is simply not yet supported as you suggested.

@Gibtnix
Copy link
Owner

Gibtnix commented Aug 27, 2021

But did the software detect your keyboard using sudo msiklm test? If not, the IDs were probably not correct. Make sure not to confuse decimal with hexadecimal numbers.

@emanueleghedini
Copy link
Author

Yes, the test was successful for both couples of vendor and product IDs that were listed.

@Gibtnix
Copy link
Owner

Gibtnix commented Aug 28, 2021

OK, then I think your keyboard uses a different command structure and is not compatible with the current implementation, sorry...

@Raunak-Singh-Inventor
Copy link

@Gibtnix Same problem with MSI Ge76 Raider Pop OS (Ubuntu) linux, any resolution???

@Tatsh
Copy link

Tatsh commented Jun 20, 2022

Someone is going to have to run a USB monitor while using the Steelseries GG app. This can be done with Wireshark and USBpcap.

@Gibtnix
Copy link
Owner

Gibtnix commented Jun 20, 2022

Is exactly as @Tatsh said - there is no documentation available on how to communicate with the keyboard. I've added some comments at #46 and I'm open to extend the program for other devices. But I cannot find out which command structure is required for which keyboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants