[SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

Aurelio3351 · 2024-02-19 05:46:12

Hi

Some days ago i installed Arch in my MSI Creator Z16 and i'm very happy with the experience (all works great and i managed to resolve all the hybrid graphics problems).

But, i didn't manage to get the keyboard RGB working. Before i installed Arch, i was using Windows, and i thought that the RGB was completely hardware controlled, because it turns on as soon as you turn on the Laptop, but when first booting archiso as soon as GRUB loads, it turns off, and i tried with the Arch Wiki guide https://wiki.archlinux.org/title/keyboard_backlight, with a lot of AUR packages dedicated to MSI laptops specifically, and with some other guides, but nothing worked, and i didn't found anything about my laptop model or even about the "MSI Creator" laptop branch.

Sorry if I make any mistake or if some important details are missing, it's my first post in this forum and i will learn how to make good posts with time.

Thanks in advance.

Edit: Read the last post of this topic for the solution.

Last edited by Aurelio3351 (2024-02-21 02:35:23)

seth · 2024-02-19 13:46:49

https://github.com/Gibtnix/MSIKLM
https://github.com/Koromix/rygel

But the creator keyboard looks like Fn+PgUp/Down would control the keyboard backlight?

Aurelio3351 · 2024-02-20 02:27:07

But the creator keyboard looks like Fn+PgUp/Down would control the keyboard backlight?

In Windows, you can control the keyboard brightness with F8 key.

When using MSIKLM:

[aurelio3351@Z16Aurelio MSIKLM]$ sudo msiklm test
No compatible keyboard found!
Check you're using sudo!

Meestic (Tool from the rygel repository) says that it's only for MSI Delta 15 Laptops but tried it anywhay:

[aurelio3351@Z16Aurelio Fast]$ ./meestic
Error: Cannot find Mystic Light HID device (1462:1562, 1462:1563 or 1462:1564)

Sorry for my late response.

Last edited by Aurelio3351 (2024-02-20 02:28:27)

seth · 2024-02-20 07:43:09

Does the key produce any kind of output in "sudo evtest"?
Interesting devices in /sys/class/leds/ or /sys/class/backlight?

Aurelio3351 · 2024-02-20 19:46:28

Interesting devices in /sys/class/leds/ or /sys/class/backlight?

The first thing i did when trying to get this working was trying to turn on all those devices with brightnessctl, and none of them was my keyboard; they where the capslock or numlock leds, you know.

[aurelio3351@Z16Aurelio ~]$ ls /sys/class/leds
input3::capslock  input3::numlock  input3::scrolllock  phy0-led

(phy0-led is the shutdown button led)

[aurelio3351@Z16Aurelio ~]$ ls /sys/class/backlight
intel_backlight

(intel_backlight is the screen)

Does the key produce any kind of output in "sudo evtest"?

When using "sudo evtest":

[aurelio3351@Z16Aurelio ~]$ sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      Lid Switch
/dev/input/event1:      Sleep Button
/dev/input/event10:     Intel HID 5 button array
/dev/input/event11:     PC Speaker
/dev/input/event12:     MSI WMI hotkeys
/dev/input/event13:     gpio-keys
/dev/input/event14:     PNP0C50:00 06CB:CE4C Mouse
/dev/input/event15:     PNP0C50:00 06CB:CE4C Touchpad
/dev/input/event16:     HDA NVidia HDMI/DP,pcm=3
/dev/input/event17:     HDA NVidia HDMI/DP,pcm=7
/dev/input/event18:     HDA NVidia HDMI/DP,pcm=8
/dev/input/event19:     HDA NVidia HDMI/DP,pcm=9
/dev/input/event2:      Power Button
/dev/input/event20:     sof-hda-dsp Mic
/dev/input/event21:     sof-hda-dsp Headphone
/dev/input/event22:     sof-hda-dsp HDMI/DP,pcm=3
/dev/input/event23:     sof-hda-dsp HDMI/DP,pcm=4
/dev/input/event24:     sof-hda-dsp HDMI/DP,pcm=5
/dev/input/event25:     PS/2 Generic Mouse
/dev/input/event3:      AT Translated Set 2 keyboard
/dev/input/event4:      Video Bus
/dev/input/event5:      Video Bus
/dev/input/event6:      Silicon Integrated System Co. SiS HID Touch Controller
/dev/input/event7:      Silicon Integrated System Co. SiS HID Touch Controller Mouse
/dev/input/event8:      SteelSeries SteelSeries KLC
/dev/input/event9:      Intel HID events
Select the device event number [0-25]:

The "SteelSeries SteelSeries KLC" called my attention because the keyboard is Steelseries brand (it has a Steelseries logo) so i choosed it.

Select the device event number [0-25]: 8
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x1038 product 0x113a version 0x111
Input device name: "SteelSeries SteelSeries KLC"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 1 (KEY_ESC)
    Event code 28 (KEY_ENTER)
    Event code 74 (KEY_KPMINUS)
    Event code 78 (KEY_KPPLUS)
    Event code 103 (KEY_UP)
    Event code 105 (KEY_LEFT)
    Event code 106 (KEY_RIGHT)
    Event code 108 (KEY_DOWN)
    Event code 110 (KEY_INSERT)
    Event code 111 (KEY_DELETE)
    Event code 113 (KEY_MUTE)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
    Event code 119 (KEY_PAUSE)
    Event code 120 (KEY_SCALE)
    Event code 128 (KEY_STOP)
    Event code 130 (KEY_PROPS)
    Event code 131 (KEY_UNDO)
    Event code 133 (KEY_COPY)
    Event code 134 (KEY_OPEN)
    Event code 135 (KEY_PASTE)
    Event code 136 (KEY_FIND)
    Event code 137 (KEY_CUT)
    Event code 138 (KEY_HELP)
    Event code 139 (KEY_MENU)
    Event code 140 (KEY_CALC)
    Event code 142 (KEY_SLEEP)
    Event code 144 (KEY_FILE)
    Event code 150 (KEY_WWW)
    Event code 152 (KEY_SCREENLOCK)
    Event code 155 (KEY_MAIL)
    Event code 156 (KEY_BOOKMARKS)
    Event code 158 (KEY_BACK)
    Event code 159 (KEY_FORWARD)
    Event code 161 (KEY_EJECTCD)
    Event code 163 (KEY_NEXTSONG)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 165 (KEY_PREVIOUSSONG)
    Event code 166 (KEY_STOPCD)
    Event code 167 (KEY_RECORD)
    Event code 168 (KEY_REWIND)
    Event code 169 (KEY_PHONE)
    Event code 171 (KEY_CONFIG)
    Event code 172 (KEY_HOMEPAGE)
    Event code 173 (KEY_REFRESH)
    Event code 174 (KEY_EXIT)
    Event code 176 (KEY_EDIT)
    Event code 177 (KEY_SCROLLUP)
    Event code 178 (KEY_SCROLLDOWN)
    Event code 181 (KEY_NEW)
    Event code 182 (KEY_REDO)
    Event code 204 (KEY_DASHBOARD)
    Event code 206 (KEY_CLOSE)
    Event code 207 (KEY_PLAY)
    Event code 208 (KEY_FASTFORWARD)
    Event code 209 (KEY_BASSBOOST)
    Event code 210 (KEY_PRINT)
    Event code 212 (KEY_CAMERA)
    Event code 216 (KEY_CHAT)
    Event code 217 (KEY_SEARCH)
    Event code 219 (KEY_FINANCE)
    Event code 223 (KEY_CANCEL)
    Event code 224 (KEY_BRIGHTNESSDOWN)
    Event code 225 (KEY_BRIGHTNESSUP)
    Event code 228 (KEY_KBDILLUMTOGGLE)
    Event code 229 (KEY_KBDILLUMDOWN)
    Event code 230 (KEY_KBDILLUMUP)
    Event code 231 (KEY_SEND)
    Event code 232 (KEY_REPLY)
    Event code 233 (KEY_FORWARDMAIL)
    Event code 234 (KEY_SAVE)
    Event code 235 (KEY_DOCUMENTS)
    Event code 240 (KEY_UNKNOWN)
    Event code 241 (KEY_VIDEO_NEXT)
    Event code 244 (KEY_BRIGHTNESS_ZERO)
    Event code 256 (BTN_0)
    Event code 353 (KEY_SELECT)
    Event code 354 (KEY_GOTO)
    Event code 358 (KEY_INFO)
    Event code 362 (KEY_PROGRAM)
    Event code 366 (KEY_PVR)
    Event code 370 (KEY_SUBTITLE)
    Event code 372 (KEY_ZOOM)
    Event code 374 (KEY_KEYBOARD)
    Event code 375 (KEY_SCREEN)
    Event code 376 (KEY_PC)
    Event code 377 (KEY_TV)
    Event code 378 (KEY_TV2)
    Event code 379 (KEY_VCR)
    Event code 380 (KEY_VCR2)
    Event code 381 (KEY_SAT)
    Event code 383 (KEY_CD)
    Event code 384 (KEY_TAPE)
    Event code 386 (KEY_TUNER)
    Event code 387 (KEY_PLAYER)
    Event code 389 (KEY_DVD)
    Event code 392 (KEY_AUDIO)
    Event code 393 (KEY_VIDEO)
    Event code 396 (KEY_MEMO)
    Event code 397 (KEY_CALENDAR)
    Event code 398 (KEY_RED)
    Event code 399 (KEY_GREEN)
    Event code 400 (KEY_YELLOW)
    Event code 401 (KEY_BLUE)
    Event code 402 (KEY_CHANNELUP)
    Event code 403 (KEY_CHANNELDOWN)
    Event code 405 (KEY_LAST)
    Event code 407 (KEY_NEXT)
    Event code 408 (KEY_RESTART)
    Event code 409 (KEY_SLOW)
    Event code 410 (KEY_SHUFFLE)
    Event code 412 (KEY_PREVIOUS)
    Event code 416 (KEY_VIDEOPHONE)
    Event code 417 (KEY_GAMES)
    Event code 418 (KEY_ZOOMIN)
    Event code 419 (KEY_ZOOMOUT)
    Event code 420 (KEY_ZOOMRESET)
    Event code 421 (KEY_WORDPROCESSOR)
    Event code 422 (KEY_EDITOR)
    Event code 423 (KEY_SPREADSHEET)
    Event code 424 (KEY_GRAPHICSEDITOR)
    Event code 425 (KEY_PRESENTATION)
    Event code 426 (KEY_DATABASE)
    Event code 427 (KEY_NEWS)
    Event code 428 (KEY_VOICEMAIL)
    Event code 429 (KEY_ADDRESSBOOK)
    Event code 430 (KEY_MESSENGER)
    Event code 431 (KEY_DISPLAYTOGGLE)
    Event code 432 (KEY_SPELLCHECK)
    Event code 433 (KEY_LOGOFF)
    Event code 439 (KEY_MEDIA_REPEAT)
    Event code 442 (KEY_IMAGES)
    Event code 576 (KEY_BUTTONCONFIG)
    Event code 577 (KEY_TASKMANAGER)
    Event code 578 (KEY_JOURNAL)
    Event code 579 (KEY_CONTROLPANEL)
    Event code 580 (KEY_APPSELECT)
    Event code 581 (KEY_SCREENSAVER)
    Event code 582 (KEY_VOICECOMMAND)
    Event code 583 (KEY_ASSISTANT)
    Event code 584 (?)
    Event code 585 (?)
    Event code 586 (?)
    Event code 587 (?)
    Event code 588 (?)
    Event code 589 (?)
    Event code 592 (KEY_BRIGHTNESS_MIN)
    Event code 593 (KEY_BRIGHTNESS_MAX)
    Event code 608 (KEY_KBDINPUTASSIST_PREV)
    Event code 609 (KEY_KBDINPUTASSIST_NEXT)
    Event code 610 (KEY_KBDINPUTASSIST_PREVGROUP)
    Event code 611 (KEY_KBDINPUTASSIST_NEXTGROUP)
    Event code 612 (KEY_KBDINPUTASSIST_ACCEPT)
    Event code 613 (KEY_KBDINPUTASSIST_CANCEL)
  Event type 2 (EV_REL)
    Event code 6 (REL_HWHEEL)
    Event code 12 (REL_HWHEEL_HI_RES)
  Event type 3 (EV_ABS)
    Event code 32 (ABS_VOLUME)
      Value      0
      Min        0
      Max     4095
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)

