search

KeyofBlueS / kfrgb

Control RGB Leds of a Kingston Fury Beast/Renegade DDR5 RAM
GNU General Public License v3.0
12 stars 2 forks source link

Not changing color on Kingston Fury Renegade #21

Closed ghost closed 3 months ago

ghost commented 3 months ago

Hello. Unfortunately my 4 RAM slots do not want to change color.

My RAM is Kingston Fury Renegade - 2x White(KF560C32RWAK2-64) and 2x Silver(KF560C32RSAK2-64)

I have determined that they are on i2c-6. When selecting this address I see in the box that the RAM resets the color

Also when selecting slot 4 I have all slots completely reset, but 1-3 just resets slot 1, 2 and 3 sudo kfrgb --smbus 6 --mode static --color 0,255,50 --ramslots 4

I am using ArchLinux 6.6.23-1-lts My motherboard is ASUS ROG STRIX X670E-A On Windows 11 Fury Control changes color

lsmod | grep 'i2c'
i2c_piix4              32768  0
i2c_dev                28672  0

My error log

 ✘ arch@computer  ~  sudo kfrgb --smbus 6 --mode static --color 0,255,50 --ramslots 1,2,3,4

- ERROR: bus i2c-6: do not support I2C Block Read, model detection is not possible!

grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
- RAM in slot 1 on SMBus i2c-6 doesn't seems to be a Kingston Fury BEAST\RENEGADE DDR5!
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
- RAM in slot 2 on SMBus i2c-6 doesn't seems to be a Kingston Fury BEAST\RENEGADE DDR5!
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
- RAM in slot 3 on SMBus i2c-6 doesn't seems to be a Kingston Fury BEAST\RENEGADE DDR5!
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
- RAM in slot 4 on SMBus i2c-6 doesn't seems to be a Kingston Fury BEAST\RENEGADE DDR5!

- Please select an SMBus (or type 'quit' to exit from kfrgb:
grep: warning: stray \ before white space
grep: warning: stray \ before white space
 6) i2c-6   smbus       SMBus PIIX4 adapter port 0 at 0b00  SMBus adapter
 7) i2c-7   smbus       SMBus PIIX4 adapter port 2 at 0b00  SMBus adapter
 8) i2c-8   smbus       SMBus PIIX4 adapter port 1 at 0b20  SMBus adapter
 choose> 6

- ERROR: bus i2c-6: do not support I2C Block Read, model detection is not possible!

grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
- RAM in slot 1 on SMBus i2c-6 doesn't seems to be a Kingston Fury BEAST\RENEGADE DDR5!
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
- RAM in slot 2 on SMBus i2c-6 doesn't seems to be a Kingston Fury BEAST\RENEGADE DDR5!
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
- RAM in slot 3 on SMBus i2c-6 doesn't seems to be a Kingston Fury BEAST\RENEGADE DDR5!
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
grep: warning: stray \ before white space
- RAM in slot 4 on SMBus i2c-6 doesn't seems to be a Kingston Fury BEAST\RENEGADE DDR5!

- Please select an SMBus (or type 'quit' to exit from kfrgb:
grep: warning: stray \ before white space
grep: warning: stray \ before white space
 6) i2c-6   smbus       SMBus PIIX4 adapter port 0 at 0b00  SMBus adapter
 7) i2c-7   smbus       SMBus PIIX4 adapter port 2 at 0b00  SMBus adapter
 8) i2c-8   smbus       SMBus PIIX4 adapter port 1 at 0b20  SMBus adapter
 choose>
ghost commented 3 months ago

When using debug, the following happens

sudo kfrgb --smbus 6 --mode static --color 0,255,50 --ramslots 1,2,3,4 --off --debug

https://pastebin.com/jyFr7m4u

ghost commented 3 months ago

Also, this issue didn't help me https://github.com/KeyofBlueS/kfrgb/issues/16

KeyofBlueS commented 3 months ago

Hi. As the message - ERROR: bus i2c-6: do not support I2C Block Read, model detection is not possible! says, the only way is to try the undocumented option --iwanttoriskandskipmodeldetectionevenifiknowthisisstronglynotrecommended (please use it with caution).

Also update the script to get rid of those grep warnings.

ghost commented 3 months ago

