Search results for query: vendor-reset

...- it now transcodes perfectly with great performance. The "Reset Bug" seems fairly similar to our issue: https://github.com/gnif/vendor-reset/issues/66 (archive.org link, as script is nla: https://web.archive.org/web/20250207151440/http://www.alexforencich.com/wiki/en/pcie/hot-reset-linux)...

Solved. Radeon RX 7xxx Series is unsupported by Proxmox forever because the GPUs don't restart correctly with the Virtual Machines. It appears only the 7000s have this issue. The 6000s and 9000s "can" work with significant technical capability of the owner, but some reports find the builds are...

Well, it's not so rosy, but now I'm wondering why. You see, I discovered that on one random 256GB drive in one PCIe slot, everything worked fine for about two weeks, but I decided it was time to switch to a ZFS1 RAID with two 4TB WD Red drives, and after that, it stopped working. And now I'm...

where are you finding the latest bioses for K12 ?

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...

...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...

I started using Proxmox some days ago and put a considerable amount of hours into trying to get my Intel A310 GPU to work properly for passthrough to a VM, or, to be more precise: to hand it back to the system after the VM is shutdown. I am a Linux novice as well but learned a lot these past...

never mind fixed it by compiling https://github.com/piotrminkina/vendor-reset/tree/issue/kernel-6.12.x-build And adding my gpu id the xxxx:xxxx to the device table. then setting the reset method from bus to device-specific (this has to be done every time i start the vm so i just made a...

vendor-reset is the name of a project to fix FLR for AMD GPUs and not an issue. Maybe the system logs will show signs of not properly resetting, but your system crashes and might not write the logs to disk. Your GPU is know to potentially have reset problem. vendor-reset does not work for your...

Do the kernel dmesg logs show whether or not it is a vendor-reset issue? The reason I am asking this is because the dmesg log specifically states that the vendor-reset executes perfectly fine, doesn't seem to error out at all. The thing that is really standing out to me is the CPU softlock...

...and connected to the real PCIe bus, this can cause problems in the Proxmox host as well. People have had problems like this before. Maybe you can find a work-around for your type of GPU (like vendor-reset for older GPUs) on the internet? Or maybe you need a different GPU or learn to live...

Hello all, I'm having some problems while trying to passthrough the GPU to a VM, here is my IOMMU configuration and lspci, the GPU itself is the Reaper AMD Radeon™ RX 9060 XT 16GB: IOMMU: IOMMU Group 83: 03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL...

@uzumo I looked into using vendor reset when I made the original post but the github readme did not list the W7600 as a compatible card so I decided not to try it. @Sviat You are right, it was the driver in the linux VM. The amdgpu driver in Debian 13 was the issue. Thinking Debian 13 was...

Finally success here as well.. I messed up and needed to do a full reset of the bios. With the recovery of the standard values and once more entering the few options it started working. Don't know what bios setting blocked the working, but it solved the [ 21.315157] vfio-pci...

...severely unusable (WebUI also becomes unusable). I have tried researching the issue, and people online mention that it might be a GPU vendor-reset issue, however the dmesg logs don't mention anything about failed vendor-resets, in fact it mentions that the vendor-reset executes fine without...

...will test if this is actually working. Edit for quick update: without doing any troubleshooting at all, all I can say is that the vendor-reset kernel module does not work on my AMD Ryzen 5. lsmod shows the module being loaded, but after a shutdown of my Win11 VM, it doesn't claim the monitor...

vendor-reset has indeed not been updated for recent kernels, but you can fix the source code yourself: https://github.com/gnif/vendor-reset/pull/103 EDIT: A simpler manual fix is also possible as shown in one of the issues/PRs but maybe switching to the branch mentioned above is the easiest?

@jaminmc what kernel / pve are you using? The repo you mentioned fails to compile on most kernel 6.17.2. Is this method of running the vendor reset module the "official" one?

I’m using https://github.com/gnif/vendor-reset/ to achieve perfect resets on my Vega64 and APU in my Ryzen 7 9700x. However, I’m hoping to create a hook script that will return a GPU to amdgpu after the VM is stopped, so I’ll give a similar script a shot.

I don't think setting vendor-reset will have any effect on Navi33 (RDNA3). That generation will likely use a bus reset. * I think it's probably a bus reset for RDNA2 and later. cat "/sys/bus/pci/devices/0000:03:00.0/reset_method" https://github.com/gnif/vendor-reset We'll need to...