Not working on kingston fury ddr5 rgb ram

[CellophaneWomp]

Hi, i just installed linux on my machine, but the RAM rgb is bothering me. when i run sudo kfrgb --off, it says that it didnt find any supported ram, but i have kingston fury ddr5 ram, and on windows fury ctrl worked fine. I have two 16gb sticks, on slots 2 and 4. The packaging doesnt mention nor "beast" nor "renegade" (nor impact, for that matter), am i out of luck? The part number is KF556C36-16, and the command sudo kfrgb --debug returns:
`-----------------------------------------------------------------------------------------------------------------

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 (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 i915 gmbus dpa I2C adapter
  i2c-2 i2c i915 gmbus dpb I2C adapter
  i2c-3 i2c i915 gmbus dpc I2C adapter
  i2c-4 i2c i915 gmbus tc1 I2C adapter
  i2c-5 i2c i915 gmbus tc2 I2C adapter
  i2c-6 i2c i915 gmbus tc3 I2C adapter
  i2c-7 i2c i915 gmbus tc4 I2C adapter
  i2c-8 i2c i915 gmbus tc5 I2C adapter
  i2c-9 i2c i915 gmbus tc6 I2C adapter
  i2c-10 i2c AUX USBC1/DDI TC1/PHY B I2C adapter
  i2c-11 smbus SMBus I801 adapter at 0000:00:1f.4 SMBus adapter
  i2c-12 i2c NVIDIA i2c adapter 3 at 1:00.0 I2C adapter
  i2c-13 i2c NVIDIA i2c adapter 4 at 1:00.0 I2C adapter
  i2c-14 i2c NVIDIA i2c adapter 5 at 1:00.0 I2C adapter
  i2c-15 i2c NVIDIA i2c adapter 6 at 1:00.0 I2C adapter

---

---

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

---

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

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

• Address 0x60 not found in SMBus i2c-11

• Address 0x48 not found in SMBus i2c-11

• Address 0x50 not found in SMBus i2c-11

• i2cdump 11 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 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• RAM in slot 2 on SMBus i2c-11 doesn't seems to be a Kingston Fury BEAST\RENEGADE DDR5!

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

• Address 0x61 found in SMBus i2c-11

• Address 0x49 found in SMBus i2c-11

• Address 0x51 found in SMBus i2c-11

• i2cdump 11 0x61 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):
  0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
  00: 5a 00 46 55 52 59 05 15 00 53 01 00 01 01 00 19 Z.FURY??.S?.??.?
  10: 00 00 00 01 2c 05 dc 0f 05 05 0f 01 64 40 01 00 ...?,???????d@?.
  20: 5a 50 00 00 10 10 10 0c 04 00 00 00 00 00 64 50 ZP..?????.....dP
  30: 55 0a ff 00 00 00 ff 00 ff 64 00 00 00 ff ef ef U?.......d....??
  40: 5a 80 00 80 00 6d 77 ff c8 00 ff 55 ff 3c 7d ff Z?.?.mw.?..U.<}.
  50: 00 ff 00 00 ff 00 00 ff 00 00 ff 00 00 ff 00 00 ................
  60: 5a 00 00 ff 00 00 ff 00 00 ff 00 00 ff 00 00 ff Z...............
  70: 00 00 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
  80: 5a 00 00 00 00 c8 a8 84 82 01 00 ff ff ff ff ff Z....?????......
  90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
  a0: 5a ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Z...............
  b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
  c0: 5a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Z...............
  d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
  e0: 5a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Z...............
  f0: 00 bb 00 06 3f 00 00 00 00 00 00 00 00 00 00 00 .?.??...........

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

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

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

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

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

• model: FURY

---

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

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

• Address 0x62 not found in SMBus i2c-11

• Address 0x4a not found in SMBus i2c-11

• Address 0x52 not found in SMBus i2c-11

• i2cdump 11 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 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

• RAM in slot 4 on SMBus i2c-11 doesn't seems to be a Kingston Fury BEAST\RENEGADE DDR5!

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

• Address 0x63 found in SMBus i2c-11

• Address 0x4b found in SMBus i2c-11

• Address 0x53 found in SMBus i2c-11

• i2cdump 11 0x63 i (check blocks 0x02, 0x03, 0x04, 0x05, 0x07):
  0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
  00: 5a 00 46 55 52 59 05 15 00 53 01 00 00 01 00 19 Z.FURY??.S?..?.?
  10: 00 00 00 01 2c 05 dc 0f 05 05 0f 01 64 40 01 00 ...?,???????d@?.
  20: 5a 50 00 00 10 10 10 0c 04 00 00 00 00 00 64 50 ZP..?????.....dP
  30: 55 0a ff 00 00 00 ff 00 ff 64 00 00 00 ff ef ef U?.......d....??
  40: 5a 80 00 80 00 6d 77 ff c8 00 ff 55 ff 3c 7d ff Z?.?.mw.?..U.<}.
  50: 00 ff 00 00 ff 00 00 ff 00 00 ff 00 00 ff 00 00 ................
  60: 5a 00 00 ff 00 00 ff 00 00 ff 00 00 ff 00 00 ff Z...............
  70: 00 00 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
  80: 5a 00 00 00 00 c8 a8 84 82 01 00 ff ff ff ff ff Z....?????......
  90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
  a0: 5a ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Z...............
  b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
  c0: 5a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Z...............
  d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
  e0: 5a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Z...............
  f0: 00 bb 00 06 3f 00 00 00 00 00 00 00 00 00 00 00 .?.??...........

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

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

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

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

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

• model: FURY

---

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

• lshw (check bank 4):

• Address 0x64 not found in SMBus i2c-11

• Address 0x4c not found in SMBus i2c-11

• Address 0x54 not found in SMBus i2c-11

• i2cdump 11 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 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

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

• lshw (check bank 5):

• Address 0x65 not found in SMBus i2c-11

• Address 0x4d not found in SMBus i2c-11

• Address 0x55 not found in SMBus i2c-11

• i2cdump 11 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 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

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

• lshw (check bank 6):

• Address 0x66 not found in SMBus i2c-11

• Address 0x4e not found in SMBus i2c-11

• Address 0x56 not found in SMBus i2c-11

• i2cdump 11 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 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

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

• lshw (check bank 7):

• Address 0x67 not found in SMBus i2c-11

• Address 0x4f not found in SMBus i2c-11

• Address 0x57 not found in SMBus i2c-11

• i2cdump 11 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 for BEAST or 0x11 for RENEGADE)

• model: UNKNOWN

---

---

`

