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

Can I disable RSWP via SMBus by shorting HSA pin to GND on the adapter? #44

Open
MykeHalk opened this issue Oct 6, 2024 · 0 comments
Open

Comments

@MykeHalk
Copy link

MykeHalk commented Oct 6, 2024

I was wondering if its possible to disable RSWP by shorting HSA pin to GND on the adapter and plugging it into the motherboard?

So basically I would set SPD Write Disable to FALSE and install the affected DIMM into an DDR5 adapter and then just plug it into the motherboard and disable RSWP via SMBus. I just want to verify with you that it is a plausible method.

I have made a picture to illustrate the wire connecting from GND pin 6 on the front to HSA pin 148 on the back. Would this be correct?

61e3vyNr52L

I would also like to add, I tried using OpenRGB with my ram modules and one of the DIMM's is no longer being recognized in the vendor RGB control software, Fury CTRL. Whenever I open Fury CTRL, IT only shows 1 of my DIMM's and if I remove the DIMM that is recognized in Fury CTRL and Boot with only the affected DIMM, Fury CTRL fails to start noting "Warning. Not Supported DIMM found!

warning-not-supported-dimm-found-v0-832qkxvcsg8a1

I dumped both SPD files and the only difference between them is address 00000200 and 00000240

(0x51)
00000200 01 98 08 24 21 CE 0A EB DD 4B 46 35 36 30 43 33 --> EB DD
.
.
.
00000240 00 00 41 01 0B 00 00 00 00 00 00 00 00 00 00 00 --> 0B

(0x53)
00000200 01 98 08 24 21 CE 0A EA 37 4B 46 35 36 30 43 33 --> EA 37
.
.
.
00000240 00 00 41 01 10 00 00 00 00 00 00 00 00 00 00 00 -->10

Here is paste of both SPD dumps - https://privatebin.net/?28fdd7fa7566e9cd#8wzcpohKc8Do3byk16nJb189HBhAWMRQAxZvvwoCb27Z

0x53 is the "good" DIMM that responds to Fury CTRL but tbh the difference seems to only be the serial number... im not sure though so im going to try to change 0x240's 0B to 10 to see if it might fix the issue because im not really sure what else the problem could be.

if you have any input i would really appreciate it because this is really frustrating.

Many thanks and looking forward to hearing from you.

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

No branches or pull requests

1 participant