OpenRGB crashing my pc. Everything goes dark, but the pc stays on

General system Newbie
1

Hello! I’m trying to use OpenRGB to control the colors on my case fans, omen keyboard & mouse, gpu fan, etc and every time I launch OpenRGB, it makes my system go dark. I have to hard reset my pc to get back to a usable state. Below is my system information and any help would be great!

[rainmaker0102@AsusGamingPC ~]$ inxi -Fxxc0z
System:
  Kernel: 6.6.42-1-lts arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
  Desktop: KDE Plasma v: 6.1.3 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME B650M-A AX II v: Rev 1.xx
    serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 2413
    date: 02/02/2024
CPU:
  Info: 6-core model: AMD Ryzen 5 7600X bits: 64 type: MT MCP arch: Zen 4
    rev: 2 cache: L1: 384 KiB L2: 6 MiB L3: 32 MiB
  Speed (MHz): avg: 2658 high: 4497 min/max: 400/5453 cores: 1: 3594 2: 400
    3: 4497 4: 400 5: 3281 6: 400 7: 400 8: 4023 9: 4395 10: 3508 11: 3498
    12: 3511 bogomips: 112637
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] vendor: PNY
    driver: nvidia v: 555.58.02 arch: Ampere pcie: speed: 16 GT/s lanes: 16
    ports: active: none off: DP-1,HDMI-A-1 empty: DP-2,DP-3 bus-ID: 01:00.0
    chip-ID: 10de:2504
  Device-2: AMD Raphael vendor: ASUSTeK driver: amdgpu v: kernel
    arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports: active: none
    empty: DP-4,DP-5,HDMI-A-2 bus-ID: 0d:00.0 chip-ID: 1002:164e temp: 38.0 C
  Device-3: Microdia IC800 1080P HD driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-1:2 chip-ID: 0c45:636b
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.1
    compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
    alternate: fbdev,nouveau,nv,vesa dri: radeonsi gpu: nvidia,amdgpu
    d-rect: 3840x1080 display-ID: 0
  Monitor-1: DP-1 pos: primary,left res: 1920x1080 size: N/A
  Monitor-2: HDMI-A-1 pos: right res: 1920x1080 size: N/A
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: radeonsi
    device: 3 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland:
    drv: nvidia x11: drv: zink inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 555.58.02
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
    display-ID: :1.0
  API: Vulkan v: 1.3.279 surfaces: xcb,xlib,wayland device: 0
    type: discrete-gpu driver: nvidia device-ID: 10de:2504
Audio:
  Device-1: NVIDIA GA106 High Definition Audio vendor: PNY
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:228e
  Device-2: AMD Rembrandt Radeon High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 0d:00.1 chip-ID: 1002:1640
  Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 0d:00.6 chip-ID: 1022:15e3
  Device-4: Microdia IC800 1080P HD driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-1:2 chip-ID: 0c45:636b
  API: ALSA v: k6.6.42-1-lts status: kernel-api
  Server-1: PipeWire v: 1.2.1 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: speed: 5 GT/s lanes: 1 port: b000 bus-ID: 07:00.0 chip-ID: 10ec:8125
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8852BE PCIe 802.11ax Wireless Network
    vendor: AzureWave driver: rtw89_8852be v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: a000 bus-ID: 08:00.0 chip-ID: 10ec:b852
  IF: wlan0 state: down mac: <filter>
Bluetooth:
  Device-1: IMC Networks Bluetooth Radio driver: btusb v: 0.8 type: USB
    rev: 1.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-2:2 chip-ID: 13d3:3571
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
    lmp-v: 12
Drives:
  Local Storage: total: 5.46 TiB used: 3.07 TiB (56.3%)
  ID-1: /dev/sda vendor: PNY model: CS900 2TB SSD size: 1.82 TiB
    speed: 6.0 Gb/s serial: <filter>
  ID-2: /dev/sdb vendor: Seagate model: ST4000NM0035-1V4107 size: 3.64 TiB
    speed: 6.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 1.8 TiB used: 843.24 GiB (45.7%) fs: btrfs dev: /dev/sda2
  ID-2: /boot/efi size: 1022 MiB used: 584 KiB (0.1%) fs: vfat
    dev: /dev/sda1
  ID-3: /home size: 1.8 TiB used: 843.24 GiB (45.7%) fs: btrfs
    dev: /dev/sda2
  ID-4: /var/log size: 1.8 TiB used: 843.24 GiB (45.7%) fs: btrfs
    dev: /dev/sda2
