Askannz/msi-perkeyrgb

Does not work for gl65

koder5665 opened this issue · 15 comments

Any major compatibility issue with gl65 ?

Compatibility with what?
I'm running Ubuntu 20.04 Mate desktop on a new MSI GE75 with no major issues to complain about.
I haven't found a way to light the USB ports yet, and only have limited control of the keyboard back lights. Other than that I've not yet found anything else to complain about.
I did have an internal speaker issue which requires me to run a script each time I boot or use the headphone jack.
That was resolved by the command:
alsactl restore

Am also running on ubuntu 20.04 desktop . Cant get keyboards lit with any of the presets supported in this package.

What the output of lsusb?
And what command are you using to light the keys?

I am on a GL65 and other than not being able to edit the colors of extra keys when I press function keys ( I can't seem to do this on windows either, might be wrong), everything works just fine. I just have to run it as sudo everytime I want to change something (Also, I am very happy to find this project, I wanted to make it so that say on a tiling window manager, when I press the windows key, only the keys bound to shortcuts light up and are color coded. Super happy about this project. Might be able to contribute some code as well)

I'm not sure what you're wanting to do, but if you want something other than the same colour lighting all the keys you need to create a config file and use the -c option to path the config file.
I just use the following command usually:
msi-perkeyrgb --model GE75 -s ffffff
for a white backlight
or for a theme
msi-perkeyrgb --model GE75 -p {theme name}
themes:
aqua, chakra, default, disco, drain, freeway, rainbow-split, roulette

It's 0130 here, so off to bed now.

The README.md file explains how to apply different colours to individual keys.

image
What I was trying to do is change this red color. When I press the function key, these keys turn red. I couldn't find the key codes for some keys, but for those that I did usingn xev, say for example 93, I get: 93 is not a valid keycode.

My assumption is that these colors are hard coded (like I don't have a shortcut bound to the sleep key but pressing that still puts the system to sleep, so that is probably hard coded) and I can't change them, but would love it if I could.

It is not exactly an issue to me, more of a creature comfort.

As best I can tell, pressing the FN key lights those keys red by default.
The key codes for each key are:

0 - 8 INVALID KEY CODES

ESC = 9
1 = 10
2 = 11
3 = 12
4 = 13
5 = 14
6 = 15
7 = 16
8 = 17
9 = 18
0 = 19

  • = 20
    = = 21
    BACKSPACE = 22
    TAB = 23
    Q = 24
    W = 25
    E = 26
    R = 27
    T = 28
    Y = 29
    U = 30
    I = 31
    O = 32
    P = 33
    [ = 34
    ] = 35
    ENTER = 36
    CTRL = 37
    A = 38
    S = 39
    D = 40
    F = 41
    G = 42
    H = 43
    J = 44
    K = 45
    L = 46
    ; = 47
    ' = 48
    ` = 49
    \ = 50
    LSHIFT = 51
    Z = 52
    X = 53
    C = 54
    V = 55
    B = 56
    N = 57
    M = 58
    , = 59
    . = 60
    / = 61
    RSHIFT = 62
  • = 63 # NUM PAD
    LALT = 64
    SPACE BAR = 65
    CAPS LOCK = 66
    F1 = 67
    F2 = 68
    F3 = 69
    F4 = 70
    F5 = 71
    F6 = 72
    F7 = 73
    F8 = 74
    F9 = 75
    F10 = 76
    NUM LOCK = 77
    SCROLL LOCK = 78
    7 = 79 # NUM PAD
    8 = 80 # NUM PAD
    9 = 81 # NUM PAD
  • = 82 # NUM PAD
    4 = 83 # NUM PAD
    5 = 84 # NUM PAD
    6 = 85 # NUM PAD
  • = 86 # NUM PAD
    1 = 87 # NUM PAD
    2 = 88 # NUM PAD
    3 = 89 # NUM PAD
    0 = 90 # NUM PAD
    . = 91 # NUM PAD

92 AND 93 INVALID KEY CODES

KEY BETWEEN SPACEBAR AND RALT = 94
F11 = 95
F12 = 96

97 - 103 INVALID KEY CODES

ENTER = 104 # NUM PAD
RCTRL = 105
/ = 106
PRT SCR = 107
RALT = 108

109 110 INVALID KEY CODES

UP ARROW = 111
PGUP = 112
LEFT ARROW = 113
RIGHT ARROW = 114

115 INVALID KEY CODE

DOWN ARROW = 116
PGDN = 117
INSERT = 118
DELETE = 119

120 - 126 INVALID KEY CODES

PAUSE = 127

128 - 132 INVALID KEY CODES

RIGHT WIN KEY = 133

134 - 155 INVALID KEY CODES # STOPPED LOOKING AT 155

KEY CODE FOR "ARROW" AND "." ON NUM PAD NOT FOUND

FN = fn

I am running
msi-perkeyrgb --model GE75 -s ffff00
as GE75 was closest to gl65. Tried running this up with creating a new config file as well to no avail.

Output of lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1038:1122 SteelSeries ApS SteelSeries KLC
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 001 Device 006: ID 8087:0026 Intel Corp.
Bus 001 Device 005: ID 04f2:b695 Chicony Electronics Co., Ltd HD Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

"msi-perkeyrgb --model GE75 -s ffff00" Lights my keyboard yellow.
What's in /etc/udev/rules.d/99-msi-rgb.rules?
And have you tried increasing the brightness of the keyboard back lighting?

So stupid, didnt check brightness before. Thanks its working now.

It took me a while to find out how to do that too.
I don't understand WHY computer hardware manufacturers are not REQUIRED BY LAW to provide FULL documentation on how to communicate functionally with their products. I see nothing proprietary being exposed by allowing hardware users the ability to create their own software to control the hardware they purchase. Perhaps a class action suit by all Linux users would prevail in accomplishing that?

I'm still searching to find how to turn the lights on in the USB ports; anyone have any luck with that?

wait, do the usb ports of GL65 have lights in them ? ( I just go this laptop, so don't know much )

As best I can tell, pressing the FN key lights those keys red by default.

This is what I wanted to change, but seems it cannot be changed. I was actually ricing my system with green as the base color.

It took me a while to find out how to do that too.
I don't understand WHY computer hardware manufacturers are not REQUIRED BY LAW to provide FULL documentation on how to communicate functionally with their products. I see nothing proprietary being exposed by allowing hardware users the ability to create their own software to control the hardware they purchase. Perhaps a class action suit by all Linux users would prevail in accomplishing that?

I'm still searching to find how to turn the lights on in the USB ports; anyone have any luck with that?

wait, do the usb ports of GL65 have lights in them ? ( I just go this laptop, so don't know much )

As best I can tell, pressing the FN key lights those keys red by default.

This is what I wanted to change, but seems it cannot be changed. I was actually ricing my system with green as the base color.
I'm not familiar with the specs of the GL65, and just recently got my GE75 and the lighting was the major factor due to my poor eyesight. I have to use a flash light to find the USB ports on the side when I need to plug something in. I turned the USB lights on in Windows, but they don't light when I use Linux. I'm going to ask MSI if they can provide some info on how to view and change the keyboard/USB port lighting settings. If I get some help from them I'll pass it along.
Something else I noticed is a key between the space bar and the right alt key, keycode 94, showing "|" and "" on the key cap, but produces "<" or ">" when used.

Something else I noticed is a key between the space bar and the right alt key, keycode 94, showing "|" and "" on the key cap, but produces "<" or ">" when used.

Same on GL65