225+ or 425+ Owners - Plex HW Transcoding.

[EZTutty]

Do you have to change some permissions to get the Package to work?

I tried putting a package together a while ago and couldn't get around the permissions without messing with ssh (which I was trying to avoid to make it easier to install for the everyday person).

 

[Rusty]

"Transcode Drivers for x25" package, with HDR Tone Mapping, is available on my Community Package Repository (for DSM 7.2.2 and DSM 7.3).

View attachment 34264

Go to "Package Center > Settings > Package Sources > Add" and add:

Name: 007revad​

Location: https://spkrepo.007daver.workers.dev/​

View attachment 34265

Nice one! Added instructions for this in the article as well.

 

[007revad]

During installation the wizard ui shows this:

Clicking on the "Set package permissions" link takes you to a page that has steps for setting the required permissions via SSH or via Task Scheduler. See Transcode_for_x25/set_package_permissions.md at main · 007revad/Transcode_for_x25

The nice thing about installing the driver modules via a package is it manages the loading and unloading automatically.

When you start the package it:

1. Unloads the default i915 drivers.
2. Loads the good i915 drivers.

When you stop the package it:

1. Unloads the good i915 drivers.
2. Loads the default i915 drivers.

 

[PlichtaO]

During installation the wizard ui shows this:
View attachment 34266

Clicking on the "Set package permissions" link takes you to a page that has steps for setting the required permissions via SSH or via Task Scheduler. See Transcode_for_x25/set_package_permissions.md at main · 007revad/Transcode_for_x25

The nice thing about installing the driver modules via a package is it manages the loading and unloading automatically.

When you start the package it:

1. Unloads the default i915 drivers.
2. Loads the good i915 drivers.

When you stop the package it:

1. Unloads the good i915 drivers.
2. Loads the default i915 drivers.

Hello, I couldn't get the first line of the script to work. Looking at the directory structure, I noticed that the folder is called "TranscodeDrivers" and not "Transcode-drivers". Using "TranscodeDrivers" works. However, what does this offer compared to the script we've been using for the past few months (which we could run at startup with the task scheduler)?

 

[007revad]

Thanks @PlichtaO

When I changed the Package's name I forgot to update the "set permissions" readme. All fixed now.

For people who have been using the script the only benefit to switching to the package is it is easier to update the package if newer drivers are released, or needed for a future DSM update.

The package is more for new DS425+ or DS225+ owners who have no SSH experience. They can add my package source to Package Center then install the package from Package Center's Community page... and package Center will then show them when there's updated drivers available. GitHub - 007revad/Synology_package_source: Synology package source for packages from GitHub

 

[firefly]

New DS225 user and I have a hard time in getting the @007revad script to work. I tried both the package and running the scripts through task scheduler. With the package it shows "running" but I am not getting GPU transcoding. Running the script through task scheduler it shows the following error log with trouble loading the drivers.

Appreciate anyone can shed some light on what I missed here.

Loading good modules:

Loaded /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/i2c-algo-bit.ko

insmod: ERROR: could not insert module /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/drm_panel_orientation_quirks.ko: File exists

 ERROR Failed to load /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/drm_panel_orientation_quirks.ko

insmod: ERROR: could not insert module /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/dmabuf.ko: File exists

 ERROR Failed to load /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/dmabuf.ko

insmod: ERROR: could not insert module /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/drm.ko: File exists

 ERROR Failed to load /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/drm.ko

insmod: ERROR: could not insert module /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/drm_kms_helper.ko: File exists

 ERROR Failed to load /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/drm_kms_helper.ko

insmod: ERROR: could not insert module /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/drm_display_helper.ko: File exists

 ERROR Failed to load /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/drm_display_helper.ko

insmod: ERROR: could not insert module /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/drm_buddy.ko: File exists

 ERROR Failed to load /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/drm_buddy.ko

insmod: ERROR: could not insert module /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/ttm.ko: File exists

 ERROR Failed to load /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/ttm.ko

insmod: ERROR: could not insert module /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/intel-gtt.ko: File exists

 ERROR Failed to load /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/intel-gtt.ko

insmod: ERROR: could not insert module /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/i915-compat.ko: File exists

 ERROR Failed to load /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/i915-compat.ko

Loaded /volume1/script/Transcode_for_x25-3.0.11/x25_drivers_v3_dsm73/i915.ko



Finished

 

[007revad]

Those errors are just noise (false errors) because those modules were already loaded. The fact that i915.ko loaded without any error means all the other modules were loaded.

If you run this in a scheduled task, or via SSH,

ls -la /dev/dri/

and the output includes renderD128 and card0 then the drives are loaded correctly.

Dave@SENNA:~$ ls -la /dev/dri/
total 0
drwxr-xr-x  2 root root              80 May  1 23:00 .
drwxr-xr-x 19 root root           14860 May  1 23:02 ..
crw-------  1 root root        226,   0 May  1 23:00 card0
crw-rw----  1 root videodriver 226, 128 May  1 23:00 renderD128

Which would mean that maybe you don't have hardware assisted transcoding enabled in Plex (or Jellyfin).

 

[firefly]

Those errors are just noise (false errors) because those modules were already loaded. The fact that i915.ko loaded without any error means all the other modules were loaded.

If you run this in a scheduled task, or via SSH,

ls -la /dev/dri/

and the output includes renderD128 and card0 then the drives are loaded correctly.

Dave@SENNA:~$ ls -la /dev/dri/
total 0
drwxr-xr-x  2 root root              80 May  1 23:00 .
drwxr-xr-x 19 root root           14860 May  1 23:02 ..
crw-------  1 root root        226,   0 May  1 23:00 card0
crw-rw----  1 root videodriver 226, 128 May  1 23:00 renderD128

Which would mean that maybe you don't have hardware assisted transcoding enabled in Plex (or Jellyfin).

Thanks for pointing me in the right direction and the driver indeed loaded correctly. It turns out I have to use a yaml to build the Tdarr container and map the /dev/drv to it before it can see the GPU. It's working flawlessly now but the compression is nowhere near as good as the CPU.