G.SKILL Trident Z RGB not available under Supported Devices (lemmy.ca)

submitted 5 months ago* (last edited 5 months ago) by isVeryLoud@lemmy.ca to c/openrgb@lemmy.ml

7 comments fedilink hide all child comments

Hello! Fedora 39, I've been stumped by this issue for a long time.

I have 4 DDR4 sets of 8 GB G.SKILL Trident Z RGB.

I tried the latest Flatpak, RPM as well as building the master branch for source, but every version can't find Trident Z in the "Supported Devices" section, and it doesn't show up under Devices.

I validated that the i2c modules were loaded, and the udev rules were put in place, both using the RPM and by running the script provided over at https://openrgb.org/udev.html

When running OpenRGB, in the terminal, I get:

[i2c_smbus_linux] Failed to read i2c device PCI device ID

even when running as sudo.

My motherboard is an AORUS X470 ULTRA GAMING (cringe name, I know), if it makes any difference for i2c support. As a side note, this motherboard has RGB, but it's not detected in OpenRGB. I think it should be supported, and I see it when running openrgb --list-devices -vv, but maybe the revision is wrong.

[Gigabyte RGB Fusion 2 SMBus] Success - Found 'X470 AORUS ULTRA GAMING-CF' in the JSON list
[Gigabyte RGB Fusion 2 SMBus] Bus 02 is not a motherboard or the subvendor does not match the one for Gigabyte Technology Co., Ltd., skipping detection
[Gigabyte RGB Fusion 2 SMBus] Bus 06 is not a motherboard or the subvendor does not match the one for Gigabyte Technology Co., Ltd., skipping detection
[Gigabyte RGB Fusion 2 SMBus] no devices found
[Gigabyte RGB Fusion 2 SMBus] detection end

Please let me know if further details are required.

TIA!

top 7 comments

sorted by: hot top controversial new old

[-] CalcProgrammer1@lemmy.ml 3 points 5 months ago

Trident Z RGB falls under ENE DRAM and should work fine as long as you have the appropriate i2c driver loaded for your motherboard.

[-] CalcProgrammer1@lemmy.ml 2 points 5 months ago

Can you post the output of lsmod | grep i2c?

[-] isVeryLoud@lemmy.ca 1 points 5 months ago

Hello! I just want to poke you on this :)

[-] isVeryLoud@lemmy.ca 1 points 5 months ago

veryloud@IOT-Rice-Cooker:~/Projects/OpenRGB$ sudo lsmod | grep i2c
i2c_i801               36864  0
i2c_smbus              20480  1 i2c_i801
i2c_dev                28672  48
i2c_piix4              32768  0
i2c_algo_bit           20480  2 igb,amdgpu

[-] CalcProgrammer1@lemmy.ml 1 points 5 months ago

Oh, you have a Gigabyte motherboard. These have a quirk with i2c where you have to add a kernel command line parameter. I forget exactly what it is, maybe "acpi_enforce_resources=lax"? I think this is mentioned in the Readme on Gitlab.

[-] isVeryLoud@lemmy.ca 1 points 5 months ago

Ah thank you, I didn't spot it in the README, I'll give it a try :)

[-] isVeryLoud@lemmy.ca 1 points 4 months ago

I had the opportunity to test this today, thank you, it's what I was missing! I should have RTFM'd :)

this post was submitted on 25 Feb 2024

8 points (100.0% liked)

OpenRGB

432 readers

1 users here now

The official Lemmy community for the OpenRGB project.

Official website: https://openrgb.org

GitLab: https://gitlab.com/CalcProgrammer1/OpenRGB

founded 3 years ago

MODERATORS

CalcProgrammer1@lemmy.ml