A follow up to my earlier post about the leds-valve DKMS module, now it is usable within the latest experimental build of OpenRGB itself as long as that leds-valve module is loaded.

Support for the #Valve #SteamMachine under #Linux has been merged into #OpenRGB. This relies on the leds-valve kernel module that is included in the SteamOS kernel. A DKMS package is available to install this kernel module on #Arch and #Debian distros:

https://gitlab.com/CalcProgrammer1/leds-valve-dkms

or AUR leds-valve-dkms-git

you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 2 days ago (2 children)

Just curious (I don't have a Steam Machine and don't plan to get one), doesn't Steam fight for control of the LEDs if you run both Steam and OpenRGB at the same time?

  • source
  • hideshow 4 child comments
  • [–] [S] 7 points 2 days ago

    In game mode yes, at least during downloads when it uses the LEDs as an indicator. It does not stream effects in software otherwise, it just lets you choose from the built in effects, so OpenRGB can take over without Steam trying to fight it most of the time.

  • source
  • parent
  • [–] 9 points 2 days ago (1 child)

    From a very surface level look at the code it looks like the module disconnects the data coming from steam while OpenRGB is active. But i dont really do C so i might be totally off here.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 2 points 2 days ago (1 child)

    It does not, but Steam isn't constantly writing to the LEDs. The Customization tab in game mode just lets you pick from the built in hardware effects so it's not continuously writing. That means it generally is not fighting OpenRGB. The only time it does seem to write to the LEDs repeatedly is during downloads when it uses the LEDs as a progress bar. Also, in desktop mode (on SteamOS or on other distros) it does not seem that Steam touches LEDs at all.

  • source
  • parent
  • hideshow 2 child comments