does work only for you if parsec is installed? because for me the display works fine until windows enables the amd graphics driver and then it all goes to garbled crap. if i disable to amd driver the display comes back but i have only 800x600 resolution.
GMKTEC K12 | Ryzen 7 H 255 | Problem with IGPU
- Thread starter Glupikocz
- Start date
-
- Tags
- 780m igpu passthrough proxmox
I did this: I installed the latest Proxmox and did all the updates, and then I immediately started entering commands from: https://pve.proxmox.com/wiki/PCI_Passthrough
That is
next:
next:
And this github: https://github.com/isc30/ryzen-gpu-passthrough-proxmox
And its all, all working fine
That is
dmesg | grep -e DMAR -e IOMMUdmesg | grep 'remapping'echo "options vfio_iommu_type1 allow_unsafe_interrupts=1" > /etc/modprobe.d/iommu_unsafe_interrupts.confnext:
Code:
echo "blacklist amdgpu" >> /etc/modprobe.d/blacklist.conf
echo "blacklist radeon" >> /etc/modprobe.d/blacklist.conf
Code:
echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf
echo "blacklist nvidia*" >> /etc/modprobe.d/blacklist.confecho "blacklist i915" >> /etc/modprobe.d/blacklist.confnext:
echo "options kvm ignore_msrs=1 report_ignored_msrs=0" > /etc/modprobe.d/kvm.confAnd this github: https://github.com/isc30/ryzen-gpu-passthrough-proxmox
lspci -nn | grep -e 'AMD/ATI'
Code:
sed -i 's/GRUB_CMDLINE_LINUX_DEFAULT="quiet"/GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt"/g' /etc/default/grub
update-grub
Code:
echo "vfio" >> /etc/modules
echo "vfio_iommu_type1" >> /etc/modules
echo "vfio_pci" >> /etc/modules
echo "vfio_virqfd" >> /etc/modulesecho "options vfio-pci ids=1002:1900,1002:1640" >> /etc/modprobe.d/vfio.conf
Code:
echo "softdep radeon pre: vfio-pci" >> /etc/modprobe.d/vfio.conf
echo "softdep amdgpu pre: vfio-pci" >> /etc/modprobe.d/vfio.conf
echo "softdep snd_hda_intel pre: vfio-pci" >> /etc/modprobe.d/vfio.conf
Code:
update-initramfs -u -k all
shutdown -r nowAnd its all, all working fine
Unfortunately, I don't know, because I've always used Parsec, but as far as I know, you can upload Virtual Display without Parsec. It's available anyway; it used to work for me on GMKTEC M5PRO before I started using Parsec or Moonlight.
https://github.com/VirtualDrivers/Virtual-Display-Driver
Maybe u have discord?
the bios has been flashed like an hour ago.
i freshly extracted vbios and gop and i reinstalled the drivers. it always ends up the same. if driver active, display is garbled (can still access and use gpu fine via anydesk), if inactive, display is on and shows stuff in 800x600, but obviously no gpu is available.
i freshly extracted vbios and gop and i reinstalled the drivers. it always ends up the same. if driver active, display is garbled (can still access and use gpu fine via anydesk), if inactive, display is on and shows stuff in 800x600, but obviously no gpu is available.
i will now try and see what happens if i pass the gpu to an ubuntu machine and see if that one works as intended.
i passed it through to a different windows 11 vm and there it seems to be actually working.
now i need to figure out why the other vm doesnt behave the same.
now i need to figure out why the other vm doesnt behave the same.
i have given up on the original vm and moved everthing to the new windows vm.
its working well, except that if i restart the actual vm inside proxmox it has issues with the graphics afterwards. its only partially working (like half the screen visible, the other half flickering/garbled).
i assume thats because of vendor-reset not fully supporting the gpu.
only a complete host-reboot (gracefully) will restore the gpu to 100%.
luckily it doesnt lock up the host at all, just the gpu wont be fully functional until host reboot.
if i just restart windows inside the vm its not an issue. i can do that as much as i need and it keeps working. so windows update and other windows related reboots wont break anything.
i dont restart the vm from proxmox usually, so that shouldnt be a big issue for me.
its working well, except that if i restart the actual vm inside proxmox it has issues with the graphics afterwards. its only partially working (like half the screen visible, the other half flickering/garbled).
i assume thats because of vendor-reset not fully supporting the gpu.
only a complete host-reboot (gracefully) will restore the gpu to 100%.
luckily it doesnt lock up the host at all, just the gpu wont be fully functional until host reboot.
if i just restart windows inside the vm its not an issue. i can do that as much as i need and it keeps working. so windows update and other windows related reboots wont break anything.
i dont restart the vm from proxmox usually, so that shouldnt be a big issue for me.
other than the gpu crapping out when i reboot the machine via proxmox (see above) everything is running fine.
vendor-reset is an old (no longer maintained) tool and doesnt fully support the igpu, but works well enough.
as long as i initiate reboots within the vm all is good. thats most important since it covers all windows update reboots.
vendor-reset is an old (no longer maintained) tool and doesnt fully support the igpu, but works well enough.
as long as i initiate reboots within the vm all is good. thats most important since it covers all windows update reboots.