HW transcoding not working on N5095 with Ubuntu 22.04.01 LTS and 1.29.1

Well, here we are again. I’m even going to preface this by saying that it’s not Plex’s fault that this isn’t working. However, since I’m running what’s an allegedly supported environment, I’m here again for help in case someone knows what I’m missing to get it to work.

I have installed Ubuntu 22.04.01 LTS (and PMS 1.29.1, but this will only be relevant later when I get HW acceleration working in any form) on my Beelink U59 with an Intel N5095 and I get no hardware acceleration whatsoever.

rafael@upsilon:~$ cat /proc/cpuinfo | grep 'model name' | head -1
model name      : Intel(R) Celeron(R) N5095 @ 2.00GHz
rafael@upsilon:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.1 LTS
Release:        22.04
Codename:       jammy
rafael@upsilon:~$ uname -a
Linux upsilon 5.15.0-50-generic #56-Ubuntu SMP Tue Sep 20 13:23:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
rafael@upsilon:~$ lspci -k | grep -EA3 'VGA|3D|Display'
00:02.0 VGA compatible controller: Intel Corporation JasperLake [UHD Graphics] (rev 01)
        DeviceName: Onboard - Video
        Subsystem: Intel Corporation JasperLake [UHD Graphics]
        Kernel driver in use: i915

This is the plexinstaller.log:

rafael@upsilon:~$ cat /tmp/plexinstaller.log
# Plex Media Server installation configuration info:  seg 10 out 2022 22:11:20 WEST
Init=0
Systemd=1
Custom=0
LinuxContainer=0
NewInstall=0
HaveOverride=0
OverrideFile=""
PlexUser="plex"
PlexGroup="plex"
VideoGroup="render"
AppSuppDir="/var/lib/plexmediaserver/Library/Application Support"
PlexTempDir="/dev/shm"
LangEncoding="en_US.UTF-8"
ExistingVersion=12901
DistroName="ubuntu"
DistroVersion="2204"
HaveHardware=1
HaveTranscoderPref=1
NeedUser=0
NeedGroup=0
NeedVideo=0
Verbose=1
Running=1
Errors=0
Warnings=0
Havei915=1
HaveNvidia=0
Platform="U59"
Processor="Intel(R) Celeron(R) N5095 @ 2.00GHz"
Distro="Ubuntu 22.04.1 LTS"
Kernel="Linux upsilon 5.15.0-50-generic #56-Ubuntu SMP Tue Sep 20 13:23:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux"
Memory="15781 902 164"

The reason for this is that I’m not being able to get GuC/HuC to work on this Ubuntu release (unlike in 20.04.5, where I was able to get it to work after a lot of juggling with the kernel versions). This is the output I get after having done echo "options i915 enable_guc=2" > /etc/modprobe.d/i915.conf and update-initramfs -u:

rafael@upsilon:~$ sudo dmesg | grep i915
[    4.354304] i915 0000:00:02.0: vgaarb: deactivate vga console
[    4.368184] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    4.369823] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/icl_dmc_ver1_09.bin (v1.9)
[    4.613206] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[    4.630988] i915 0000:00:02.0: GuC initialization failed -110
[    4.631000] i915 0000:00:02.0: Enabling uc failed (-5)
[    4.631004] i915 0000:00:02.0: Failed to initialize GPU, declaring it wedged!
[    4.631320] i915 0000:00:02.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by intel_gt_set_wedged_on_init+0x33/0x40 [i915]
[    4.828677] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[    4.831671] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    4.866553] fbcon: i915drmfb (fb0) is primary device
[    4.914225] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device

I have also tried setting the GuC to 3 and downloading extra i915 firmware like suggested in PMS 1.29.1 HW Tonemapping Testing, Questions , and Answers and some other threads.

Sorry for doing this yet again, but @ChuckPa, did you do anything special when setting up your test machines? I didn’t do anything I haven’t specified in the thread.

I didn’t do anything. I always test on a pure machine.

  1. Load the OS
  2. Do the updates
  3. Mount the NFS shares for media
  4. Load PMS
  5. Setup and go

You can try this. Ridley did a little more work on JasperLake

You log snippet shows what looks like a pattern is forming for 22.04.1 – Firmware is messed up. 20.04 was fine where 22.04 isn’t so lucky

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.