Hey everyone,

 

Despite a lot of googling, did not find any result for iommu group breakdown. So I bought it, and here it is, with IOMMU Enabled in the latest stable 1.50 bios:

 

tl;dr: good groups, except for 2 of the USB controllers being in the same one.

 

Group 0:        [1022:1482]     00:01.0  Host bridge                              Starship/Matisse PCIe Dummy Host Bridge
Group 1:        [1022:1483] [R] 00:01.2  PCI bridge                               Starship/Matisse GPP Bridge
Group 2:        [1022:1482]     00:02.0  Host bridge                              Starship/Matisse PCIe Dummy Host Bridge
Group 3:        [1022:1482]     00:03.0  Host bridge                              Starship/Matisse PCIe Dummy Host Bridge
Group 4:        [1022:1483] [R] 00:03.1  PCI bridge                               Starship/Matisse GPP Bridge
Group 5:        [1022:1482]     00:04.0  Host bridge                              Starship/Matisse PCIe Dummy Host Bridge
Group 6:        [1022:1482]     00:05.0  Host bridge                              Starship/Matisse PCIe Dummy Host Bridge
Group 7:        [1022:1482]     00:07.0  Host bridge                              Starship/Matisse PCIe Dummy Host Bridge
Group 8:        [1022:1484] [R] 00:07.1  PCI bridge                               Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
Group 9:        [1022:1482]     00:08.0  Host bridge                              Starship/Matisse PCIe Dummy Host Bridge
Group 10:       [1022:1484] [R] 00:08.1  PCI bridge                               Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
Group 11:       [1022:790b]     00:14.0  SMBus                                    FCH SMBus Controller
                [1022:790e]     00:14.3  ISA bridge                               FCH LPC Bridge
Group 12:       [1022:1440]     00:18.0  Host bridge                              Matisse/Vermeer Data Fabric: Device 18h; Function 0
                [1022:1441]     00:18.1  Host bridge                              Matisse/Vermeer Data Fabric: Device 18h; Function 1
                [1022:1442]     00:18.2  Host bridge                              Matisse/Vermeer Data Fabric: Device 18h; Function 2
                [1022:1443]     00:18.3  Host bridge                              Matisse/Vermeer Data Fabric: Device 18h; Function 3
                [1022:1444]     00:18.4  Host bridge                              Matisse/Vermeer Data Fabric: Device 18h; Function 4
                [1022:1445]     00:18.5  Host bridge                              Matisse/Vermeer Data Fabric: Device 18h; Function 5
                [1022:1446]     00:18.6  Host bridge                              Matisse/Vermeer Data Fabric: Device 18h; Function 6
                [1022:1447]     00:18.7  Host bridge                              Matisse/Vermeer Data Fabric: Device 18h; Function 7
Group 13:       [1022:57ad] [R] 01:00.0  PCI bridge                               Matisse Switch Upstream
Group 14:       [1022:57a3] [R] 02:02.0  PCI bridge                               Matisse PCIe GPP Bridge
Group 15:       [1022:57a3] [R] 02:04.0  PCI bridge                               Matisse PCIe GPP Bridge
Group 16:       [1022:57a3] [R] 02:06.0  PCI bridge                               Matisse PCIe GPP Bridge
Group 17:       [1022:57a3] [R] 02:07.0  PCI bridge                               Matisse PCIe GPP Bridge
Group 18:       [1022:57a4] [R] 02:08.0  PCI bridge                               Matisse PCIe GPP Bridge
                [1022:1485] [R] 07:00.0  Non-Essential Instrumentation [1300]     Starship/Matisse Reserved SPP
                [1022:149c]     07:00.1  USB controller                           Matisse USB 3.0 Host Controller  <= 3.2gen2 type A above type-c
