Jump to content

switch

Members
  • Posts

    39
  • Joined

  • Last visited

  • Days Won

    1

Report Comments posted by switch

  1. On 11/2/2019 at 2:59 PM, rix said:

    For those of you interested in how to fix this: The PMS 1.18.1 branch includes a new driver that breaks Hardware Transcoding for Apollo Lake Intel CPUs.

     

    In Linuxserver.io's docker image this is located at /usr/lib/plexmediaserver/iHD_drv_video.so

     

    Just delete iHD_drv_video.so and transcoding will work again.

    Great find, thanks! How did you find out about it? Google doesn't find much about the iHD_drv_video.so driver on the Plex forums. Have you reported the issue to the Plex devs? If so, is there a thread that you can link me to so I can +1 it? :)

  2. On 9/17/2019 at 6:17 AM, seaeel said:

    --- Got it fixed with setting intel_iommu=off with syslinux.cfg. While with disable this option causes you cannot pass pci devices to VM. I don't have a need for passing devices to VM so I feel fine with current situation but hope future kernel could got this fix.

    This is perfect! Thanks a lot for your effort! Can confirm that "intel_iommu=igfx_off" is working for me as well on 6.7.3-rc3. Since this is clearly a bug in the Linux kernel and not within unRAID itself, I have now marked this bug report as resolved.

     

    @limetech, this appears to be fixed in the kernel v5.0 and up, will unRAID 6.8 include a v5.0+ kernel?

  3. 9 hours ago, d3fault said:

    Have you i915.alpha_support=1 in the syslinux.cfg?

    Then please test to remove it.

    My syslinux.cfg is absolutely untouched, as stated in the first post. I did however try to add it during my troubleshooting attempts and in makes precisely zero difference.

    You mentioned HW transcoding works for you on a J3455, what version of unRAID are you on?

  4. 8 hours ago, limetech said:

    Well it's either kernel, driver, docker, weird bios interaction (and use of hacks like that fit-headless), or something else.  Hard to know where to begin.

    I think we can rule "weird bios interactions and use of hacks" out, since HW transcoding works perfectly fine on 6.6.7. I am not using any HDMI headless dongles, I have a proper HDMI cable attached to the iGPU output and connected to a real monitor (transcoding works fine on 6.6.7 even without the iGPU being connected to anything). No other GPU in my system. Is there a way to "transplant" the Docker engine used in 6.6.7 to a later stable build so we can potentially rule it out as well? Does anyone know if there perhaps were any changes to the mainline kernel between 6.6.7 and 6.7.x that could break this? Would it be of any use to test the HW transcoding on a Slackware distro with the same kernel version or is unRAID's kernel too heavily modified for a test like this to have any value?

    2 hours ago, GHunter said:

    Not a single diagnostics posted in this thread either.

    My mistake. I'm pretty new to unRAID and it didn't occur to me there's the option to download the diagnostics. I will provide that as soon as possible, but since I'll need to upgrade to 6.7.x to actually make transcoding not work again so there is something to troubleshoot, it's going to be a PITA. Maybe some of the other affected guys currently on 6.7.x will be kind enough to post their diagnostics in the meantime? Anyone? :)

  5. 12 hours ago, semmtex said:

    Yes. On 6.7.X I have a lot more CPU usage when transcoding than on 6.6.7 utilising QuickSync HW Transcoding.

    I can confirm this. Plus, running vainfo clearly shows the supported encode/decode formats:

    root@7011518d444b:/# vainfo
    error: XDG_RUNTIME_DIR not set in the environment.
    error: can't connect to X server!
    libva info: VA-API version 1.1.0
    libva info: va_getDriverName() returns 0
    libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
    libva info: Found init function __vaDriverInit_1_1
    libva info: va_openDriver() returns 0
    vainfo: VA-API version: 1.1 (libva 2.1.0)
    vainfo: Driver version: Intel i965 driver for Intel(R) Gemini Lake - 2.1.0
    vainfo: Supported profile and entrypoints
          VAProfileMPEG2Simple            : VAEntrypointVLD
          VAProfileMPEG2Main              : VAEntrypointVLD
          VAProfileH264ConstrainedBaseline: VAEntrypointVLD
          VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
          VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
          VAProfileH264Main               : VAEntrypointVLD
          VAProfileH264Main               : VAEntrypointEncSlice
          VAProfileH264Main               : VAEntrypointEncSliceLP
          VAProfileH264High               : VAEntrypointVLD
          VAProfileH264High               : VAEntrypointEncSlice
          VAProfileH264High               : VAEntrypointEncSliceLP
          VAProfileH264MultiviewHigh      : VAEntrypointVLD
          VAProfileH264MultiviewHigh      : VAEntrypointEncSlice
          VAProfileH264StereoHigh         : VAEntrypointVLD
          VAProfileH264StereoHigh         : VAEntrypointEncSlice
          VAProfileVC1Simple              : VAEntrypointVLD
          VAProfileVC1Main                : VAEntrypointVLD
          VAProfileVC1Advanced            : VAEntrypointVLD
          VAProfileNone                   : VAEntrypointVideoProc
          VAProfileJPEGBaseline           : VAEntrypointVLD
          VAProfileJPEGBaseline           : VAEntrypointEncPicture
          VAProfileVP8Version0_3          : VAEntrypointVLD
          VAProfileVP8Version0_3          : VAEntrypointEncSlice
          VAProfileHEVCMain               : VAEntrypointVLD
          VAProfileHEVCMain               : VAEntrypointEncSlice
          VAProfileHEVCMain10             : VAEntrypointVLD
          VAProfileHEVCMain10             : VAEntrypointEncSlice
          VAProfileVP9Profile0            : VAEntrypointVLD
          VAProfileVP9Profile0            : VAEntrypointEncSlice
          VAProfileVP9Profile2            : VAEntrypointVLD

    So can we please stop focusing on the hardware, which is clearly capable of HW transcoding and instead focus on the real issue - unRAID ver. 6.7.0 and up?

  6. 2 hours ago, saarg said:

    As for you guys using the J4105, it doesn't look like it support quick sync from a quick Google search.

    I know that ARK does not specifically mention QuickSync support, BUT... J4105 has a UHD600 graphics built in and UHD600 does indeed support QuickSync. This is further evidenced by HW transcoding working perfectly fine on unRAID 6.6.7

     

    https://en.wikichip.org/wiki/intel/celeron/j4105#Graphics

    https://en.wikichip.org/wiki/intel/uhd_graphics/600#Hardware_Accelerated_Video

×
×
  • Create New...