Re: [HowTo]Install OpenRGB based on AMD chipsets.

dummy@example.com (RedGreen925) — Sun, 05 Jan 2025 18:08:55 +0000

Couple of points you are not patching the kernel, you are passing it a boot option through grub. If you patch a kernel, a re-compile then installation of new version is necessary where you boot with the patched to see the changes. For the grub there is no need to make a new file the update-grub command run as root or normal user using sudo at the front of it will have the option used in the grub.cfg upon the next boot. And now I look at that part again you do not mention you need to reboot for that change to take place setting the option and having the grub file updated does nothing to have it used, only booting the kernel with the updated/new file has it take effect. Other than those items a reasonable effort at it.

[HowTo]Install OpenRGB based on AMD chipsets.

dummy@example.com (wingcommander1999) — Sun, 05 Jan 2025 15:56:42 +0000

After a long time on Linux Mint Debian Edition, I come back to Devuan.

Before proposing my new HowTo, I wish you lots of good things for this new year 2025.

This HowTo based on the OpenRGB Wiki/Gitlab and other sources allows you to bring up all the RGB components of your computer, whether you are on an AMD or Intel chipset.

I. Installation, configuration and activation of I2C modules.

First step we need to dowload the I2C-Tools, open an terminal in Root:

apt install i2c-tools - y

Second step load the i2c module for AMD chipset:

modprobe i2c-dev

Add the user to the i2c group:

usermod $USER -aG i2c

Third step edit and load the i2c driver for your AMD chipset:

nano /etc/modules-load.d/i2c.conf

Add the line below to the file:

i2c-piix4

Load the i2c-piix4 module:

modprobe i2c-piix4

Now all necessary modules and driver are loaded.

II. Patching the kernel & UDEV rules.

Advice:Do not patch the kernel if you don't have a Gigabyte/Aorus motherboard.

Some Gigabyte/Aorus motherboards have an ACPI conflict with the SMBus controller, being on a Gigabyte motherboard I am impacted by this conflict.

First step edit the grub:

nano /etc/default/grub

Add the line below to your grub file:

GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax"

To load the added command line we have to reload the grub and re-generate the grub.cfg file:

grub-mkconfig -o /boot/grub/grub.cfg

Second step download and install the UDEV rules:

wget https://gitlab.com/CalcProgrammer1/OpenRGB/-/raw/ca3c2ad54188c604c7626136ceda574e9fde3bc0/60-openrgb.rules?inline=false

Copy the file to the UDEV rules folder:

cp -R 60-openrgb.rules /etc/udev/rules.d/

If you installed openRGB before configuring for chipset support, you will get an error message telling you that there can only be one configuration file in the UDEV rules.

For this we need to remove one UDEV rules file at the location below:

cd /usr/lib/udev/rules.d

rm -R 60-openrgb.rules

Third step reload the UDEV rules && reboot:

sudo udevadm control --reload-rules && sudo udevadm trigger

reboot

At this point you can install OpenRGB, the application once launched will show all your RGB components.

Enjoy!

Sources:

OpenRGB Wiki
Grub editing
OpenRGB UDEV rules file

Dev1 Galaxy Forum / [HowTo]Install OpenRGB based on AMD chipsets.

Re: [HowTo]Install OpenRGB based on AMD chipsets.

[HowTo]Install OpenRGB based on AMD chipsets.