Gigabyte X570 AORUS Elite / Pro (WiFi) / Ultra Tips & Tricks


Recommended Posts

11 hours ago, righardt.marais said:

Hi

 

Hi Sleepyme

 

I initially tried the i440fv machine when you create the VM as it comes as the standard config but this did not work for my setup and a friend suggested I use the Q35 machine instead. This also did not work in the end.

 

tx

Start from scratch. Download the Unraid USB Creator. For version select Next -> 6.8.0 RC5. Click customize. Check Allow UEFI boot. Insert your new unraid usb into the white port on your motherboard labeled BIOS. Boot your computer into the bios. Reset all settings to factory optimized/default settings. Save and reboot back into the bios. Make ONLY these changes:

 

Tweaker -> Advanced CPU Settings -> SVM Mode -> Enable

Settings -> Miscellaneous -> IOMMU -> Enable

Settings -> AMD CBS -> ACS Enable -> Enable

Settings -> AMD CBS -> Enable AER Cap -> Enable

 

Save and reboot. Assuming you don't have any other boot media attached it will boot unraid. From the web gui Main menu, click the name of your Boot Device (flash). Under Syslinux Config -> Unraid OS, add "video=efifb:off" after "append initrd=/bzroot". The line should now read "append initrd=/bzroot video=efifb:off". Reboot unraid.

 

Create a new vm using win10 template. Use the latest win10 install iso and virtio driver iso. Use the Q35 chipset, and the rest default/usual. Get windows installed/working with vnc graphics. Download appropriate vbios from https://www.techpowerup.com/vgabios/. Pass it along with your gpu video/sound. 

 

If you haven't seen it already, spaceinvader one has a video specific for the 5700 XT. The long and short is you need to pass a vbios, and you need to use Q35 to get the drivers to install properly. I would try doing everything fresh and in the order I suggested.

  • Like 1
Link to comment

Will give it a try in the morning, thanks for helping.

 

Edit:

Hi Skitals

 

I have created everything brand new, new Unraid image download(latest rc9) cleaned the drives and followed your steps to the T.

One thing I did notice that I did wrong previously was that I updated the video card drivers with the Virtio drivers as I would for normal VM operation. After I "did not do the driver update for video card" - it passed the card "once". I did not have keyboard mouse passed so I could not get the VM stopped - Force stopped it.

After rebooting the Unraid system for good measure - and passing keyboard - nothing, no card passed to screen. I have tried different output methods (hdmi, DP) as I thought it had something to do with output method used as I used hdmi initially and after getting excited moved my case to its final resting space (not my desk) and used the DP on my 49" Samsung screen.

I have seen others complain about the AMD cards and Unraid not working nicely.

 

 

As a last resort I am going to start over again and just try using a Nvidia card I borrowed from work. Just to see what happens.

I am so disappointed in the unsuccessful marriage between AMD 5700XT and Unraid - between AMD reset bug and not even working like mine.

 

If there is anyone out there who has the hardware I have and successfully got Unraid to work with X5700XT / Aorus mobo with pass through graphics....please shout.

Maybe one of the reviewers who gets hardware could do a POC for us.

 

Unraid-first-and-only-passthrough-of-X5700XT.jpeg

Edited by righardt.marais
Link to comment
On 12/6/2019 at 6:42 PM, righardt.marais said:

As a last resort I am going to start over again and just try using a Nvidia card I borrowed from work. Just to see what happens.

I am so disappointed in the unsuccessful marriage between AMD 5700XT and Unraid - between AMD reset bug and not even working like mine.

 

If there is anyone out there who has the hardware I have and successfully got Unraid to work with X5700XT / Aorus mobo with pass through graphics....please shout.

I just so happened to buy a 5700 XT since my last post. It works fine. It passes fine with vbios. The latest Adenaline drivers don't work with i440 chipset (you will get a black screen at 40% when installing the drivers). I switched to Q35 and it works fine with the drivers. If you already have the amd drivers installed, you will need to use Q35. The navi reset patch v1 seems to work with this hardware. I am on 6.8.0-RC5 and using the custom 5.3.8 kernel here for the reset patch: 

 

