Motherboard [16/10/2024]ASRock DeskMini A/X300 BIOS / "P1.90.SL01"(S3 support) & "P1.90C"(ACS support) for X300 /"P3.70E" for A300 - AGESA Combo V2 PI "1.2.0.Cc"
- Thread starter HydrAxx747
- Start date
@HydrAxx747 I received at 1.90 with ACS enabled by default from ASRock. In theory it should enable IOMMU groups without the
There is a risk that it's compatible wth Cezanne (5xxx series) only and may completely stop booting with older chips.
drive.google.com
pcie_acs_override=downstream kernel param that wrecks security, and do whatever the equivalent of ARI enumeration does.There is a risk that it's compatible wth Cezanne (5xxx series) only and may completely stop booting with older chips.
X300-BIOS - Google Drive
drive.google.com
Thanks a lot for sharing, my friend! It's good and important to pool our resources and knowledge as DeskMini users. I'll add it to the sharing folder tonight when I have a little more time, and I'll credit you for sharing this test BIOS and clarify what you told me about compatibility only with "Cézanne" APUs (this is also specified in the file name of the archive you shared) so that some people avoid unnecessarily bricking their DeskMini X300@HydrAxx747 I received at 1.90 with ACS enabled by default from ASRock. In theory it should enable IOMMU groups without thepcie_acs_override=downstreamkernel param that wrecks security, and do whatever the equivalent of ARI enumeration does.
There is a risk that it's compatible wth Cezanne (5xxx series) only and may completely stop booting with older chips.
X300-BIOS - Google Drive
, again a big thank you for your contribution, it will not be forgotten. This is the way!That BIOS comes with the usual APU support for 2000G, 3000G, 4000G & 5000G series:@HydrAxx747 I received at 1.90 with ACS enabled by default from ASRock. In theory it should enable IOMMU groups without thepcie_acs_override=downstreamkernel param that wrecks security, and do whatever the equivalent of ARI enumeration does.
There is a risk that it's compatible wth Cezanne (5xxx series) only and may completely stop booting with older chips.
X300-BIOS - Google Drive
Maybe then it's the option that only works correctly on Cezanne APUs in this case? Because I admit the precision in the file name of the archive containing the BIOS is not really clear and leaves all this subject to interpretation, so it would be necessary to test this with different generations of APUs... Because if the BIOS department of ASRock added this precision, it is because there is necessarily a reason for that, otherwise I would not see the point of having specified itThat BIOS comes with the usual APU support for 2000G, 3000G, 4000G & 5000G:
Yeah, would've been good if ASRock would've given some information regarding that.Maybe then it's the option that only works correctly on Cezanne APUs in this case? Because I admit the precision in the file name of the archive containing the BIOS is not really clear and leaves all this subject to interpretation, so it would be necessary to test this with different generations of APUs... Because if the BIOS department of ASRock added this precision, it is because there is necessarily a reason for that, otherwise I would not see the point of having specified it
I apologise, to be super clear that the file name was modified by me based on the email. They said that some Ryzen versions don't support ACS, and I stressed that I had a Cezanne before they sent it.
It's possible it will work on older chips, but I didn't want to be responsible for breaking anyone's computer, so I added the post-fix for safety.
Sorry for not making it clearer, that's on me.
It's possible it will work on older chips, but I didn't want to be responsible for breaking anyone's computer, so I added the post-fix for safety.
Sorry for not making it clearer, that's on me.
Thanks @obrida! I just tried the BIOS with my 5700G and it gives me the following groups:@HydrAxx747 I received at 1.90 with ACS enabled by default from ASRock. In theory it should enable IOMMU groups without thepcie_acs_override=downstreamkernel param that wrecks security, and do whatever the equivalent of ARI enumeration does.
There is a risk that it's compatible wth Cezanne (5xxx series) only and may completely stop booting with older chips.
X300-BIOS - Google Drive
```
IOMMU Group 0:
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
IOMMU Group 1:
00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1633]
IOMMU Group 2:
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
IOMMU Group 3:
00:02.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
IOMMU Group 4:
00:02.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
IOMMU Group 5:
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
IOMMU Group 6:
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635]
IOMMU Group 7:
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 51)
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
IOMMU Group 8:
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0 [1022:166a]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1 [1022:166b]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2 [1022:166c]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3 [1022:166d]
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4 [1022:166e]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5 [1022:166f]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6 [1022:1670]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7 [1022:1671]
IOMMU Group 9:
01:00.0 Non-Volatile memory controller [0108]: Micron/Crucial Technology P2 [Nick P2] / P3 / P3 Plus NVMe PCIe SSD (DRAM-less) [c0a9:540a] (rev 01)
IOMMU Group 10:
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
IOMMU Group 11:
03:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] [8086:2725] (rev 1a)
IOMMU Group 12:
04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c8)
IOMMU Group 13:
04:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637]
IOMMU Group 14:
04:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df]
IOMMU Group 15:
04:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639]
IOMMU Group 16:
04:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639]
IOMMU Group 17:
04:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor [1022:15e2] (rev 01)
IOMMU Group 18:
04:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller [1022:15e3]
```
This is actually one extra group than the ACS kernel patch (`Multimedia controller`).
I tested it on a 3200G and it also not only booted, but separated the devices into distinct IOMMU groups. So it's safe for (some)other chips!
Inside the CTRL-Q menu in advanced, there's 4x4 bifurcation, "thunderbolt enable" and a raft of other stuff I don't understand.
This maybe the last and best BIOS ASRock have gifted us! Thanks ASRock Engineering!
Inside the CTRL-Q menu in advanced, there's 4x4 bifurcation, "thunderbolt enable" and a raft of other stuff I don't understand.
This maybe the last and best BIOS ASRock have gifted us! Thanks ASRock Engineering!
Thanks for the info, so compatibility of the ACS function with Picasso APUs also confirmed if I understand correctly... Well, more than checking the Renoir APUs (well almost confirmed given the previous post by "headkaze"), Raven Ridge (Ryzen 2xxxG/GE) and Dali (some batches of Athlon PRO 300GE/320GE and Athlon 3000G, the others being mostly castrated "Raven Ridge"), but the problem is that I don't have any of these models in stock at homeI tested it on a 3200G and it also not only booted, but separated the devices into distinct IOMMU groups. So it's safe for (some)other chips!
Inside the CTRL-Q menu in advanced, there's 4x4 bifurcation, "thunderbolt enable" and a raft of other stuff I don't understand.
This maybe the last and best BIOS ASRock have gifted us! Thanks ASRock Engineering!
, I got rid of my only Athlon 3000G ("Dali" Die) which I used to update the BIOS of old AM4 motherboards with A320, B350/450 or X370/470 chipsets which were incompatible with the "new" CPUs/APUs in Zen2/Zen3 architecture when I had to prepare configs from second-hand market hardware, but that period is over... well at least with the cards that still had those old chipsets.Happy to check for you if you tell me where to look, although given the S3 BIOSs were also custom, I'm guessing not
Hello ,
I use the deskmini x300 and I noticed that with the new UEFi 1.90 with and without S3, securboot no longer works for me. It stays permanently in setup mode and no longer switches to user mode. Does anyone know anything about it or is it just an error with me ?
I use the deskmini x300 and I noticed that with the new UEFi 1.90 with and without S3, securboot no longer works for me. It stays permanently in setup mode and no longer switches to user mode. Does anyone know anything about it or is it just an error with me ?
Hello! I have a A300 with a 5700G. The original bios was the 3.60, i have done an upgrade to the 3.60S and then to the 1.9 from the X300. Now the system works flawlessly but i can't save the bios setting otherwise the system will lock up at boot. It's like a soft-lock and the only way to restore the system is to do a clear cmos. It's a common problem? There are any solutions?
Thx
Thx
@Dr. Nick 1.90C BIOS Options:
...and ones I'm interested in but don't understand:
- Does the thunderbolt mean it can do TB3 PCI tunneling over the USB-C ports?
- Does the lanes selection mean I could bifurcate the M.2 slots to hold 2 each with a PCI riser?
Code:
# Advanced\ACPI Configuration
Suspend to RAM: [Auto,Disabled]
Deep Sleep: [Disabled,Enabled]
RTC Alarm Power On; [By OS,Disabled,Enabled]
Code:
# Advanced\AMD PBS
Thunderbolt Support: [Disabled, Enabled]
[...]
PCIe\GFX lanes Configuration: [x8,x4x4]- Does the thunderbolt mean it can do TB3 PCI tunneling over the USB-C ports?
- Does the lanes selection mean I could bifurcate the M.2 slots to hold 2 each with a PCI riser?
Last edited:
You have to use UMAF to change BIOS settings (be sure to leave the menus 'til it asks to save the settings, and confirm with Y!).
Can you use DRAM frequency above 2666 MHz? IIRC that was a problem with the 8-core APUs on the A300?
