Hardware transcoding not working under Debian Linux

Plex Media Server Desktops & Laptops
21 
Hardware-Accelerated Streaming on Linux requires:

64-bit Ubuntu (16.04 or later) or 64-bit Fedora (26 or later) distributions. (Other distributions may be capable, but are not officially supported.)
If your Linux computer also has a dedicated graphics card, the video encoding acceleration of Intel Quick Sync Video may become unavailable when the GPU is in use. If your computer has an NVIDIA GPU, please install the latest Latest NVIDIA drivers for Linux to make sure that Plex can use your NVIDIA graphics card for video encoding (only) when Intel Quick Sync Video becomes unavailable.

Ubuntu and Fedora - Officially supported.
Other distributions may be capable, but are not officially supported.)

22

why isn’t Debian officially supported? i mean its sooo near on Ubuntu…

23

If you want this to work better, I recommend trying the new packaging I’ve written.

I did a complete overhaul of all this.

  1. It is udev independent. It uses the group as primary but will change perms to rw with udev
  2. It won’t break an existing installation.
  3. It reports everything it finds during preinst phase.
  4. It tells you what it found and how it configured (it adapts to your site config)
24

Regrading Debian being Officially Supported, I can say this:

The new packaging, when complete and mainstream, will make a number of Linux distributions officially supportable.

The only time required will be for myself to go through and regression test each distro, determine a baseline minimum in a VM.

25

Sounds promising. Does this affect how you install updates to the PMS as well? Would love to have some kind of automatic update process that I don’t have to manually trigger.

26

I rewrote the package’s internal routines preinst, postinst, prerm, postrm

preinst - is the validation and data gathering component. It gathers all the info it can find and checks for basic access permissions and functionality. The purpose is to prevent, if possible, getting an installation which fails to start after upgrade. I can’t control PMS itself but I can validate the operational environment (e.g. does the username exist, etc, etc). All this is passive. Nothing is touched until the end. At the end, if still valid, shutdown PMS if running for the actual installation. It then transfers all the info it has collected to postinst

postinst - performs the actual installation. It uses all the information passed to it. It still does a lot of validation and making linkages as needed because it must also handle first-time installations.

prerm - does a graceful shutdown of PMS if running

postrm - if remove was specified, the auto-start linkages are removed (disabled), If purge was specified, it does a proper purge, including removal of the config files and metadata. After a purge, the installation will be “fresh”. It’s a “get out of jail quickly” card :slight_smile:

With it this way, you can now safely setup a cron job or any other automated means to query /
update plex because you know it won’t try to install and fail part way through only to leave you with a broken installation.

As an added feature, I’ve added system log auditting. You’ll see what happens in the syslog. This way you know

27

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.