-
Notifications
You must be signed in to change notification settings - Fork 68
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
Not working on Memphis2-S #64
Comments
@kaitlyndotmoe The NVRAM patches are the only ones I didn't develop or assist with so I'm not sure how they work. But you can try replacing one of the entries in the whitelist that are non-critical with name |
So, I actually took a Z97-PRO ASUS BIOS and patched that (as it's NVRAM whitelist can be patched) and took it's NvramSmi and replaced my NvramSmi with that one, and sure enough, it worked! But now there is another problem, ReBar isn't detected by GPU-Z. I'm starting to think this BIOS lacks proper 4G decoding despite the option being enabled? |
@kaitlyndotmoe it's not going to be detected without a rebar capable gpu |
Understood, thanks then! |
Have you confirmed that nvram write works and they stay across power cycles ? |
As far as I'm aware, it works perfectly fine. But I'll check that and report back if it doesn't. |
Update: it seems to persist and stay across power cycles. |
Hi, @kaitlyndotmoe, can you tell me what was the BIOS version you took? I'm afraid I'm facing the same issue than you with an ASUS Z97-AR 3503 |
Can you please add more details? I have the same shitty hp motherboard and what you did is remarkable |
System
Description
I did everything correctly, enabled 4G decoding, etc. But attempting to turn on the ReBar DXE via ReBarStatus does not work (returns GetLastError: 5). Checking the wiki says I need the NVRAM whitelist patch, but the problem is that none of those whitelist patches work on my system, so I attempted to make my own NVRAM whitelist by patching VarNotInEfiGlobalVarList to return false. Unfortunately, this still did not work. Any ideas?
I have attached the patch I created (may or may not work), but I doubt it's correct.
The text was updated successfully, but these errors were encountered: