Kingston Fury DDR5 RAM in slot 1(~8) not found on SMBus i2c-3.

[sousaesilvarafael]

Hi. I'm getting the following situation:

sudo kfrgb --smbus 3

• Kingston Fury DDR5 RAM in slot 1 not found on SMBus i2c-3.

• Kingston Fury DDR5 RAM in slot 2 not found on SMBus i2c-3.

• Kingston Fury DDR5 RAM in slot 3 not found on SMBus i2c-3.

• Kingston Fury DDR5 RAM in slot 4 not found on SMBus i2c-3.

• Kingston Fury DDR5 RAM in slot 5 not found on SMBus i2c-3.

• Kingston Fury DDR5 RAM in slot 6 not found on SMBus i2c-3.

• Kingston Fury DDR5 RAM in slot 7 not found on SMBus i2c-3.

• Kingston Fury DDR5 RAM in slot 8 not found on SMBus i2c-3.

• Please select an SMBus (or type 'quit' or 'q' to exit from kfrgb):

3. i2c-3 smbus SMBus I801 adapter at 0000:00:1f.4 SMBus adapter

And if I hit 3 it keeps on a loop with those messages.
Had to install i2ctools.
My motherboard is an ASUS TUF GAMING B760M-PLUS WIFI II and the memorys are 2 x 16GB DDR5 Kingston Fury Beast on slots 2 and 4.
Is there any way to turn off the led with this script?

[KeyofBlueS]

Hi @sousaesilvarafael, can you please post the full output of sudo kfrgb --debug ?

[sousaesilvarafael]

---

---

ABOUT DETECTION

Setting register &0x0b to 0x04 on addresses 0x5[0-7] allows to read the DIMM model name, but
very often address 0x5 is write protected (as in my system), which makes this method useless.

kfrgb will:

• lshw: check for 'vendor: Kingston' and 'product: KF5*'.
• i2cdetect: check if addresses 0x6[0-7], 0x5[0-7] and 0x4[8-f] exist on an smbus that support Quick Command.
• i2cdump (mode i): on address 0x6[0-7] check if blocks 0x02=0x46, 0x03=0x55, 0x04=0x52, 0x05=0x59,
  0x07=0x10/0x12/0x15 (for BEAST) OR =0x11 (for RENEGADE).

The detection passes if all checks are true.
The detection fails at the first error in the chain.

---

---

• i2cdetect -l (check i2c-buses):
  i2c-0 i2c Synopsys DesignWare I2C adapter I2C adapter
  i2c-1 i2c Synopsys DesignWare I2C adapter I2C adapter
  i2c-2 i2c Synopsys DesignWare I2C adapter I2C adapter
  i2c-3 smbus SMBus I801 adapter at 0000:00:1f.4 SMBus adapter
  i2c-4 i2c NVIDIA i2c adapter 3 at 1:00.0 I2C adapter
  i2c-5 i2c NVIDIA i2c adapter 4 at 1:00.0 I2C adapter
  i2c-6 i2c NVIDIA i2c adapter 5 at 1:00.0 I2C adapter
  i2c-7 i2c NVIDIA i2c adapter 6 at 1:00.0 I2C adapter

---

---

• i2cdetect -y 3 (check SMBus i2c-3):
  0 1 2 3 4 5 6 7 8 9 a b c d e f
  00: -- -- -- -- -- -- -- --
  10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  70: -- -- -- -- -- -- -- --

---

• Kingston Fury DDR5 RAM in slot 1 not found on SMBus i2c-3.

• lshw (check bank 0):
  *-bank:0 UNCLAIMED
  description: [empty]
  physical id: 0
  slot: Controller0-DIMM0

• Address 0x60 not found in SMBus i2c-3

• Address 0x48 not found in SMBus i2c-3

• Address 0x50 not found in SMBus i2c-3

• i2cdump 3 0x60 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 2 not found on SMBus i2c-3.

• lshw (check bank 1):
  *-bank:1 UNCLAIMED
  description: DIMM Synchronous 5600 MHz (0.2 ns)
  product: KF556C40-16
  vendor: Kingston
  physical id: 1
  serial: 19163D05
  slot: Controller0-DIMM1
  size: 16GiB
  width: 64 bits
  clock: 1305MHz (0.8ns)

• Address 0x61 not found in SMBus i2c-3

