SOLVED: Arc A380 transcoding suddently stopped working

[juki]

Hey all!

I've got a weird problem where hardware encoding was working fine until a couple of fairly innocuous-looking package upgrades a few days back and now the driver is failing. It's an Arc A380 GPU paired with an Intel i5-12400 on Ubuntu 23.10 (bare metal, not docker) so most of this worked out-the-box. 

The integrated GPU is disabled in the bios, and /dev/dri lists

Code:

$ ls -l /dev/dri
total 0
drwxr-xr-x  2 root root        80 Jan 20 21:51 by-path
crw-rw----+ 1 root video  226,  0 Jan 20 21:51 card0
crw-rw----+ 1 root render 226, 128 Jan 20 21:51 renderD128

vainfo (packaged with jellyfin) is failing with

Code:

$ sudo /usr/lib/jellyfin-ffmpeg/vainfo
Trying display: drm
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva error: /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva error: /usr/lib/jellyfin-ffmpeg/lib/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

and intel_gpu_top also fails with

Code:

$ sudo intel_gpu_top
intel_gpu_top: ../tools/intel_gpu_top.c:1932: init_engine_classes: Assertion `max >= 0' failed.
Aborted

The driver libs with jellyfin-ffmpeg have these permissions (should it be root : root?):

Code:

$ ls -l /usr/lib/jellyfin-ffmpeg/lib/dri/
total 56816
-rw-r--r-- 1 root root  8730792 Nov 29 20:36 i965_drv_video.so
-rw-r--r-- 1 root root 37150552 Nov 29 20:36 iHD_drv_video.so
-rw-r--r-- 1 root root 12294736 Nov 29 20:36 radeonsi_drv_video.so

and finally, /var/log/apt/history.log shows the packages installed:

Code:

Start-Date: 2024-01-16  06:03:55
Commandline: /usr/bin/unattended-upgrade
Upgrade: libjavascriptcoregtk-4.1-0:amd64 (2.42.3-0ubuntu0.23.10.1, 2.42.4-0ubuntu0.23.10.1), gir1.2-javascriptcoregtk-4.1:amd64 (2.42.3-0ubuntu0.23.10.1, 2.42.4-0ubuntu0.23.10.1), gir1.2-javascriptcoregtk-6.0:amd64 (2.42.3-0ubuntu0.23.10.1, 2.42.4-0ubuntu0.23.10.1), gir1.2-webkit2-4.1:amd64 (2.42.3-0ubuntu0.23.10.1, 2.42.4-0ubuntu0.23.10.1), libjavascriptcoregtk-6.0-1:amd64 (2.42.3-0ubuntu0.23.10.1, 2.42.4-0ubuntu0.23.10.1), libwebkit2gtk-4.1-0:amd64 (2.42.3-0ubuntu0.23.10.1, 2.42.4-0ubuntu0.23.10.1), gir1.2-webkit-6.0:amd64 (2.42.3-0ubuntu0.23.10.1, 2.42.4-0ubuntu0.23.10.1), libwebkitgtk-6.0-4:amd64 (2.42.3-0ubuntu0.23.10.1, 2.42.4-0ubuntu0.23.10.1)
End-Date: 2024-01-16  06:03:57

Start-Date: 2024-01-18  06:13:36
Commandline: /usr/bin/unattended-upgrade
Upgrade: xserver-xorg-core:amd64 (2:21.1.7-3ubuntu2.4, 2:21.1.7-3ubuntu2.6), xserver-xorg-legacy:amd64 (2:21.1.7-3ubuntu2.4, 2:21.1.7-3ubuntu2.6), xserver-common:amd64 (2:21.1.7-3ubuntu2.4, 2:21.1.7-3ubuntu2.6), xwayland:amd64 (2:23.2.0-1ubuntu0.3, 2:23.2.0-1ubuntu0.4), xserver-xephyr:amd64 (2:21.1.7-3ubuntu2.4, 2:21.1.7-3ubuntu2.6)
End-Date: 2024-01-18  06:13:38

Start-Date: 2024-01-18  14:08:00
Commandline: aptdaemon role='role-commit-packages' sender=':1.307'
Upgrade: libpam-runtime:amd64 (1.5.2-6ubuntu1, 1.5.2-6ubuntu1.1), mutter-common-bin:amd64 (45.2-0ubuntu2~really45.0, 45.2-0ubuntu3), tzdata:amd64 (2023c-9ubuntu1, 2023d-0ubuntu0.23.10), tzdata-icu:amd64 (2023c-9ubuntu1, 2023d-0ubuntu0.23.10), libmutter-13-0:amd64 (45.2-0ubuntu2~really45.0, 45.2-0ubuntu3), udisks2:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), mutter-common:amd64 (45.2-0ubuntu2~really45.0, 45.2-0ubuntu3), gnome-shell:amd64 (45.1-0ubuntu1, 45.2-0ubuntu1), libudisks2-0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), gnome-shell-extension-desktop-icons-ng:amd64 (46+really47.0.5-1, 46+really47.0.7-0ubuntu1), libpam-modules:amd64 (1.5.2-6ubuntu1, 1.5.2-6ubuntu1.1), gir1.2-mutter-13:amd64 (45.2-0ubuntu2~really45.0, 45.2-0ubuntu3), base-files:amd64 (13ubuntu2, 13ubuntu2.1), systemd-hwe-hwdb:amd64 (253.5.2, 253.5.3), gnome-shell-common:amd64 (45.1-0ubuntu1, 45.2-0ubuntu1), python3-distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), distro-info-data:amd64 (0.58ubuntu0.1, 0.58ubuntu0.2), linux-firmware:amd64 (20230919.git3672ccab-0ubuntu2.4, 20230919.git3672ccab-0ubuntu2.5), libpam-modules-bin:amd64 (1.5.2-6ubuntu1, 1.5.2-6ubuntu1.1), distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), libpam0g:amd64 (1.5.2-6ubuntu1, 1.5.2-6ubuntu1.1), gnome-characters:amd64 (45.0-1, 45.0-1ubuntu1), libtorrent-rasterbar2.0:amd64 (2.0.9.git20231120.9c18976452-1ppa1~23.10, 2.0.9.git20240117.18f821ea1a-1ppa1~23.10), qbittorrent-nox:amd64 (1:4.6.2.99~202311282222-8123-1773b1ea0~ubuntu23.10.1, 1:4.6.3.99~202401170003-8129-cfa7a6db4~ubuntu23.10.1)
End-Date: 2024-01-18  14:08:19

Start-Date: 2024-01-19  06:56:07
Commandline: /usr/bin/unattended-upgrade
Upgrade: ubuntu-report:amd64 (1.7.2, 1.7.2ubuntu0.1), ipp-usb:amd64 (0.9.23-1build1, 0.9.23-1ubuntu0.23.10.1), libsysmetrics1:amd64 (1.7.2, 1.7.2ubuntu0.1)
End-Date: 2024-01-19  06:56:10

Any ideas where to go from here? I'm not sure where to start

[TheDreadPirate]

I don't know why this would happen after an update, but double check that jellyfin is still in the correct render group.

[juki]

I don't know why this would happen after an update, but double check that jellyfin is still in the correct render group.

Yep, appears so...

Code:

$ groups jellyfin
jellyfin : jellyfin video render media

(media is the group for the media drive)

---

I'm not sure this is even anything in particular to do with Jellyfin, installing libva-utilis and running vainfo gives a similar error with the OS va libs

Code:

$ sudo vainfo
[sudo] password for ghostpirate:
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: can't connect to X server!
libva info: VA-API version 1.19.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_18
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_19
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

I just don't know who else to ask, my google skills have failed me thus far! 🙃

[TheDreadPirate]

Reinstall all the Intel drive and opencl packages?

[tmsrxzar]

"I just don't know who else to ask, my google skills have failed me thus far!"

how about https://discourse.ubuntu.com

or browse https://bugs.launchpad.net/ubuntu

[Host-in-the-Shell]

Did you by any chance update your bios to a new version recently? I had this issue pop up for me after updating mine and what happened was that the update changed many options to default that I required to be able to transcode with the Arc380. That varies from case to case, but for me it disabled 4g decoding, resizable bar, ASPM, and reenabled CSM support. After changing the aforementioned settings, everything went back to normal.

I'm not sure if Ubuntu does automatic firmware/bios updates or if you happened to perform one yourself, but just in case, you should check that your bios settings haven't been changed.

[juki]

Did you by any chance update your bios to a new version recently? I had this issue pop up for me after updating mine and what happened was that the update changed many options to default that I required to be able to transcode with the Arc380. That varies from case to case, but for me it disabled 4g decoding, resizable bar, ASPM, and reenabled CSM  support. After changing the aforementioned settings, everything went back to normal.

I'm not sure if Ubuntu does automatic firmware/bios updates or if you happened to perform one yourself, but just in case, you should check that your bios settings haven't been changed.

Not that I'm aware of, all the settings look the same. Good idea though, thanks!

Reinstall all the Intel drive and opencl packages?

This led me down a rabbit hole reading how to do that and ended up finding a couple obscure posts about Secure Boot causing very similar issues...
https://bugs.launchpad.net/ubuntu/+sourc...ug/1752194
https://askubuntu.com/questions/1217785/...el-command

Sure enough, disabling Secure Boot resolved this and I have no idea why that would be any different now than it was a few weeks ago...
Reinstalling the packages is probably the correct solution instead of disabling Secure Boot, but I'm not quite confident enough to go down that route.

"I just don't know who else to ask, my google skills have failed me thus far!"

how about https://discourse.ubuntu.com

or browse https://bugs.launchpad.net/ubuntu

I'm really quite new to all this, sorry. It was more a thought of "maybe others on the jellyfin forums have bumped into this as I'm on the most common distro and I've not done anything particularly weird afaik".