• Dremor
    link
    English
    111 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

    • @[email protected]OP
      link
      fedilink
      English
      111 months ago

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

      • Dremor
        link
        English
        111 months ago

        Got Discord? I’m not the dev, but I’ll try to help you if I can.

          • Dremor
            link
            English
            111 months ago

            On the OpenRGB Discord community, in the only voice channel available.

            • @[email protected]OP
              link
              fedilink
              English
              111 months ago

              Oh… in a voice channel… Sorry but english is not my native language (french) and I’m afraid we won’t understand each other very well. Thank you anyway for your help.

              • Dremor
                link
                English
                111 months ago

                Don’t worry, I’m French too.

    • @[email protected]M
      link
      fedilink
      English
      110 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
        link
        English
        210 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.

        • @[email protected]M
          link
          fedilink
          English
          110 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!