@ChuckPa Sorry, troubleshooting went late into the night and i passed out while it was installing. I’m happy to report that natively it wokrs as epxected, i’m transcoding a 4k stream with it barely affecting my CPU. So thats great! I would like to get it going in Docker eventually but I think i might take a break after bashing my head against this all weekend. Thanks so much for your help!
@Menel Taking a look at your compose, here is mine:
Setting network mode to host will vastly simplify remote connecting to the Plex server. If you’re on a standard Ubuntu install this compose should even automatically set to transcode on RAM as it should be.
Just change your paths for the /config and the actual media folders. Also obviously change your TZ to yours, and add the Claim token (and change PUID and PGID if you’ve a different user setup in Ubuntu)
OK, so for me, PLEX transcode still does not work, no matter if in docker or directly on system, plex have rights to access /dev/dri, system recognizes GPU correctly
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.20 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.1.0 ()
and a lot of profiles
and here is LSPCI
bckp@friday:/$ lspci
00:00.0 Host bridge: Intel Corporation Device a71b (rev 01)
00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-U [Intel Graphics] (rev 04)
00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant (rev 01)
00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 01)
00:06.2 PCI bridge: Intel Corporation Device a73d (rev 01)
00:07.0 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 01)
00:07.2 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port #2 (rev 01)
00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 01)
00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog and Telemetry (rev 01)
00:0d.0 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller (rev 01)
00:0d.2 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #0 (rev 01)
00:0d.3 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #1 (rev 01)
00:12.0 Serial controller: Intel Corporation Alder Lake-P Integrated Sensor Hub (rev 01)
00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01)
00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01)
00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01)
00:17.0 SATA controller: Intel Corporation Alder Lake-P SATA AHCI Controller (rev 01)
00:1d.0 PCI bridge: Intel Corporation Alder Lake PCI Express Root Port #9 (rev 01)
00:1f.0 ISA bridge: Intel Corporation Raptor Lake LPC/eSPI Controller (rev 01)
00:1f.3 Multimedia audio controller: Intel Corporation Raptor Lake-P/U/H cAVS (rev 01)
00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01)
00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01)
02:00.0 Non-Volatile memory controller: Phison Electronics Corporation PS5013-E13 PCIe3 NVMe Controller (DRAM-less) (rev 01)
57:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
Interesting is, Jellyfin in docker succesfully engage HW transcoder (seen in gputop)
We are still using FFMPEG 4.4 (from previous team)
We are, with the current team, upgrading FFMPEG to 6.1
I know you’re all anxious. We’re making what we have work the best it can.
This is a big upgrade. FFMPEG is one thing, All the Plex additives to FFMPEG are what take time.
It was more informative, we spoke here 24.04.1 will solve some issues, so just inform it did not i did not know about ffmpeg versions, good to know, i will wait, no rush needed.
Plex is awesome, only thing is, my kids time to time hit download button and that make my nas hurts, it has passive cooled ryzen 1600, it hits 80 degs instantly
RAID resync is always fun, last time i have faulty WD drive, replaced it with another one, run resync for 33 hours, and when it finished, another WD drive failed…
it will also fluctuate based on video load at that part (the contents) of the video stream. More CGI in the video means more sharp edges which cause more abrupt color changes.
I am experiencing the same issue with passing though a UHD 630 iGPU to Ubuntu. 22.04 is fine but with 24.04 intel_gpu_top just shows 100% usage while nothing seems to be getting done. I see the same dmesg messages as you too.
I’m not seeing any usage in intel_gpu_top under 24.04.1. When I do a clean install of 24.04.1 it works, but not when I execute a do-release-upgrade from 22.04.4 to 24.04.1. I don’t really want to start from scratch with my Ubuntu VM.
I tried a clean install and same issue. I’m running in a VM with the GPU passed though. (XCP-NG) Jellyfin also has the same issue so i’m thinking its something specific with 24.04. 22.04 is totally fine with both however.
I’ve been reading some of the advice here for a while and decided to rebuild my head server to remove an excess layer of virtualization by switching from Ubuntu 24.04.1 VM → docker to just a dedicated LXC for Plex built from tteck’s script.
Unfortunately, Plex is not doing any HW transcoding for me I’m on a Beelink SEI12 running an Intel i5-12450H with Proxmox 8.2.4. I’m running the current PlexPass version 1.41.0.8930 and the LXC container is running on 22.04.4 LTS. I did a test run lowering the quality and saw the following errors:
lol
)
i did not know about ffmpeg versions, good to know, i will wait, no rush needed.
