After upgrade server,can't use hw trancoding

It works because you already have the codecs.

The new version must download the new codecs.
It can’t download the new codecs because it can’t lookup plex.tv to connect to it.

Have you resolved your networking (DNS) issue?

yes can resolved, also can’t hareware acceleration.

root@debian10:~# nslookup plex.tv
Server:		127.0.0.1
Address:	127.0.0.1#53

Non-authoritative answer:
Name:	plex.tv
Address: 99.81.213.165
Mar 11, 2020 14:59:41.827 [0x7ff6bd7fa700] DEBUG - MDE: Selected protocol hls; container: mpegts
Mar 11, 2020 14:59:41.827 [0x7ff6bd7fa700] DEBUG - MDE: analyzing media item 23451
Mar 11, 2020 14:59:41.827 [0x7ff6bd7fa700] DEBUG - MDE: Jellyfish 20 Mbps Hd: Direct Play is disabled
Mar 11, 2020 14:59:41.827 [0x7ff6bd7fa700] DEBUG - MDE: Jellyfish 20 Mbps Hd: media must be transcoded in order to use the hls protocol
Mar 11, 2020 14:59:41.827 [0x7ff6bd7fa700] DEBUG - MDE: Jellyfish 20 Mbps Hd: no direct play video profile exists for http/mkv/hevc
Mar 11, 2020 14:59:41.827 [0x7ff6bd7fa700] DEBUG - MDE: Jellyfish 20 Mbps Hd: selected media 0 / 23451
Mar 11, 2020 14:59:41.827 [0x7ff6bd7fa700] DEBUG - Streaming Resource: Calculated bandwidth of 41748kbps exceeds bandwidth limit. Changing decision parameters provided by client to fit bandwidth limit of 4000kbps
Mar 11, 2020 14:59:41.827 [0x7ff6bd7fa700] DEBUG - Streaming Resource: Determining preferred transcode encoders through transcode only decision.
Mar 11, 2020 14:59:41.827 [0x7ff6bd7fa700] DEBUG - Codecs: testing h264_vaapi (encoder)
Mar 11, 2020 14:59:41.830 [0x7ff6bd7fa700] DEBUG - Codecs: hardware transcoding: testing API vaapi
Mar 11, 2020 14:59:41.830 [0x7ff6bd7fa700] DEBUG - Codecs: hardware transcoding: opening hw device failed - probably not supported by this system, error: Input/output error

I found the next problem

The transcoder temp directory, which is used to download the codecs as well, is not writable

Mar 11, 2020 14:59:43.402 [0x7ff6bd7fa700] DEBUG - TPU: hardware transcoding: enabled, but no hardware decode accelerator found
Mar 11, 2020 14:59:43.403 [0x7ff6bd7fa700] DEBUG - [Universal] Using local file path instead of URL: /downloads/sd/movies/testdir/jellyfish-20-mbps-hd-hevc.mkv
Mar 11, 2020 14:59:43.403 [0x7ff6bd7fa700] DEBUG - TPU: hardware transcoding: zero-copy support not present
Mar 11, 2020 14:59:43.403 [0x7ff6bd7fa700] DEBUG - TPU: hardware transcoding: final decoder: , final encoder: 
Mar 11, 2020 14:59:43.405 [0x7ff6bd7fa700] ERROR - IsFileWritable: failed to create file '"/downloads/sd/plex-transcode/fe7d2b80-e513-48a6-84d4-cde4e9be8122"'
Mar 11, 2020 14:59:43.405 [0x7ff6bd7fa700] WARN - IsDirWritable: directory '"/downloads/sd/plex-transcode"' is not writable
Mar 11, 2020 14:59:43.405 [0x7ff6bd7fa700] DEBUG - Job running: EAE_ROOT='/tmp/pms-82cf230c-3235-4b74-a93a-21505701bd2f/EasyAudioEncoder' FFMPEG_EXTERNAL_LIBS='/var/lib/plexmediaserver/Library/Application\ Support/Plex\ Media\ Server/Codecs/0bc617e-2974-linux-x86_64/' XDG_CACHE_HOME='/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Cache' XDG_DATA_HOME='/usr/lib/plexmediaserver/Resources' X_PLEX_TOKEN='xxxxxxxxxxxxxxxxxxxx' '/usr/lib/plexmediaserver/Plex Transcoder' '-codec:0' 'hevc' '-analyzeduration' '20000000' '-probesize' '20000000' '-i' '/downloads/sd/movies/testdir/jellyfish-20-mbps-hd-hevc.mkv' '-filter_complex' '[0:0]scale=w=1280:h=720[0];[0]format=pix_fmts=yuv420p|nv12[1]' '-map' '[1]' '-codec:0' 'libx264' '-crf:0' '23' '-maxrate:0' '3807k' '-bufsize:0' '7614k' '-r:0' '29.969999999999999' '-preset:0' 'veryfast' '-level:0' '5.1' '-x264opts:0' 'subme=0:me_range=4:rc_lookahead=10:me=dia:no_chroma_me:8x8dct=0:partitions=none' '-force_key_frames:0' 'expr:gte(t,0+n_forced*3)' '-segment_format' 'mpegts' '-f' 'ssegment' '-individual_header_trailer' '0' '-segment_time' '3' '-segment_start_number' '0' '-segment_copyts' '1' '-segment_time_delta' '0.0625' '-segment_list' 'http://127.0.0.1:32400/video/:/transcode/session/284af72a7c790b07-com-plexapp-android/bc5c3b4f-f554-4be8-8783-082ac681257f/seglist?X-Plex-Http-Pipeline=infinite' '-segment_list_type' 'csv' '-segment_list_size' '5' '-segment_list_separate_stream_times' '1' '-segment_list_unfinished' '1' '-max_delay' '5000000' '-avoid_negative_ts' 'disabled' '-map_metadata' '-1' '-map_chapters' '-1' 'media-%05d.ts' '-start_at_zero' '-copyts' '-vsync' 'cfr' '-y' '-nostats' '-loglevel' 'quiet' '-loglevel_plex' 'error' '-progressurl' 'http://127.0.0.1:32400/video/:/transcode/session/284af72a7c790b07-com-plexapp-android/bc5c3b4f-f554-4be8-8783-082ac681257f/progress'

