Im not hitting any limits beyond maybe uploads, but im increasingly getting a fairly long loading time when posting replies.
Like 15-30sec of that blue bar going on top of page before it actualy posts, it does seem a bit unhappy at times.
EU ASRock Rack B450D4U-V1LQ5 mATX AM4
- Thread starter Cruzader
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Like 15-30sec of that blue bar going on top of page before it actualy posts, it does seem a bit unhappy at times.
the "limits" are not same for all users and depends on the place/thread. don't ask me why.
beside that, these days the STH forum software has issues again.
Can you please share the files I asked you for the Configuration (the 3 different Types mentioned in my Previous Post) ? Maybe you missed something.After bios mod I did a quick compare of SCELNX output, and to me it seems that the settings were the same between original and modded bios. But only with modded bios ECC would be activated upon boot.
Yes I saw your dmidecode data with UUID similar to what I had.
Regarding to UUID I found this nice writeup how to set a generated UUID. The same utility allows to change also other SMBIOS data.
Change SMBIOS UUID on AMI firmware PCs
Change SMBIOS UUID on AMI firmware PCs. GitHub Gist: instantly share code, notes, and snippets.gist.github.com
That's also why I like other People cross-checking MY Results
.
Still undecided to be honest. I was thinking of migrating off the Supermicro X10SLL-F/X10SLM-F Series since this is approx. 4 Times more CPU Power with the 5700X (and twice the RAM), but nothing set in Stone, especially since nobody wants to buy my 2nd Hand Gear here in DenmarkWhat will you do with them?
. But the Supermicro X10SLL-F/X10SLM-F and even better the Supermicro X11SSL-F/X11SSM-F still has something I miss in these newer (Fujitsu TX1320, ASRock Rack B450D4U-V1LQ5) Systems: some PCIe Slot (x8 or x16 Mechanical or open-Ended x4) connected to the PCH/DMI/Chipset. Yeah, it's slow, but for ASPM to work on the Mellanox ConnectX-4 LX, that seems like the only Option (and should still be enough for 10gbps).But in Terms of Software, pretty sure I'll go with Proxmox VE for the Host as usual. Then some VMs for OPNSense (originally I thought I'd use the Xeon E3 v6 for that, but maybe not, let's see), a/several VMs for Docker/Podman Containers (heck might even try to run Kubernetes in the long term), some heavy intensive Builders / Distcc Helpers I guess. I don't think I'll go the HA route with CEPH, I'll probably just stick with ZFS as usual too.
Given it's an AMD Ryzen System, maybe one I could use to mine some XMR, unsure. I never went into Crypto but maybe a bit could be useful.
I also asked @Cruzader like 5 Times what he's doing with his Stuff and he never answered
. Wonder if he's working towards cracking some Encryption or whatnot (although GPUs would be way better for that) .EDIT 1: @chlastakov: and what are you going to do with your 12
?
Mainly to play, test things on desk. I bought this for playing. Probably learn Kubernetes clustering, build separate NAS. Since they were super cheap, learn how to hack BIOSStill undecided to be honest. I was thinking of migrating off the Supermicro X10SLL-F/X10SLM-F Series since this is approx. 4 Times more CPU Power with the 5700X (and twice the RAM), but nothing set in Stone, especially since nobody wants to buy my 2nd Hand Gear here in Denmark
But in Terms of Software, pretty sure I'll go with Proxmox VE for the Host as usual. Then some VMs for OPNSense (originally I thought I'd use the Xeon E3 v6 for that, but maybe not, let's see), a/several VMs for Docker/Podman Containers (heck might even try to run Kubernetes in the long term), some heavy intensive Builders / Distcc Helpers I guess. I don't think I'll go the HA route with CEPH, I'll probably just stick with ZFS as usual too.
Given it's an AMD Ryzen System, maybe one I could use to mine some XMR, unsure. I never went into Crypto but maybe a bit could be useful.
I also asked @Cruzader like 5 Times what he's doing with his Stuff and he never answered
EDIT 1: @chlastakov: and what are you going to do with your 12
Already ordered programmer.
They accepted EUR 8 / piece for 12 pieces plus 20 shipping.
I was actually tempted to offer 5 EUR / piece for 24
.But now it's holiday Season until next Tuesday nobody will answer or accept anyways ...
I still have my doubts that will cool the 5700X well enough though.
I'll try a stress Test hopefully later Today with the Thermalright AXP120-X67 (I typically just let
gcc compile the Linux Kernel using the build folder as tmpfs and see how hot it gets).About the Open Chassis that you suggested, I think I'd rather go with Amazon.de (or Aliexpress if there are good Deals) since that is like half price and they already include VAT / Duties / Shipping / etc:
But I don't really have any space to put such thing, so I guess I'll just use some Silverstone ML03 / 2U Chassis as usual.
EDIT 1: furthermore that CPU Cooler Fan has a stated Lifetime of 50'000 Hours, so approx. 6 Years at 40°C. Not sure how proprietary it is (Fan without Frame, so not "Standard" as in 80mm/120mm Fan IMHO), but that could potentially also harbor some Surprises.
EDIT 2: there are few Problems.
Testing with the Thermalright AXP120-X67, after updating to BIOS L2.12 and attempting to reconfigure ECC (NO BIOS Reset to Default done !) apparently ECC is NOT working. Furthermore the CPU reaches 70+ °C when trying to compile Linux Kernel, which is quite high for such a beefy Cooler. Chassis (Silverstone ML03) was closed and 4x80mm Arctic P8 PWM Fans were used for Intake.
Furthermore Fan Control from Linux does NOT appear to be working. All Fan Speeds read 0 and attempting to set the Duty Cycle directly to
hwmon doesn't do anything:
Code:
root@LiveUbuntu02:~# sensors
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +67.2°C
Tccd1: +68.5°C
nct6779-isa-0290
Adapter: ISA adapter
Vcore: 632.00 mV (min = +0.00 V, max = +1.74 V)
in1: 408.00 mV (min = +0.00 V, max = +0.00 V) ALARM
AVCC: 3.34 V (min = +0.00 V, max = +0.00 V) ALARM
+3.3V: 3.34 V (min = +0.00 V, max = +0.00 V) ALARM
in4: 536.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in5: 352.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in6: 304.00 mV (min = +0.00 V, max = +0.00 V) ALARM
3VSB: 3.39 V (min = +0.00 V, max = +0.00 V) ALARM
Vbat: 3.22 V (min = +0.00 V, max = +0.00 V) ALARM
in9: 0.00 V (min = +0.00 V, max = +0.00 V)
in10: 768.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in11: 328.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in12: 360.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in13: 280.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in14: 296.00 mV (min = +0.00 V, max = +0.00 V) ALARM
fan1: 0 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan5: 0 RPM (min = 0 RPM)
SYSTIN: +35.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor
CPUTIN: +47.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
AUXTIN0: +77.0°C sensor = thermistor
AUXTIN1: +39.0°C sensor = thermistor
AUXTIN2: +81.0°C sensor = thermistor
AUXTIN3: +83.0°C sensor = thermistor
PCH_CHIP_CPU_MAX_TEMP: +0.0°C
PCH_CHIP_TEMP: +0.0°C
PCH_CPU_TEMP: +0.0°C
PCH_MCH_TEMP: +0.0°C
PCH_DIM0_TEMP: +0.0°C
PCH_DIM1_TEMP: +0.0°C
TSI0_TEMP: +67.1°C
intrusion0: ALARM
intrusion1: ALARM
beep_enable: disabledhwmon (in /sys) and only 4 by lm-sensors.Is this set by BIOS and there is nothing we can do about it ? IIRC we can set a Fixed Fan Speed in BIOS but I'd really like to have it adjustable from the OS ...
EDIT 3: in
Advanced -> Hardware Monitor, if I change from Auto to Manual and then set each Fan as Smart Fan (and put e.g. 40°C until 50%, 50°C until 70%, 60°C up to 90%, then 70°C to 100%). Or something like that. I have the Feeling that they allow far too high temperatures before ramping up the Speed. Nevertheless, still no OS control in that Mode (but Max Temperature down to 65°C during Kernel Compile).EDIT 4: also in full Manual Mode with fixed 50% Reference set in BIOS, OS cannot control Fan Speed
.EDIT 5: I guess that since the X470D4U Motherboard comes with the BMC, they just wired the Chip to the BMC to let the BMC control it.
But of course if the BMC is NOT installed (and the B450D4U-V1LQ5 only has Video/VGA Output - when it works), then most likely only the BIOS is in control of it. The
Nuvoton NCT6779D (I guess the Nuvoton NCT6779D-R is the Packaging, as in "Delivered in Reel" ?) should be supported by the Linux Kernel, and it's being loaded as nct6775, but it seems like most stuff does NOT work:
Code:
root@LiveUbuntu02:/tools_local# dmesg | grep -i nct
[ 0.671415] pinctrl core: initialized pinctrl subsystem
[ 2.603443] xor: automatically using best checksumming function avx
[ 6.229772] nct6775: Found NCT6779D or compatible chip at 0x2e:0x290
[ 84.163781] nct6775: Found NCT6779D or compatible chip at 0x2e:0x290
EDIT 6: I think it's only possible to configure the Fan Curve in BIOS after All. Make sure you set it to
Manual and then Smart Fan, the configure your Fan Curve according to what you desire. Kinda disappointing that we don't get access in the OS / Linux though .By the Way, the ECC seems to have started working as soon as I changed either Boot to UEFI or Advanced -> HWMON to Manual. It did NOT unlock any Menu, although now it shows working on this 2nd System:
Code:
root@LiveUbuntu02:/tools_local# dmesg | grep -i edac
[ 0.735164] EDAC MC: Ver: 3.0.0
[ 7.041313] EDAC MC0: Giving out device to module amd64_edac controller F19h_M20h: DEV 0000:00:18.3 (INTERRUPT)
[ 7.041316] EDAC amd64: F19h_M20h detected (node 0).
[ 7.041320] EDAC MC: UMC0 chip selects:
[ 7.041321] EDAC amd64: MC: 0: 8192MB 1: 8192MB
[ 7.041322] EDAC amd64: MC: 2: 8192MB 3: 8192MB
[ 7.041326] EDAC MC: UMC1 chip selects:
[ 7.041327] EDAC amd64: MC: 0: 8192MB 1: 8192MB
[ 7.041328] EDAC amd64: MC: 2: 8192MB 3: 8192MB
Code:
root@LiveUbuntu02:/tools_local# dmidecode -t memory | grep -i correction
Error Correction Type: Multi-bit ECCextract.nsh Script, in one Case running my patch.nsh Script (and ECC NOT working yet), and after running my patch.nsh Script AND changing IIRC BOOT Order and HWMon Fan Setting in BIOS:
Code:
diff noreset_after_L2.12_Update_After_Patching.txt noreset_after_L2.12_Update_After_Patching_and_BIOS_Settings_Changed_ECC_NOW_works.txt
359c359
< AmdSetup(20480):0x20=0xFF
---
> AmdSetup(20480):0x20=0x0C
909c909
< Setup(1):0x183=0x00
---
> Setup(1):0x183=0x01
917,926c917,926
< Setup(1):0x18D=0x01
< Setup(1):0x18E=0x02
< Setup(1):0x18F=0x03
< Setup(1):0x190=0x04
< Setup(1):0x191=0x05
< Setup(1):0x192=0x06
< Setup(1):0x193=0x07
< Setup(1):0x194=0x08
< Setup(1):0x195=0x09
< Setup(1):0x196=0x0A
---
> Setup(1):0x18D=0x00
> Setup(1):0x18E=0x00
> Setup(1):0x18F=0x00
> Setup(1):0x190=0x01
> Setup(1):0x191=0x01
> Setup(1):0x192=0x01
> Setup(1):0x193=0x01
> Setup(1):0x194=0x02
> Setup(1):0x195=0x02
> Setup(1):0x196=0x02Section_Volume_image_9E21FD93-9C72-4C15-8C4B-E77F1DB2D792_body.vol.6.7.en-US.ifr.txt.Whereas the Change from
AmdSetup(0x5000):0x20=0xFF to AmdSetup(0x5000):0x20=0x0C might be what allowed ECC to finally work (defined in File_DXE_driver_CbsSetupDxeSSP_CbsSetupDxeSSP_body.fbd.0.0.en-US.ifr.txt).Looking at it in VSCodium also shows some EXTRA Entries:
Code:
AmdSetup(0x5000):0x25D=0x0F
AmdSetup(0x5000):0x25E=0x0F
AmdSetup(0x5000):0x25F=0x0F
AmdSetup(0x5000):0x260=0x0F
AmdSetup(0x5000):0x261=0x0F
AmdSetup(0x5000):0x262=0x0F
AmdSetup(0x5000):0x263=0x00
AmdSetup(0x5000):0x267=0xF8
AmdSetup(0x5000):0x269=0xFF
AmdSetup(0x5000):0x26A=0x00
AmdSetup(0x5000):0x26B=0xFF
AmdSetup(0x5000):0x26C=0xFF
AmdSetup(0x5000):0x26=0x00
Last edited:
@ALinden: I think I have to give up with .
I think that the Reason is that these "smart" People from ASROCK, for some Weird Reason, used (mainly, but this is FAR from the only Time they did it)
As Reminder,
What I don't understand at all is that you said that you "Moved Out" the.
This is NOT what appears when I compare the Original BIOS which I extracted using
pastebin.com
Essentially what you did (or what
I.e. the comparison is changed from
So I can totally see that you fixed the ASRock ****** and now we don't have a Mutually-Excluding Condition anymore between the 300 different Menus.
I'd still like to understand exactly how you did it (how you modified & rebuilt the BIOS exactly). And why the Issue did NOT show up with AMD Ryzen 3000 CPUs, since I couldn't see (maybe I missed it) where they check for the CPU Type / Family. Probably a Default Value in one of their Hidden Variables I guess (but I thought I went through all of them).
It would also be great to unlock the Overclock Menu to be able to Undervolt.
I gave a quick try with.
EDIT 1: also the Power Options such as PCIe ASPM Configuration (both for CPU and PCH/Chipset) would be great to have
EDIT 2: Power Consumption Measurements with the worst possible PSU ever (?) ... must be a 80-- PSU or something like that
Test Conditions: nothing Attached, just USB3 as Boot Device, Keyboard, CPU Fan, 4xChassis 80mm Fan
Idle: 31W
During Linux Kernel Compile: 138W
I can imagine it's the PSU but I don't like that Idle Figure .. Did anybody else do a quick Test about Power Consumption ?
setup_var.efi to unlock the Menus. I tried changing like 60 further Variables but to no effect. Half don't exist and the other ones had no effect either .I think that the Reason is that these "smart" People from ASROCK, for some Weird Reason, used (mainly, but this is FAR from the only Time they did it)
QuestionId: 0x9, VarStoreId: 0x5000, VarOffset: 0x20, Flags: 0x20, Size: 8 as a Main Switch for pretty much Everything. And on top of that they put A LOT of Unique and Mutually Excluding Conditions for all the Menu Entries (like you need 0xFF for something, then 0xA and 0xB for something else etc). So unlocking a Menu Option causes all other Menu Options to disappear. Sometimes Mutually Exclusive Conditions are needed and make sense, but this is not what is being done in many Instances in this BIOS.As Reminder,
QuestionId: 0x9, VarStoreId: 0x5000, VarOffset: 0x20, Flags: 0x20, Size: 8 is used to Enable Combo CBS.What I don't understand at all is that you said that you "Moved Out" the
UMC Common Options from the SuppressIf Block/Statement .This is NOT what appears when I compare the Original BIOS which I extracted using
uefitool + ifrextractor and your Modded BIOS:
Files /home/user/Patched_BIOS/Section_Volume_image_9E21FD93-9C72-4C15-8C4B-E77F1 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
Essentially what you did (or what
uefitool did, when you replaced/rebuilt the BIOS ?) resulted "only" in the following Change in all Files (Line Number will differ, but it's always QuestionId: 0x9) - I let a script compare all 418-419 Files that got extracted from both BIOSes:
Code:
< EqIdVal QuestionId: 0x9, Value: 0xC
> EqIdVal QuestionId: 0x9, Value: 0xFF
293c293
< EqIdVal QuestionId: 0x9, Value: 0xC
> EqIdVal QuestionId: 0x9, Value: 0x70x7 or 0xFF (depending on the Place the Comparison takes place) to 0xC (or 0x0C).So I can totally see that you fixed the ASRock ****** and now we don't have a Mutually-Excluding Condition anymore between the 300 different Menus
.I'd still like to understand exactly how you did it (how you modified & rebuilt the BIOS exactly)
. And why the Issue did NOT show up with AMD Ryzen 3000 CPUs, since I couldn't see (maybe I missed it) where they check for the CPU Type / Family. Probably a Default Value in one of their Hidden Variables I guess (but I thought I went through all of them).It would also be great to unlock the Overclock Menu to be able to Undervolt
.I gave a quick try with
amdctl from GitHub - kevinlekiller/amdctl: Set P-State voltages and clock speeds on recent AMD CPUs on Linux. but it didn't seem to have any Noticeable Effect .EDIT 1: also the Power Options such as PCIe ASPM Configuration (both for CPU and PCH/Chipset) would be great to have
EDIT 2: Power Consumption Measurements with the worst possible PSU ever (?) ... must be a 80-- PSU or something like that
Test Conditions: nothing Attached, just USB3 as Boot Device, Keyboard, CPU Fan, 4xChassis 80mm Fan
Idle: 31W
During Linux Kernel Compile: 138W
I can imagine it's the PSU but I don't like that Idle Figure .. Did anybody else do a quick Test about Power Consumption ?
Last edited:
you have to find the bytes of "EqIdVal QuestionId: 0x9, Value: 0xC" in the CbsSetupDxeXX.sct file,
modify and exchange the original with your modified version with UEFITool_0.28.0 ( NE can't modify BIOS)
UEFITool calculates new checksum of the ffs entry.
the signed status of the whole BIOS is now invalid, not accepted by AFU tools,
same is if you simply just change the BIOS logo.
Code:
0x1C53C Suppress If: {0A 82}
0x1C53E Variable 0x9 equals 0xFF {12 86 09 00 FF 00}
0x1C544 Not {17 02}
0x1C546 End {29 02}
0x1C548 Ref: UMC Common Options, Variable: 0xFFFF {0F 0F 07 00 07 00 03 00 00 00 FF FF 00 03 70}
0x1C557 End If {29 02}Thank you for answering @RolloZ170 .
Or is it a Release in another Repository ?
Usually uefitool I exported Files in the following Formats (ignore the exact Name / GUID), I mean mainly the initial Prefix + Extension:
These are all Binary Files. If you try to open them with
Do you mean to edit them / search using
Or do I need to export another "kind" of Section (e.g. the FFSv2 Section) ?
For the CbsSetupDxeSSP in particular, I can export the Following "Types" (default Names as given by
-
-
-
-
-
I read some BIOS Chips are 1.8V, but on the CH341A PCB I see only 3.3V and 5.0V. There is a Jumper (by default bridging Pin 1&2) but I don't see 1.8V on the PCB.
Are we sure this BIOS Chip is 3.3V ? Otherwise I would fry the BIOS Chip
.Are you talking about this Release to do the Replacement ? Release 0.28.0 · LongSoft/UEFITool
Or is it a Release in another Repository ?
First of all, how do you get the CbsSetupDxeXX.sct (I assume SSP) File ?
Usually uefitool I exported Files in the following Formats (ignore the exact Name / GUID), I mean mainly the initial Prefix + Extension:
Code:
File_Volume_image_1DF36FF9-C7EA-47A3-BD5B-426C250DB776_body.fbd
File_Volume_image_3E3B6DC0-064D-4B01-9203-7836C9B498E7_body.fbd
File_Volume_image_54F7572F-1FD1-44DA-B635-0E49CAD1E4EF_body.fbd
File_Volume_image_84366C9E-CD61-4B6E-8BC7-384541382842_body.fbd
File_Volume_image_9E21FD93-9C72-4C15-8C4B-E77F1DB2D792_body.fbd
File_Volume_image_C0492C7F-75E2-487C-B2DD-000E6CF7B905_body.fbd
Section_Volume_image_1DF36FF9-C7EA-47A3-BD5B-426C250DB776_body.vol
Section_Volume_image_3E3B6DC0-064D-4B01-9203-7836C9B498E7_body.vol
Section_Volume_image_54F7572F-1FD1-44DA-B635-0E49CAD1E4EF_body.vol
Section_Volume_image_84366C9E-CD61-4B6E-8BC7-384541382842_body.vol
Section_Volume_image_9E21FD93-9C72-4C15-8C4B-E77F1DB2D792_body.vol
Section_Volume_image_C0492C7F-75E2-487C-B2DD-000E6CF7B905_body.vol
Volume_FFSv2_03FE8617-2E04-472E-93E9-545227EB0786_body.vbd
Volume_FFSv2_34E280D7-8B23-40E9-9647-B3AB8A20E58A_body.vbd
Volume_FFSv2_51C81E99-DF1A-4DC5-9966-0B8D9AA09CAD_body.vbd
Volume_FFSv2_5C60F367-A505-419A-859E-2A4FF6CA6FE5_body.vbd
Volume_FFSv2_61C0F511-A691-4F54-974F-B9A42172CE53_body.vbd
Volume_FFSv2_E5274881-D739-4209-9882-7C564B19E263_body.vbdnano you'll just see some "weird" Symbols.Do you mean to edit them / search using
hexdump or ghidra possibly ?Or do I need to export another "kind" of Section (e.g. the FFSv2 Section) ?
For the CbsSetupDxeSSP in particular, I can export the Following "Types" (default Names as given by
uefitool A68, I just noticed uefitool A70 was released last Month):-
DXE Driver-> File_DXE_driver_CbsSetupDxeSSP_CbsSetupDxeSSP_body.fbd-
DXE Dependency Section -> Section_DXE_dependency_CbsSetupDxeSSP_CbsSetupDxeSSP_body.bin-
PE32 Image Section -> Section_PE32_image_CbsSetupDxeSSP_CbsSetupDxeSSP_body.efi-
UI Section -> Section_UI_CbsSetupDxeSSP_CbsSetupDxeSSP_body.bin-
Version Section -> Section_Version_CbsSetupDxeSSP_CbsSetupDxeSSP_body.binYeah, I get that I will need to use the BIOS Programmer. I got a couple of CH341A but I'm a bit concerned about the Voltage.
I read some BIOS Chips are 1.8V, but on the CH341A PCB I see only 3.3V and 5.0V. There is a Jumper (by default bridging Pin 1&2) but I don't see 1.8V on the PCB.
Are we sure this BIOS Chip is 3.3V ? Otherwise I would fry the BIOS Chip
NE = NewEngine = no modify of BIOS.
0.28.0 is imho the last release with mod. support.
its important that you replace as is do with the same file type you have exptracted it.
the PE Image extract as is give a sct file.
check the chip label. w25q128 / mx25L128 is 3V (2.7-3.3)Are we sure this BIOS Chip is 3.3V ? Otherwise I would fry the BIOS Chip
OK but I meant the Repository Link was correct or ? It's not on a completely different Repository or something ?
As I showed you, the PE32 Image Section by default gets saved as
Section_PE32_image_CbsSetupDxeSSP_CbsSetupDxeSSP_body.efi.Not sure why
you are at the right place but you can't use the newer NE version.
Me neither
. But for AMD Ryzen 5000 Series / Vermeer it would seem it's SSP ...But then again to Export the File, should I use 0.28.0 or NE ? Because NE is NOT exporting any File as .cst Extension (at least, of the Types I tried so far).