And you can see there are "KEY_BRIGHTNESS_MIN" and "KEY_BRIGHTNESS_MAX" events, so i think this is the right way.
I let it on testing some time but nothing happened.
Is there anything else I can do with this evtest?

seth · 2024-02-20 21:23:27

Is there anything else I can do with this evtest?

No, I just wanted to see whether the key does the LEDs in HW or reports to the OS.

Does https://aur.archlinux.org/packages/msi-perkeyrgb cover your device?

Aurelio3351 · 2024-02-20 22:31:25

Does https://aur.archlinux.org/packages/msi-perkeyrgb cover your device?

This package was one of the things that i tried first, but i will give it another chance because i think i didn't tried it well then.

The GitHub page says the package was only tested in GXXX (For example GE63) MSI Laptop models that i really don't know, but i searched my model (Creator Z16) in the MSI web page (https://www.msi.com/Content-Creation/Cr … cification) and it says that it's keyboard is a "Per key RGB MiniLED keyboard by Steelseries", just like the package describes, so i tried the package with all the models that the GitHub page lists, but none worked:

[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb
No laptop model specified, using GE63 as default.
No MSI keyboards with a known product/vendor IDs were found. However, if you think your keyboard should work with this program, you can try overriding the ID by adding the option "--id VENDOR_ID:PRODUCT_ID". In that case you will also need to give yourself proper read/write permissions to the corresponding /dev/hidraw* device.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GE73
No MSI keyboards with a known product/vendor IDs were found. However, if you think your keyboard should work with this program, you can try overriding the ID by adding the option "--id VENDOR_ID:PRODUCT_ID". In that case you will also need to give yourself proper read/write permissions to the corresponding /dev/hidraw* device.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GE75
No MSI keyboards with a known product/vendor IDs were found. However, if you think your keyboard should work with this program, you can try overriding the ID by adding the option "--id VENDOR_ID:PRODUCT_ID". In that case you will also need to give yourself proper read/write permissions to the corresponding /dev/hidraw* device.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GL63
No MSI keyboards with a known product/vendor IDs were found. However, if you think your keyboard should work with this program, you can try overriding the ID by adding the option "--id VENDOR_ID:PRODUCT_ID". In that case you will also need to give yourself proper read/write permissions to the corresponding /dev/hidraw* device.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GS63
No MSI keyboards with a known product/vendor IDs were found. However, if you think your keyboard should work with this program, you can try overriding the ID by adding the option "--id VENDOR_ID:PRODUCT_ID". In that case you will also need to give yourself proper read/write permissions to the corresponding /dev/hidraw* device.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GS65
No MSI keyboards with a known product/vendor IDs were found. However, if you think your keyboard should work with this program, you can try overriding the ID by adding the option "--id VENDOR_ID:PRODUCT_ID". In that case you will also need to give yourself proper read/write permissions to the corresponding /dev/hidraw* device.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GS75
No MSI keyboards with a known product/vendor IDs were found. However, if you think your keyboard should work with this program, you can try overriding the ID by adding the option "--id VENDOR_ID:PRODUCT_ID". In that case you will also need to give yourself proper read/write permissions to the corresponding /dev/hidraw* device.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GT63
No MSI keyboards with a known product/vendor IDs were found. However, if you think your keyboard should work with this program, you can try overriding the ID by adding the option "--id VENDOR_ID:PRODUCT_ID". In that case you will also need to give yourself proper read/write permissions to the corresponding /dev/hidraw* device.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GT75
Unknown MSI model : GT75

(I ran the first one without any parameter and it choosed the GE63)
(Strangely, it didn't take the GT75 model (last one) that is listed on the GitHub page)

In every error message it says "However, if you think your keyboard should work with this program, you can try overriding the ID by adding the option "--id VENDOR_ID:PRODUCT_ID".", so maybe if i found the VENDOR_ID/PRODUCT_ID of my Laptop, it will work.

Last edited by Aurelio3351 (2024-02-20 22:35:20)

seth · 2024-02-20 22:37:54

Input device ID: bus 0x3 vendor 0x1038 product 0x113a version 0x111

--id 1038:113a

Edit: google has https://wiki.archlinux.org/title/User:M … RGB_lights

Last edited by seth (2024-02-20 22:39:09)

Aurelio3351 · 2024-02-20 22:49:00

Sadly, it didn't work:

[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --id 1038:113a -p default
No laptop model specified, using GE63 as default.
No USB device with ID 1038:113a found.

Tried with all other models:

[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GE73 --id 1038:113a -p default
No USB device with ID 1038:113a found.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GE75 --id 1038:113a -p default
No USB device with ID 1038:113a found.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GL63 --id 1038:113a -p default
No USB device with ID 1038:113a found.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GS63 --id 1038:113a -p default
No USB device with ID 1038:113a found.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GS65 --id 1038:113a -p default
No USB device with ID 1038:113a found.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GS75 --id 1038:113a -p default
No USB device with ID 1038:113a found.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GT63  --id 1038:113a -p default
No USB device with ID 1038:113a found.
[aurelio3351@Z16Aurelio ~]$ sudo msi-perkeyrgb --model GT75 --id 1038:113a -p default
Unknown MSI model : GT75

seth · 2024-02-20 22:58:30

No USB device with ID 1038:113a found.

lsusb

Aurelio3351 · 2024-02-20 23:00:15

lsusb result:

[aurelio3351@Z16Aurelio ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
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 27c6:6094 Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 003 Device 004: ID 5986:116f Bison Electronics Inc. HD Camera
Bus 003 Device 006: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 007: ID 0457:1595 Silicon Integrated Systems Corp. SiS HID Touch Controller
Bus 003 Device 008: ID 054c:0d5e Sony Corp. Wireless Headset
Bus 003 Device 009: ID 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

seth · 2024-02-20 23:11:43

wtf? How did evtest find it? 0x3 is BUS_USB…

Also, https://unix.stackexchange.com/question … oesnt-work

Aurelio3351 · 2024-02-20 23:30:28

Yeah, it's really strange. Using the guide you provided, finding the idVendor with "find -L /sys/bus/usb/devices/ -maxdepth 2 -name idVendor -exec sh -c 'echo "{}->"; cat {}' \;" throws this:

[root@Z16Aurelio aurelio3351]# find -L /sys/bus/usb/devices/ -maxdepth 2 -name idVendor -exec sh -c 'echo "{}->"; cat {}' \;
/sys/bus/usb/devices/3-8/idVendor->
5986
/sys/bus/usb/devices/3-11/idVendor->
054c
/sys/bus/usb/devices/usb3/idVendor->
1d6b
/sys/bus/usb/devices/3-6/idVendor->
0457
/sys/bus/usb/devices/usb1/idVendor->
1d6b
/sys/bus/usb/devices/3-2/idVendor->
27c6
/sys/bus/usb/devices/3-14/idVendor->
8087
/sys/bus/usb/devices/usb4/idVendor->
1d6b
/sys/bus/usb/devices/usb2/idVendor->
1d6b
/sys/bus/usb/devices/3-1/idVendor->
046d

None it's the keyboard id. It's like the keyboard it's not registered as an USB device, but it is, because evtest says that.

Aurelio3351 · 2024-02-21 00:04:46

This are the things why Arch and Linux in general are just incredible.

I rebooted my Laptop and executed "lsusb" again and now for some fucking reason the SteelSeries device now shows!

[aurelio3351@Z16Aurelio ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
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 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse
Bus 003 Device 003: ID 27c6:6094 Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 003 Device 005: ID 5986:116f Bison Electronics Inc. HD Camera
Bus 003 Device 006: ID 054c:0d5e Sony Corp. Wireless Headset
Bus 003 Device 007: ID 1038:113a SteelSeries ApS SteelSeries KLC
Bus 003 Device 008: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 009: ID 0457:1595 Silicon Integrated Systems Corp. SiS HID Touch Controller
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Tried to turn it on now with msi-perkeyrgb and the leds show some signals when using default but it doesn't turn on (i supose default it's just all turned off) but i tried with the aqua preset and it gives an error and now THE DEVICE DISAPPEARED AGAIN!

Im gonna try rebooting again...

Last edited by Aurelio3351 (2024-02-21 01:17:03)

Aurelio3351 · 2024-02-21 02:32:24

Finally, after a lot of time spent on this, i've managed to turn the keyboard RGB on:
The problem of the device not showing with lsusb is solved with turning off and turning on the Laptop (NOT REBOOTING), it may be some sort of bug when messing with the USB buses.

The real problem is that you need to "unbind" the USB device that controlls the keyboard RGB, for that you can follow this guide: https://unix.stackexchange.com/question … oesnt-work (Thanks to Seth who sent the guide and for all the help). And that should be it, there is no need to use the msi-perkeyrgb or any other package (unless you want to change the colors), the keyboard will turn on with the default color set that it has on Windows.

If you want to change the colors, you can use the msiperkey-rgb (AUR) package https://github.com/Askannz/msi-perkeyrgb (You have to use this package before using the unbind command, but if you already used it, just reboot, change the color, and run the unbind command again), but the problem is that this package is focused on other MSI Laptop models, so the majority of his color presets do not work well (read the GitHub README file and all this topic for the information on how to use it, because it will not work by default), and if you change the color with this package you will overwrite the default color set of the keyboard, so be careful. (If you found a better package for the Creator Z16, or have any other useful information about this, it would be of great help)

The last thing is that you have to set this "unbind" command to run at startup (the original guide was made for Fedora, so its method will not work): I recommend you use the ./xinitrc to do this (just write the command in the file and it will run when X starts), but you have a lot of methods to run the command at startup (see https://wiki.archlinux.org/title/Autostarting for more information).

And that's it. As i said earlier, i recommend you read all the topic before doing anything, and i hope this is helpful for people with the same problem.
Again, special thanks to Seth for all the help.

Last edited by Aurelio3351 (2024-02-21 06:22:33)

seth · 2024-02-21 08:59:39

\o/

You may want to record your findings in https://wiki.archlinux.org/title/Laptop/MSI

Arch Linux

#1 2024-02-19 05:46:12

[SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#2 2024-02-19 13:46:49

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#3 2024-02-20 02:27:07

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#4 2024-02-20 07:43:09

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#5 2024-02-20 19:46:28

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#6 2024-02-20 21:23:27

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#7 2024-02-20 22:31:25

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#8 2024-02-20 22:37:54

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#9 2024-02-20 22:49:00

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#10 2024-02-20 22:58:30

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#11 2024-02-20 23:00:15

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#12 2024-02-20 23:11:43

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#13 2024-02-20 23:30:28

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#14 2024-02-21 00:04:46

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#15 2024-02-21 02:32:24

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

#16 2024-02-21 08:59:39

Re: [SOLVED] Laptop keyboard RGB not working (MSI Creator Z16 Laptop)

Board footer