I have noticed some bugs with HDMI and legacy boot on this card/mobo combo. I'm waiting for a new displayport monitor to come in, so I can't confirm if the issue is present on displayport as well. I get the "no signal" bug if the bios is set to CSM Enabled (legacy boot support) AND the card is in a certain state. The biggest issue is that there is a somewhat documented CSM bug with this bios where it reenables itself. My windows and unraid installs are both UEFI, but for some reason something is triggering CSM to become reenabled. I think its the 5700 XT switching between BIOS and UEFI boot. When the state of the motherboard and the gpu get out of sync, the only way to reset it and get a signal for the bios is the turn off the computer, turn off the power supply, unplug the power supply, unplug the hdmi, then reconnect everything and turn the computer back on. When this happens, the motherboard has always reverted to CSM Enabled.  Interestingly, if I DON'T need to get into the bios, I can just let Unraid boot with "no signal" and when I fire up a vm the card/signal comes to life. Occasionally I will get "no signal" when starting a VM, OR it will be super low res. Turning the monitor off and back on fixes this. There is some kind of handshake not happening.

 

This is all frustrating since I have ZERO issues with my 1070 to a display connected with DVI. I'm hoping that all these issues are somehow because my current monitors are ancient and don't support more modern hdmi (let alone displayport) standards.

 

The takeaway here is: Disable CSM in the bios. Use the kernel above with the reset patch. Use Q35 chipset for your Win10 VM. Use UEFI/OVMF for everything (both bare metal and kvm). Use displayport over hdmi. Don't use an ancient display. The first 4 recommendations solved 95% of my problems, hopefully the new monitor with displayport solves the last 5%.

Link to comment

Just ran 3dmark Time Spy, here are my refults: https://www.3dmark.com/3dm/41799540

 

Gigabyte 5700 XT Gaming OC, Ryzen 3900X (passing all but first 2 cores), 16 out of 32GB ram, Windows installed on a 1TB Gen4 m.2 NVME (passing through nvme controller, can also boot Win10 bare metal). Machine type set to Q35-4.0.1. I think my results are pretty good! Getting better numbers in a VM than reviews for this specific vendor card.

 

Edit: Adrenalin 2020 drivers came out, seeing a nice bump in performance: http://www.3dmark.com/spy/9630130

3dmark score 9252 -> 9761

Graphics score 8986 -> 9533

 

Edited by Skitals
Link to comment
22 hours ago, Skitals said:

Just ran 3dmark Time Spy, here are my refults: https://www.3dmark.com/3dm/41799540

 

Gigabyte 5700 XT Gaming OC, Ryzen 3900X (passing all but first 2 cores), 16 out of 32GB ram, Windows installed on a 1TB Gen4 m.2 NVME (passing through nvme controller, can also boot Win10 bare metal). Machine type set to Q35-4.0.1. I think my results are pretty good! Getting better numbers in a VM than reviews for this specific vendor card.

 

Edit: Adrenalin 2020 drivers came out, seeing a nice bump in performance: http://www.3dmark.com/spy/9630130

3dmark score 9252 -> 9761

Graphics score 8986 -> 9533

 

Hi, wondering if you compared it to your actual barebone setup? I tried it myself with a 3600 and baremetal is more powerful...I guess it depends on the cpu raw power.

Can you run an aida64 ram bench (win 10 VM)?

Rgds

Link to comment
On 12/11/2019 at 11:42 AM, luca2 said:

Hi, wondering if you compared it to your actual barebone setup? I tried it myself with a 3600 and baremetal is more powerful...I guess it depends on the cpu raw power.

Can you run an aida64 ram bench (win 10 VM)?

Rgds

It took some tinkering to get things stable but here are the final results for Time Spy

 

Bare metal:

3dmark: 9 871

graphics: 9 488

cpu: 12 805

 

q35-4.0.1:

3dmark: 9 760

graphics: 9 487

cpu: 11 671

 

It is virtually (haha) identical when you consider the kvm is only running on 20 out of 24 cpu threads.

 

Link to comment
On 12/11/2019 at 11:42 AM, luca2 said:

Hi, wondering if you compared it to your actual barebone setup? I tried it myself with a 3600 and baremetal is more powerful...I guess it depends on the cpu raw power.

Can you run an aida64 ram bench (win 10 VM)?

Rgds

No experience with aida64, but here are my results (aida64 v6.20.5300)

Memory Read: 53295 MB/s

Memory Write: 44206 MB/s

Memory Copy: 51345 MB/s

