• Veilleuse@lemmy.mlOPEnglish
      1·
      10 months ago

      Here is the result (sorry, I’m a low-level Ubuntu knowledge user 🥴) :

      $ sudo modprobe openrgb
modprobe: FATAL: Module openrgb not found in directory /lib/modules/6.2.0-26-generic
      • Dremor@lemmy.worldEnglish
        1·
        10 months ago

        Openrgb isn’t a kernel module. You should be loading i2c-dev, with modprobe i2c-dev

          • Dremor@lemmy.worldEnglish
            1·
            10 months ago

            If you mean there is no return in the terminal, this is normal. I know, it is counterintuitive, but it is like that. No return => module loaded

            • CalcProgrammer1@lemmy.mlMEnglish
              1·
              10 months ago

              You also need to load the i2c driver for your motherboard. i2c-dev is the framework for accessing i2c from userspace but does not provide the actual hardware interface. This is provided by another module. For Intel boards, this is i2c-i801. For AMD, this is i2c-piix4.

              It doesn’t hurt to load both.

              sudo modprobe i2c-piix4

              sudo modprobe i2c-i801

              • Dremor@lemmy.worldEnglish
                2·
                10 months ago

                Good to know. Strangely enough i2c-dev seem to be enough to detect my RAM, without loading i2c-piix4 (Asus Dark Hero). Those were the only devices not detected without i2c.

                • CalcProgrammer1@lemmy.mlMEnglish
                  1·
                  10 months ago

                  It’s possible that i2c-piix4 is already being loaded for some reason or that the driver is compiled into your kernel rather than as a module. Kernel configurations vary across distros. Glad it’s working either way!

            • Veilleuse@lemmy.mlOPEnglish
              1·
              10 months ago

              OK! 👍 Thank you for explanations. But even if it is loaded, OpenRGB still says that it is not.