Search results

Thanks. Yes, 5.4 works as well if you enable the additional flag for AMD GPU's. I've got Jellyfin working and am working on Frigate. It seems very closely linked with mesa and libva drivers.

I got it working in a Jellyfin container with the ANMD mod configured so I guess its related entirely to what is in the docker image rather than libraries installed on the proxmox host or lxc container.

Thanks for this. I have exactly the same setup as you (ASRock X300 & 4650G) and am trying to get VAAPI working with Frigate. I've upgraded to kernel 5.11 and installed the packages above. I can see amdgpu is loading the IGPU and /dev/dri is populated but VAAPI always fails ("Failed to initialise...

@j1a2o @thex I have a 4650g as above with exactly the same problem. Did you make any progress with this? I've found some different information in other places, specifically that AMD's drivers are needed. I tried to install the latest AMD drivers but the DKMS build fails on kernel 5.11 and the...

Managed to somehow get this working by loading an application that needs the TPU. This must trigger the library and the udev rule kicks in. Then you need to pass the new device also to the LXC container. I'm not sure how this will work after a reboot but I'll give it a try.

Hi, I've built an ASRock X300 with AMD 4650g processor to run a couple of small VM's including Home Assistant and also Frigate (hence the need for the Coral USB). I've installed the latest Proxmox and gotten everything up and running except the Coral USB seems to be not identifying. lsusb...

@avw I restored the BIOS to the previous working version. Will try again when I am more prepared.

@Joris L. I removed all the boot parameters and also restored the BIOS to default settings. It still hung even with VFIO disabled. I also confirmed the root partition and other local partitions were all mounted fine. The only thing I didn't do was regenerate the initramfs but I ran out of time...

@avw what were the symptoms of your issue? Could you boot? Did you try to reinstall? I'm not sure I can revert as I remember MSI or AMD had blocked BIOS downgrading but I'll have to recheck.

I'm guessing the PCI IDs and the network device has changed also. I am not sure though because I can't get to a terminal. When I had vfio.conf in place, it hung on that exact line every time. Once removed, it hangs at different stages, usually when the pve services/daemons are starting...

Hi, In order to try to get better results with GPU pass through, I upgraded the BIOS on my MSI B450M Mortar. That started the nightmare. Since then, I've been unable to boot into Proxmox. I'm running latest Proxmox 6.2 (non subscription). Initially, I tried rescue boot from the install iso...

@Joris L. Did the BIOS upgrade and now unable to boot Proxmox. I'm getting the following error and boot is hanging: vfio-pci 0000:26:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem I re-enabled SVM and IOMMU in the BIOS but no luck. I tried a rescue boot from the...

You guessed correctly :)

I'll give it a try as soon as I get a moment and report back. Thanks.

OK, so firstly, to be 100% sure, if I run the above script, I need to do so after shutting down the VM with the AMD GPU passed through. And when I do run it, it will put the whole PC to sleep so any other running VM's will also be suspended? I am not sure on this last part. And then also, this...

Thanks for this. When should this be run? When the VM is shut down? If it suspends the host then other VM's will also be suspended?

Hi, I have a Ryzen 2700 system with both an RX580 and NVidia 1050ti passed through to separate VM's. I was having issues when VM's were stopped or rebooted within the VM. I found this script online and set a cron for it to run on every reboot: echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0...

Thanks for the reply. I ended up using dd to get a raw image of the VM disks I wanted to restore and then re-initialized the drives in Proxmox and imported the images back in.

I have some more data. root@pve:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─ssd2-ssd2_tmeta 253:11 0 4.7G 0 lvm │ └─ssd2-ssd2-tpool 253:13 0 456.3G 0 lvm │ ├─ssd2-ssd2...

I can see when I boot that Proxmox sees the other disks and they're listed on the web admin panel (in LVM and LVM Thin). However, in the left navigation I can only see local and local-lvm but not my two extra disks (called shared and ssd2). I added a dummy VM and did a 'qm rescan' as you...