• Address 0x49 not found in SMBus i2c-3

• Address 0x51 not found in SMBus i2c-3

• i2cdump 3 0x61 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 3 not found on SMBus i2c-3.

• lshw (check bank 2):
  *-bank:2 UNCLAIMED
  description: [empty]
  physical id: 2
  slot: Controller1-DIMM0

• Address 0x62 not found in SMBus i2c-3

• Address 0x4a not found in SMBus i2c-3

• Address 0x52 not found in SMBus i2c-3

• i2cdump 3 0x62 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 4 not found on SMBus i2c-3.

• lshw (check bank 3):
  *-bank:3 UNCLAIMED
  description: DIMM Synchronous 5600 MHz (0.2 ns)
  product: KF556C40-16
  vendor: Kingston
  physical id: 3
  serial: D0063BC9
  slot: Controller1-DIMM1
  size: 16GiB
  width: 64 bits
  clock: 1305MHz (0.8ns)

• Address 0x63 not found in SMBus i2c-3

• Address 0x4b not found in SMBus i2c-3

• Address 0x53 not found in SMBus i2c-3

• i2cdump 3 0x63 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 5 not found on SMBus i2c-3.

• lshw (check bank 4):

• Address 0x64 not found in SMBus i2c-3

• Address 0x4c not found in SMBus i2c-3

• Address 0x54 not found in SMBus i2c-3

• i2cdump 3 0x64 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 6 not found on SMBus i2c-3.

• lshw (check bank 5):

• Address 0x65 not found in SMBus i2c-3

• Address 0x4d not found in SMBus i2c-3

• Address 0x55 not found in SMBus i2c-3

• i2cdump 3 0x65 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 7 not found on SMBus i2c-3.

• lshw (check bank 6):

• Address 0x66 not found in SMBus i2c-3

• Address 0x4e not found in SMBus i2c-3

• Address 0x56 not found in SMBus i2c-3

• i2cdump 3 0x66 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 8 not found on SMBus i2c-3.

• lshw (check bank 7):

• Address 0x67 not found in SMBus i2c-3

• Address 0x4f not found in SMBus i2c-3

• Address 0x57 not found in SMBus i2c-3

• i2cdump 3 0x67 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

---

[KeyofBlueS]

Thank you for the debug log. Could you please follow the instructions provided here and check whether they resolve the issue? If the problem persists, please share an updated log after completing those steps so we can investigate further.

[sousaesilvarafael]

I did every step on the link but nothing positive and saw the same output from debug:

sudo kfrgb --debug

---

ABOUT DETECTION

Setting register &0x0b to 0x04 on addresses 0x5[0-7] allows to read the DIMM model name, but
very often address 0x5 is write protected (as in my system), which makes this method useless.

kfrgb will:

• lshw: check for 'vendor: Kingston' and 'product: KF5*'.
• i2cdetect: check if addresses 0x6[0-7], 0x5[0-7] and 0x4[8-f] exist on an smbus that support Quick Command.
• i2cdump (mode i): on address 0x6[0-7] check if blocks 0x02=0x46, 0x03=0x55, 0x04=0x52, 0x05=0x59,
  0x07=0x10/0x12/0x15 (for BEAST) OR =0x11 (for RENEGADE).

The detection passes if all checks are true.
The detection fails at the first error in the chain.

---

---

• i2cdetect -l (check i2c-buses):
  i2c-0 i2c Synopsys DesignWare I2C adapter I2C adapter
  i2c-1 i2c Synopsys DesignWare I2C adapter I2C adapter
  i2c-2 i2c Synopsys DesignWare I2C adapter I2C adapter
  i2c-3 smbus SMBus I801 adapter at 0000:00:1f.4 SMBus adapter
  i2c-4 i2c NVIDIA i2c adapter 3 at 1:00.0 I2C adapter
  i2c-5 i2c NVIDIA i2c adapter 4 at 1:00.0 I2C adapter
  i2c-6 i2c NVIDIA i2c adapter 5 at 1:00.0 I2C adapter
  i2c-7 i2c NVIDIA i2c adapter 6 at 1:00.0 I2C adapter

---

---

• i2cdetect -y 3 (check SMBus i2c-3):
  0 1 2 3 4 5 6 7 8 9 a b c d e f
  00: -- -- -- -- -- -- -- --
  10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  70: -- -- -- -- -- -- -- --

