Jump to content

flyize

Members
  • Posts

    432
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by flyize

  1. 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.

    • Like 3
  2. 3 hours ago, SimonF said:

    If you are blacklisting the module you will need remove the blacklist 

     

    on 5.18 you should just be able to put in modprobe.d/i915.cfg instead of the blacklist command.

     

    options i915 enable_guc=2

     

    Not sure which option you need for force probe

     

    But you can add a similar option for the force probe but on 5.15 kernel you can do

     

    options i915 force_probe=4c8a

    options i915 enable_guc=2

     

     

    I shall try this.

     

    I think intel_gpu_top blacklists the driver automatically (or *something* is on my server). So I'll need to remove that first.

     

    edit: GPU Statistics and intel_gpu_top are gone, and I have no idea what's force blacklisting it. I remove it from modprobe, reboot, it comes back. Is Unraid doing it?

  3. 11 minutes ago, SimonF said:

    blacklisting just stops the module from being loaded, but you need i915 for /dev/dri to be created.

     

    blacklisting is need on 6.10 if you are using intel gpu top to load the module with the correct force probe for Alderlake. May not be required for 5.18 kernel as support should be in stock kernel.

     

    You can add to syslinx or in the modprode.d/i915.conf the guc=2 options but I dont know if that works with Alderlake.

    This suggests that it does. Just to confirm, that setting should work irregardless of the blacklist?

     

     

     

  4. 4 hours ago, SimonF said:

    Installed 5.18rc and same as you plex just crashed when trying to transcode.

    What is the purpose of blacklisting the i915 drivers? Any chance they work with RC7 and the 5.18 kernel? I've seen some suggestions that adding "options i915 enable_guc=2" makes QS work, but I assume that command means nothing if we're blacklisting the drivers.

  5. 20 hours ago, SimonF said:

    Used 5.18rc2 vers of firmware from github.

     

    computenode kernel: i915 0000:00:02.0: [drm] Transparent Hugepage mode 'huge=within_size'
    computenode kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
    computenode kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
    computenode kernel: i915 0000:00:02.0: [drm] GuC firmware i915/tgl_guc_69.0.3.bin version 69.0
    computenode kernel: i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9
    computenode kernel: i915 0000:00:02.0: [drm] HuC authenticated
    computenode kernel: i915 0000:00:02.0: [drm] GuC submission disabled
    computenode kernel: i915 0000:00:02.0: [drm] GuC SLPC disabled
    computenode kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
    computenode elogind-uaccess-command[13899]: Failed to reset ACL on /dev/dri/card0: Operation not supported

     

    Looks better.

    Were you able to test transcoding?

  6. 1 hour ago, SimonF said:

    Used 5.18rc2 vers of firmware from github.

     

    computenode kernel: i915 0000:00:02.0: [drm] Transparent Hugepage mode 'huge=within_size'
    computenode kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
    computenode kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
    computenode kernel: i915 0000:00:02.0: [drm] GuC firmware i915/tgl_guc_69.0.3.bin version 69.0
    computenode kernel: i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9
    computenode kernel: i915 0000:00:02.0: [drm] HuC authenticated
    computenode kernel: i915 0000:00:02.0: [drm] GuC submission disabled
    computenode kernel: i915 0000:00:02.0: [drm] GuC SLPC disabled
    computenode kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
    computenode elogind-uaccess-command[13899]: Failed to reset ACL on /dev/dri/card0: Operation not supported

     

    Looks better.

    Interesting. That doesn't have whatever 6.10RCx changes were done.

×
×
  • Create New...