Yeah, thanks, it works. Can I use this in autorun without keyboard interaction(the script asks me if I'm ready to move on)?

sudo kfrgb --smbus 6 --mode static --color 0,255,50 --brightness 100 --ramslots 1,2,3,4 --iwanttoriskandskipmodeldetectionevenifiknowthisisstronglynotrecommended                                                   INT ✘  35s   12:58:04  

- ERROR: bus i2c-6: do not support I2C Block Read, model detection is not possible!

- BIG WARNING: YOU SELECTED THE OPTION TO SKIP THE MODEL DETECTION.
               I CANNOT BE REASONABLY SURE IF THIS DEVICE IS REALLY
               A Kingston Fury BEAST\RENEGADE DDR5 RAM!
- A possible Kingston Fury DDR5 RAM in slot 1 found on SMBus i2c-6! (Please MAKE REALLY SURE this is a Kingston Fury BEAST\RENEGADE DDR5 RGB!)
   description: DIMM Synchronous Unbuffered (Unregistered) 4800 MHz (0.2 ns)
   product: KF560C32-32
   vendor: Kingston
   physical id: 0
   serial: 2E0839DB
   slot: DIMM 0
   size: 32GiB
   width: 64 bits
   clock: 505MHz (2.0ns)

- BIG WARNING: YOU SELECTED THE OPTION TO SKIP THE MODEL DETECTION.
               I CANNOT BE REASONABLY SURE IF THIS DEVICE IS REALLY
               A Kingston Fury BEAST\RENEGADE DDR5 RAM!
- A possible Kingston Fury DDR5 RAM in slot 2 found on SMBus i2c-6! (Please MAKE REALLY SURE this is a Kingston Fury BEAST\RENEGADE DDR5 RGB!)
   description: DIMM Synchronous Unbuffered (Unregistered) 4800 MHz (0.2 ns)
   product: KF560C32-32
   vendor: Kingston
   physical id: 1
   serial: 380234BB
   slot: DIMM 1
   size: 32GiB
   width: 64 bits
   clock: 505MHz (2.0ns)

- BIG WARNING: YOU SELECTED THE OPTION TO SKIP THE MODEL DETECTION.
               I CANNOT BE REASONABLY SURE IF THIS DEVICE IS REALLY
               A Kingston Fury BEAST\RENEGADE DDR5 RAM!
- A possible Kingston Fury DDR5 RAM in slot 3 found on SMBus i2c-6! (Please MAKE REALLY SURE this is a Kingston Fury BEAST\RENEGADE DDR5 RGB!)
   description: DIMM Synchronous Unbuffered (Unregistered) 4800 MHz (0.2 ns)
   product: KF560C32-32
   vendor: Kingston
   physical id: 2
   serial: 3B083747
   slot: DIMM 0
   size: 32GiB
   width: 64 bits
   clock: 505MHz (2.0ns)

- BIG WARNING: YOU SELECTED THE OPTION TO SKIP THE MODEL DETECTION.
               I CANNOT BE REASONABLY SURE IF THIS DEVICE IS REALLY
               A Kingston Fury BEAST\RENEGADE DDR5 RAM!
- A possible Kingston Fury DDR5 RAM in slot 4 found on SMBus i2c-6! (Please MAKE REALLY SURE this is a Kingston Fury BEAST\RENEGADE DDR5 RGB!)
   description: DIMM Synchronous Unbuffered (Unregistered) 4800 MHz (0.2 ns)
   product: KF560C32-32
   vendor: Kingston
   physical id: 3
   serial: 4402342F
   slot: DIMM 1
   size: 32GiB
   width: 64 bits

- do you want to proceed?
0) No
1) Yes
 choose> 1

- SMBus: i2c-6 smbus SMBus PIIX4 adapter port 0 at 0b00 SMBus adapter
- RAMs in Slots: 1 - 2 - 3 - 4

- Mode: static
  - Color is: [   ][   ][   ][   ][   ][   ][   ][   ][   ][   ][   ][   ]
  - Brightness: 100

- ### DISCLAIMER
- BIG WARNING: YOU SELECTED THE OPTION TO SKIP THE MODEL DETECTION.
               I CANNOT BE REASONABLY SURE IF THESE DEVICES ARE REALLY
               A Kingston Fury BEAST\RENEGADE DDR5 RAMs!
- Please make really sure if RAMs in Slots 1 - 2 - 3 - 4 on SMBus 6 are really a 'Kingston Fury BEAST\RENEGADE DDR5 RGB'.
- For more info, please refer to https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/2879.
- Even if you enter the correct values, the procedure is still risky!
- This program can confuse your I2C bus, cause data loss or brick your hardware! Proceed AT YOUR OWN RISK!

- do you want to proceed?
0) No
1) Yes
 choose> 1

- Setting mode static for RAM on slot 1 in SMBus 6
 * Initializing...
 * Setting mode...
 * Setting allcolor...
 * Setting brightness...
 * Finalizing...
 * Done!
- Setting mode static for RAM on slot 2 in SMBus 6
 * Initializing...
 * Setting mode...
 * Setting allcolor...
 * Setting brightness...
 * Finalizing...
 * Done!
- Setting mode static for RAM on slot 3 in SMBus 6
 * Initializing...
 * Setting mode...
 * Setting allcolor...
 * Setting brightness...
 * Finalizing...
 * Done!
- Setting mode static for RAM on slot 4 in SMBus 6
 * Initializing...
 * Setting mode...
 * Setting allcolor...
 * Setting brightness...
 * Finalizing...
 * Done!
KeyofBlueS commented 3 months ago

Sure, just use the option --nowarn

ghost commented 3 months ago

Thank you