Memory Latency: 87.4 ns

 

Edit: I had noticed high cpu usage while the guest report 1%, changing this from no to yes helped a bit and brough latency "down" to 83.3 ns. Still seems a bit high, yes?

 

Quote

<timer name='hpet' present='yes'/>

Edit 2: Okay, I got memory latency "down" to 79.0ns AND reduced my idle cpu usage to practically 0% by making these two changes:

Switched the usb controller to 3.0 nec.

Turned hpet back OFF and added these hyperv flags:

Quote

      <vpindex state='on'/>
      <synic state='on'/>
      <stimer state='on'/>

Here are the new results:

 

Memory Read: 56165 MB/s

Memory Write: 44619 MB/s

Memory Copy: 52043 MB/s

Memory Latency: 79.0 ns

Edited by Skitals
Link to comment

Thanks @Skitals for this post!  I was having a tough time configuring my ASUS ROG Strix X570-E for VFIO, and the information you distilled here really helped!

 

For other Unraid users looking to run this board (which I recommend!), the information that @Skitals put forth is basically the same for the ASUS ROG Strix X570-E.  I will note the differences I saw in my experience.  Note this data was pulled with MB Bios 1405 (11/26/2019) [AGESA 1.0.0.4 Patch B].

 

UEFI / BIOS Settings:

Advanced -> AMD CBS -> IOMMU -> Enabled (Enable IOMMU)

Advanced -> CPU Configuration -> SVM Mode -> Enabled (Enable CPU Virtualization)

Advanced -> USB Configuration -> XHCI Hand-off- > Enabled (XHCI handled by BIOS [might not be necessary])

 

Settings -> AMD CBS -> ACS Enable -> Enable (Not an option on the ASUS ROG Strix X570-E)

Settings -> AMD CBS -> Enable AER Cap -> Enable (Not an option on the ASUS ROG Strix X570-E)

 

USB Pass-through:

This part was all really the same (HUGE THANKS on this part!).  As @Skitals did, of the 3 USB controllers on the board, I also tried to pass through the obvious one that was by itself.  I played with a TON of settings and recommendations found all over the forums, especially here, (including xen-pciback.hide boot configurations), but none worked with that controller.  When trying to boot a VM with this configuration, it would hard lock the server and force me to do a dirty restart 😡.  Finally, after finding and trying the recommendation here ... it was quite simple!  For this board, the 2 USB controllers that are connected (that you can pass-through) are the 3 Type A and 1 Type C ports below the Ethernet jacks (pictured below) and the internal headers on the motherboard (for routing to the USB connections on the case and/or extenders).  The 4 Type A headers between the HDMI/Display Port and the Realtek 2.5G Ethernet/2x USB Type A are the ones that will remain in use for Unraid.  I attached my boot drive in the "BIOS" USB position (the one with flash button) and it works just fine.  I did not try passing though all the 0b:00.# devices as we need to do with the other controllers (i.e. 06:00.0 06:00.1 06:00.3).  I just tried reserving 0b:00.3, but if I did all the devices, I bet this would have worked too.  Though, at this point, I'm not going to bother trying.

 

Update 12/24/2019: I wanted to try and get my sound card passed so, I did bother trying to pass through all the 0b:00.# devices (i.e. 0b:00.0 0b:00.1 0b:00.3 0b:00.4).  It did not work.  Here's a reddit VFIO thread with other people talking about the same problem.  Looks like we'll all need a AGESA patch to fix this one.

 

Here are the USB controllers on my IOMMU (from the full list, below):

 

Passed-Though USB Controller

[1022:1485] 06:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP

[1022:149c] 06:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

[1022:149c] 06:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

 

Unraid USB Controller

IOMMU group 29:[1022:149c] 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

12858027_4.png

 

Single (NVIDIA) GPU Pass-through:

Also the same.  I needed to add the video=efifb:off declaration to get my system to boot and remove the association to my single NVIDIA GTX 1060.

 

