-
-
Notifications
You must be signed in to change notification settings - Fork 2
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 bank ID not equal ram slot index #26
Comments
Hello there, Could you test the script from the dev branch to ensure it's functioning correctly? |
I checkout to
I use i2c tool command to off DIMM led of slot 3, it work:
I pretty sure my ram slots is 1 and 3. |
If it doesn't work it mean I did not correctly understood something... |
This is debug log from the dev branch
|
Something seems off. The RAM in slots 1 and 3 is showing incorrect values compared to the previous log. This issue occurred while I was experimenting with i2c-tools. I can't recall exactly how I fixed it last time, but here are a few suggestions:
What puzzles me is why the script checks RAM slot 3 but still looks at bank 2 instead of bank 1. It might be that the code I implemented in the dev branch to determine the number of RAM slots on the motherboard is incorrect. Could you please post the output of the following command: |
I think I fixed the bank issue. Please try the updated script in the dev branch, if the code to determine the number of RAM slots on the motherboard is correct, it should work now. EDIT: no, I dont think the updated script changes anything. So as I said before, please post the output of the following command: |
This is
|
I updated dev branch, and it worked. Slot 3 memory led color can be change, thanks :). |
Hi,
My motherboard is Asus ROG STRIX Z790-I GAMING WIFI.
This motherboard only has 2 ram slots, but only slot 1 can be changed.
I found root cause, for my case, the script cannot recognize another DIMM because the ram bank ID not equal the ram slot index.
There is the debug message:
The text was updated successfully, but these errors were encountered: