Attention amd vfio users do not update your bios

tkoham · May 20, 2019, 2:45am

good to know man keep us posted.

dodgypast · July 8, 2019, 2:09pm

Sorry to bump this but with Ryzen 3000 coming out I was wondering if there had been any official communication from AMD on this, or is AMD now a dead platform for vfio users?

wendell · July 8, 2019, 2:25pm

I am happy to report that x570 is generally better than it’s ever been on the AMD platform. It does vary from board to board. Check out the Linux channel video.

For older boards you should wait. The engineering time is focused on newest boards first seems like because newer boards have some other quirks

In a week or two check back here but I’d say things will be fine.

dodgypast · July 8, 2019, 2:31pm

Thanks for the quick update.

dodgypast · July 17, 2019, 5:30am

Just to confirm the latest Gigabyte BIOS for the AX-370 Gaming 5 based on AGESA 1.0.0.3 AB doesn’t work.

mlem · July 17, 2019, 3:25pm

Doesn’t work as in you get the same pci header type error or some other way? I thought the kernel patch still works.

dodgypast · July 18, 2019, 3:02am

still getting the pci header error.

I can’t patch the kernel as I’m on unRAID.

section279 · July 18, 2019, 3:49am

What version of unraid are you on? I wouldn’t generally recommend unraid as a VFIO platform.

Have a look at these posts on the unraid forum, report back whether you still have issues:

qwijibo · July 20, 2019, 2:37am

I have upgraded to an x570 from a B450. (Still running a 2600).
Have lost the abillity to passthrough the GPU on unraid also with the pci header error.

pantato · July 20, 2019, 6:43am

use VFIO

AsVHEn · July 20, 2019, 1:25pm

Hi, I am trying to pasthrough an RX590 with a 2700x, x470 Taichi Debian host to a Win 10 guest:
I follow a guide (I cann’t put links to it)
But I get the same Error: unknown pci header type ‘127’
I tried to patch kernel following another guide to it:
But then, when I try to “make” it, I get this error:

dpkg-source: información: el paquete tiene marcas borrosas lo cual no está permitido, o está corrompido
dpkg-source: información: si quilt aplica el parche «debian/dfsg/arch-powerpc-platforms-8xx-ucode-disable.patch» adecuadamente, utilice «quilt refresh» para actualizarlo
dpkg-source: fallo: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B .pc/debian/dfsg/arch-powerpc-platforms-8xx-ucode-disable.patch/ --reject-file=- < linux-4.19.37.orig.q2Fx9H/debian/patches/debian/dfsg/arch-powerpc-platforms-8xx-ucode-disable.patch subprocess returned exit status 1
dpkg-buildpackage: fallo: dpkg-source -i.git -b . subprocess returned exit status 2
make[1]: *** [scripts/package/Makefile:75: deb-pkg] Error 2
make: *** [Makefile:1379: deb-pkg] Error 2

(I have spanish Debian, sorry for that)
What should I do to compile patched kernel? Thank you in advance.

pantato · July 21, 2019, 5:27am

I’ll recommend using Arch, as always, though. It’s much easier to do these types of things. Also, make sure you’re using this patch: https://clbin.com/VCiYJ

pantato · July 21, 2019, 6:51am

that is NOT the patch for this issue

AsVHEn · July 21, 2019, 7:45am

I tried with this guide (I said another but it was just I wanted to say it was guided to ) and patch.
Switching to Fedora or Arch is something I have in mind if I cann’t get successful.

section279 · July 21, 2019, 8:34am

Dude chill, I didn’t read his code blocks because of the Spanish, I didn’t realise it wasn’t the usual noob issue.

I’d need to see the make file given it’s referenced in the error. I’d suspect file access issues given it’s a dpkg error 2.

AsVHEn · July 21, 2019, 9:02am

is it, isn’t?
http:// www .mediafire.com/folder/m9zcvcr09t1qw/Files

AsVHEn · July 21, 2019, 11:20am

I changed:

> make -j8 deb-pkg LOCALVERSION=-custom
> cd ..
> dpkg -i *.deb

to this:

> sudo make -j $(nproc)
> sudo make modules_install
> sudo make install
> sudo update-initramfs -c -k 4.1.14 $
> sudo update-grub

And it seem it works. Now I don’t get error on virtual machine, and I was able to get output from passed card after drivers install. It’s stuck on TianoCore screen but it’s a good start .
(And followingthis I have complete output )

pantato · July 21, 2019, 9:00pm

that happens to me sometimes, it just usually needs a reset

brodyck · July 22, 2019, 10:37pm

I’d like to add that I got this issue on an ASROCK B450M Steel Legend motherboard. I updated to see if a newer BIOS would decrease latency in the VM in any way. I updated from v1.00 to v2.30. I’m getting exactly what is described here, but haven’t compiled the kernel with the patch yet. Will update when I have.

I was only having occasional problems with it after rebooting the VM, and then this BIOS prevented it from booting at all.

pantato · July 23, 2019, 2:52am

I’m pretty sure the patch is a sure fire fix. The pci.patch, NOT the quirks.patch