Kingston Fury Beast DDR5 RGB controller script

rgbram.sh

#!/bin/bash
#
# Kingston Fury Beast DDR5 RGB controller script
#
# Sauce:
# https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/2879#note_1336953263
#
# Supports only static colors.
#
# Usage examples:
#
# sudo ./rgbram.sh ff 00 00 # red
# sudo ./rgbram.sh 00 ff ff # cyan
# sudo ./rgbram.sh 00 00 00 # lights out

if ! [ "$(i2cdetect -l | grep I801)" ]; then
  echo "Intel I801 not detected!"
  exit 2
fi

# from 0 to 0x63
brightness=0x2

ramstick1=0x61
ramstick2=0x63

i2cbus=$(i2cdetect -l | grep I801 | awk '{ print $1 }' | sed 's/i2c-//')
i2cbusdet=$(i2cdetect -l | grep I801)

if ! [[ $1 =~ ^[0-9a-fA-F]{2}$ ]]; then
  echo "$1 is not a valid octet hex value"
  exit 1
fi
red=$1

if ! [[ $2 =~ ^[0-9a-fA-F]{2}$ ]]; then
  echo "$2 is not a valid octet hex value"
  exit 1
fi
green=$2

if ! [[ $3 =~ ^[0-9a-fA-F]{2}$ ]]; then
  echo "$3 is not a valid octet hex value"
  exit 1
fi
blue=$3

echo "Detected bus: $i2cbusdet"
echo -e "Setting up color value of #$red$green$blue\n"

# ram stick 1

i2cset -y $i2cbus $ramstick1 0x08 0x53
sleep 0.020
i2cset -y $i2cbus $ramstick1 0x09 0x00
sleep 0.020
i2cset -y $i2cbus $ramstick1 0x31 0x$red
sleep 0.020
i2cset -y $i2cbus $ramstick1 0x32 0x$green
sleep 0.020
i2cset -y $i2cbus $ramstick1 0x33 0x$blue
sleep 0.020
i2cset -y $i2cbus $ramstick1 0x20 $brightness
sleep 0.020
i2cset -y $i2cbus $ramstick1 0x08 0x44

# ram stick 2

i2cset -y $i2cbus $ramstick2 0x08 0x53
sleep 0.020
i2cset -y $i2cbus $ramstick2 0x09 0x00
sleep 0.020
i2cset -y $i2cbus $ramstick2 0x31 0x$red
sleep 0.020
i2cset -y $i2cbus $ramstick2 0x32 0x$green
sleep 0.020
i2cset -y $i2cbus $ramstick2 0x33 0x$blue
sleep 0.020
i2cset -y $i2cbus $ramstick2 0x20 $brightness
sleep 0.020
i2cset -y $i2cbus $ramstick2 0x08 0x44

My setup evidently doesn't support I2C Block Read/Write operations necessary for i2ctransfer, so this is the first tool I encountered that actually worked. Thanks so much!

thanks a lot. I spend couple of days with controlling these RAMs on linux. I tried with openrgb, kfrgb and virtualization of W10. With the first two I was unsuccessful. W10 worked, but there is no storage for rgb config on the ram itself, so it went back to default after reboot. This script solved everything. I can even turn them off on suspend with help of services.