[Bug Report] No RAM module detected on Gigabyte x299 Designare-EX
Description of Bug
OpenRGB does not detect any type of RAM module on Gigabyte x299 Designare-EX motherboard. This was tested with ENE modules (g.Skill), Crucial Ballistix and Gigabyte Aorus RGB modules. All RAM modules are detected and controlled by official software (g.Skill, Gigabyte Fusion) on Windows 10 OS.
i2cdetect tool shows only one i2c/smbus related to the motherboard:
# i2cdetect -l
i2c-3 i2c NVIDIA i2c adapter 4 at c1:00.0 I2C adapter
i2c-1 i2c NVIDIA i2c adapter 1 at c1:00.0 I2C adapter
i2c-6 i2c NVIDIA i2c adapter 8 at c1:00.0 I2C adapter
i2c-4 i2c NVIDIA i2c adapter 6 at c1:00.0 I2C adapter
i2c-2 i2c NVIDIA i2c adapter 2 at c1:00.0 I2C adapter
i2c-0 smbus SMBus I801 adapter at 4000 SMBus adapter
i2c-7 i2c NVIDIA i2c adapter 9 at c1:00.0 I2C adapter
i2c-5 i2c NVIDIA i2c adapter 7 at c1:00.0 I2C adapter
However for whatever RAM module is inserted, none shows up on that bus (nor or any nVidia bus).
# i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 00 -- -- -- -- -- -- -- 08 -- -- -- 0c -- -- --
10: 10 -- -- 13 -- 15 -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: 40 -- 42 43 44 -- 46 -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- 68 69 -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
There is nothing extraordinary showing up on the USB bus either.
# lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Per advise on the Discord channel, I looked into ACPI tables to see, if there is another I2C bus present. Full ACPI DSDTdsdt.dsl disassembly is attached. There seem to be several other I2C busses, but neither are accessible to OpenRGB on Linux nor on Windows.
ACPI DSDT Table snippet
Scope (_SB.PC00)
{
Device (I2C0)
{
Name (LINK, "\\_SB.PC00.I2C0")
Name (_HID, "INT3442") // _HID: Hardware ID
Name (_ADR, 0x00150000) // _ADR: Address
}
}
Scope (_SB.PC00)
{
Device (I2C1)
{
Name (LINK, "\\_SB.PC00.I2C1")
Name (_HID, "INT3443") // _HID: Hardware ID
Name (_ADR, 0x00150001) // _ADR: Address
}
}
Attached Log
ACPI DSDT Table dsdt.dsl
Operating System
OS - Linux Debian GNU/Linux 11u4 OS - Windows Windows 10 Pro 21H2
OpenRGB version: 0.71, pipeline and manual build (Change set: 31c24eb6)
Hardware Configuration
MB: Gigabyte X299 Designare-EX RAM: g.Skill 4x16GB 3200MHz, Crucial Ballistix 2x8GB 3600MHz, Gigabyte Aorus RGB 2x8GB 4400MHz