mattz
-
Posts
81 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by mattz
-
-
@ZooMass There have been a few people here who successfully downgraded their Asus PRIME and are up-and-running with an older BIOS--not sure what version. Follow these instructions from @Borbosch:
On 3/29/2019 at 4:48 PM, Borbosch said:I just registered for saying thank you for this thread. 6 Hours i searched and searched without any clue why the passthrough won't work on my Asus PRIME x470-Pro.
The answer was the newest Bios-Update. I managed to downgrade with the tool Afuefix64 and the Instructions found here:
Below "How to flash a official bios".
When you are trying to downgrade it, will warn you with the message "rom file information does not match system bios", but it works nonetheless.
Thanks again!
-
1
-
-
On 5/29/2019 at 2:23 AM, Maor said:
@mattz In my experience, the only mobo vendor who cares about bios updates is Asus and from what I have seen in the forums Asrock got better and their support is able to even provide unofficial bioses.
But it seems, the problem affects all motherboards, so probably it is a bug made by AMD and needs to be fixed by AMD.
@Maor Good tip- I don't put _any_ thought around hardware support when I purchase, but _GOOD_ support would likely change my mind. And agree about the AMD bug, maybe it was some recent spec that wasn't tested well.
On 5/29/2019 at 9:42 AM, killeriq said:Not really in mood doing that right now System is working...
@killeriq - well put, that about sums it up for me!
I don't really like the "If it ain't broke, don't fix it mentality"; however, I may stick to it in this case.
-
19 hours ago, testdasi said:
Don't think the X470 BIOS issues affect X399.
@testdasi- This issue also affects many x370 boards--3 cases reported on that post. I think it's linked to the prep for Ryzen 3 and would further extrapolate that if x399 boards are prepping for Ryzen 3 with BIOS updates, they would also be affected. You own one, have you recently updated BIOS and seen any GPU pass-thru issues?
To stay on topic... I still very much like the 2700x and Ryzen. Prices are dropping nicely. However, for your use cases, would likely be overkill. Get an ITX build with an integrated GPU/APU and go for cores and RAM over larger architecture.
-
On 5/1/2019 at 7:45 AM, CyberMew said:
Got a x470 msi carbon pro board with ryzen 2700 with the latest bios, and dynamix system temps is not detecting any drivers. is there something we should do to fix it?
@CyberMew - I have an MSI x470 and had the same issue. I solved it by installing the NerdPack plugin to be able to run a Perl script, if I remember correctly, for the Dynamix "System Temp" plugin. Unfortunately I can't remember exactly where I got the instructions to do this- it may have been through the Dynamix video guide.
-
On 4/15/2019 at 1:54 PM, killeriq said:
Nothing to do with VM , as ive explained this only happens with latest Bios, when i revert 1 version back, all good again.
Ive found few topics about the D3 error on Threadripper like 1y ago, same now with latest Bios
@killeriq - Wanted to mention, I also started a thread about this D3 error. It is all about the latest Ryzen BIOSes. So far the only solution is to go to a previous (working) motherboard BIOS version.
So, just a word of warning about anyone looking for a Ryzen mobo and CPU. *Many* if not all motherboard BIOSes, including MSI and ASUS brands for the x370 and x470 after March (prepping for the Ryzen 3, I think) are giving these D3 errors for VMs.
-
4 hours ago, Maor said:
hopefully this will be fixed with the Ryzen 3xxx launch. Report to your board vendors.
@Maor - Glad the downgrade fixed it, but agree it's not a long term solution!
I reached out to MSI about my board, but they replied that they "only support windows", so they were not willing to go into any conversation about this issue. And it was hard to even get to that stage... Mobo Tech Support appears to not exactly the most technically advanced group. 🤦♂️
-
This may be a bit late, but wanted to contribute.
Would help recommendation if I knew more about the use case. Multimedia, but are you just hosting files or doing transcoding? And a single Windows VM- will it be the daily diver?
* CPU cores, plan for more so go with the 8 cores if you can. Once you start using Docker and some VMs, you will be glad to have extra cores to dedicate to tasks
* Cache drive- go for more space if you plan to use some VM's (especially for gaming and caching media)
Everything else looks good.
-
Welcome, @LumberJackGeek!
I would say @jonathanm's recommendation is probably the way to go: Install UnRaid and test on another rig. It wouldn't have to be your production server, but maybe something low-powered with the new drives and then switch over.
2 hours ago, jonathanm said:Is there ANY way you can source some old hardware to temporarily spin up another box? That way you can keep your existing rig running while you put Unraid through its paces using a trial install, and if you like it you can migrate your data over the network to your new drives. After the drives are populated, it's easy to move all the Unraid drives with data intact back to your permanent server hardware.
And I wanted clarification on this...
7 hours ago, LumberJackGeek said:I currently have about 15 gigs of data in RAID10 using Windows Server 2019 storage spaces, and I am considering switching to unRAID.
Do you really have only 15 GigaBytes of data?? You can save that to a $10 flash drive or upload to some cloud storage while you try out UnRaid on your hardware.
-
On 3/29/2019 at 4:48 PM, Borbosch said:
I just registered for saying thank you for this thread. 6 Hours i searched and searched without any clue why the passthrough won't work on my Asus PRIME x470-Pro.
The answer was the newest Bios-Update. I managed to downgrade with the tool Afuefix64 and the Instructions found here:
Below "How to flash a official bios".
When you are trying to downgrade it, will warn you with the message "rom file information does not match system bios", but it works nonetheless.
Thanks again!
20 hours ago, swixter said:I did revert Unraid to the prior version, 6.7 rc6 but received the same errors. At this point I wished ASUS, and other MFGs, allowed downgrading the BIOS...
Will be following this topic.
@swixter - Try the *unsupported* BIOS Downgrade utility that @Borbosch posted earlier in this thread. It should allow you to downgrade to an earlier mobo BIOS version. Right now, that's the only fix anyone has found for this problem.
-
On 5/11/2019 at 6:04 PM, tw0884 said:
Since 6.7 has been released, you guys should post when you update unRAID and which MSI bios' don't break VM's. Anyone brave to try the latest again?
I did try 6.7-rc5 with the latest BIOS when I was was originally having the issue and no luck- same error. They were both using Linux Kernel 4.19.
I am holding out hope that the NEXT UnRaid version will include Linux Kernel 5 and because kernel 5.2 (I think) will have Zen 2 support, we will see a fix for our problems with this stuff.
15 hours ago, John_M said:To anyone following this thread it would be useful to see if there's a correlation across the various motherboard brands. I'm interested to know if it's related to a particular AGESA version. You can help by posting your motherboard make and model, the BIOS version that broke your system and the latest version that fixes it. I have a personal interest in the Asus PRIME X470-Pro.
This is a good idea @John_M! I will find all the model numbers listed in this thread and make an edit to the OP to include them there. I am curious on what is the root cause. At one point I contemplated buying a new high-end x470 mobo, but then I saw posts from other folks here with the same issues on other manufacturers.
-
1
-
-
9 hours ago, xsinmyeyes said:
I also wanted to say thank you for this thread.
I just built a Ryzen 5 2600X with an Asus ROG STRIX X370-F setup. Wasted a few hours defeated by the stuck in D3 issue. I rolled back the bios to an early version (4009) and windows VM works with GPU passthrough (gtx 1060).
What a way to discover a work-around, right?? I bet there are _a lot_ of folks going through the same issue. Wonder if there are any other keywords we can use for this thread?
I imagine one day there will be some sort of update to correct this, but I am not sure if it'll be a motherboard BIOS or Linux Kernel, or ...
-
@shuruga2 - Sorry about the delayed response. The only success I had with this was to downgrade the BIOS back to an earlier edition, and that works like a charm. You should be able to do this with some *unsupported* software.
Check the post I started here--other folks have helped me with my MSI bios downgrade, but I think someone mentioned Asus (which is your Prime x370, right?):
-
1 hour ago, Borbosch said:
I just registered for saying thank you for this thread. 6 Hours i searched and searched without any clue why the passthrough won't work on my Asus PRIME x470-Pro.
The answer was the newest Bios-Update. I managed to downgrade with the tool Afuefix64 and the Instructions found here:
Below "How to flash a official bios".
When you are trying to downgrade it, will warn you with the message "rom file information does not match system bios", but it works nonetheless.
Thanks again!
@Borbosch Glad we can commiserate with you on this one. I find it worrisome and hopeful that your Asus motherboard also had this error. At one point I was hoping it was just an MSI issue, but is sounds much larger.
I hope that a future Linux Kernel update (maybe??) is able to address this issue. Otherwise, all these manufacturers are going to have to come out with "fix" BIOS updates again. And being stuck on an old BIOS version is not a long term solution for this issue, but it does work right now...
-
1
-
-
27 minutes ago, tw0884 said:
I did not, but it did it for me. Everything was cleared, including any OC Profile you may have had saved. So you'll have to modify back all your settings. Using custom settings on the Smart Fan curve is a real pain. 😐
-
1
-
-
2 hours ago, tw0884 said:
I'm pretty tempted to update to rc6 for a fix but may try the downgrade first...let me know how this turns out as I cannot run unRAID and W10 concurrently
@tw0884 - that Flash Tool worked like a charm with the older (v14) BIOS! I recommend you do the mobo BIOS downgrade. Updating to rc5 didn't help me at all with my problem. Maybe the Linux Kernel bump they brought in on rc6 will help, but I wouldn't bet on it... Maybe for a bigger upgrade I would try again.
I have successfully booted into my Windows 10 VM with the GPU pass-through! I am ecstatic. Sucks that the only solution is to use an unofficial flash tool to downgrade the BIOS to get this working... but good enough for me!
-
1
-
-
20 hours ago, tw0884 said:
Hey mattz,
Just wanted to chime in that I'm having the same issues with my MSI b450 gaming carbon Ac after updating my bios to the same version you did( 7B85v16). Same two errors on W10 VM Start, same CPU pairings changing after update. Running 6.7.0 rc4. GPU stubbed and unable to pass through to VM. Cheers
Running: ryzen 2600
Sapphire Rx 580
MSI B450 gaming carbon Ac.
Note: I did find a tool that is supposed to be able to downgrade the MSI BIOS here.
@tw0884 - Sorry to hear you are also having problems. But it also makes me feel good I'm not just crazy and someone else sees it. I'll bet there are a lot more ppl noticing the problem as the update. Awesome find on that downgrade tool! I am going to give that a try... hope I don't brick my mobo but so hungry for a fix for the VM.
FAILED - I bought a $40 video card and tried using it to no avail: 1) The mobo has no way to specify that card as the primary unless I move it to the top physical slot and 2) when I have a second card, the PCI-E goes from 16x lanes down to 8x lanes. I am not sure how big of an impact that may have, but I am not a fan of losing half the lanes.
FAILED - I also tried using the Flashback+ built into the BIOS with no luck. I put in the flash drive with a "MSI.ROM" for the v14 BIOS, the computer powers on for 1 second, powers off, then the Flashback+ LED flashes 3 times and stays on. I guess that indicates an error with the flash process. I hit the power button and the computer boots up with the current BIOS v18. I have read that it is very particular about USB sticks, so I could go out an buy a few other brands but... Blah.
I am going to load Windows 10 natively on an old SSD I have to see if everything boots OK. And then try out the MSI downgrade BIOS tool (thank you tw0884!).
And then, the more desperate move, I will look to buy a new motherboard, different brand. MSI said I could start the RMA process, but if I have to disconnect everything and be out a motherboard for a week (or 2??), I am going to bail on MSI--the same problem will happen anyway once the BIOS is updated. I do worry, though, that it's not exclusively an MSI problem but linked to how Ryzen 2 talks to the sysytem... That means that the Linux Kernel(??) would have to get changed (maybe it's fixed in v5?) or... something else? But I don't want to sit idly by for it. However, since it was only the latest BIOS update where I had this problem, hoping other brands completely avoided causing this issue.
-
1
-
-
This is just a rant... But going through some mobo BIOS issues (in my other forum thread posts).
Does it surprise anyone that MSI takes the stance they "do not support other OSes except Windows"? Maybe all (most??) motherboard manufacturers take the same stance from a support standpoint.
I do still like the hardware...
-
Not to dredge up ancient history, but I am now having the "stuck in D3" issue after an upgrade of my BIOS from v14 to v18 on the MSI X470 Gaming M7 motherboard with a Ryzen 2 2700x CPU. Using an Nvidia EVGA 1070 card. This just happened last weekend (Mar 2019). The BIOS update seemed innocuous enough, but it did quite a number to my VM setup... In fact, I cannot pass through my GPU or sound card without errors.
Sounds like all the TR folks went with a BIOS update in late 2017 and got everything working. Why this cropped up for me now is beyond me! I am going to buy a super cheap secondary GPU to try to run for Unraid so I can get my main GPU on a VM again... Any other options you can see for me?
-
You know, I really don't get it. It seems like this is a Threadripper / Ryzen 2 issue from over a year ago. Some pretty ingenious folks on reddit posted a fix for it. However, the final fix was a BIOS update to x399 mobos.
My CPU is a Ryzen 2 2700x... And it only broke with this error message on the _LATEST_ BIOS update. I have emailed MSI's tech support, but I am not getting much help from them... They still think I need to reinstall Windows to make it work. 😕
-
1
-
-
Upgraded Unraid OS to 6.7.0-rc5. No good, still have that "Stuck in D3" error.
Was holding out hope the Linux Kernel update to 4.19 would help, but that's a no-go... Not sure where to go now.
-
Ok, so... I can't revert my BIOS, the MSI M-Flash does not allow to go to an older version. So at this point I am stuck unable to load my GPU into any VM, even Ubuntu.
Searching for anything around a D3 power state with Nvidia has turned up very little. I did see a few references to a Linux Kernel (even the few posts that show D3 on this forum), and it pointed to Linux Kernel 4.19 (as of Unraid 6.6.7 it is still 4.18). I did notice that a Kernel update to 4.19 is coming in the 6.7.0 release--not to mention qemu to v.3.1 which @david7279 originally mentioned, so maybe I hold my breath until then!
Should I get into the Next branch or wait until Stable? Would it do any good for me to get into the conversation about this next version or is my problem such an edge case I should wait for Stable?
Cheers,
-
And... just for good measure, if I try it _without_ the GPU ROM BIOS, I get the same error, plus some other messages...
I am doing a full computer reboot after every attempt with a "stuck in D3" error to make sure everything is clean.
Would having a second graphics card be a way out of this mess? Again, this all worked BEFORE the v18 BIOS update, when I was on v14...
-
Ok, removed all PCIe isolation:
Removed the GPU and pass-through the Mobo Audio:
The VM boots OK and I do see the audio device! But I do still see the warnings in the Log:
Now... If I add back the GPU, GPU ROM, and GPU Audio card...
I get the "stuck in D3" error again:
It is strange that the second shot, the "Other PCI Devices" the "USB 3.0 Host controller" went away, especially since it shouldn't have been available in the first place since I didn't isolate it.
-
@Jaster Good Q's - I do have the GPU audio as primary, my Audio controller as 2nd Audio. However, passing through those other groups because of the Log Messages I was getting (screen shot below). I hope I do not need to pass through anything else, but after the BIOS update I got those messages.
For the other Q's
- GPU ROM is valid... or at least, it worked for me until the mobo BIOS update. Would I need a new ROM after a mobo BIOS update??
- HVM is enabled
This is the selection I have for the error below:
I don't really like the "If it ain't broke, don't fix it mentality"; however, I may stick to it in this case.
Asrock bios update breaks PCIE passthrough
in Motherboards and CPUs
Posted · Edited by mattz
@mrjrp15 - @bastl already linked to it, there is a link to the [unofficial] ASUS downgrade utility in that topic: Asus downgrade utility Afuefix64 from overclock.net Downgrade to the last version that worked and let us know how it worked.