Swap:
  ID-1: swap-1 type: partition size: 17.13 GiB used: 98 MiB (0.6%)
    priority: -2 dev: /dev/sda3
Sensors:
  System Temperatures: cpu: 42.6 C mobo: N/A gpu: amdgpu temp: 39.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 30.57 GiB used: 2.56 GiB (8.4%)
  Processes: 381 Power: uptime: 2m wakeups: 0 Init: systemd v: 256
    default: graphical
  Packages: pm: pacman pkgs: 1710 Compilers: clang: 18.1.8 gcc: 14.1.1
    Shell: Bash v: 5.2.26 running-in: konsole inxi: 3.3.35
2

To clarify, does it make your RGB go dark, or your display go dark (desktop environment)?

If it’s your desktop environment, perhaps run OpenRGB from the command line and share the output.

How did you install OpenRGB? There are multiple options in the AUR, and the official package.

yay -Q | grep openrgb
3

I’m using OpenRGB (have done so for the last year or so) What Motherboard are you using? Do you get any screens when you start OpenRGB? There is a Pre-screen that will define how many leds are being controlled in each zone…you can really set each to the max value (120) & OK it.

There are a few Motherboards that do not control well…have you looked at the supported devices list? Goto: https://gitlab.com/CalcProgrammer1/OpenRGB for info. If you have a problem & need to file a bug report, remember that you will need to run the git version (latest support) before anybody will even help.

4

OK…I see you are using an Asus Motherboard…I’m using an Asus ROG Z790-H & there was a BIOS update a short while ago that really messed with the onboard RGB…I needed to log into Winblows & use the 'Crate application to reenable the RGB…then I had control via OpenRGB back in Arch… Really check & see if there are BIOS updates (I’ve had 6 in the last 3 months!!!) & do them if you have not…It was about 3 updates ago that the Aura firmware was updated. (I had a non-controllable Motherboard…until I did the steps above…)

5

@Rainmaker0102 is currently running v2413. There are two newer BIOS updates, both updating AGESA. I’m not sure that has any significance for RGB control, but I could be mistaken.

6

As I indicated…there was an Aura firmware update not too long ago—not sure if it was rolled out to that motherboard…but I would not be surprised (there was NO indication that Aura was being updated also when I did the BIOS update) …it made me pull my hair out for a while…

7

Thanks for the input!
To answer your question, my monitor, mouse, and keyboard all go dark. I don’t think my fans go dark. It’s pretty much inoperable in this state and I have to do a hard shutoff to get my pc back. It might take ssh but I haven’t tried yet. This behavior is consistent with the AUR and official repo versions of OpenRGB, with the exception that I can briefly see the window for OpenRGB before the computer goes dark.

1 Like
8

I cannot find my motherboard on this list. Mine is the ASUS PRIME B650M-A AX II. I’ve checked with fwupd and it says my system firmware is unsupported. I’ll try here shortly about manually updating the firmware on the motherboard

9

I’d usually put the BIOS update on a reliable USB drive, then use the native update utility within the BIOS to perform the update.

1 Like
10

Well…if it’s not on the list…the support is spotty at best. I’d try contacting the devs & see if you can get an answer…sometimes it takes a week or so to get a response…You might look through the bug reports & see if your hardware is mentioned–that could give you a good heads-up.

The way Blink notes to do BIOS updates is the best way…remember to unzip & rename the update.

11

I’ve got the new update, but still crashes. Going to try the git version next

1 Like
12

If it does also, it’s time to start a bug report…You will find the logs in your home under /.config/OpenRGB/logs ( I now remind myself to check & clean that log file every couple of months—there were over 500 logs in there…need to add that to my housekeeping script)

13

Thanks for all the help. Unfortunately it doesn’t even generate anything really useful. Just an empty log.

14

The issue has been opened. Those who want to follow the issue on gitlab can go here

1 Like
15

Luck on a response…let’s see if one of the devs takes an interest…

16

In regard to that…when you really get OpenRGB to work there is a setting for verbose output in log files.

My output looks like:

    OpenRGB v0.91
    Commit: 9c7aad82594b49a132ce3a6b91b41a15c14c537a from 2024-07-19 20:43:14 -0500
    Launched: 20240803_173503
====================================================================================================

