Hello @ChuckPa
do you have any ideas on how to proceed with my issue?
I retested on our lab ASUSTOR (AS6102) N5105 CPU with PMS 1.28.0 and it works as it should.
vendor_id : GenuineIntel
cpu family : 6
model : 156
model name : Intel(R) Celeron(R) N5105 @ 2.00GHz
stepping : 0
microcode : 0x2400001f
cpu MHz : 2000.000
cache size : 4096 KB
root@ASUSTOR-AS6102T:/volume1/.@root # uname -a
Linux ASUSTOR-AS6102T 5.13.x #1 SMP Wed Jul 13 00:14:49 CST 2022 x86_64 GNU/Linux
root@ASUSTOR-AS6102T:/volume1/.@root #
There is a known problem with PMS 1.28.1 beta.
Are you using the default 5.13 Linux kernel?
hostnamectl says the following:
Kernel: Linux 5.15.0-46-generic
Should I be on 5.13 @ChuckPa ?
Update:
Downgraded to 5.13.19, still no hw transcoding.
Did you turn off HDR tone mapping ?
The problem shows itself when the tone mapping option is enabled.
You don’t even need HDR content to cause the failure.
I disabled HDR tone mapping, enabled guc as per the recommendation of @Phaellow, still hw transcode does not work.
I might try downgrading to 20.04 because that is what worked for them but I won’t have physical access to the machine again until October so maybe the problem just disappears on its own by then (or someone on this forum conjures up an ssh command that solves it).
Thank you for your help.
1.28.1.6057 is out this morning. Does this version still have the hw transcoding bug or is it ok to upgrade from 1.28.0? I didn’t see any mention of fixed to hw transcoding in the release notes.
Just coming on duty here. Not had time to check it out. I will advise (or you can) 
Typically, keeping the same major & minor (“28.1”) but changing the build (“6057”) indicates a ‘hot fix’.
Transcoding not working would justify a hot fix release like this if the correction was minor enough
I just updated and checked but the bug is still there. No hardware transcoding with 1.28.1.6057. Is the dev team aware of this bug?
yes they are
1 Like
Would you consider giving this a try?
Here is successful PMS 1.28.0 using the same N5105 in a container.
I had already reverted back to 1.28.0 to get hw transcoding working again.
fair enough.
All we can do now is wait.
Engineering was given all the info. We need be patient while they sort it out.
1 Like
I just tested 1.28.1.6092 which was released this morning but the bug persists 
Looking at the release announcement is a duplication of the previous release notes.
Nothing stated about transcoder fixes.
Those are my packaging changes from the initial 1.28.1 release.
Well it looks like 1.28.1 was released to the public which is disappointing that they it broke hw transcoding on linux but they still pushed it out to general availability. 1.28.2 was released this morning but i just tested and it still has the bug breaking hw transcoding. At this point i will be frozen on 1.28.0 as software transcoding 4k HDR brings my system to a crawl.
yep… same boat here stuck on beta 1.28.0
Same here…reverted to 1.28.0 and hw transcoding now works again.
Extremely disappointed that plex publicly released 1.28.1 when they knew it broke core functionality.
Same problem on Intel i3 10100.
This was fixed in a dev build 1.28.3. 1.29.0 beta pushed out today without the fix, what gives?
Dev builds won’t automatically show up in the next formal release.
All you’re seeing is the dev used 1.28.3 as the base.
There is still QA to complete.
I’ve not seen a complete build to QA but do have the 1.28.3 experimental build.