[KeyofBlueS]

Hello,

This script is designed to work exclusively with Kingston Fury BEAST and RENEGADE DDR5 RGB modules.

Your RAM has been detected as KF556C36-16. Based on reports from this repository and information available online, it appears that your module is likely a Fury BEAST. However, there is an issue with model detection.

Specifically, for the modules at address 0x61 (slot 2) and 0x63 (slot 4), register block 0x07 returns the value 0x15. For supported models, this value should be 0x10 or 0x12 for BEAST, or 0x11 for RENEGADE. Because of this mismatch, the script cannot reliably identify the model and therefore aborts.

The value 0x15 may indicate a newer hardware revision. While the script might still work, there is also a risk of damaging the RAM if the RGB control mechanism differs from the previously tested revisions.

If you understand and accept this risk (which I do not recommend), you may bypass model detection by using the option
--iwanttoriskandskipmodeldetectionevenifiknowthisisstronglynotrecommended.

Additionally, since your SMBus 11 (the bus used by your RAM) does support I2C Block Read, you must also specify the option
--iwanttoriskandskipmodeldetectionevenifiknowthisisstronglynotrecommendedforreal.

Without this option, the script will automatically re-enable model detection as a safety measure and will display the following error message:

- ERROR: bus i2c-11 DO SUPPORT I2C Block Read, THERE IS NO NEED TO SKIP MODEL DETECTION!
  MODEL DETECTION IS NOW REENABLED FOR SECURITY REASON!

Again, this is strongly discouraged, but the option exists should you decide to proceed.

If you do try this and it works correctly, please let me know. That information would allow me to add support for the 0x15 revision in a future update of the script.

[CellophaneWomp]

Hi, due to the recent RAM shortages problems, i dont want to try the not recommended flags. Also, I said in the post that theres no other branding than Kingston Fury ddr5 on the package, but on the ram itself i just noticed theres the Beast branding on the side (it just wasnt that visible with the LED on). Is there any other way I can help you? Do you plan on eventually adding support for my modules?

[KeyofBlueS]

I recommend that you try OpenRGB. This script was originally meant as a temporary solution while waiting for official support to be added to OpenRGB.

OpenRGB now includes support for Kingston Fury BEAST and RENEGADE DDR5 RGB modules, and it may already support your specific hardware revision as well.

[CellophaneWomp]

Yea, I tried that too, but with no luck unfortunately. Should i open an issue there too?

[KeyofBlueS]

I recommend following the instructions here before opening an issue there.