I don’t know how to tell if it’s systemd or grub unless i see it on boot. It is a totally different look.
It’s colored and on the top is written “grub” and its version…
Is your computer Bios or Uefi? Systemd-boot looks like this.
UEFI. And no, it is not my boot-screen…
Anyway, how can I switch to systemd-boot (I know, here’s off-topic, but here we are, so…)
No i don’t want you to do that. I’m just asking because if you add a kernel parameter it’s different if you are using grub or systemd boot.
EDit: What do you currently have set up for that module? Are you adding something to /etc/modules-load.d
As said above (days ago) now, I have to .conf files, both for i2c-dev than i2c-piix4…
Are they needed? Do they make any difference?
Edit: What is your hardware.? Post the url
inxi -Faz | eos-sendlog
Edit: Prior to adding the .conf files did you try loading the modules manually?
Sometimes they require to be loaded with a kernel parameter but i don’t think i would have the .conf files also.
Did you read up on this when you installed it?
I don’t know, I just followed the instructions given from another user (check above on this thread).
Not the whole document. I have not so much time and I spent my time both on linux and learnign coding when my job permit it. Any way I read this part of it:
AMD*
sudo modprobe i2c-piix4*
Unmodified kernel will have one interface, patched kernel will have two. The first at 0x0B00 and the second at 0x0B20. The 0x0B20 interface is for motherboard LEDs.*
If RGB RAM or certain motherboard on-board LEDs are not loading the profile on startup, you need to add the loading entries to: /etc/modules-load.d/*
i2c-dev*
i2c-i801 or i2c-piix4 (according to your chipset)*
"
But I noticed also this:
" Some Gigabyte/Aorus motherboards have an ACPI conflict with the SMBus controller. Please add a kernel parameter to resolve this conflict. "
But I guess would be a little complicated for me…
Maybe, I’ve already done something like this one time, but I don’t remember how to access to the kernel parameters (maybe once, when I tried to compile a kernel all by my self…). What is the command/conf file to open to do that?
Can you please give me the hardware output. Post the url so i can look at everything.
inxi -Faz | eos-sendlog
It’s hard to help if i don’t have log info. 
Sorry, I found time to answer just now.
Here it is:
https://0x0.st/Ho5f.txt
only as a headsup… needs to run as root user because normal user will not be able to create that file there…
Files are already created in that path. Done as root user, otherwise it is not possible to create it.
What is the UEFI Bios version?
Machine:
Type: Desktop System: Gigabyte product: TRX40 DESIGNARE v: -CF
serial: <superuser required>
Mobo: Gigabyte model: TRX40 DESIGNARE serial: <superuser required>
UEFI: American Megatrends LLC. v: FD date: 09/07/2022
Latest version shows F6 on the Gigabyte site which could equate to FE?
Edit: Can you also check /usr/lib/modules-load.d/openrgb.conf
Does it have listed i2c-dev
Edi2: You can check if the smbus modules are loading with.
lsmod | grep 12c
Edit3: Do you have i2c-tools installed?
Edit4: You may need the following kernel parameter for Gigabyte boards.
acpi_enforce_resources=lax
FD
There is no openrgb.conf file in there…
No results digiting this command…
Yes
Can you please remember to me where I can find its path? I just found it one time, but I don’t remember at moment where I can find it. Anyway, being my pc configured to be an audio workstation, in the past I had to disable some settings from UEFI… Maybe could be there the answer?
But, what about the config files that I didn’t found in the path that you suggest?
It’s strange that the module isn’t showing if you already created the .conf file
/etc/modules-load.d/i2c-dev.conf
and you added
i2c-dev
I don’t recall if you said you installed and are using grub or you are using systemd boot. If it is grub then you add acpi_enforce_resources=lax to the grub command line in /etc/default/grub and then update grub with sudo grub-mkconfig -o /boot/grub/grub.cfg
If you are using systemd-boot then acpi_enforce_resources=lax would have to be added to /etc/kernel/cmdline and then run sudo reinstall-kernels
You could also create the .conf in /usr/lib/modules-load.d/openrgb.conf and add i2c-dev but if you already have it loading on boot i don’t see why it would be needed but you could try as it won’t hurt.
I added acpi_enforce_resources=lax and created /usr/lib/modules-load.d/openrgb.conf but when I rescan the devices in the openrgb app it keeps to say that one or more i2c/SMBus interfaces failed to initialize, etc, etc… (look old post with the screenshot)…
Then, I don’t know if could be important, but if I get the command sudo i2cdetect -l, it lists all the i2c relative to the gpu and nothing else.
Did you try loading the modules manually.
sudo modprobe 12c-dev
Also
sudo modprobe i2c_piix4
Edit2: In the original .conf file maybe add both modules and try reboot
/etc/modules-load.d/i2c-dev.conf
add
12c-dev
12c_piix4
Edit: You can check if this module is loading
lsmod | grep i2c_piix4
On that, it raises this:
modprobe: FATAL: Module 12c-dev not found in directory /lib/modules/6.2.10-arch1-1
On that, nothing happens
…
Done…
the terminal print this:
i2c_piix4 36864 0