I have modify 777 permission to temp directory, but remain can’t hardware acceleration.

Now we’re over the stupid stuff and right back to the initial problem.

It still thinks there is an Nvidia card loaded.

Did you load the Nvidia drivers on this system?
You don’t need them.

I don’t have Nvidia card and don’t install nvdia drivers.
Then next step what do?

I think this log information is key, why “error: Input/output error”?

Mar 11, 2020 14:59:41.830 [0x7ff6bd7fa700] DEBUG - Codecs: hardware transcoding: testing API vaapi
Mar 11, 2020 14:59:41.830 [0x7ff6bd7fa700] DEBUG - Codecs: hardware transcoding: opening hw device failed - probably not supported by this system, error: Input/output error

Look at the block.

Mar 12, 2020 08:25:39.741 [0x7f5e6affd700] DEBUG - Codecs: hardware transcoding: opening hw device failed - probably not supported by this system, error: Unknown error occurred
Mar 12, 2020 08:25:39.742 [0x7f5e6affd700] DEBUG - Codecs: testing hevc (decoder) with hwdevice vaapi
Mar 12, 2020 08:25:39.742 [0x7f5e6affd700] DEBUG - Codecs: hardware transcoding: testing API vaapi
Mar 12, 2020 08:25:39.742 [0x7f5e6affd700] DEBUG - Codecs: hardware transcoding: opening hw device failed - probably not supported by this system, error: Input/output error
Mar 12, 2020 08:25:39.742 [0x7f5e6affd700] DEBUG - Codecs: testing hevc (decoder) with hwdevice nvdec

What it’s doing at this point is attempting to transcode the smallest video frame size possible (static image). If it succeeds, then HEVC is enabled. Seeing this failure is indicating one of two things:
a. It isn’t HEVC-capable
b. The passthrough isn’t working right.

Is the ASIC in use by any other VMs? (those VMs have “accelerated graphics enabled” (chrome has an option for that and will collide… it’s happened to me).

Redo the test with H.264 – see if that works.
If H.264 works, then the CPU isn’t capable of HEVC. Strange but, in that environment, it isn’t.

Hi, the passthrough graphics HD 620 only allcate to this one vm, and don’t enable any accelerated graphics.

Then, I test H.264 video, and remain can’t use hardware accelecation.

old PMS version plexmediaserver_1.18.5.2309-f5213a238_amd64.deb is normal, it can hardware accelecation, whether HEVC or H.264

you always tell me test all kind of vedio, and suspect my profile or system or hardware problem, But I want to say old version is normal. so this problem is not my problem, just new version problem.

why don’t you find different between these two versions? I think do this can better and fast find this problem cause.

I very disappointment.

I am just the support guy.

I don’t have ESXI. I have VMware Workstation and another KVM manager on a different system. They work.

I don’t know what to tell you.
I’m sorry, I can’t figure this one out because I don’t have the configuration you do.
I do have a spare box here I might be able to setup as the ESXI host.

If the older version works, stay with it. Nothing is making you update.

I found same problem in below post, and I follow his method set “svga.present=FALSE”, amazing! it is ok, now PMS can use hardware accelecation trancoding.

The problem have sloved, thanks you for patience help!

When I change this setting, I have a black screen in esx and don’t know where the boot failed…

Yes,me too,This parameter is vm graphic card, so disable this will result black screen, I use ssh connect system, so I don’t need graphic.

I need this screen, because since new plex version I have upgrade my Ubuntu to 18.04 and now I have some freeze boot, network who dont want up, freeze on vmware daemon, etc… Its seem to be aleatory…

If it’s work with docker (map render 129 to 128), maybe we can do that on linux?!
Also maybe I can force plex to see what render I want?

Thanks for your reply, I stop to search for this black screen :).

