revolverunit

joined 2 years ago
 

Hi all. Not sure what to make of this issue. OpenRGB (installed from AUR) detects all my other devices just fine, but not the Addressable RGB controller.

The weird thing is, I have the Razer Extras plugin installed, and when I press the button to reload the controller, my fans flash, so the controller is getting detected but for some reason OpenRGB itself doesn't pick it up. It's definitely detected by lsusb as well

When I run *openrgb --list-devices -vv everything else looks fine until

[Razer Chroma Addressable RGB Controller] is enabled [ResourceManager] Calling detection progress callbacks. [ResourceManager] Calling detection progress callbacks.

and then it goes right on to the libusb HID devices section.

Is there something I'm missing, or perhaps a dependency I didn't install?

 

It seems to mostly happen to 3D games, very rarely for 2D ones.

Normally, this wouldn't be much of an issue for me since I install everything to secondary SSDs anyways, but the one piece of software that is driving me up a wall is Steam VR, since its installation folder can't be moved.

I could find plenty of fixes when it came to the opposite problem (launching games from another drive) but nothing for my situation.

Any solutions or even just point me in the right direction where to start when it comes to troubleshooting something like this?

OS: Endeavour OS

GPU: RTX 2070 (latest Nvidia drivers)

CPU: Ryzen 2700X

Happens on both X11 and Wayland environments and everything is up-to-date

Edit: also this seems to happen with every version of Proton