Well done! Unfortunately, the latest PMS release doesn’t resolve my issue and am still in the same predicament on Slackware -current. (Living with unresolved issues is a way of life on unsupported distros.)
As of now, I don’t see any security notes in the changelogs from 1.22.x to 1.23.x, so I’m content to see if a fix comes about. Is this correct?
In this case I’m using the latest version; having tried both the latest “production” 480.x and “features” 485.x. Perhaps the next update will be the ringer.
As stated earlier in the thread, hardware transcoding works just as expected with both of these newest drivers, as long as I use PMS version 1.22.3.4523-d0ce30438. So far, each release of 1.23.x has not worked with hardware transcoding. I know this both from the dashboard and via the nvidia-smi tools, (plus, good old physical check – no fans).
This may or may not be relevant or related, but I’m running Plex server Version 1.24.1.4931 on Ubuntu 20.04 with Nvidia 460.91.03 drivers, and hardware transcoding with my GTX 1080 started failing a week or so ago.
I also have Docker installed, and had just set up Tdarr in Docker, and installed nvidia-container-toolkit 1.5.1-1, libnvidia-container-tools 1.4.0-1, libnvidia-container1:amd64 1.4.0-1, and nvidia-container-runtime 3.5.0-1.
On a hunch I removed those packages and automagicly hardware transcoding worked again.
This may be a new Plex issue, existing, or Nvidia’s screw up. I don’t know, but this may spring up for other folks. Happy to supply additional info if needed.