Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

CodingMicrobe

Members
  • Joined

  • Last visited

Everything posted by CodingMicrobe

  1. @bigbangus wondering if you've had any progress on this issue? I upgrades from 6.9.2 to 6.10-rc3 yesterday and while everything else works fine, suddenly my GTX 760 GPU which is being used for my Windows 10 VM is throwing error 43, and VM is stuck at 800x600 resolution. I tried reinstalling Nvidia drivers (v470), which now officially support virtualization, without any success. Also made a brand new Windows 10 VM, same issue.
  2. Yeah. That’s what I had working (with monitor connected to my system with only APU graphics, no other GPU), even in a VM, until I installed AMD drivers then it broke partially. good luck with testing Parsec, just keep in mind you may not get true graphics acceleration.
  3. Interesting because I have tried that version I posted several times and no success once drivers are installed. Can you text with a monitor? I feel like you are in the same situation we are in, but the issue is masked by the fact you’re running it headless.
  4. Hi, could you please share your XML and what changes were required in Unraid, beyond ACS override, efifb, VFIO. Also does the VM still work with AMD drivers installed? the issues we were having was with display output, since once you connect via RDP/parsec windows may use the generic drivers and not AMD. worth testing with a monitor if possible.
  5. I have given up for now since it really does seem like something is wrong upon installing the AMD drivers and that is beyond me on how to fix.
  6. I have tried with Ubuntu 20.04.2 and 20.10, but couldn't get either to work, even after enabling the amdgpu.exp_hw_support=1 flag in the kernel & updating krub accordingly... Similar issue with Manjaro XFCE 20.2.1. I have not tried Linux Mint.
  7. I have narrowed it down to AMD drivers which are automatically installed by Windows Update. I can "Pause Updates for 7 days" in W10, but that's like putting a bandage on a bleeding wound, doesn't do much long-term. I am looking into why this may be occurring, however also came across these posts on Reddit where people point out that it may be a driver version issue, since AMD may be detecting VMs and not allowing us to run the driver properly. For what it's worth, the mouse usually works fine and I can move it around and see it on my display, everything 'behind' the mouse (the entire W10 UI) is that garbled pixelated mess though.
  8. UPDATE: got it working very well on Unraid! Very easy to setup once I knew what to look for and the little 'tricks' to be careful for. Just playing around with it a bit further to ensure it's stable, but I will be very happy to share a guide shortly! Do you think I should make a post of its own for that? EDIT: Well, it was working before this happened and persisted after a reboot. No idea what changed unless Windows tried to pull drivers in the background which messed things up?
  9. I got iGPU passthrough (with audio over HDMI as well, did not test display port yet) working in a Proxmox Windows 10 VM! Seems to be limited to ~30hz refresh rate but I am investigating if AMD driver updates will fix the issue. I will test on Unraid in the coming days once I am happy with the Proxmox install. But briefly, what was key was passing the VBIOS file (latest version works fine, see file Renoir-017.010.000.028.000000.ROM from previous post), AND using a q35 machine (not default i440fx) with SeaBIOS (NOT OVMF). I will try to get it working on Unraid soon and make a guide, but will also make a guide for Proxmox for those who use PVE. Cheers!
  10. Thank you for trying and reporting back. My APU arrives tomorrow so we will see how that goes!
  11. Once my APU arrives, I'll be trying with Proxmox which also uses KVM, just like Unraid. I am hopeful I can get it to work there, and if so, I'll definitely port it over to Unraid. Might take a couple weeks though.
  12. Hello, I had more discussion with other users from other forums and the version of VBIOS (or from which motherboard it came) shouldn't matter. These are the 3 versions I have extracted, 017.010.000.015, 017.010.000.026, 017.010.000.028. Same as I posted above just renamed properly for their versions. Renoir-017.010.000.015.000000.ROM Renoir-017.010.000.026.000000.ROM Renoir-017.010.000.028.000000.ROM
  13. I believe once you set it for a VM, you cannot easily change it (for Windows VM at least, not sure about other distros of Linux). There is a way to change SeaBIOS to OVMF, but the opposite is much more difficult/impossible - and I think you would just need to make a new VM, at least for testing purposes now.
  14. Might be worth trying to run these commands on the Unraid server immediately upon bootup (via SSH! or userscripts plugin), and THEN starting the VM via web UI from another computer. Very important not to use unraid GUI mode or text mode at all. echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind Also are you running the VM with SeaBIOS or OVMF? I think SeaBIOS is preferred for this type of pass-through, since the VBIOSs provided by AMD don't support UEFI firmware (which is what OVMF is).
  15. Good point, I will try to make a guide within a few days!
  16. That’s promising that windows device manager can see it! Do you get any VGA/HDMI/DP output when you connect directly to motherboard (not VNC/RDP)? What error does windows give you?
  17. Here is the VBIOS extracted from BIOS version 1401 for the ASUS PRIME A520M-K, it is slightly newer than the one I posted above. The one I posted was compiled by AMD March 10 2020, this one was compiled August 25 2020). Hopefully it improves things, because taking the server out of the rack is a hassle I agree... I also attached the *latest* VBIOS (compiled by AMD on November 13 2020), from BIOS version 1804. I haven't found any more recent VBIOS yet. For others who come across this post, I named VBIOS files with the motherboard BIOS&version I extracted them from, but in theory they are universal for all Renoir APUs. So far I have extracted 3 Renoir APU VBIOSs, compiled/released by AMD on these dates: March 10 2020 (from ASRock DeskMini X300, BIOS v1.40; attached above in my other post) August 25 2020 (from ASUS A520MK, BIOS v1401; also found in ASTock B550M-ITX/ac, BIOS v1.50; attached here) November 13 2020 (from ASUS A520MK, BIOS v1804; attached here) A520MK-1401-RenoirVBIOS.ROM A520MK-1804-RenoirVBIOS.ROM
  18. @DrMucki also why use Splashtop? Can you try just plugging in an HDMI/VGA/DP cable directly to your motherboard to see if you get output from iGPU Windows VM - without Splashtop at all? That can help narrow down if the issue is with Splashtop & AMD iGPUs, or with the passthrough itself.
  19. So it sounds like you got it working, but it was very very poor performance, with poor resolution and lag on keyboard/mouse inputs? What specific motherboard & BIOS version do you have? I can extract the VBIOS from that version of the BIOS for you. Maybe there is a newer version.
  20. Hi, Attached is the Renoir VBIOS I extracted from the ASRock DeskMini X300 BIOS file. I am still waiting on my APU to arrive so can't test it yet, but @TGP seems to get an error when using it about failing to allocate BAR space (I attached their error they PM'ed me below). They said they were using ACS override patch to make the iGPU in its own IOMMU group, but I wonder if this may be the cause of their issue. Also came across this post where someone has the same error and resolves it, may be worth looking into (see link below). Let me know how this VBIOS works! I'd love to get this working with a Windows VM eventually like you! Cheers. 2021-03-07T10:19:06.269103Z qemu-system-x86_64: -device vfio-pci,host=0000:0c:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/cache/Public/ISO/RenoirVBIOS.rom: Failed to mmap 0000:0c:00.0 BAR 0. Performance may be slow RenoirVBIOS.rom
  21. Have you checked this post out? That message (type 127) seems to be an AMD thing when the GPU can't reset properly: https://forums.unraid.net/topic/76510-execution-error-internal-error-unknown-pci-header-type-127/ EDIT: it may be possible to extract iGPU VBIOS with UEFITool, but I believe this is Windows-only (unsure, just found this online), see https://github.com/LongSoft/UEFITool/issues/26 EDIT2: I think I got the Renoir APU VBIOS, I will PM you and if it works, I'll make it public.
  22. I am about to purchase a Renoir APU (4650G or 4750G) and would also like to pass through the iGPU to a VM, either via unraid or Proxmox VE. Unfortunately I haven't seen anyone do it successfully yet throughout all my research, and if they do get it, it seems to be "unstable", but they don't describe any errors...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.