Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RAM stick not found on SMBus #30

Open
dietriro opened this issue Feb 12, 2025 · 4 comments
Open

RAM stick not found on SMBus #30

dietriro opened this issue Feb 12, 2025 · 4 comments
Labels
question Further information is requested

Comments

@dietriro
Copy link

Hi there,

first thanks a lot for your work! I appreciate it that someone takes the time to implement such a script and shares it.

I have little to no knowledge about SMBus communication. I am just trying to turn off the LEDs on my Kingston Fury Beast DDR5 RAM.
The stick that I installed cannot be found, however. Here is the output from i2cdetect and from your script:

$ sudo ./kfrgb.sh --ramslots 1

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

  • Please select an SMBus (or type 'quit' or 'q' to exit from /home/robind/downloads/kfrgb.sh):

  1. i2c-2 smbus SMBus I801 adapter at 3000 SMBus adapter
    choose>

$ sudo i2cdetect -l
i2c-0 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-1 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-2 smbus SMBus I801 adapter at 3000 SMBus adapter

$ sudo i2cdetect -y 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 08 -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- 44 -- -- -- -- -- 4a -- -- -- -- --
50: -- -- 52 -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- 62 -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

I use the RAM for a linux server, so I don't have Windows running or even a visual desktop environment. That's why your tool would come in really handy.

Thanks in advance for your help!

@dietriro
Copy link
Author

I might have found a reason for this. In the startup log I was able to find the following:

[ 2.540388] i2c i2c-2: 1/2 memory slots populated (from DMI)
[ 2.540390] i2c i2c-2: Memory type 0x22 not supported yet, not instantiating SPD

But I don't really know what it means or how it could help to solve the problem.

@KeyofBlueS
Copy link
Owner

Hi Dietriro, I really appreciate your kind words!

Would you mind sharing the output of the following command?

sudo ./kfrgb.sh --debug

@KeyofBlueS KeyofBlueS added the question Further information is requested label Feb 14, 2025
@Sduck865
Copy link

Hi there!
I have the same problem, as for the truth im pretty new to linux.
nobara 41, kingston fury beast 2x32g on slot 2-4, gigabyte aorus elite ax v2, ryzen 7 9700x (i disabled Igpu on the BIOS), gigabyte master rtx4070ti
Here is my output:

sudo ./kfrgb.sh --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.

/opt/kfrgb/kfrgb.sh 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 Synopsys DesignWare I2C adapter I2C adapter
    i2c-2 i2c NVIDIA i2c adapter 1 at 1:00.0 I2C adapter
    i2c-3 i2c NVIDIA i2c adapter 2 at 1:00.0 I2C 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
    No SMBus found!

ERROR: exit

I tried to fix based on this link, unfortunatelly without any success:
#29
I loaded the i2c-piix4 module, and there is no spd5118 module loaded, but still no SMBus.

Any kind of help will be very appreciated, and also sorry for my bad english :)

@Sduck865
Copy link

The correct way to add "acpi_enforce_resources=lax" parameter is solved my problem!
(Nobara: grubby --update-kernel=ALL --args="acpi_enforce_resources=lax")

Also, i have to "rmmod spd5118" driver after each restart, maybe later i will figure it out how to solve this part.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants