Cross_5 Posted July 6, 2019 Share Posted July 6, 2019 (edited) Hey if I setting up a Win10 VM and select my Radeon RX 580 became I two defferent error. 1) Unknown PCI header type '127' or same time 2) unable to execute QEMU command 'cont': Resetting the Virtual Machine is required. PCI Slot1: NVIDIA NVS 300 PCI Slot2: Radeon RX580 Have anyone are idee? Edited July 6, 2019 by Cross_5 Quote Link to comment
dodgypast Posted July 8, 2019 Share Posted July 8, 2019 (edited) I've just read someone else who got this problem due to a bios update on a gigabyte motherboard and I had to downgrade my bios on a gigabyte motherboard due to the same error so I would guess that's the place to start. Please report this to gigabyte here: https://esupport.gigabyte.com The more who complain the more likely they will test future BIOS on unRAID. Edited July 8, 2019 by dodgypast Quote Link to comment
nlash Posted July 8, 2019 Share Posted July 8, 2019 7 hours ago, dodgypast said: I've just read someone else who got this problem due to a bios update on a gigabyte motherboard and I had to downgrade my bios on a gigabyte motherboard due to the same error so I would guess that's the place to start. Just to confirm, I've had to do exactly this on two boards from two different manufacturers (Gigabyte and MSI). Essentially, you need the bios that predates "- Support new upcoming AMD cpu." Quote Link to comment
dodgypast Posted July 8, 2019 Share Posted July 8, 2019 further research led me to this link:https://forum.level1techs.com/t/attention-amd-vfio-users-do-not-update-your-bios/142685 It's an AMD issues with the BIOS code they're giving to OEMs. It would be nice to know what the developers are doing to try and get AMD to do something about it... or even acknowledge / warn users that their product cannot perform one of it's heavily advertised features in a significant set of circumstances. Quote Link to comment
Cross_5 Posted July 9, 2019 Author Share Posted July 9, 2019 On 7/8/2019 at 8:24 AM, dodgypast said: I've just read someone else who got this problem due to a bios update on a gigabyte motherboard and I had to downgrade my bios on a gigabyte motherboard due to the same error so I would guess that's the place to start. Please report this to gigabyte here: https://esupport.gigabyte.com The more who complain the more likely they will test future BIOS on unRAID. I've try Bios version F40, F31, F30 and F6 now but not work and are new error: Did not find USB device 046d:c07c all version under F40 the same error and if I add my Radeon RX 580 to the VM error: unknown pci source type 'vendor'. Which version work at you?? Quote Link to comment
dodgypast Posted July 9, 2019 Share Posted July 9, 2019 F25 for the ax370. I saw someone mention F5 working for a x470 gigabyte board. Quote Link to comment
Cross_5 Posted July 9, 2019 Author Share Posted July 9, 2019 3 hours ago, dodgypast said: F25 for the ax370. I saw someone mention F5 working for a x470 gigabyte board. Thank you, F5 work but I must set up a new vm. Old VM dont work. Quote Link to comment
sturmstar Posted July 10, 2019 Share Posted July 10, 2019 I had / have exactly this problem. I also have the Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING-CF - currently with F6 Bios Version. Until F6 everything is working fine. Since F30 (also F31 and F40) there is exactly this "VM Unknown PCI header type '127'" error with my Nvidia Cards. I hope there will be another update after F40 - and I hope these bugs will be resolved because it would be a shame if I couldn't upgrade to Ryzen3 because of buggy bios-updates. Quote Link to comment
sturmstar Posted July 18, 2019 Share Posted July 18, 2019 F41b for Gigabyte Boards (with AGESA 1.0.0.3AB) is out ... I'm not able to test this version until the next couple of days ... maybe someone else can test ... Quote Link to comment
dodgypast Posted July 19, 2019 Share Posted July 19, 2019 (edited) 20 hours ago, sturmstar said: F41b for Gigabyte Boards (with AGESA 1.0.0.3AB) is out ... I'm not able to test this version until the next couple of days ... maybe someone else can test ... I've tested it and it doesn't work for the ax370 board, I would imagine it's the same on the x470 as it's based on the same AGESA. Edited July 19, 2019 by dodgypast Quote Link to comment
sturmstar Posted August 2, 2019 Share Posted August 2, 2019 F42a for Gigabyte with AGESA 1.0.0.3ABB is out - rumors says that the issue with VFIO is finally fixed. Perhaps I'm able to test this tommorow Quote Link to comment
sturmstar Posted August 3, 2019 Share Posted August 3, 2019 I just tested it. It still doesn't work with F42a. 😭 Same problems and errors Going Back to f6 again Quote Link to comment
Cross_5 Posted August 3, 2019 Author Share Posted August 3, 2019 6 hours ago, sturmstar said: I just tested it. It still doesn't work with F42a. 😭 Same problems and errors Going Back to f6 again Thank you for the Test. 👍 Quote Link to comment
helin0x Posted August 3, 2019 Share Posted August 3, 2019 Curious to know if the issue affect x570 boards as well, or just x3/470 Quote Link to comment
Leoyzen Posted August 22, 2019 Share Posted August 22, 2019 On 8/4/2019 at 3:43 AM, helin0x said: Curious to know if the issue affect x570 boards as well, or just x3/470 with 1003ab bios MSI x570 ACE has exactly the same problem(AER ERROR),but with kernel patch there is not pci 127 type error for x570. There is an update 1003abb bios update that I havent test yet Quote Link to comment
dodgypast Posted August 23, 2019 Share Posted August 23, 2019 On 8/22/2019 at 11:29 AM, Leoyzen said: with 1003ab bios MSI x570 ACE has exactly the same problem(AER ERROR),but with kernel patch there is not pci 127 type error for x570. There is an update 1003abb bios update that I havent test yet How do you do the kernel patch? Quote Link to comment
LintHart Posted September 8, 2019 Share Posted September 8, 2019 On 8/24/2019 at 12:58 AM, dodgypast said: How do you do the kernel patch? Planning a new build so I’d very much like to know this too is this all still a problem with the latest bios’s? ASRock very recently released another round of bios for their birds since the 1003ab. Quote Link to comment
sturmstar Posted November 17, 2019 Share Posted November 17, 2019 Hi everyone. Just for info - at last - I have tested the latest GIGABYTE Bios F50a for my x470 board - and (with ACS downstream enabled) I can use GPU Passthrough for all of my cards (two) without Error 127 It took over half a year (from F6 to F50a) - but they finally fixed the bug. So I can now finally use Unraid without Kernel Patch AND a newer Bios version as F6... Bye! Quote Link to comment
Cross_5 Posted December 19, 2019 Author Share Posted December 19, 2019 Just for info, X570 AORUS PRO Bios F11 Work fine Quote Link to comment
KptnKMan Posted March 14, 2020 Share Posted March 14, 2020 Also info update on this, using ASUS TUF GAMING X570-PLUS (WI-FI) BIOS with latest 1405 bios, also now getting this error. Something to note, I wasn't experiencing any issues until I upgraded my gfx to RX-5600XT. My older R9-290 worked without any issue. Quote Link to comment
testdasi Posted March 14, 2020 Share Posted March 14, 2020 5 hours ago, KptnKMan said: Also info update on this, using ASUS TUF GAMING X570-PLUS (WI-FI) BIOS with latest 1405 bios, also now getting this error. Something to note, I wasn't experiencing any issues until I upgraded my gfx to RX-5600XT. My older R9-290 worked without any issue. Navi reset but is a known issue around here. It's best if you compile your own kernel with the navi patch. Alternatively, a forum member has compiled a custom kernel with various patches including navi with optional kernel upgrade too. Link below, try at your own risk. Quote Link to comment
KptnKMan Posted March 17, 2020 Share Posted March 17, 2020 (edited) Thanks @testdasi but in the reading around this forum, I've decided to return the 5600XT and get a second hand 1080TI from a friend of mine. Maybe next year or year after I'll see how AMD is doing again with their hardware. Edited March 17, 2020 by KptnKMan Quote Link to comment
Recommended Posts
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.