Ryzen internal graphics passthrough

[scottpk]

Hello,

 

I am new to unRAID but I have gotten through setting up an array and creating a share, which I am able to access from my laptop. The case is HTPC size and fits in the entertainment center, so I am trying to set up a VM with passthrough so that I can watch movies - I've made some headway in that I've gone from complaints about IOMMU group, to the video blanking out and then the TV not detecting a signal when the VM starts, to getting a signal that indicates a problem (it is green or teal with some vertical lines). But I have not been able to get it to fully work experimenting with different BIOS options.

 

So far choosing the OVMF BIOS option got me no signal, and the SeaBIOS option got me these vertical bars. I have to reboot to get rid of them, the VM refuses to stop through the UI.

 

 

Here's the info that shows in the corner:

M/B: ASRock - B450M Pro4

CPU: AMD Ryzen 3 2200G with Radeon Vega Graphics @ 3500

HVM: Enabled

IOMMU: Enabled

Cache: 384 kB, 2048 kB, 4096 kB

Memory: 8 GB (max. installable capacity 256 GB)

Network: bond0: fault-tolerance (active-backup), mtu 1500
 eth0: 1000 Mb/s, full duplex, mtu 1500

Kernel: Linux 4.18.20-unRAID x86_64

OpenSSL: 1.1.1a

 

I see there is a field where I can provide a copy of the video BIOS, but I don't know how to extract this or if it's even something I should do... Is there something I am missing that I will need to do? If possible I would like to avoid installing a video card, the case is compact and the Vega graphics should be fine for movies and TV anyway.

 

 

[scottpk]

I've tinkered with this a bit more - I have changed the BIOS so that now unRAID is booted through UEFI. Now I do not get a solid screen, rather I get a flash of the pattern from before followed by a black screen (not no signal, the display uses blue for no signal).

 

I have noticed the following gets repeated all over the system log:

Apr 3 21:22:06 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:06 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844afa0]
Apr 3 21:22:07 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:07 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844afd0]
Apr 3 21:22:08 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:08 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b000]
Apr 3 21:22:09 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:09 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b030]
Apr 3 21:22:10 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:10 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b060]
Apr 3 21:22:11 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:11 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b090]
Apr 3 21:22:12 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:12 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b0c0]
Apr 3 21:22:13 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:13 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b0f0]
Apr 3 21:22:14 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:14 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b120]
Apr 3 21:22:15 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:15 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b150]
Apr 3 21:22:16 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:16 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b180]
Apr 3 21:22:17 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:17 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b1b0]
Apr 3 21:22:18 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:18 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b1e0]
Apr 3 21:22:19 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:19 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b210]
Apr 3 21:22:20 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:20 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b240]
Apr 3 21:22:21 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:21 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b270]
Apr 3 21:22:22 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:22 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b2a0]
Apr 3 21:22:23 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:23 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b2d0]
Apr 3 21:22:24 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [
Apr 3 21:22:24 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b300]

Has anyone had any luck getting passthrough to work on the Ryzen APUs?

[scottpk]

I've figured out how to extract the video BIOS, but still this is not working for me.

[scottpk]

This can be ignored now - I've ended up picking up a low-profile GeForce GTX 1050 Ti which is letting me do just this.