Note, this was not required earlier on when working with this board.  While I'm not 100% sure what I changed to make this necessary I think I have an idea.  I migrated from another setup with a legacy, non-UEFI BIOS.  My Unraid USB boot drive was not set up for UEFI (i.e. the tick box in the Flash drive options), and when I first started Unraid after the hardware upgrade, I needed to enable the BIOS option for the Compatibility Support Module (CSM) to get the flash drive to boot.  This allowed me to boot Unraid, have the main display on the GTX 1060 show the boot process and drop to a CLI, while also allowing dockers to utilize the NVIDIA card (via the Linuxserver.io Nvidia build of Unraid) and the VM Manager to pass-through the card when booting a VM.  When powering off the VM, I was returned to a CLI and everything worked!  This was nice ... but I didn't want to use the CSM if I didn't need to.  So, after telling the flash drive that I'm using UEFI and switching off CSM in BIOS, I needed to use the video=efifb:off declaration to have the boot process drop utilization of the card.  So, no more CLI interface on my main display 😥.

 

Fan Speed Sensors and PWM Controllers:

These I didn't play with at all when it didn't work right off in Unraid 6.8.0-stable.  There are some kernel patches that need to be applied for this to work with x570 boards and Ryzen 3000 processors that are currently either deployed or optional in the Linux 5.4 kernel.  I opened a request to include them in the future builds of Unraid.  If you're like me and want them for our setups, drop a like and a comment to let Limetech know there is interest!

 

 

IOMMU:

Here is how my system looks.  Note, there is a GeForce GTX 1060 and a LSI SAS2008 HBA installed; everything else is the MB itself.  The ACS patch is OFF.

MB Bios 1405 (11/26/2019) [AGESA 1.0.0.4 Patch B].

 

