Before getting started. Yes, I tried openrgb
. Didn’t discover my ram sticks.
Now for the question itself. I have a KINGSTON FURY Beast RGB DDR5 6000MHz 64GB Kit 2x32GB (KF560C36BBEAK2-64)
ram stick duo. Installed into a MSI Tomahawk x870 mobo (latest bios).
And I do realize the next question being “why did you go rgb sticks in the first place?”, my answer would be “was going through AMD’s EXPO supported ram list, and what my local retailers (live outside of US and EU) had to offer”.
So what I am looking for is a piece of software for Fedora (41, KDE), that would allow me to turn off the damn rgb, which feels like it could be used as headlights for cars in a foggy weather. I am yet not considering to try my luck and to “disable the rgb” without software means.
Are you wanting to only turn off the RAM leds while still using other rgb lights in your case? Or go completely dark?
Edit: motherboard LED toggle does not effect the RAM rgb.
openrgb should have instructed you to install rules from their site.
Hmmm. I need to find the manual. That would be one GODLIKE switch.
There were instructions? I just installed it, and had hopes that it would detect it (it did detect a razor mouse and keychron kb).
I take it back, it does not have any effect on the RAM. Editing previous post.
Nah. X870 Tomahawk doesn’t seem to have one.
Are you sure that spd5118
module isn’t interfering with i2c
bus on your system?
See OpenRGB/Documentation/SMBusAccess.md at master · CalcProgrammer1/OpenRGB · GitHub
Hm. Gonna give it a try. Thanks
Finally got my hands on that problem (was too lazy at weekend).
This is what I got after all module loads (even the intel ones), described in that page:
i2cdetect -l
i2c-0 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-1 i2c AMDGPU DM i2c hw bus 0 I2C adapter
i2c-2 i2c AMDGPU DM i2c hw bus 1 I2C adapter
i2c-3 i2c AMDGPU DM i2c hw bus 2 I2C adapter
i2c-4 i2c AMDGPU DM i2c hw bus 3 I2C adapter
i2c-5 i2c AMDGPU DM aux hw bus 1 I2C adapter
i2c-6 i2c AMDGPU DM aux hw bus 2 I2C adapter
i2c-7 i2c AMDGPU DM aux hw bus 3 I2C adapter
i2c-8 smbus SMBus PIIX4 adapter port 0 at 0b00 SMBus adapter
i2c-9 smbus SMBus PIIX4 adapter port 2 at 0b00 SMBus adapter
i2c-10 smbus SMBus PIIX4 adapter port 1 at 0b20 SMBus adapter
Stupid question. Is it reasonable to apply isolation tape or something similar to a ram stick just to block that darn rgb? I’ve read quite a few “openRGB bricked my ram, mobo, dog, house, marriage” to wonder if this solution would be better (I just want the darn thing off). And, according to youtube, physically disassembling the sticks is also a potential “whoopsie”.
Just boot Windows and use the vendor’s software to turn it off
I guess you could just throw some electrical tape over it…
Does it remain off? Smartass developers on mostly all non-cheap rgb-containing items I have decided that “We need to make the user suffer and force to have our trash piece software running. How? We will not store the RGB state on the device’s memory. Let it be applied on every boot!” (followed by a minute of acknowledgment how smart and superior this person is, followed by silent praise)