Same github thread linked above also has a comment stating that they no longer are having the issue with 6.8.10 on Fedora. This kernel (6.8.10-300.fc40.x86_64) is already on fedora 40.
I’d test this myself but I’ve no iGPU so hopefully someone else can confirm one way or another.
Not necessarily.
22.04LTS switched kernel several times.
Went through a major kernel change. If you go download 22.04LTS Desktop right now and install it, comes out of box with 6.5. 22.04 originally shipped with 5.x
Switching to either kernel mentioned in the jellyfin issue does nothing for Ubuntu 24.04 (tried both 6.8.10 and 6.9.1). Same issues are still present, so whatever’s broken isn’t the same in each. I’m using 6.5.11 and it works.
If you are facing the Intel Compute Runtime issue, that’s only going to be fixed when Plex releases a new preview build with the new drivers. Just upgrading the kernel won’t solve that problem.
Just to reiterate, there were 2 issues with 6.8+ kernels:
The 1st one requires new builds from Plex (with the new ICR included) to resolve, whereas the 2nd one can be resolved via a kernel upgrade to 6.8.10 or higher.
Just to be clear, this issue is only present if you have plex installed directly on your Linux system, not in the docker container from Plex or linuxserver.io?
It should be present even in containers since containers also use the host kernel.
Docker does not insulate in any way here.
Further, the PMS executables which you have on the native package are what you have in the docker image as well as the drivers & codecs downloaded from Plex.tv.
If it’s an X86_64 CPU then it gets the same binaries as all other x86_64 CPUs
So I either wait for Unbuntu to update kernel, which there is no info on, or I can update the kernel using a mainline release and lose security updates.
Looks like I am rebuilding my cluster this weekend to 22.04 
Stepping back from the 6.8 kernel to 6.5 cures this for most.
Care must be exercised when doing so because the i915 driver (which has the fault in the drm functions)
also has linkages throughout the host in other packages & services
You must be certain to address them all.
/usr/lib/x86_64-linux-gnu/dri/i915_dri.so
/usr/lib/x86_64-linux-gnu/pkgconfig/i915-perf.pc
/usr/lib/x86_64-linux-gnu/libi915_perf.so
/usr/lib/x86_64-linux-gnu/libi915_perf.so.1
/usr/lib/i386-linux-gnu/dri/i915_dri.so
The upcoming Unraid version 7 will be based on kernel 6.8.10. So no HW HDR tone mapping?
If the Unraid folks have applied the i915 drm patches then you’ll be ok.
Reading from two different sources tells me:
I advise you check with them.
I’m not going to pretend to be near the expert most are on here. I’m a recent PlexPass user. I made the mistake of upgrading Ubuntu which I’m also new to. I’ve always had Jellyfin as a backup to my Plex. What I’m having a hard time understanding is why Jellyfin is able to utilize the intel integrated GPU but Plex is having an issue. Is there something that allows Jellyfin to HW transcode but not Plex? Sorry if it’s a dumb question.
Simply because Jellyfin has already taken the upgraded compute runtime and released a new build with that and Plex has yet to do the same, probably because they were already in the middle of a refactor of their transcoding pipeline when this issue showed up.
I missed this thread before building my new Plex Server on Ubuntu 24.04
Running an intel 13500 cpu and Apple TV 4K V3 clients.
I’m having zero issue with hardware transcoding…
| Distributor ID: | Ubuntu |
|---|---|
| Description: | Ubuntu 24.04 LTS |
| Release: | 24.04 |
| Codename: | noble |
6.8.0-31-generic
PlexMedia Server 1.40.2.8395-c67dce28e
Testing just now using my MacBook Air to force a video transcode
Going to guess you disabled tonemapping, that’s the issue.
Yes, if you disable tone mapping it works. This issue is specifically for HDR content being tone mapped.
You’re transcoding using the iGPU and not a dedicated one? Would be very weird if you are literally the only person who isn’t affected given the devs have already confirmed it’s an issue lol