After many tests with new release and roll back, hw decode doens’t work anymore with “1.18.5.2309-f5213a238” version…

So, I migrated my actual pms to docker with dvi render129 mapped to 128.
It seem to work, the docker image see 1 render (128) and he have access.
https://hub.docker.com/r/linuxserver/plex/

I test many things, lastet version and old, nobody want work.

On the latest version, I see on the log: “can’t load cuda”. I understood it’s a problem with iHD_drv_video.so driver and I rename it to iHD_drv_video.so.bck.

Now hw transcrode can be launched, but on my client its a black screen (or green??) paused and on my server I can see transcode work and stream go to up (I see seconds move).
If I remove hw transcode, it’s work but with cpu…

Don’t know where Im wrong, I try to check log but it seem to be good.

The driver “i965_drv_video.so” seem to be the same between old and acutal pms version.
If I install the laste intel ubuntu driver, md5sum are different. I’m doing a test with the laster Intel driver on the docker image, not work.

I understand there’s a bug with the intel driver?
I’m on an Intel i57600K and a Ubuntu 18.04 OS (updated for the occasion).
But why my rollback to “1.18.5.2309-f5213a238” is not working anymore?

Wouldn’t it be easier for me to buy an NVIDIA CUDA card?

Thanks

__ edit: 18.04

There should be no driver bugs with Intel 8xxx and older, 9xxx is probably also good. The only Intel driver issue I know of is when the Intel chip is newer than the linux kernel’s hwe, and that’s not you.
e.g.: Intel 10xxxx CometLake chips on Ubuntu 18.04 is probably iffy. 20.04LTS tomorrow hopefully resolves with its new linux kernel, with 18.04.5 following later this year.

Your 7600 should have no driver issue.

I’d personally reroll the entire OS from scratch onto 18.04LTS (20.04LTS comes tomorrow… but Id personally have a hard time jumping on it day1) before buying a cuda card, but you do you.

Hello Menel,

Thanks to reply :).
Ill test hw decode on a fresh ubuntu 18.04 who I have.
I tell u.

Thanks

yes, I have tested many versions in Feb, you can see in 13th post in this topic.

I have found just plexmediaserver_1.18.5.2309-f5213a238_amd64.deb is normal. and before is normal, after this versions are all not normal.

I have report to manager, but he said he just a support guy. I think that mean is that official will not fix it.

it is real, to date, official never attention my report ,it is tragedy.
I think maybe official never fix it, so I am using Emby now, Emby hw is normal and fast.

I have been trying to find a way to diagnose further.
I apologize for the language problems I do not understand.

  1. Stop Plex
  2. Edit Preferences.xml
  3. add VaapiDriver="i965" before closing />. A space in front is needed.
  4. It will look like this: VaapiDriver="i965" />
  5. Start Plex

This disables the iHD_drv_video.so driver.

You may also delete the driver and restart Plex if you prefer.

As for the -10xxx CPUs, The Linux kernel does not have the HWE for the i915 to communicate with the QSV ASIC.

I created a new plex via docker on a new vm.
Unfortunately, when pairing my plex account with the server via the IP address of the new one, I find my account with the old server offline (which I stopped) and that’s it!
I can’t associate my new server with my premium plex account.
Maybe it’s normal that a premium plex account can only be associated to one server?

  1. There is no limit how many servers you can associate with the account.
  2. I do not understand:
    a. Create a VM
    b. Create a Docker, in the VM , for Plex.

Plex, in a Docker, in a VM, adds so much complexity that it is VERY difficult to manage and makes associating difficult.

Easiest: Plex on the native host (no abstraction)
Easy: Plex in a peer-IP VM (1 layer of abstraction - has graphical UI)
Harder: Plex in a Docker (1 layer of abstraction - no GUI - Must use CLAIM TOKEN)
Most Difficult: Plex in a Docker in a VM (2 layers of abstraction).

Linux-native installation is as portable as any Docker container.
Exporting a VM, using OVA format, while awkward, is doable.

I strongly recommend NOT making it complex. It is NOT necessary.

Complexity, for the sake of complexity, is NOBODY’s friend.