KF556C36-16 seems to be detected but can't go beyond SMBus selection. #23
Comments
|
Hi @bennyb0i! The error message "ERROR: bus i2c-0: does not support I2C Block Read, a more precise model detection is not possible!" indicates that the script is unable to determine the exact RAM model (specifically, whether it is a Beast or a Renegade) due to the lack of I2C Block Read support on the bus. You have the option to disable this specific check by using the undocumented option I have also updated the script to make this option more secure for i2c buses that DO support I2C Block Read. Therefore, even though this update may not directly benefit your current situation, I still recommend updating the script. Let me know if you have any questions! |
|
Cool, thanks for the insight. I was considering to use the undocumented option, though figured I'd open up an issue to get an opinion first. Curious though, do you know of a way to enable I2C block read support, or is it something essentially hard-coded into the bus and unchangeable? In any case, I'll grab the updated script! |
You did well!
I'm not sure. I've looked into it but couldn't find anything helpful, and since I haven't experienced the issue myself, it's hard for me to investigate further.
👌 |
|
To follow up, I took a deep breath and tried it out today with the At least I can turn the dang RGB off when the computer sleeps now, haha. Thanks for putting this together. I hope OpenRGB will support the Kingston Furys soon, but this is a great tool in the meantime 😃 Cheers! |
|
Thank you for the feedback, and I'm glad to hear your problem is resolved. |
|
My SMBus controller (SMBus PIIX4) is also lacking the I2C Block Read functionality, but I was able to get the check string using byte read: $ i2cset -y 1 0x50 0x0b 0x04
$ i2cdump -y -r 0x89-0x8b 1 0x50
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
80: 4b 46 35 KF5 Created a new issue for this, #25 |
Hey there, been trying to get the script to work with my 2 sticks of Kingston Fury Beast. I get a "do not support I2C Block Read..." error, though it seems to detect the ram, but won't let me advance beyond choosing which SMBus to use (it just loops around at that point).
Pressing 0 for the i2c-0 smbus just loops back through the same, asking me to pick an SMBus over and over again.
The text was updated successfully, but these errors were encountered: