Recent content by paulmorabi

  1. [SOLVED] Coral USB device, udev rules not correctly identifying

    I used Frigate and ran it in a LXC container via docker. Make sure to pass through the right devices also.
  2. AMD Ryzen 7 "Renoir" 4750G APU and iGPU pass-thru (to Windows 10 guest)?

    Thanks for this. Do you know what the idmap does? There's also been some progress in this thread here. I've got it working also with latest mesa libraries and a few other tweaks. These may be useful for you. No 10 bit transcoding yet though.
  3. proxmox 7.1, unable to access render128 in lxc with vainfo

    Yeah, fingers crossed it gets better over time. I've done quite a bit more testing and I've noticed a few things: * The SMU driver is really important. Without this, the iGPU crashes regardless of mesa versions. I've seen the odd page fault in dmesg but no crashing. Hopefully this makes it into...
  4. proxmox 7.1, unable to access render128 in lxc with vainfo

    Thanks for this. I installed both and you are correct, this makes the transcoding much more stable. I got one "retry page fault" in dmesg that recovered itself whereas previously a reboot would have been required. I enabled 10bit and it throws an ffmpeg error on a 4k file. Thanks so much for...
  5. proxmox 7.1, unable to access render128 in lxc with vainfo

    I tried the mesa libraries from the repo you listed above and transcoding worked for a while before crashing: [4264928.290153] amdgpu 0000:03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32770, for process ffmpeg pid 2319355 thread ffmpeg:cs0 pid 2319356)...
  6. proxmox 7.1, unable to access render128 in lxc with vainfo

    What is the SMU stuff? Did you add this to the host or to the container?
  7. proxmox 7.1, unable to access render128 in lxc with vainfo

    Awesome! Congratulations! So, just to confirm, what packages did you install from the ppa:oibaf/graphics-drivers repo? And you did this with an lxc/d container? I will give this a try also!
  8. proxmox 7.1, unable to access render128 in lxc with vainfo

    No worries, I know what it's like to debug this. So, first thing is I'm using Proxmox 7.1 with a 4650G so the generation and models of our AMD processors are different. I do get stable video stream decoding running Frigate in LXC. With Jellyfin, using the latest mesa libraries, I get an error...
  9. proxmox 7.1, unable to access render128 in lxc with vainfo

    so you’re using an image of the full distro with Xorg? Or using the base OS image and then jellyfin via container or running ffmpeg directly? What is your CPU? Have you tried the latest mesa from here? These don’t work for me but they also don’t crash the system or cause errors in dmesg.
  10. proxmox 7.1, unable to access render128 in lxc with vainfo

    What jellyfin container image are you using? Via docker or lxc/d? What CPU/iGPU are you using? Did the crashing happen transcoding the same files as the day previously when it worked? (it wouldn’t be unheard of for transcoding to fail on some codecs/nitrates and work on others).
  11. [SOLVED] Coral USB device, udev rules not correctly identifying

    Yep I did manage to get it working. What are you passing through to the container? It should be the devices that map to the Genesys Logic and also the Google Inc. device.
  12. proxmox 7.1, unable to access render128 in lxc with vainfo

    Maybe you’re onto something with this. Did you use Ubuntu via container or VM? I’m not surprised different versions of ffmpeg would give different results as they are all complied/built with different options and support library versions. However, if it doesn’t work and then works, it’s very...
  13. proxmox 7.1, unable to access render128 in lxc with vainfo

    Have you tried to get another app/container working with the passed through GPU? I managed to get it working with frigate so i know its something specific to jellyfin and/or the libraries in the container. Failing that, you could also install docker on the host and try that way. The latter is...
  14. proxmox 7.1, unable to access render128 in lxc with vainfo

    I suspected similar but in my case, it didn’t make a difference that I could see. The hardware is being passed through to the container so the mesa libraries in the container should be accessing it directly rather than via the host. I guess its possible the host‘s kernel/mesa is doing something...
  15. proxmox 7.1, unable to access render128 in lxc with vainfo

    Let me know how you go with that. Also did you try with a container other than Jellyfin? Because it works for me with frigate.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!