NS50 and 3D graphics acceleration

I’m using a NitroPad NS50 with the default Ubuntu 22.04 system, rendering happens through llvmpipe and there is no 3D acceleration (gnome-shell eats CPU time by only moving the mouse, can’t enable 3D acceleration in VMs). Is there a way to enable it?

I checked dmesg, and these are errors regarding the GPU:

[ 18.070088] i915 0000:00:02.0: vgaarb: deactivate vga console
[ 18.070143] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[ 18.071036] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 18.072703] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc_ver2_16.bin (v2.16)
[ 18.330249] i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_70.bin version 70.5.1
[ 18.330261] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc.bin version 7.9.3
[ 18.535744] i915 0000:00:02.0: [drm] GuC load failed: status = 0x400000A0
[ 18.535758] i915 0000:00:02.0: [drm] GuC load failed: status: Reset = 0, BootROM = 0x50, UKernel = 0x00, MIA = 0x00, Auth = 0x01
[ 18.535767] i915 0000:00:02.0: [drm] GuC firmware signature verification failed
[ 18.535843] i915 0000:00:02.0: GuC initialization failed -8
[ 18.535859] i915 0000:00:02.0: Please file a bug on drm/i915; see How to file i915 bugs · Wiki · drm / intel · GitLab for details.
[ 18.535864] i915 0000:00:02.0: Enabling uc failed (-5)
[ 18.535872] i915 0000:00:02.0: Failed to initialize GPU, declaring it wedged!
[ 18.537809] i915 0000:00:02.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by intel_gt_set_wedged_on_init+0x34/0x50 [i915]
[ 18.598586] i915 0000:00:02.0: [drm] Skipping intel_backlight registration
[ 18.599530] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[ 18.637276] fbcon: i915drmfb (fb0) is primary device
[ 18.943571] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[ 32.055042] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

Hey hey,

yes, we also saw this, I added a github issue for this. We are investigating this issue, the current assumption is that this has to be most likely solved by the firmware. Using the EDK2/UEFI firmware we don’t see this happening, thus we assume this might have something to do with HEADS. Cannot give an ETA yet.

best

Thanks!

May this be useful to resolve the issue?