mattz

Members
  • Posts

    81
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by mattz

  1. @killeriq- I think I'm in the same boat now. I just upgraded my x470 board to the Ryzen 3900x from the 2700x (wanted the cores!). However, I am no longer able to pass through my motherboard's USB Controller 3.0 the same way I did with the 2700x. I now get the same error you had and the whole system will lock up, requiring a hard reboot: kernel: vfio-pci 0000:0c:00.0: not ready 1023ms after FLR; waiting It is something others are encountering--the only way to fix it is to avoid passing through that particular USB controller, and use other USB Controllers, if you can: There is also a Kernel patch, it appears, that could fix it. So, I am not sure, does the latest Unraid BIOS fix it for you? It could be the kernel patch made it in...
  2. I wanted to mention, this issue has just recently been affecting me. I am on an MSI x470 Gaming M7 AC motherboard. The issue occurred when I switched from the 2700x CPU to the 3900x CPU (I wanted more cores!!). I swapped the CPUs and all the VFIO Bus:Device.Function numbers changed (that's probably expected). However, the `USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller` (IOMMU group 22 in the pic below) I had passed-through with the 2700x no longer works in pass-thru, even after adjusting for the vfio numbers. Using it now locks up the system no matter what combo of "Non-essential" components I tag with vfio and pass with it. @Skitals described this problem with all x570 boards... Looks like it's the same for x470 boards with a 3000 series CPU. Why the heck is this a problem in the 3000 series, BTW?? I am going down the path of passing through the other USB controllers, as stated above. Unfortunately, on this board one of the controllers is the front USB, which are not very accessible to me. The other contains 3 regular USB ports and 1 USB-C port on the back to use, but that is contained in a very large IOMMU group that includes things like the Ethernet controller (IOMMU group 17), so I have my doubts about isolating that back USB panel. Will provide an update when I get this going... Worst case I buy a separate, PCI USB controller and go that route.
  3. @wbsmolen - I agree- I think it is unrelated to this particular BIOS issue. I found this post about an x570 earlier in this thread to confirm it's probably not this issue, but it also may be related to your problem... ? Good luck.
  4. There were some x570's that had the issue... can't remember which ones. However, you should be good with any BIOS after November 2019. Anything this version or later: AGESA AMD BIOS version 1.0.0.4 Patch B (1004 B) fixes
  5. @mojotaker - Agree with @boris. It sounds unrelated to the pass-through issues. If this is the first time you are using the GPU for pass-through, you may need to double-check the Vbios is properly set up. Use this as a reference:
  6. Woo hoo! Glad it worked for you. I understand being hesitant to update the BIOS, but I think having an up-to-date BIOS, if not the latest, is super important. Cheers.
  7. Thanks for responding with the updates on the latest mobo BIOS tests, @klingon00, @boris, @juan11perez, @dodgypast, and others. Sounds like the AGESA AMD BIOS version 1.0.0.4 Patch B (1004 B) is fixing this pass-through issues for folks across the board (pun intended) for x370 and x470 mobos! So, after 9 months from this issue first popping up, AMD has solved it! Better late than never... Just a note: if you update to this latest BIOS from a working old BIOS your CPU pinnings and IOMMU groups will change, so you will have to update your UnRaid configurations.
  8. @cgi2099 - It sounds like this was the issue causing your errors. Downgrading your motherboard BIOS fixed it, there is a new patch from AMD that is having success so you can update your BIOS to this version: AGESA AMD BIOS version 1.0.0.4 Patch B (1004 B). It started rolling out in BIOSes after late November 2019.
  9. Wanted to throw out there: I upgraded my BIOS to the latest 1.0.0.4 Patch B (version 7B77v1D for my mobo), my GPU pass through with the MSI x470 Gaming M7 AC and a Ryzen 2700x now works without a hitch! Of course, the CPU Pinning numbers did change in addition to some IOMMU groups. Edit - Did this after upgrade to Unraid 6.8.0. If you have been listening to this thread, waiting to update your motherboard BIOS because of this issue, I think it's a safe time to try if your manufacturer has that latest version. per MSI for my motherboard it is - Update AMD ComboPI1.0.0.4 Patch B (SMU v46.54). Cheers!
  10. @JM2005- still a great time to buy. New stuff has released and other prices have dropped since your first post in July. * CPU - AMD Ryzen 2700x is $160 on Amazon right now (https://www.amazon.com/dp/B07B428M7F), but the AMD Ryzen 3000 series has released and offers better per-core performance. Your old setup with a Xeon makes me think an AMD ThreadRipper would be more comparable, and I think the prices have been good with that, too. But that does add a premium price to the motherboard you choose to pair. * RAM - super cheap right now, shoot for 32 GB. Are you looking for ECC? That will be more, of course, but there are some good high-performance DDR4 deals, I use https://slickdeals.net/. * Motherboard - for the Ryzen, the x470 or newer x570 prices are looking good, you can find a lot of choices for MicroATX. If you can find a local Fry's or MicroPC, you can probabaly get a discount for a combo CPU+Mobo deal. * NVME drives keep dropping and would be great for your cache/VM/Docker storage needs, again I use https://slickdeals.net/
  11. From what I am seeing, the latest AGESA AMD BIOS version 1.0.0.4 Patch B is working for some folks with ASUS PRIME X470 PRO. Read it on AMD support page https://community.amd.com/thread/241650 And if @whiskeykilo gets it working on the MSI B450 Gaming Pro AC, there may be good evidence on other platforms, too. I will try upgrading my BIOS with this latest version, maybe over this long weekend and get back.
  12. Late reply on this one, but I went with the super long Cat5e cable (for $17. Thank you, Amazon) for making the connection. Much easier, cheaper, and more reliable for 2 weeks of use.
  13. For the first time in 3 years of using Unraid I need to use wifi to connect my server to my router. I am relocating, staying in an AirBNB for 2 weeks and would need to run a 200ft cable across the house to make the connection. I bought a mobo with a wifi card a while back just in case I ran into this exact use case; however, I didn't know about the Unraid limitation. @johnnie.black - Thank you for the heads-up on this. I was searching around, worried that my motherboard wireless just wasn't supported by Linux-- its an MSI X470 Gaming M7 AC. However, sounds like from this that Unraid has no drivers or capabilities to support a wireless card. For morbid curiosity - if I did want to get dirty and install iwconfig, drivers, etc. to try to use bond0 with the wireless card... Would that even be an option? It would be less headache to just buy the 200ft ethernet cable and have it running down the stairs than to try that, I have a feeling. Thank you!
  14. Sounds like a pretty classic use case--and a good idea to have an off-site backup. I have been using Duplicati to do my backup to the cloud. You should be able to work it by hosting maybe an FTP server on both ends. It allows you to upload multiple chunks, do incremental backups, and encrypt so your buddy can't see your files. I use the Community App for it:
  15. Welcome! I do think Unraid is a great use case for you... @Bruce11 - Best advice is from @primeval_god below: Knowing basic Linux commands like ls, cd, cp, rm is super helpful. Know how to SSH into the server. And learn to use Docker. The Unraid Web GUI interface can do 90% of it without a problem, but you will eventually run into the need to do 10% using the terminal. And eventually you will likely want to do more through the terminal. @JustusAurelius - I have the AMD 2700x for my build, and I love it (you can read about my server on my blog). I think it pairs very well with Unraid. At this moment, though, you will get better bang for your buck with the newer 3000 line of processes. The 2700x gives you 8 cores (for 16 threads). For your use case, buy plenty of RAM, at least 32 GB, depending on the gameserver requirements. I use all of the examples you have above, and you should be able to run them just fine. My server runs 24x7, and I connect to it from external all the time via a VPN I set up. Example breakdown: * I use a Windows 10 VM on Unraid as my primary gaming machine, pass-through a Nvida 1070 graphics card. I dedicate 6 threads and 16 GB RAM here. * Game servers can be hosted on Docker using the Unraid App, or each their own Linux VM. Dedicate maybe 2 threads and maybe 2-4 GB RAM each (depending). * Nextcloud I have running in a Docker container and it takes up almost no CPU or RAM power. * NAS file share is a breeze, but this is the bread-and-butter of Unraid What do you think? Would love to hear how it goes!
  16. Thank you , @ZooMass and @qwijibo for trying that latest AGESA. It's disheartening it didn't work. It sounds like, though, from the post below that it might ALSO require an updated Linux kernel. I believe Unraid is working on this for the next version, but I am not sure when that will be released. @Leoyzen - When you upgraded the Linux Kernel for the fix, did you also have the latest AGESA BIOS for that x570? Quite a few people on this thread are battling with the issues.
  17. Along with what @boris said above... It looks like this issue has been fixed! Got this message from AMD Tech Support: I have no clue when it is going to roll out, or even what the heck a A1003 ABB version is, but it should be coming down the pipe sometime! Edit - * looks like it's already available for you ASUS folks! https://rog.asus.com/forum/showthread.php?112403-Agesa-1-0-0-3-abb * and you ASROCK folks - https://www.asrock.com/support/index.asp?cat=BIOS * and Gigabyte - https://hardforum.com/threads/agesa-1-0-0-3-abb.1984916/ * where is MSI?? Anyone willing to give it a shot and report back??
  18. @AGoulimis, I am not familiar with this error and doubt it's specific to this pass-through issue; however, it may help someone! And 3 screens, nice! The one thing I can comment on - I do think it's reasonable to see the GPU on a different hostdev slot. Those BIOS updates changed the CPU pinning for me, so it could have impacts on how devices are assigned, especially as they pass-through to the VM.
  19. @Brucej32 - You should be good with the x370 and Ryzen 1700 if you downgrade the BIOS like @xsinmyeyes said, but if you're considering investing in a new 3000 series AMD Ryzen CPU... You won't be able to do the pass-through yet... This would be amazing, @boris! I am a bit skeptical for a few reasons... Mostly because I cannot find a changelog for this update- apparently the AGESA number system is really inconsistent(??). So, I have questions like: How long will it take to roll out to all motherboards? Will it cover all motherboards? etc. But it is hopeful. If you get a chance to try it, would love to see if it allows pass-through to work!
  20. That's great to hear! Thanks for the info, @GHunter. Although, it appears this issue is specific to the AGESA BIOS for AMD motherboards. And a BIOS fix may be the only way to get the GPU pass-through working again... Should this issue be closed, if that's the case?
  21. Wow, @SpaceInvaderOne has such a big following... This error is coming out of the wood works when he posts. If you read this SpaceIO, this thread documents a bunch of cases when it happens, too.
  22. I think both of you are spot-on here. Downgrading the mobo BIOS brings back pass-thru functionality, but I do think it will NOT WORK with the new Ryzen 3 line of processors... Someone added a post to the AMD forum, and I added this thread as a comment on it: https://community.amd.com/message/2921732
  23. Have a thread going with 13 reports of AMD motherboards that, after upgrade to the latest BIOS, get the following error for Windows 10 VMs with GPU pass-through: vfio: Unable to power on device, stuck in D3 It affects the x300, X400, and the new X570 series mobos. This has been an issue since March 2019 when AMD motherboard manufacturers began preparing for the AMD 3000 CPUs. In the thread, I noted during some early research that the same issue plagued the AMD TheadRipper on x399 motherboards back in 2018(??), and I think the final solution came in the form of a Linux Kernel upgrade. This is my first report. Let me know if I need to change anything, or if it's not applicable here. Thank you!
  24. @widdefmh If it's worth anything, I think you did the right thing by upgrading your mobo BIOS before you installed Unraid. It is unfortunate you ran into this issue. Sounds like you tried several things with no success--that's about right. I also tried 2 GPUs and was unsuccessful. You can still downgrade to fix this: use the Asus downgrade utility Afuefix64 from overclock.net. No one has posted about the ROG STRIX B350, so I am not sure what BIOS you should use. Check for one back before March 2019 (check the change log and choose one before they introduced the Ryzen 3000 upgrade).