Jump to content

Luukholleman

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by Luukholleman

  1. On 6/3/2022 at 6:04 AM, Cajones said:

    Mind providing instructions on what you did exactly? I know it's a pain, but I don't understand why no one can replicate even with similar hardware. 

     

    To me, I think plex is a large culprit as many people seem to have stability with jellyfin.  My server will crash regardless of transcoding as long as igpu is passed through to plex. 

     

    I installed the kernel with these instructions 

     

    Linked /dev/dri device to my docker plex container using the linuxserver variant (lscr.io/linuxserver/plex).

    I don't have force_probe=i195 in my boot config.

    I do have "blacklist i915" in /etc/modprobe.d/i915.conf

    I have intel_gpu_top installed.

    After that I enabled transcoding but left HDR tone mapping disabled.

    • Thanks 2
  2. 3 hours ago, Wintersdark said:

    Nope, stock kernel definitely crashes on the 12400.  I think I got two days once, but roughly once a day crashes. Heavy use server, mind you, it wouldn't just crash when it transcodes a particular file, it would often do several just fine.  

     

     

     

    But hard crashes inevitably.

    Either I'm very lucky or I gotta disagree. Been running RC kernel for 2 weeks now. 

     

    My server is never doing nothing. I'm constantly running encoding jobs in the background on 6 cores, other stuff running on the other 6, often transcoding on the GPU on foreground with 4 plex users. Hope I don't jinx it but it doesn't crash.

    • Confused 1
  3. 18 hours ago, jbrukardt said:

    Thats the first result ive seen that has no crashyness.   You're sure you're hardware transcoding with the iGPU?

    100% sure, CPU low, iGPU usage goes brrrrrrrrr

     

    17 hours ago, Oggie said:

    What cpu do you have ?

    12400, combined with Gigabyte B660M DS3H if that matters.

     

    Running for 2 days now without problems and heavy use on 5.18 and 6.10.1. HDR tonemapping is still broken on plex (on emby it works), plex was working on it AFAIK. But HW resolution/quality transcoding works 100%.

  4. 12 hours ago, michaeldt said:

    Well, I bought a UPS, so had to shut it down to connect the UPS up. But after I rebooted, I played a film through plex again and it was still fine (only played a few minutes). Haven't used plex since, but the server is still up now (2days). I'll run a whole film through this evening while I do other stuff and see if it crashes.


    Update: So some files play fine, others cause a crash. I'm not yet sure what the difference is, but it's not working universally, so I'd advise against upgrading for now if you need a lot of transcoding. 

    Weird, I've been running on 6.10 with 5.18rc7 for some time now with 0 issues and heavy transcoding.

     

    I'll install 5.18 release today/tomorrow.

  5. Some further testing yes I think it works. It's just that Plex has a bug i think. On emby it fully works.

     

    Played 3 4k HDR to SDR transcodes and a background Plex optimize encode at the same time. No crash or anything.

     

    Why I think Plex is the problem now is that Plex is transcoding at 10-20 fps and needs burned in subtitles to have no artifacts. Emby is working perfectly while transcoding HDR to SDR at 160fps.

     

    Running on an 12400 btw.

  6. Installed it, confirmed it's running with uname -r which shows 5.18.0-rc7-thor-Unraid

     

    HW HDR mapping (still) not (fully) working for me sadly. Still having artifacts. Except when I burn in PGS subs, then it works... Weird but true. But it's progress!

     

    Running latest plex and Unraid 6.10 (stable)
     

    Edit: actually also works if I force plex to burn in subtitles always.

  7. 2 hours ago, flyize said:

    If anyone else wants to try @thor2002ro's latest kernel, its very simple.

     

    1. Backup your USB drive. You're very unlikely to screw up, but you should be doing this anyway
    2. Download the latest kernel from https://github.com/thor2002ro/unraid_kernel/releases
    3. Download the latest firmware file from https://github.com/thor2002ro/unraid_kernel/releases. Note: this isn't always included with every release. As of this writing, the latest firmware file is found under 5.18rc2 20220412 o3 clang14 thin LTO 6.9.2.
    4. Power down your Unraid server and plug the USB drive into your computer.
    5. In the root of the drive, move or rename the following files: bzimage, bzimage.sha256, bzmodules, bzmodules.sha256, bzfirmware, bzfiremware.sha256
    6. Unzip and move all the downloaded files into the root of the USB drive.
    7. Open /syslinux/syslinux.cfg in a text editor. Look for the following entry:
    label Unraid OS
      menu default
      kernel /bzimage
      append initrd=/bzroot

    and add

    md_mod.unraid_patch=22

    to the append section. It should look like this:

     label Unraid OS
      menu default
      kernel /bzimage
      append initrd=/bzroot md_mod.unraid_patch=22

     

    Note: Pay attention to the release notes from @thor2002ro as that Unraid patch number may change!

     

    8. Plug the USB drive back into the server and start her up!

    9. Profit.

    Do I then need to remove "i915.force_probe=4680" from the boot configuration and remove the blacklist of the driver?

×
×
  • Create New...