---

• Kingston Fury DDR5 RAM in slot 1 not found on SMBus i2c-3.

• lshw (check bank 0):
  *-bank:0 UNCLAIMED
  description: [empty]
  physical id: 0
  slot: Controller0-DIMM0

• Address 0x60 not found in SMBus i2c-3

• Address 0x48 not found in SMBus i2c-3

• Address 0x50 not found in SMBus i2c-3

• i2cdump 3 0x60 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 2 not found on SMBus i2c-3.

• lshw (check bank 1):
  *-bank:1 UNCLAIMED
  description: DIMM Synchronous 5600 MHz (0.2 ns)
  product: KF556C40-16
  vendor: Kingston
  physical id: 1
  serial: 19163D05
  slot: Controller0-DIMM1
  size: 16GiB
  width: 64 bits
  clock: 1305MHz (0.8ns)

• Address 0x61 not found in SMBus i2c-3

• Address 0x49 not found in SMBus i2c-3

• Address 0x51 not found in SMBus i2c-3

• i2cdump 3 0x61 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 3 not found on SMBus i2c-3.

• lshw (check bank 2):
  *-bank:2 UNCLAIMED
  description: [empty]
  physical id: 2
  slot: Controller1-DIMM0

• Address 0x62 not found in SMBus i2c-3

• Address 0x4a not found in SMBus i2c-3

• Address 0x52 not found in SMBus i2c-3

• i2cdump 3 0x62 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 4 not found on SMBus i2c-3.

• lshw (check bank 3):
  *-bank:3 UNCLAIMED
  description: DIMM Synchronous 5600 MHz (0.2 ns)
  product: KF556C40-16
  vendor: Kingston
  physical id: 3
  serial: D0063BC9
  slot: Controller1-DIMM1
  size: 16GiB
  width: 64 bits
  clock: 1305MHz (0.8ns)

• Address 0x63 not found in SMBus i2c-3

• Address 0x4b not found in SMBus i2c-3

• Address 0x53 not found in SMBus i2c-3

• i2cdump 3 0x63 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 5 not found on SMBus i2c-3.

• lshw (check bank 4):

• Address 0x64 not found in SMBus i2c-3

• Address 0x4c not found in SMBus i2c-3

• Address 0x54 not found in SMBus i2c-3

• i2cdump 3 0x64 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 6 not found on SMBus i2c-3.

• lshw (check bank 5):

• Address 0x65 not found in SMBus i2c-3

• Address 0x4d not found in SMBus i2c-3

• Address 0x55 not found in SMBus i2c-3

• i2cdump 3 0x65 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 7 not found on SMBus i2c-3.

• lshw (check bank 6):

• Address 0x66 not found in SMBus i2c-3

• Address 0x4e not found in SMBus i2c-3

• Address 0x56 not found in SMBus i2c-3

• i2cdump 3 0x66 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 8 not found on SMBus i2c-3.

• lshw (check bank 7):

• Address 0x67 not found in SMBus i2c-3

• Address 0x4f not found in SMBus i2c-3

• Address 0x57 not found in SMBus i2c-3

• i2cdump 3 0x67 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

---

[sousaesilvarafael]

On Windows, the only app that turns off the led is the SignalRGB.

[KeyofBlueS]

Just to confirm, does the official Kingston FURY CTRL work on Windows?

Also, could you please provide the output of the following commands on Linux?
lsmod | grep i2c
sudo i2cdetect -F 3
ls /sys/bus/i2c/drivers/spd5118/
find /sys/bus/i2c/devices -maxdepth 1 -type l | sort

[sousaesilvarafael]

Yes, the official FURY CTRL works on Windows but I have a Logitech keyboard g213 that's why I use Signal RGB.

lsmod | grep i2c
i2c_i801 36864 1
i2c_smbus 20480 1 i2c_i801
i2c_mux 20480 1 i2c_i801

sudo i2cdetect -F 3
[sudo: authenticate] Senha:
Functionalities implemented by /dev/i2c-3:
I2C no
SMBus Quick Command yes
SMBus Send Byte yes
SMBus Receive Byte yes
SMBus Write Byte yes
SMBus Read Byte yes
SMBus Write Word yes
SMBus Read Word yes
SMBus Process Call yes
SMBus Block Write yes
SMBus Block Read yes
SMBus Block Process Call yes
SMBus PEC yes
I2C Block Write yes
I2C Block Read yes
SMBus Host Notify yes
10-bit addressing no
Target mode no

