if other processors have Cbs menu, why should this be hidden if not because nobody looks at these options(in this BIOS)So you meanSuppressIfis a hardcoded Value (in the Firmware File), NOT something that is based on the Register/Variable actual Value ?
They were only explicit about NO 4000 Series Support in latest BIOS.This is interesting! Yes, the original supported CPU list does include G-sku’s for 2000-series, but without graphics actually working. I mean, how could it if the Aspeed is the GPU?
Then maybe, MAYBE, that could mean that 5000-series APUs would also post!? Just without the graphics…
e.g.So you meanSuppressIfis a hardcoded Value (in the Firmware File),
Then why do they claim it supports 3000 AND 5000 Series CPUsa single BIOS AGESA can not support two different architectures.
latest BIOS only supports Matisse and Vermeer CPU(3000 series and 5000 series with no iGPU) So no 4000 series
the Dxe's are taken dynamicaly based on the CPU type, but use same VarStores.Which is even more weird since the same ID figures in each of the different CBS Files.
I'm more puzzled it posts at all than USB not working if that is the Issue.Maybe that is where the statement - "in the last BIOS release only 3000 and 5000 series are supported" - holds true
@dbram Did you only have trouble with your 2600X, but not with your three 3000 series CPU?
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 if I could reach and type something in the EFI ShellIt seems there are three ROM-s available for ASPEED:
Maybe we just need to flash the combined VBIOS+UEFI ROM to ASPEED and then VGA will also work pre-os in legacy BIOS mode.
- VBIOS
- UEFI
- VBIOS+UEFI
You can flash in EFI console.
Download link:
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.
Get some USB3 Header -> Internal Ports Adapter (or a Chassis with one), you will need it most likely.Regarding no support for 4000 series. Isn’t that series only APUs? Could that be why they say it’s not supported…
I don’t have any APU at my disposal so I couldn’t test unfortunately. But it would be fun if someone could try. For server use it could open up for a more power efficient yet powerful solution. If the iGPU would be accessible then that’s a bonus.
I’ve ordered a Ryzen 7 PRO 3700 on eBay to try out on my board. Will take a while for it to show up unfortunately.
that works as you explained. butnot all QuestionId are modified just by other options.The example I provided in my Previous Post (QuestionId: 0x62).
correct.Is theNotas 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
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 ...
Depends ... Mainly on how good you can offload and if you have a NIC (almost mandatory above 25gbps I think) that can do RDMA/ROCE v2.What would be lowest possible CPU that will handle full 40G network speed?
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.
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 ?
I gave a try with a Mellanox ConnectX-4 (non-LX) 100gbps QSFP28 in a Supermicro X11SSL-F with an Intel Xeon E3 1230 v5 I think.I was planning to use Mellanox CX-3 with Ubuntu 24.04 LTS. Don't have experience with RDMA/ROCE yet. Is it possible to plant this MB with CPU that can handle 40G wihthout RDMA / ROCE?
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
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 ?
You asked for the lowest, I gave you my Opinion. You can of course also try to put a 5950x in it ...Looks like I should rather heading for Ryzen 5600X
have some experience with asrock rack. i am done with them.Easier would be asking ASRock, but most likely that's also NOT free ...
most options do. but if ECC is not wanted or supported by code its checked at every POST and set according to rules.My impression was thatsetup_var.eficould be impacted when manually changing Settings later on. But I always thought that it survived Reboots.
look at the set of numbers. you can find them with a hex editor in the sct file. you could move a ref. out of the suppress If e.g.I'm also NOT sure that when disassemblying with uefitool and ifrextractor it's 100% like it should be (i.e. you can disassemble, modify a bit, then reassemble and it would just work). I fear it's MUCH more complicated than that ...
0x1C593 Suppress If: {0A 82}
0x1C595 Variable 0x9 equals 0x2 {12 86 09 00 02 00}
0x1C59B Not {17 02}
0x1C59D Variable 0x9 equals 0x3 {12 06 09 00 03 00}
0x1C5A3 Not {17 02}
0x1C5A5 And {15 02}
0x1C5A7 Variable 0x9 equals 0x4 {12 06 09 00 04 00}
0x1C5AD Not {17 02}
0x1C5AF And {15 02}
0x1C5B1 End {29 02}
0x1C5B3 Ref: NTB Common Options, Variable: 0xFFFF {0F 0F 0A 00 0A 00 06 00 00 00 FF FF 00 06 70}
0x1C5C2 End If {29 02}
You want to mount these ASRock Boards and AMD 5700X as "Blades" ?It was so nice weather this weekend that i ended up not getting around to it at all
Was 17degrees and only 3m/s on the disc golf course.
I did get as far as to ask for a shipping quote on 2 of these tho.
Pricey at about 10200-10500 area NOK per (with import,shipping etc all included).
View attachment 42732
Got the first set of compute nodes moved onto these boards, they are working as expected and have not really looked much more at them beyond that.@Cruzader: any Progress on your Side ? This lack of ECC is quite a big Issue IMHO ...
not help if options are ignored then. but you see all options.Uhm but again how would that help with the hardcoded Hardware based Checks ?
UEFITool replace as isAnd how would you rebuild the BIOS after modification ?
yes, without BMC/IPMI the only optionAnd Flashing must be done via a SOP/SOIP Clip,
Yeah, I get that. Even if you only had to pay 10 EUR more for it to get 2 Times the Performance it would be worth itYes, thank you for that. I can now make my picture. Since I can buy 5600X cheaper than 5300U, I hope it will work well.

here's mine :I think 5000 Series CPUs is out of Luck concerning ECC Support. I tried everything I could think of short of Reverse Engineering the X86 Part of the BIOS as @RolloZ170 mentioned (but I don't think I have the Skills to do that TBH).
After a fresh Boot you could try greppingCode:dmidecode | grep -i "Error correction"dmesg:
If it ONLY reports this, then ECC is not Enabled:Code:dmesg | grep -i edac
Thank youCode:[ 0.650269] EDAC MC: Ver: 3.0.0![]()
# dmidecode | grep -i "Error correction"
Error Correction Type: Multi-bit ECC
Error Correction Type: Multi-bit ECC
Error Correction Type: Multi-bit ECC
Error Correction Type: Multi-bit ECC
# dmesg | grep -i edac
[ 0.687160] EDAC MC: Ver: 3.0.0
[ 4.203283] EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 0000:00:18.3 (INTERRUPT)
[ 4.203288] EDAC amd64: F17h_M70h detected (node 0).
[ 4.203293] EDAC MC: UMC0 chip selects:
[ 4.203294] EDAC amd64: MC: 0: 0MB 1: 0MB
[ 4.203297] EDAC amd64: MC: 2: 8192MB 3: 8192MB
[ 4.203302] EDAC MC: UMC1 chip selects:
[ 4.203303] EDAC amd64: MC: 0: 0MB 1: 0MB
[ 4.203306] EDAC amd64: MC: 2: 8192MB 3: 8192MB