• determinist@kbin.earth
    link
    fedilink
    arrow-up
    16
    ·
    1 month ago

    No version of this software, including this one, has ever detected my keyboard or mouse even though they are both on the list of (claimed) supported devices.

  • otacon239@lemmy.world
    link
    fedilink
    English
    arrow-up
    11
    ·
    1 month ago

    I might try it again, but last time I tried using it, it would just kernel panic my whole system when I opened the software.

    • skulblaka@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 month ago

      My roommate installed CachyOS two days ago, migrating from Windows, and when I was helping him set up we used OpenRGB. Works like a treat, at least on this system.

      Personally I run Mint and I use ckb-next on account of having a bunch of Corsair rainbow barfers, but the differences between the two seem minor. ckb-next is built for Corsair specifically.

  • zewm@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 month ago

    Did they fix ram yet? The only stupid component I got with lights is the ram and ORGB never saves config through rebooting.

    • MrSoup@lemmy.zip
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 month ago

      Once I found a standalone script to run at boot which turns off ram leds. Try looking it up, it was a github gist.

    • MrScruff@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 month ago

      There’s nothing to fix. Either your ram doesn’t have onboard memory for storing a lighting profile, or openrgb have intentionally disabled it to prevent hardware degradation.

      Just launch openrgb with the profile set on boot.

  • sidebro@lemmy.zip
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 month ago

    Been using this for months already. Detects all my stuff without fault and works like a charm.