ls /sys/bus/i2c/drivers/spd5118/
ls: cannot access '/sys/bus/i2c/drivers/spd5118/': No such file or directory

find /sys/bus/i2c/devices -maxdepth 1 -type l | sort
/sys/bus/i2c/devices/i2c-0
/sys/bus/i2c/devices/i2c-1
/sys/bus/i2c/devices/i2c-2
/sys/bus/i2c/devices/i2c-3
/sys/bus/i2c/devices/i2c-4
/sys/bus/i2c/devices/i2c-5
/sys/bus/i2c/devices/i2c-6
/sys/bus/i2c/devices/i2c-7

[KeyofBlueS]

From your lsmod | grep i2c output, i2c-dev is not present.

Check if i2c-dev is built into kernel:
cat /lib/modules/$(uname -r)/modules.builtin | grep i2c

Before continuing, please make sure i2c-dev is enabled and available on your system (following the procedure linked earlier), then re-test and send me the updated outputs of:

sudo kfrgb --debug
lsmod | grep i2c
sudo i2cdetect -F 3
find /sys/bus/i2c/devices -maxdepth 1 -type l | sort

Also, have you added the acpi_enforce_resources=lax kernel parameter as described in the instructions linked earlier?
I know it is mainly mentioned for Gigabyte/AORUS motherboards, but it can help on other boards as well when there are ACPI conflicts.

[sousaesilvarafael]

I did every step on the tutorial and with the step "Load the i2c-dev module: sudo modprobe i2c-dev" i got no answer on console.

[KeyofBlueS]

At this point, if you have already followed the guide, verified that i2c-dev is built into the kernel (or otherwise available), and added the acpi_enforce_resources=lax kernel parameter, then I'm honestly running out of ideas on my side.

To double-check those two points, please post the output of:

cat /lib/modules/$(uname -r)/modules.builtin | grep i2c
cat /proc/cmdline

The first command will help confirm whether i2c-dev is built into your kernel, and the second will show whether acpi_enforce_resources=lax is actually being applied at boot.

Unfortunately, in the current state of your system, the SMBus does not expose any DIMM-related devices at all. Because of that, neither kfrgb, OpenRGB, nor any similar application will be able to communicate with your RAM.

My recommendation at this point is to ask for help in your distribution's community as well. Feel free to link this issue in your help request, and post a link to that discussion here as well. Someone familiar with your specific motherboard, kernel, or distribution may spot something we've missed.

Don't give up yet!

[sousaesilvarafael]

cat /lib/modules/$(uname -r)/modules.builtin | grep i2c
kernel/drivers/base/regmap/regmap-i2c.ko
kernel/drivers/mfd/tps65912-i2c.ko
kernel/drivers/input/touchscreen/elants_i2c.ko
kernel/drivers/i2c/i2c-core.ko
kernel/drivers/i2c/i2c-dev.ko
kernel/drivers/i2c/busses/i2c-designware-core.ko
kernel/drivers/i2c/busses/i2c-designware-platform.ko

sudo dmidecode -t memory | grep -Ei 'Manufacturer|Part Number|Locator'
Locator: Controller0-DIMM0
Bank Locator: BANK 0
Locator: Controller0-DIMM1
Bank Locator: BANK 0
Manufacturer: Kingston
Part Number: KF556C40-16
Module Manufacturer ID: Bank 2, Hex 0x98
Memory Subsystem Controller Manufacturer ID: Unknown
Locator: Controller1-DIMM0
Bank Locator: BANK 0
Locator: Controller1-DIMM1
Bank Locator: BANK 0
Manufacturer: Kingston
Part Number: KF556C40-16
Module Manufacturer ID: Bank 2, Hex 0x98
Memory Subsystem Controller Manufacturer ID: Unknown

