Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

openrgb and i2c

Featured Replies

I know this has been asked before, but nothing seems to be working for me.

 

Ive installed both openrgb, anlong with ich777's patch. when i run the openrgb docker I get Capture.JPG.034abe8dff6846dfdffed29d9d59489a.JPG

 

Ive tried running "modprobe 12c-dev", and "modprobe 12c-piix4" doesnt do anything.

 

when i run "ls /dev/i2*" I get "/dev/i2c-0" and/dev-i2c-1"

I then passed through these devices to the docker along with 2 variable arguments i found here. still no luck

1100217545_Capture2.thumb.JPG.8e05597ee1dcedc589b694c249329002.JPG

 

I feel like im missing something very basic here... if its a kernel patch listed on the openrgb's page, I am unsure how to do that.

 

Specs of what I am trying to control:

amd 3960x MSI trx40 creators onboard rgb headers

trident z neo RAM

1x thermaltake fan controller

2x corsair rbg controllers.

 

thanbks alot for your help. 

Solved by Cheesemeister

  • Author
  • Solution

if anyone come across this, this is how it was fixed. the openrgb docker is written wrong and needed to be edited. have both open rgb and ich777's patchinstalled. then edit open rgb, go to advanced mode, scroll to the bottom where you see USER ID and Group ID they need changed to this  image.png.28d05661d6dff70492a6b7dc9eccc25e.png.3c05deaa91610568e1f775d23484ad6c.png1521008661_image.png.28d05661d6dff70492a6b7dc9eccc25e(1).png.c31e7954327e0ee991a7c5fdc11e7577.png

 

Once i did that, everything worked!

 

  • 1 month later...
On 10/15/2022 at 11:22 PM, Cheesemeister said:

if anyone come across this, this is how it was fixed. the openrgb docker is written wrong and needed to be edited. have both open rgb and ich777's patchinstalled. then edit open rgb, go to advanced mode, scroll to the bottom where you see USER ID and Group ID they need changed to this  image.png.28d05661d6dff70492a6b7dc9eccc25e.png.3c05deaa91610568e1f775d23484ad6c.png1521008661_image.png.28d05661d6dff70492a6b7dc9eccc25e(1).png.c31e7954327e0ee991a7c5fdc11e7577.png

 

Once i did that, everything worked!

 

 

You are truly a hero mate! Thank you so much!

  • 3 weeks later...

Thanks so much for figuring this out and sharing! I had given up on this until I saw your post. 

 

I changed the Keys from 0 in both to USER_ID and GROUP_ID respectively as you indicated and now I can control my RGB stuff.

 

 

Edited by mikeg_321

  • 1 month later...
On 10/15/2022 at 7:22 PM, Cheesemeister said:

if anyone come across this, this is how it was fixed. the openrgb docker is written wrong and needed to be edited. have both open rgb and ich777's patchinstalled. then edit open rgb, go to advanced mode, scroll to the bottom where you see USER ID and Group ID they need changed to this  image.png.28d05661d6dff70492a6b7dc9eccc25e.png.3c05deaa91610568e1f775d23484ad6c.png1521008661_image.png.28d05661d6dff70492a6b7dc9eccc25e(1).png.c31e7954327e0ee991a7c5fdc11e7577.png

 

Once i did that, everything worked!

 

You sir, are a life saver!

  • 3 weeks later...

Thank you, thank you, thank you! I have been messing with this on and off for weeks with no luck. No more rainbow RAM!

  • 6 months later...

Starting out with this, can you guys shed some light as to my next steps?

Got the openrgb docker and the patch installed. Variables look like above, not sure if that was from a previous failed attempt of mine or docker was updated?

Now I need to pass devices into it? Trying to make sense of instructions, is perl still a requirement? 

  • 6 months later...
On 8/10/2023 at 9:07 AM, gingerbredmen said:

Starting out with this, can you guys shed some light as to my next steps?

Got the openrgb docker and the patch installed. Variables look like above, not sure if that was from a previous failed attempt of mine or docker was updated?

Now I need to pass devices into it? Trying to make sense of instructions, is perl still a requirement? 

 

I am using a Asus ProArt z790 MB and configured OpenRGB as indicated above. I no longer get the warning message and OpenRGB is able to detect the AURA lighting RGB headers, but I'm still unable to get it to detect my Corsair Vengeance RGB RAM. Do I need to pass through additional i2c devices like in OP's? or just keep the default  /sys/bus/i2c/devices and /dev/i2c-0 ?  As part of testing I passed through all 12 of my i2c-X devices without any change.

  • 1 year later...

Hi, I’m having the same issue with my Corsair Vengeance RGB RAM on a Gigabyte B760M DS3H AX motherboard. Have you found a solution to get it recognized by OpenRGB? I tried passing through all the i2c devices as suggested, but there doesn’t seem to be any change. I was wondering if you’ve found a way to make it work, maybe with some additional configuration.

 

Thanks in advance!

  • 6 months later...
On 3/7/2025 at 4:47 AM, tisanina said:

Hi, I’m having the same issue with my Corsair Vengeance RGB RAM on a Gigabyte B760M DS3H AX motherboard. Have you found a solution to get it recognized by OpenRGB? I tried passing through all the i2c devices as suggested, but there doesn’t seem to be any change. I was wondering if you’ve found a way to make it work, maybe with some additional configuration.

 

Thanks in advance!

Did you ever find a fix? Rainbow corsair ram kills me lol.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.