I didn’t tried to do some settings like your first post. Try taking that out.
The first time I run openRGB I got an error also regarding the i2c-dev but after installing libi2c0 because it wasn’t installed when I install the openRGB and then did the modeprobe -i2c-dev the error was gone and it started working.
It didn’t work before either. If that can help the exact model of my MoBo is the MSI Gaming Plus WIFI X670E. Also my pc originally had Fedora for a day or two and OpenRGB did work on there (however fedora had a bunch more issues on it).
@HattedRobot That you would need to investigate as to what was actually installed on Fedora (incl. any patches) for the likes of the OpenRGB version which by the looks is a git pull (250311).
@HattedRobot there isn’t unless you login and select the distribution. Or browse to the repository, or; zypper in https://download.opensuse.org/repositories/hardware/openSUSE_Tumbleweed/x86_64/OpenRGB-1.0~rc2+git32.gda9a96e3-25.3.x86_64.rpm
You can add the repo and accept the signing key as well if wish to go that route? zypper ar https://download.opensuse.org/repositories/hardware/openSUSE_Tumbleweed/hardware.repo zypper in OpenRGB
With this version when I try to run OpenRGB it justs freezes my pc. However now it also seems to detect my MoBo in the terminal and my GPU in the ui before completely freezing. However I did not see a message for RAM detected.
I have to add that It doesn’t actually completely freeze and I get a frame every one or two minutes. Also it does that after the command “openrgb -l” completes.
I did not manage to fix this, but I did find a workaround. Install fedora on a usb stick and use openrgb here to change the colors for the mobo. It also seems to remember after a reboot for the gpu too so that’s a win. I then loaded the version that doesn’t crash my pc to setup the ram sticks. I will not mark this as solved as this is not a fix.
I just want to conclude by saying that I switched to CachyOS and the issue was still not fixed but upon looking at their forums I saw that this may be an issue with the AMDGPU driver with the 9070XT graphics card and not with the distro or OpenRGB. Fedora probably happened to patch a certain bug in the driver or other pieces of software interfacing with it.