Add 0x15 as valid 0x07 value for BEAST#35
Merged
KeyofBlueS merged 1 commit intoKeyofBlueS:mainfrom Mar 7, 2026
Merged
Conversation
Owner
|
Hey, thanks for coming back to share your test results, and especially for the PR, I really appreciate it! Happy to hear you were finally able to find out a solution. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have 2x32GB Kingston FURY BEAST RAM cards with part number KF560C30BBAK2-64. I tried to use your script with their RGB lights but model verification failed. All blocks were OK except block 5 (0x07) where my value was 0x15, while the only values expected for BEAST were 0x10 and 0x12. After confirming ten times that my RAM really is FURY BEAST, I took the risk and modified your script to include 0x15 as a valid value. And it worked, for which I'm incredibly grateful, because I searched for a long time. Thus I share my change for your consideration. I believe it should also help with #34.