ls -l /dev/i2c-*
crw-rw----+ 1 root i2c 89, 0 Jun 15 08:40 /dev/i2c-0
crw-rw----+ 1 root i2c 89, 1 Jun 15 08:40 /dev/i2c-1
crw-rw----+ 1 root i2c 89, 2 Jun 15 08:40 /dev/i2c-2
crw-rw----+ 1 root i2c 89, 3 Jun 15 08:40 /dev/i2c-3
crw-rw----+ 1 root i2c 89, 4 Jun 15 08:40 /dev/i2c-4
crw-rw----+ 1 root i2c 89, 5 Jun 15 08:40 /dev/i2c-5
crw-rw----+ 1 root i2c 89, 6 Jun 15 08:40 /dev/i2c-6
crw-rw----+ 1 root i2c 89, 7 Jun 15 08:40 /dev/i2c-7

[sousaesilvarafael]

cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=0d6e29f9-9664-4dca-9e5e-d77bd0e560ce ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M

[KeyofBlueS]

Thanks for the outputs!

From your cat /proc/cmdline I can see that acpi_enforce_resources=lax is not present in your kernel command line, so that parameter is currently not being applied.
Please review these instructions and make sure it is correctly added to your bootloader configuration.
After rebooting, please run again:

cat /proc/cmdline
sudo kfrgb --debug

and share the updated output.

[sousaesilvarafael]

cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=0d6e29f9-9664-4dca-9e5e-d77bd0e560ce ro quiet splash acpi_enforce_resources=lax crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M

sudo ./OpenRGB*.AppImage --verbose --loglevel 6 --print-source
Connection attempt failed
[ResourceManager] Initializing HID interfaces: Success [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:969]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1066]
| Start device detection | [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1067]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1068]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1149]
| Detecting I2C interfaces | [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1150]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1151]
[ResourceManager] Registering I2C interface: /dev/i2c-3 Device 8086:7A23 Subsystem: 1043:8882 [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:218]
[ResourceManager] Registering I2C interface: /dev/i2c-1 Device 0000:0000 Subsystem: 0000:0000 [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:218]
[ResourceManager] Registering I2C interface: /dev/i2c-6 Device 10DE:2C05 Subsystem: 1458:41A8 [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:218]
[ResourceManager] Registering I2C interface: /dev/i2c-4 Device 10DE:2C05 Subsystem: 1458:41A8 [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:218]
[ResourceManager] Registering I2C interface: /dev/i2c-2 Device 0000:0000 Subsystem: 0000:0000 [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:218]
[ResourceManager] Registering I2C interface: /dev/i2c-0 Device 0000:0000 Subsystem: 0000:0000 [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:218]
[ResourceManager] Registering I2C interface: /dev/i2c-7 Device 10DE:2C05 Subsystem: 1458:41A8 [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:218]
[ResourceManager] Registering I2C interface: /dev/i2c-5 Device 10DE:2C05 Subsystem: 1458:41A8 [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:218]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1168]
| Detecting I2C devices | [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1169]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1170]
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1215]
| Detecting I2C DIMM modules | [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1216]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1217]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1282]
| Detecting I2C PCI devices | [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1283]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1284]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1330]
| Detecting HID devices | [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1331]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1334]
[ASUS TUF GAMING B760M-PLUS WIFI II] Registering RGB controller [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:235]
[Logitech G213] Registering RGB controller [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:235]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1499]
| Detecting libusb HID devices | [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1500]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1501]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1611]
| Detecting other devices | [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1612]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1613]
[ResourceManager] Calling Post-detection callbacks [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1033]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1044]
| Detection completed | [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1045]
------------------------------------------------------ [/builds/CalcProgrammer1/OpenRGB/ResourceManager.cpp:1046]

---

---

ABOUT DETECTION

Setting register &0x0b to 0x04 on addresses 0x5[0-7] allows to read the DIMM model name, but
very often address 0x5 is write protected (as in my system), which makes this method useless.

kfrgb will:

• lshw: check for 'vendor: Kingston' and 'product: KF5*'.
• i2cdetect: check if addresses 0x6[0-7], 0x5[0-7] and 0x4[8-f] exist on an smbus that support Quick Command.
• i2cdump (mode i): on address 0x6[0-7] check if blocks 0x02=0x46, 0x03=0x55, 0x04=0x52, 0x05=0x59,
  0x07=0x10/0x12/0x15 (for BEAST) OR =0x11 (for RENEGADE).

The detection passes if all checks are true.
The detection fails at the first error in the chain.

---

---

• i2cdetect -l (check i2c-buses):
  i2c-0 i2c Synopsys DesignWare I2C adapter I2C adapter
  i2c-1 i2c Synopsys DesignWare I2C adapter I2C adapter
  i2c-2 i2c Synopsys DesignWare I2C adapter I2C adapter
  i2c-3 smbus SMBus I801 adapter at 0000:00:1f.4 SMBus adapter
  i2c-4 i2c NVIDIA i2c adapter 3 at 1:00.0 I2C adapter
  i2c-5 i2c NVIDIA i2c adapter 4 at 1:00.0 I2C adapter
  i2c-6 i2c NVIDIA i2c adapter 5 at 1:00.0 I2C adapter
  i2c-7 i2c NVIDIA i2c adapter 6 at 1:00.0 I2C adapter

---

---

• i2cdetect -y 3 (check SMBus i2c-3):
  0 1 2 3 4 5 6 7 8 9 a b c d e f
  00: -- -- -- -- -- -- -- --
  10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  70: -- -- -- -- -- -- -- --

---

• Kingston Fury DDR5 RAM in slot 1 not found on SMBus i2c-3.

• lshw (check bank 0):
  *-bank:0 UNCLAIMED
  description: [empty]
  physical id: 0
  slot: Controller0-DIMM0

• Address 0x60 not found in SMBus i2c-3

• Address 0x48 not found in SMBus i2c-3

• Address 0x50 not found in SMBus i2c-3

• i2cdump 3 0x60 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 2 not found on SMBus i2c-3.

• lshw (check bank 1):
  *-bank:1 UNCLAIMED
  description: DIMM Synchronous 5600 MHz (0.2 ns)
  product: KF556C40-16
  vendor: Kingston
  physical id: 1
  serial: 19163D05
  slot: Controller0-DIMM1
  size: 16GiB
  width: 64 bits
  clock: 1305MHz (0.8ns)

• Address 0x61 not found in SMBus i2c-3

• Address 0x49 not found in SMBus i2c-3

• Address 0x51 not found in SMBus i2c-3

• i2cdump 3 0x61 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 3 not found on SMBus i2c-3.

• lshw (check bank 2):
  *-bank:2 UNCLAIMED
  description: [empty]
  physical id: 2
  slot: Controller1-DIMM0

• Address 0x62 not found in SMBus i2c-3

• Address 0x4a not found in SMBus i2c-3

• Address 0x52 not found in SMBus i2c-3

• i2cdump 3 0x62 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 4 not found on SMBus i2c-3.

• lshw (check bank 3):
  *-bank:3 UNCLAIMED
  description: DIMM Synchronous 5600 MHz (0.2 ns)
  product: KF556C40-16
  vendor: Kingston
  physical id: 3
  serial: D0063BC9
  slot: Controller1-DIMM1
  size: 16GiB
  width: 64 bits
  clock: 1305MHz (0.8ns)

• Address 0x63 not found in SMBus i2c-3

• Address 0x4b not found in SMBus i2c-3

• Address 0x53 not found in SMBus i2c-3

• i2cdump 3 0x63 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 5 not found on SMBus i2c-3.

• lshw (check bank 4):

• Address 0x64 not found in SMBus i2c-3

• Address 0x4c not found in SMBus i2c-3

• Address 0x54 not found in SMBus i2c-3

• i2cdump 3 0x64 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 6 not found on SMBus i2c-3.

• lshw (check bank 5):

• Address 0x65 not found in SMBus i2c-3

• Address 0x4d not found in SMBus i2c-3

• Address 0x55 not found in SMBus i2c-3

• i2cdump 3 0x65 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 7 not found on SMBus i2c-3.

• lshw (check bank 6):

• Address 0x66 not found in SMBus i2c-3

• Address 0x4e not found in SMBus i2c-3

• Address 0x56 not found in SMBus i2c-3

• i2cdump 3 0x66 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• Kingston Fury DDR5 RAM in slot 8 not found on SMBus i2c-3.

• lshw (check bank 7):

• Address 0x67 not found in SMBus i2c-3

• Address 0x4f not found in SMBus i2c-3

• Address 0x57 not found in SMBus i2c-3

• i2cdump 3 0x67 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):

• block 0x02: 0x (expected 0x46)

• block 0x03: 0x (expected 0x55)

• block 0x04: 0x (expected 0x52)

• block 0x05: 0x (expected 0x59)

• block 0x07: 0x (expected 0x10/0x12/0x15 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

---