IOMMU group 0:[1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 1:[1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 2:[1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 3:[1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 4:[1022:1483] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 5:[1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 6:[1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 7:[1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 8:[1022:1484] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 9:[1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 10:[1022:1484] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 11:[1022:1484] 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 12:[1022:1484] 00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 13:[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)

[1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)

IOMMU group 14:[1022:1440] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0

[1022:1441] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1

[1022:1442] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2

[1022:1443] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3

[1022:1444] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4

[1022:1445] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5

[1022:1446] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6

[1022:1447] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7

IOMMU group 15:[1022:57ad] 01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57ad

IOMMU group 16:[1022:57a3] 02:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a3

IOMMU group 17:[1022:57a3] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a3

IOMMU group 18:[1022:57a3] 02:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a3

IOMMU group 19:[1022:57a4] 02:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a4

[1022:1485] 06:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP

[1022:149c] 06:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

[1022:149c] 06:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

IOMMU group 20:[1022:57a4] 02:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a4

[1022:7901] 07:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

IOMMU group 21:[1022:57a4] 02:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a4

[1022:7901] 08:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

IOMMU group 22:[1000:0072] 03:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

IOMMU group 23:[10ec:8125] 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller

IOMMU group 24:[8086:1539] 05:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)

IOMMU group 25:[10de:1c03] 09:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)

[10de:10f1] 09:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)

IOMMU group 26:[1022:148a] 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function

IOMMU group 27:[1022:1485] 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP

IOMMU group 28:[1022:1486] 0b:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP

IOMMU group 29:[1022:149c] 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

IOMMU group 30:[1022:1487] 0b:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller

IOMMU group 31:[1022:7901] 0c:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

IOMMU group 32:[1022:7901] 0d:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

 

USB Associations (Before reserving the 06.00.# devices):

Bus 1 --> 0000:06:00.1 (IOMMU group 19)

Bus 001 Device 005: ID 8087:0029 Intel Corp. 

Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

Bus 2 --> 0000:06:00.1 (IOMMU group 19)

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

 

Bus 3 --> 0000:06:00.3 (IOMMU group 19)

Bus 003 Device 002: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

Bus 4 --> 0000:06:00.3 (IOMMU group 19)

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

 

Bus 5 --> 0000:0b:00.3 (IOMMU group 29)
Bus 005 Device 003: ID 154b:005b PNY Flash Drive (<-- Boot Drive)
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

Bus 6 --> 0000:0b:00.3 (IOMMU group 29)

Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

 

 

Happy Computing!!!

-JesterEE

 

Edited by JesterEE
Update
Link to comment
  • 2 weeks later...
13 minutes ago, sonuyos said:

I got x570 Strix E, running on PCIe ACS override ENABLED, however whenever i try to pass through the USB controller, unraid commits suicide :(

 

Same goes for Audio too, any idea what i am doing wrong?

Hello, i have a msi mpg x570 pro wifi and i have no problem with usb passthrough but if i Pass the sound card it's not working the vm won't start without any errors. I will try with acs overide 

Link to comment
8 minutes ago, rachid596 said:

Hello, i have a msi mpg x570 pro wifi and i have no problem with usb passthrough but if i Pass the sound card it's not working the vm won't start without any errors. I will try with acs overide 

Can you send me your IOMMU list and windows xml along with flash?

Link to comment
53 minutes ago, sonuyos said:

I got x570 Strix E, running on PCIe ACS override ENABLED, however whenever i try to pass through the USB controller, unraid commits suicide :(

 

Same goes for Audio too, any idea what i am doing wrong?

I'm curious, why do you need the ACS override?

 

Make sure your passing the right USB controller. See my post above and the OP.

 

The audio I can't get to pass through with the current bios. Crossing my fingers for the future.

 

-JesterEE

Link to comment
17 minutes ago, JesterEE said:

I'm curious, why do you need the ACS override?

 

Make sure your passing the right USB controller. See my post above and the OP.

 

The audio I can't get to pass through with the current bios. Crossing my fingers for the future.

 

-JesterEE

Because everything is merged together instead of single iommu, which post you referring?

Link to comment
22 minutes ago, sonuyos said:

Your flash boot setting

 

I.e. syslinux

default menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append initrd=/bzroot vfio-pci.ids=144d:a808,1033:0194,8086:2723
label unRAID OS GUI Mode
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui vfio-pci.ids=144d:a808
label unRAID OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label unRAID OS GUI Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui unraidsafemode
label Memtest86+
  kernel /memtest

Link to comment
14 minutes ago, sonuyos said:

Because everything is merged together instead of single iommu, which post you referring?

 

"Separate IOMMU" is a deceiving metric for  hardware pass through success. Some things are just meant to be together on the board because that's the way the hardware is defined. Them's the breaks. In the "old days", separate IOMMU actually meant something because the hardware vendors just seemingly stuck things arbitrarily together with little rhym or reason. If you look at posts from around 2015 and 2016, that's what I'm talking about. You'd see things like multiple PCIe slots on the same IOMMU which would make passing one all but impossible. That's not really the case today. Usually, stuff is stuck together because it needs to be that way. From personal experience, separating IOMMU on your board is pointless, but if you get different results through trial and error tests, I'd love to hear more about that.

 

And "my post above" is exactly what it sounds like. Both, all, the whole thread really. From the error you're describing it doesn't sound like you actually read the OP/thread and tried the suggested solution. If you're looking for an alternate solution, you're venturing into uncharted territory. Please report back your findings if you find something useful.

 

-JesterEE

Link to comment
Just now, rachid596 said:

default menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append initrd=/bzroot vfio-pci.ids=144d:a808,1033:0194,8086:2723
label unRAID OS GUI Mode
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui vfio-pci.ids=144d:a808
label unRAID OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label unRAID OS GUI Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui unraidsafemode
label Memtest86+
  kernel /memtest

Your pass through these 2 correct?


[1022:149c] 2c:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
[1022:149c] 2c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

Link to comment
2 minutes ago, sonuyos said:

Your pass through these 2 correct?


[1022:149c] 2c:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
[1022:149c] 2c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

yes but i use this method in the picture.

Capture.PNG

Link to comment
Just now, JesterEE said:

 

"Separate IOMMU" is a deceiving metric for  hardware pass through success. Some things are just meant to be together on the board because that's the way the hardware is defined. Them's the breaks. In the "old days", separate IOMMU actually meant something because the hardware vendors just seemingly stuck things arbitrarily together with little rhym or reason. If you look at posts from around 2015 and 2016, that's what I'm talking about. You'd see things like multiple PCIe slots on the same IOMMU which would make passing one all but impossible. That's not really the case today. Usually, stuff is stuck together because it needs to be that way. From personal experience, separating IOMMU on your board is pointless, but if you get different results through trial and error tests, I'd love to hear more about that.

 

And "my post above" is exactly what it sounds like. Both, all, the whole thread really. From the error you're describing it doesn't sound like you actually read the OP/thread and tried the suggested solution. If you're looking for an alternate solution, you're venturing into uncharted territory. Please report back your findings if you find something useful.

 

-JesterEE

The reason i am doing it is because of all my USB Controller merged with audio and such, which makes it impossible for me to start due to the bug.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.