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.

mattispantone81

Members
  • Joined

  • Last visited

  1. Hello OpenRGB Developers/Community, I am requesting future feature support for the RGB controller on the MSI PRO B860-P WIFI motherboard. After exhausting all known Linux/Docker/BIOS community troubleshooting steps, the device remains undetected. I am documenting all my troubleshooting attempts to help narrow down the source of the incompatibility, which appears to be a deep kernel/hardware communication failure. Environment & Hardware SpecificationsComponent Detail Version/Chip Motherboard MSI PRO B860-P WIFI PCB ID: MS-7E41 I/O Controller RGB Control Chip NUVOTON NCT6687D-M Controller Chip Operating System Unraid OS Current Stable (e.g., 7.2.2 or higher) Linux Kernel Unraid Kernel Linux 6.12.54-Unraid (approx.) BIOS Version Current running version v1.A10 OpenRGB Docker Image/Release OpenRGB-GUI-Unraid (Latest, OpenRGB release 0.9) Troubleshooting Steps Taken (The Problem Persists)The fundamental error is consistently: [app ] [i2c_smbus_linux] Failed to read i2c device PCI device ID in the Docker log. BIOS Firmware Modifications: The system was rebooted after explicitly disabling the motherboard's native RGB control to prevent firmware lock: EZ Mode → EZ On/Off → EZ LED Control was set to OFF. Container Configuration: The OpenRGB-GUI-Unraid Docker container is running in Privileged Mode. Remove USER ID and GROUP ID variables were from the container template (to test if this was causing an issue - it was not). Kernel Driver Loading (Persistence via /boot/config/go): The primary access modules (i2c-dev and i2c-i801 / nct6687) are loaded persistently via the /boot/config/go file: Bash modprobe i2c-dev modprobe nct6687 Kernel Driver Hard Probing Attempts: An initial attempt was made to force load the Intel driver with a common SMBus address via the go file, but this was reverted: modprobe i2c-i801 force_probe=0x2e00. A final, persistent configuration file was created to force the kernel to activate the System Management Interface (SCMI) and probe the Nuvoton chip, which also failed to resolve the PCI Device ID reading issue: File: /etc/modprobe.d/nct6687.conf Content: Plaintext options i2c_i801 force_scmi=1 options nct6687 force_id=0x1927 Current Status and RequestEvery known software, permission, and kernel workaround has been exhausted. Given the persistence of the "Failed to read i2c device PCI device ID" error, it is concluded that either: The firmware on this new B860 board maintains an unresolvable hardware lock despite the BIOS setting. The current Nuvoton driver support in OpenRGB (v0.9) is missing the necessary device ID or communication logic for the NCT6687D-M chip on this specific MSI PRO B860-P WIFI model. I am happy to provide any debug information requested (e.g., specific PCI device information, i2cdump output, or further testing). Thank you for your work on this project!

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.