You are not logged in.
Hi, I'm very new to the linux ecosystem and my RGB lights are driving me insane, that simple.
I'm on a Arch + Hyprland with HyDE config. Things "mostly" work, but that's topic material for a different rambling post
I downloaded OpenRGB from the Extra repo and the specific trouble I'm having with it is my Kingston Fury Predator DDR4 memory not getting recognized by the software, defaulting then into an OCD inducing rainbow barf.
I know it works with my hardware config because I'm on a dual boot setup and I tested it on Win10 with all working out of the box.
❯ openrgb -l
Connection attempt failed
[i2c_smbus_linux] Failed to read i2c device PCI device ID
[i2c_smbus_linux] Failed to read i2c device PCI device ID
[i2c_smbus_linux] Failed to read i2c device PCI device ID
0: Everest GT-100 RGB
Type: Mouse
Description: Sinowealth Device
Version: V127
Location: HID: /dev/hidraw6
Modes: [Static] Off 'Glorious Mode' 'Seemless Breathing' Tail 'Spectrum Cycle' Rave Epilepsy Wave Breathing
Zones: Mouse
LEDs: 'Mouse LED'
1: MSI MAG B550 TOMAHAWK (MS-7C91)
Type: Motherboard
Description: MSI Mystic Light Device (185-byte)
Version: AP/LD 10.7 / 1.5
Location: HID: /dev/hidraw7
Serial: A020210908A7
Modes: Direct [Static] Breathing Flashing 'Double flashing' Lightning Meteor 'Color ring' Planetary 'Double meteor' Energy Blink Clock 'Color pulse' 'Color shift' 'Color wave' Marquee 'Rainbow wave' Visor 'Rainbow flashing' 'Color ring double flashing' Stack Fire
Zones: JRGB1 JRGB2 JRAINBOW1 JRAINBOW2 ONBOARD
LEDs: JRGB1 JRGB2 'JRAINBOW1 LED 1' 'JRAINBOW1 LED 2' 'JRAINBOW1 LED 3' 'JRAINBOW1 LED 4' 'JRAINBOW1 LED 5' 'JRAINBOW1 LED 6' 'JRAINBOW1 LED 7' 'JRAINBOW1 LED 8' 'JRAINBOW1 LED 9' 'JRAINBOW1 LED 10' 'JRAINBOW1 LED 11' 'JRAINBOW1 LED 12' 'JRAINBOW1 LED 13' 'JRAINBOW1 LED 14' 'JRAINBOW1 LED 15' 'JRAINBOW1 LED 16' 'JRAINBOW1 LED 17' 'JRAINBOW1 LED 18' 'JRAINBOW1 LED 19' 'JRAINBOW1 LED 20' 'JRAINBOW1 LED 21' 'JRAINBOW1 LED 22' 'JRAINBOW1 LED 23' 'JRAINBOW1 LED 24' 'JRAINBOW1 LED 25' 'JRAINBOW1 LED 26' 'JRAINBOW1 LED 27' 'JRAINBOW1 LED 28' 'JRAINBOW1 LED 29' 'JRAINBOW1 LED 30' 'JRAINBOW1 LED 31' 'JRAINBOW1 LED 32' 'JRAINBOW1 LED 33' 'JRAINBOW1 LED 34' 'JRAINBOW1 LED 35' 'JRAINBOW1 LED 36' 'JRAINBOW1 LED 37' 'JRAINBOW1 LED 38' 'JRAINBOW1 LED 39' 'JRAINBOW1 LED 40' 'JRAINBOW1 LED 41' 'JRAINBOW1 LED 42' 'JRAINBOW1 LED 43' 'JRAINBOW1 LED 44' 'JRAINBOW1 LED 45' 'JRAINBOW1 LED 46' 'JRAINBOW1 LED 47' 'JRAINBOW1 LED 48' 'JRAINBOW1 LED 49' 'JRAINBOW1 LED 50' 'JRAINBOW2 LED 1' 'JRAINBOW2 LED 2' 'JRAINBOW2 LED 3' 'JRAINBOW2 LED 4' 'JRAINBOW2 LED 5' 'JRAINBOW2 LED 6' 'JRAINBOW2 LED 7' 'JRAINBOW2 LED 8' 'JRAINBOW2 LED 9' 'JRAINBOW2 LED 10' 'JRAINBOW2 LED 11' 'JRAINBOW2 LED 12' 'JRAINBOW2 LED 13' 'JRAINBOW2 LED 14' 'JRAINBOW2 LED 15' 'JRAINBOW2 LED 16' 'JRAINBOW2 LED 17' 'JRAINBOW2 LED 18' 'JRAINBOW2 LED 19' 'JRAINBOW2 LED 20' 'JRAINBOW2 LED 21' 'JRAINBOW2 LED 22' 'JRAINBOW2 LED 23' 'JRAINBOW2 LED 24' 'JRAINBOW2 LED 25' 'JRAINBOW2 LED 26' 'JRAINBOW2 LED 27' 'JRAINBOW2 LED 28' 'JRAINBOW2 LED 29' 'JRAINBOW2 LED 30' 'JRAINBOW2 LED 31' 'JRAINBOW2 LED 32' 'JRAINBOW2 LED 33' 'JRAINBOW2 LED 34' 'JRAINBOW2 LED 35' 'JRAINBOW2 LED 36' 'JRAINBOW2 LED 37' 'JRAINBOW2 LED 38' 'JRAINBOW2 LED 39' 'JRAINBOW2 LED 40' 'JRAINBOW2 LED 41' 'JRAINBOW2 LED 42' 'JRAINBOW2 LED 43' 'JRAINBOW2 LED 44' 'JRAINBOW2 LED 45' 'JRAINBOW2 LED 46' 'JRAINBOW2 LED 47' 'JRAINBOW2 LED 48' 'JRAINBOW2 LED 49' 'JRAINBOW2 LED 50' 'ONBOARD LED 1' 'ONBOARD LED 2' 'ONBOARD LED 3' 'ONBOARD LED 4' 'ONBOARD LED 5' 'ONBOARD LED 6'Here are the listed i2c devices
❯ i2cdetect -l
i2c-0 i2c AMDGPU SMU 0 I2C adapter
i2c-1 i2c AMDGPU SMU 1 I2C adapter
i2c-2 i2c AMDGPU DM i2c hw bus 0 I2C adapter
i2c-3 i2c AMDGPU DM i2c hw bus 1 I2C adapter
i2c-4 i2c AMDGPU DM i2c hw bus 2 I2C adapter
i2c-5 i2c AMDGPU DM i2c hw bus 3 I2C adapter
i2c-6 i2c AMDGPU DM aux hw bus 0 I2C adapter
i2c-7 i2c AMDGPU DM aux hw bus 1 I2C adapter
i2c-8 i2c AMDGPU DM aux hw bus 2 I2C adapter
i2c-9 smbus SMBus PIIX4 adapter port 0 at 0b00 SMBus adapter
i2c-10 smbus SMBus PIIX4 adapter port 2 at 0b00 SMBus adapter
i2c-11 smbus SMBus PIIX4 adapter port 1 at 0b20 SMBus adapterAnd here are the listed HW IDs OpenRGB is getting:
[ i2c busses ]
1002:73DF 148C:2419 - /dev/i2c-3
1022:790B 1462:7C91 - /dev/i2c-10
1002:73DF 148C:2419 - /dev/i2c-1
0000:0000 0000:0000 - /dev/i2c-8
0000:0000 0000:0000 - /dev/i2c-6
1002:73DF 148C:2419 - /dev/i2c-4
1022:790B 1462:7C91 - /dev/i2c-11
1002:73DF 148C:2419 - /dev/i2c-2
1002:73DF 148C:2419 - /dev/i2c-0
1022:790B 1462:7C91 - /dev/i2c-9
0000:0000 0000:0000 - /dev/i2c-7
1002:73DF 148C:2419 - /dev/i2c-5
[ HID devices ]
[0CF2:A100 U=00A1 P=0xFF72 I=1] ENE - LianLi-UNI FAN-SL-v1.8
[04D9:A232 U=0006 P=0x0001 I=0] HOLTEK - USB-HID Keyboard
[04D9:A232 U=0001 P=0xFF00 I=1] HOLTEK - USB-HID Keyboard
[04D9:A232 U=0002 P=0x0001 I=2] HOLTEK - USB-HID Keyboard
[04D9:A232 U=0001 P=0x0001 I=2] HOLTEK - USB-HID Keyboard
[04D9:A232 U=0080 P=0x0001 I=2] HOLTEK - USB-HID Keyboard
[04D9:A232 U=0001 P=0x000C I=2] HOLTEK - USB-HID Keyboard
[04D9:A232 U=0001 P=0xFF02 I=2] HOLTEK - USB-HID Keyboard
[04D9:A232 U=0006 P=0x0001 I=2] HOLTEK - USB-HID Keyboard
[04D9:A232 U=0001 P=0xFF01 I=3] HOLTEK - USB-HID Keyboard
[258A:0029 U=0002 P=0x0001 I=0] SINOWEALTH - Wired Gaming Mouse
[258A:0029 U=0001 P=0x0001 I=0] SINOWEALTH - Wired Gaming Mouse
[258A:0029 U=0006 P=0x0001 I=1] SINOWEALTH - Wired Gaming Mouse
[258A:0029 U=0001 P=0x000C I=1] SINOWEALTH - Wired Gaming Mouse
[258A:0029 U=0001 P=0xFF00 I=1] SINOWEALTH - Wired Gaming Mouse
[258A:0029 U=0001 P=0xFF00 I=1] SINOWEALTH - Wired Gaming Mouse
[258A:0029 U=0001 P=0xFF00 I=1] SINOWEALTH - Wired Gaming Mouse
[1462:7C91 U=0000 P=0x0001 I=0] MSI - MYSTIC LIGHT
[1462:7C91 U=0001 P=0xFF00 I=0] MSI - MYSTIC LIGHT
[ LibUSB devices ]
1D6B:0003
045E:076D
1D6B:0002
1D6B:0003
1462:7C91
258A:0029
04D9:A232
0A12:0001
045E:02FE
0CF2:A100
05E3:0608
1D6B:0002i2c-tools are installed and modules are currently loaded as it shows:
❯ lsmod | grep i2c
i2c_piix4 36864 3
i2c_smbus 20480 1 i2c_piix4
i2c_dev 28672 24
i2c_algo_bit 20480 1 amdgpuIs there any reason you guys can point me to as to why this is happening and how do I fix it?
A udev rules, problem perhaps? I'm not sure on that, though. I'm just trying to guess.
Also "rescan devices" button crashes the whole thing and idk why ¯\_(ツ)_/¯
Offline