1005  |Info:    Initializing HID interfaces: Success
1006  |Info:    ------------------------------------------------------
1006  |Info:    |               Start device detection               |
1006  |Info:    ------------------------------------------------------
1008  |Info:    ------------------------------------------------------
1008  |Info:    |             Detecting I2C interfaces               |
1008  |Info:    ------------------------------------------------------
1009  |Info:    Registering I2C interface: /dev/i2c-3 Device 0000:0000 Subsystem: 0000:0000
1009  |Warning: [i2c_smbus_linux] Failed to read i2c device PCI device ID
1009  |Info:    Registering I2C interface: /dev/i2c-10 Device 0000:0000 Subsystem: 0000:0000
1009  |Info:    Registering I2C interface: /dev/i2c-1 Device 0000:0000 Subsystem: 0000:0000
1009  |Info:    Registering I2C interface: /dev/i2c-8 Device 8086:56A1 Subsystem: 8086:1021
1009  |Info:    Registering I2C interface: /dev/i2c-6 Device 8086:56A1 Subsystem: 8086:1021
1009  |Info:    Registering I2C interface: /dev/i2c-4 Device 8086:56A1 Subsystem: 8086:1021
1009  |Warning: [i2c_smbus_linux] Failed to read i2c device PCI device ID
1009  |Info:    Registering I2C interface: /dev/i2c-11 Device 0000:0000 Subsystem: 0000:0000
1009  |Info:    Registering I2C interface: /dev/i2c-2 Device 0000:0000 Subsystem: 0000:0000
1009  |Info:    Registering I2C interface: /dev/i2c-0 Device 8086:7A23 Subsystem: 1043:8882
1009  |Warning: [i2c_smbus_linux] Failed to read i2c device PCI device ID
1009  |Info:    Registering I2C interface: /dev/i2c-9 Device 0000:0000 Subsystem: 0000:0000
1009  |Info:    Registering I2C interface: /dev/i2c-7 Device 8086:56A1 Subsystem: 8086:1021
1009  |Info:    Registering I2C interface: /dev/i2c-5 Device 8086:56A1 Subsystem: 8086:1021
1009  |Warning: [i2c_smbus_linux] Failed to read i2c device PCI device ID
1009  |Info:    Registering I2C interface: /dev/i2c-MSFT8000:00 Device 0000:0000 Subsystem: 0000:0000
1009  |Warning: [i2c_smbus_linux] Failed to read i2c device PCI device ID
1010  |Info:    Registering I2C interface: /dev/i2c-12 Device 0000:0000 Subsystem: 0000:0000
1010  |Info:    ------------------------------------------------------
1010  |Info:    |               Detecting I2C devices                |
1010  |Info:    ------------------------------------------------------
1199  |Info:    [ENE DRAM] Registering RGB controller
1387  |Info:    [ENE DRAM] Registering RGB controller
1822  |Info:    ------------------------------------------------------
1822  |Info:    |               Detecting I2C PCI devices            |
1822  |Info:    ------------------------------------------------------
1824  |Info:    ------------------------------------------------------
1824  |Info:    |               Detecting HID devices                |
1824  |Info:    ------------------------------------------------------
1825  |Info:    [Logitech G512 RGB] Registering RGB controller
1898  |Info:    [ASUS ROG STRIX Z790-H GAMING WIFI] Registering RGB controller
1898  |Info:    ------------------------------------------------------
1898  |Info:    |            Detecting libusb HID devices            |
1898  |Info:    ------------------------------------------------------
1905  |Info:    ------------------------------------------------------
1905  |Info:    |              Detecting other devices               |
1905  |Info:    ------------------------------------------------------
1905  |Info:    ------------------------------------------------------
1905  |Info:    |                Detection completed                 |
1905  |Info:    ------------------------------------------------------
1905  |Dialog:  <h2>Some internal devices may not be detected:</h2><p>One or more I2C or SMBus interfaces failed to initialize.</p><p><b>RGB DRAM modules, some motherboards' onboard RGB lighting, and RGB Graphics Cards, will not be available in OpenRGB</b> without I2C or SMBus.</p><h4>How to fix this:</h4><p>On Linux, this is usually because the i2c-dev module is not loaded.</p><p>You must load the i2c-dev module along with the correct i2c driver for your motherboard. This is usually i2c-piix4 for AMD systems and i2c-i801 for Intel systems.</p><p>See <a href='https://help.openrgb.org/'>help.openrgb.org</a> for additional troubleshooting steps if you keep seeing this message.<br></p><h3>If you are not using internal RGB on a desktop this message is not important to you.</h3>
1 Like