MSI Z370 Krait Gaming Unintended Feature

[Royal-Jelly]

Software does not appear to control the RGB header as intended but can turn off and on a couple of leds integrated into the mainboard. Before I go on I did make sure the super I/O chip indeed is NCT6795D.

sudo ./msi-rgb 00 00 00 --verbose
Bank 12 (d0...100):
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
e0 00 00 00 00 00 00 00 ff ff 10 00 04 34 01 40
00 00 00 00 00 00 00 00 00 00 00 00 00 00 19 e2
Bank 09 (20...40):
d3 52 ff 00 00 00 40 03 00 ff 58 00 10 00 00 18
0d ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Bank 0b (60...70):
0a 20 0a 30 00 00 ff ff ff ff ff ff ff ff ff ff
Chip identifier is: d352

Here is some visual aid i decided would be fun to include:

[nagisa]

That just means your board has multiple lightning zones and whatever zone this tool controls is not the zone you expect… I think.

[dcerisano]

Boot to Win10, run MSI gaming app, turn on LEDs, boot back to Linux. (This should be in the README since I have had to suggest it too many times). It seems every mobo manufacturer has a proprietary code to fire up the RGB header?

[ErikSteiner]

I have the same motherboard and at first I thought that msi-rgb is not working. Then with this issue here, I noticed that it only controls the lights above the RAM-bank. So how could I access other banks, too. For now my motherboard is blinking like a Christmas tree. On windows this would end if the Mystic Light service is started and the default config is loaded, but here on Linux there is no default config.