the multiple QuestionId variables are set by BIOS code based on found CPU/RAM/etc.To me it simply matches the actual Value of the Answer to that Question (which we might call "Variable" Value IMHO).
the multiple QuestionId variables are set by BIOS code based on found CPU/RAM/etc.To me it simply matches the actual Value of the Answer to that Question (which we might call "Variable" Value IMHO).
sure Questionid's are used for this too.THEN show the different Memory Frequency/Timing Settings (e.g. the one at the beginning of this Post). Otherwise do NOT show the Memory Tuning Setting.
which ? there are dozends of it. this special ID was an expample.So I kinda disagree, at least for this Section, that QuestionId matches a particular CPU.
The example I provided in my Previous Post (which ? there are dozends of it. this special ID was an expample.
QuestionId: 0x62
).that works as you explained. butnot all QuestionId are modified just by other options.The example I provided in my Previous Post (QuestionId: 0x62
).
grep -ri "QuestionId: 0x9," File_DXE_driver_CbsSetupDxeSSP_CbsSetupDxeSSP_body.fbd.0.0.en-US.ifr.txt | grep -i "VarOffset"
Numeric Prompt: "Combo CBS", Help: "No help string", QuestionFlags: 0x10, QuestionId: 0x9, VarStoreId: 0x5000, VarOffset: 0x20, Flags: 0x20, Size: 8, Min: 0x0, Max: 0xFF, Step: 0x0
SuppressIf
EqIdVal QuestionId: 0x9, Value: 0xFF
Not
End
Numeric Prompt: "Combo CBS", Help: "No help string", QuestionFlags: 0x10, QuestionId: 0x9, VarStoreId: 0x5000, VarOffset: 0x20, Flags: 0x20, Size: 8, Min: 0x0, Max: 0xFF, Step: 0x0
Default DefaultId: 0x0 Value: 254
End
End
File_DXE_driver_CbsSetupDxeSSP_CbsSetupDxeSSP_body
):setup_var.efi AmdSetup(0x5000):0x20=0xFF
Not
as I think it is ? So Suppress if QuestionId(0x9) != 0xFF
?correct.Is theNot
as I think it is ? SoSuppress if QuestionId(0x9) != 0xFF
?
SuppressIf
EqIdVal QuestionId: 0x8, Value: 0xFF
Not
End
Numeric Prompt: "Combo CBS", Help: "No help string", QuestionFlags: 0x10, QuestionId: 0x8, VarStoreId: 0x5000, VarOffset: 0x20, Flags: 0x20, Size: 8, Min: 0x0, Max: 0xFF, Step: 0x0
Default DefaultId: 0x0 Value: 254
End
End
I guess you pulled the same Section from another CBS / File, hence 0x8 instead of 0x9.correct.
look here: so far i don't know what Questionsflags do.
Code:SuppressIf EqIdVal QuestionId: 0x8, Value: 0xFF Not End Numeric Prompt: "Combo CBS", Help: "No help string", QuestionFlags: 0x10, QuestionId: 0x8, VarStoreId: 0x5000, VarOffset: 0x20, Flags: 0x20, Size: 8, Min: 0x0, Max: 0xFF, Step: 0x0 Default DefaultId: 0x0 Value: 254 End End
poltics. can only be made by the BIOS author.I'm really Puzzled that this Motherboard don't support / enable ECC Memory for 5000 Series CPUs where they claim they "support" the CPU ...
only by reverse engineering the first Dxe which then forwards to the matching special Cbs for the detected CPU type...Of course, provided as you said, that there is Hardware hardcoded Supplementary Condition that we CANNOT bypass.
So you think that there is such a Check in Place after all ?only by reverse engineering the first Dxe which then forwards to the matching special Cbs for the detected CPU type...
yes. x86 code ( reverse engineering )So you think that there is such a Check in Place after all ?
i guess nobody listen to that hiddne options later.My hypothesis was that I just tried to set the wrong VarOffset for the wrong Dxe File (hence I wanted to try with the other 3 VarOffset Values) ...
i don't have that board.But what CPU are you running then ? Or you just gave up on ECC entirely ?
the usual way to unhide option menu is move them out of the "suppress if... end" clamp.I didn't try this Tool before but maybe worth a Shot to see if I missed something: UEFI Editor and GitHub - BoringBoredom/UEFI-Editor: Aptio V UEFI Editor: an alternative to AMIBCP
But if you tell me that there is anyway some hardware encoded Part, how would that work ?the usual way to unhide option menu is move them out of the "suppress if... end" clamp.
same way than BoringBoredom/UEFI-Editor but by hand.But if you tell me that there is anyway some hardware encoded Part, how would that work ?
have some experience with asrock rack. i am done with them.Easier would be asking ASRock, but most likely that's also NOT free ...
Well I would hope that it persists reboot (but Good Point, I would have to re-read the same Variable from UEFI Shell after Reboot).same way than BoringBoredom/UEFI-Editor but by hand.
but if no code os looking to that options there will be no effect.
btw: if you enable ECC, have you checked if that setting remained a reboot ? efi shell is too late to enable ECC.
setup_var.efi
could be impacted when manually changing Settings later on. But I always thought that it survived Reboots.