USB:            [05e3:0608]              Bus 001 Device 002                       Genesys Logic, Inc. Hub 
USB:            [1d6b:0002]              Bus 001 Device 001                       Linux Foundation 2.0 root hub 
USB:            [1d6b:0003]              Bus 002 Device 001                       Linux Foundation 3.0 root hub 
                [1022:149c] [R] 07:00.3  USB controller                           Matisse USB 3.0 Host Controller  <= 2.0 controller
USB:            [0781:5583]              Bus 003 Device 004                       SanDisk Corp. Ultra Fit 
USB:            [1a2c:0021]              Bus 003 Device 003                       China Resource Semico Co., Ltd Keyboard 
USB:            [26ce:01a2]              Bus 003 Device 002                       ASRock LED Controller 
USB:            [1d6b:0002]              Bus 003 Device 001                       Linux Foundation 2.0 root hub 
USB:            [1d6b:0003]              Bus 004 Device 001                       Linux Foundation 3.0 root hub 
Group 19:       [1022:57a4] [R] 02:09.0  PCI bridge                               Matisse PCIe GPP Bridge
                [1022:7901] [R] 08:00.0  SATA controller                          FCH SATA Controller [AHCI mode]
Group 20:       [1022:57a4] [R] 02:0a.0  PCI bridge                               Matisse PCIe GPP Bridge
                [1022:7901] [R] 09:00.0  SATA controller                          FCH SATA Controller [AHCI mode]
Group 21:       [1b4b:9123] [R] 03:00.0  SATA controller                          88SE9123 PCIe SATA 6.0 Gb/s controller <= x1 #1
Group 22:       [197b:0585] [R] 04:00.0  SATA controller                          JMB58x AHCI SATA controller  <= x1 #3
Group 23:       [197b:0585] [R] 05:00.0  SATA controller                          JMB58x AHCI SATA controller  <= wifi card slot
Group 24:       [10ec:3000] [R] 06:00.0  Ethernet controller                      Killer E3000 2.5GbE Controller
Group 25:       [10de:128b] [R] 0a:00.0  VGA compatible controller                GK208B [GeForce GT 710]   <= x16 #1
                [10de:0e0f]     0a:00.1  Audio device                             GK208 HDMI/DP Audio Controller
Group 26:       [1022:148a] [R] 0b:00.0  Non-Essential Instrumentation [1300]     Starship/Matisse PCIe Dummy Function
Group 27:       [1022:1485] [R] 0c:00.0  Non-Essential Instrumentation [1300]     Starship/Matisse Reserved SPP
Group 28:       [1022:1486] [R] 0c:00.1  Encryption controller                    Starship/Matisse Cryptographic Coprocessor PSPCPP
Group 29:       [1022:149c] [R] 0c:00.3  USB controller                           Matisse USB 3.0 Host Controller   <= below LAN port USB3 + between ps2+typeC
USB:            [1d6b:0002]              Bus 005 Device 001                       Linux Foundation 2.0 root hub 
USB:            [1d6b:0003]              Bus 006 Device 001                       Linux Foundation 3.0 root hub 
Group 30:       [1022:1487]     0c:00.4  Audio device                             Starship/Matisse HD Audio Controller

Used this script for the output.

 

Note: I'm extremely new to this part of UnRaid.

 

USB:

From what I can see with my very beginner eyes, unfortunately it seems that the USB controllers are all on the same group 15 except for the one in group 23.

 

The two USB devices you see (Keyboard + SanDisk Ultra Fit) are in the supposedly 2.0 slots.

 

The separated group 23 is the USB 3 pair below the NIC LAN port ('USB 3.2 Gen1 USB3_34' in manual) AND the ones between the PS2 and the type-c containing group (USB3.2 Gen1 USB3_12).

The board has 2x USB2, 2x USB3.2 gen1 and one type-c header. The 2.0 is probably on the same controller as the rear IO ones (and thus should not be passed through if you keep to the Unraid standard of "use 2.0") and same with the type-c header.

However, since the 3.2 headers are for gen1, those probably belong to the separately grouped controller. I have not yet tested this, as I don't have the cable/adapter for it.

 

So for all the marketing, the "Lightning Gaming Ports" actually share a group with another controller, lol.

 

PCIe slots:

I'm still very early in experimentation. I just put in a 2230 SATA controller (JMB58x as per lspci) into the empty wifi card slot and even that showed up separately. Same for the first and last X1 slots

 

The wifi card slot is unfortunately right next to one of the x1 slots, so you'll have to use a riser for one of them if you want to use absolutely all the slots.

 

Headless:

It will post headless.

 

Bifurcation:

BIOS (well, the shipped 1.3, did not check with the newest 1.5) had 4*4 / 8+2*4 / 8+8 options for the top, CPU connected PCIe16 slot (the rest of the slots are through the chipset, 3 x1 and 2 x16, though the latter are x4+x2, plus 2 M.2 (Gen4x4), but using PCIe device in the second one will disable 2 of the 6 onboard SATA ports)

 

Weirdness:

One weird issue I was having is that the BIOS seems to be incompatible with my "AverMedia Live Streamer Cap 4K" + GT710 combo: until I plugged in an actual display, the BIOS would just reset. First time I ever saw something like that. The combo works *after* initializing with a dummy plug or a display and changing it out to the capture combo, at least for Unraid console.

 

Test config: (just playing around)

3900X + 2x4GB DDR4 + random cards I had around.

 

Future plans:

2x windows10 VMs, so I'll need at least 2 GPUs, and I'll also put in a 2-port intel 10Gbit NIC. Hopefully SR-IOV will work.

It's an old post, but it's the only one which says that this motherboard posts headless. How? I'm not able to post without GPU.

20 hours ago, sannu said:

It's an old post, but it's the only one which says that this motherboard posts headless. How? I'm not able to post without GPU.

Hi, OP here.

While I still have it, I can't experiment on it as it's a daily driver. It might have changed with BIOS versions. Or it might have been 'enabled' by putting a GPU in temporarily, booting once and then removing it. I've noticed that it is extremely finicky with GPUs. I've had two GPUs in it and depending on basically random chance at connecting to standby power after disassembly and reassembly, it will either display boot message on one, both or none, and keep that as long as it's not fully disassembled. And sometimes on reboot it will not accept the unraid pendrive until I fully power it down and up. Also do not attempt to pass through the motherboard sound card, it's not gonna work right ever.

It's fully stable in my experience during operation, but any change is an insane problem. I wish I went with a workstation equivalent, but I'm not made out of that kind of money, and there is basically nothing else with this many usable slots now. With that said, it seems fully stable in operation with a 5950X and 128GB DDR4, a slot-powered 3050, an A400, 6 m.2 (4 in the x16 slot with a 4x4 card), 2 passed through renesas usb cards, and some sata disks, so packed to the gills with basically only the wifi slot being empty. Oh and I can't get into the BIOS because it freezes while it worked fine previously with the same config. Might have been adding the last USB card.

On 11/24/2025 at 9:25 PM, nagi said:

Or it might have been 'enabled' by putting a GPU in temporarily, booting once and then removing it.

By removing it, do you mean removing after booting, when system is running/powered on? Only reason I want to run it without GPU is to save on power, won't save much, but why waste energy :).

That's exactly why I got this board, at the time, it looked like the best one with enough PCIe slots. Currently have 5900X, but probably could be replaced with 5700G - then again, spending money on new CPU would cost more than savings on energy usage :).

By removing it, do you mean removing after booting, when system is running/powered on?

Ah, no, not during operation. I might have removed a GPU while off, but without pulling the literal cord, or switching the PSU disconnect.

This board, and AsRock in general may not be great for power saving, at least I haven't managed to get to any low C-state. I get into C2 max and in my searches I found others had to play around with hidden BIOS pages from Windows and such. I, too, wanted to consolidate a few things, but power draw seems to be basically the same as my two previous separate un-optimized systems. Granted, with added redundancy.