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

Install on Fedora #33

Open
Azumix opened this issue Oct 21, 2019 · 16 comments
Open

Install on Fedora #33

Azumix opened this issue Oct 21, 2019 · 16 comments

Comments

@Azumix
Copy link

Azumix commented Oct 21, 2019

Hello,
Thanks for your software. Is there any way to install it on Fedora / RedHat based systems ?
Thanks.

@Gibtnix
Copy link
Owner

Gibtnix commented Oct 22, 2019

Hello,
I think it should work without any problem. You only need to install the libsub package (called something like libusb-dev-*) download the repo and compile it by running 'make'. If something is missing or incorrectly configured, simply post the error message here and I'll try to help to fix the error.

@phoniclynx
Copy link

phoniclynx commented Nov 3, 2019

I get this error on Fedora

make
gcc -m64 -pipe -O3 -Wall -W -D_REENTRANT -c src/main.c -o .obj/main.o
In file included from src/main.c:10:
src/msiklm.h:15:10: fatal error: hidapi/hidapi.h: No such file or directory
   15 | #include <hidapi/hidapi.h>
      |          ^~~~~~~~~~~~~~~~~
compilation terminated.
make: *** [Makefile:38: .obj/main.o] Error 1

@Gibtnix
Copy link
Owner

Gibtnix commented Nov 3, 2019

The error occurs because the libusb package is either not installed or its install path is missing in the makefile's include directory. So first make sure that the libusb-dev equivalent package is installed (it's important to also install the header files and not only the libraries, i.e. the '-dev' package is required) and if the error still occurs, adjust the makefile's include directory accordingly.

@Dimitri2g
Copy link
Contributor

Having the same issue and I installed libusb and libusb-devel

localhost MSIKLM]$ make gcc -m64 -pipe -O3 -Wall -W -D_REENTRANT -c src/main.c -o .obj/main.o In file included from src/main.c:10: src/msiklm.h:15:10: fatal error: hidapi/hidapi.h: No such file or directory 15 | #include <hidapi/hidapi.h> | ^~~~~~~~~~~~~~~~~ compilation terminated. make: *** [Makefile:38: .obj/main.o] Error 1

@Dimitri2g
Copy link
Contributor

Fixed it.
sudo dnf install -y hidapi hidapi-devel

@Dimitri2g
Copy link
Contributor

Dimitri2g commented Apr 17, 2020

I only get the three colours across my keyboard when I do sky, yellow, purple orange.
Red, Blue, Green, don't work and none of the breathe or wave effects work.

I have a GT70 running fedora 31

@Gibtnix
Copy link
Owner

Gibtnix commented Apr 17, 2020

First of all it's good to know that it is at least partially working. You should try to add the intensity argument (i.e. 'sudo msiklm green high' instead of 'sudo msiklm green') because the explicit intensity argument will use a different command structure - maybe this one is working on your notebook. Check out the readme or the set_color function in msiklm.c for more information about it.

@Dimitri2g
Copy link
Contributor

Dimitri2g commented Apr 17, 2020

The intensity works and I get what seems to be all the colours working now. I still have not gotten the modes like wave or breathe to work so not sure if this requires some fixes or it just won't work on fedora. It used to work with the factory OS.
I would also like to say thank you for your efforts in putting this repo together and sharing it. Let me know if there is something I can do to help in the future.

@Gibtnix
Copy link
Owner

Gibtnix commented Apr 18, 2020

Honestly, I don't know why they should work on one distro but not on the other - the hardware supports it and my code is obviously the same - maybe the libusb/hiapi package does something differently? But this is only spectaculating... But of course, combine it with the intensity if you also set the color and still it might be worth a try to do it in two calls: First set the color (sudo msiklm green high or whatever color configuration you want to use) and thereafter only set the mode in a second call (sudo wave).

@Dimitri2g
Copy link
Contributor

@Gibtnix Thanks for your help. So I tried that and read through the help and everything but for some reason modes won't work properly on the GT70. Not sure if this is something that can come in a later update but it would be cool if we could 1. add dnf support and 2. potential fix what the issue is with getting modes to work on GT70 and/or similar model.

Great work with this and thank you again for being active and responding.

@Gibtnix
Copy link
Owner

Gibtnix commented Apr 22, 2020

No problem, you're welcome. For the modes it might be possible to verify whether or not it works on Windows using the SteelSeries Engine (in case you are on a dual-boot setup) and if so, maybe try to analyse the communication with the keyboard with tools like Wireshark. Still, this can also be slightly complicated. Alternatively, the mode argument is only a single byte. Thus, it is possible to explicitly test all 255 values (maybe with a 5 seconds pausing in between or so) and check if any of them work. However, I don't know if that can somehow cause any damage if you send nonsense commands....

@Dimitri2g
Copy link
Contributor

It works on windows with every mode and colour combination.
I will try to play around with some things and see. I will also set up wireshark and see. Been busy this week so I might get around to it later on.
2020-04-22_1807

@Dimitri2g
Copy link
Contributor

So modes are working now but I am not entirely sure what made it work. I reinstalled fedora and I used the ./install.sh this time around install of building manually. I have tested WAVE and BREATHE and both work.
Thank you @Gibtnix

@Gibtnix
Copy link
Owner

Gibtnix commented Apr 25, 2020

Alright, glad that it was something that could be fixed 👍

@Dimitri2g
Copy link
Contributor

@Gibtnix Can we add support in `install.sh``` for Fedora and Redhat/Centos 7/8
I tried committing a few short lines for this but I don't have permission to.

@Gibtnix
Copy link
Owner

Gibtnix commented Apr 25, 2020

Sure, you're welcome to extend the functionality. You can either create a pull request or alternatively adjust the file accordingly and attach it here. Thereafter, I will update the file in the repository.

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