Chromium hardware-accelerated build for Intel-based platforms available for beta testing

Project Discussion Desktop
, ,
44

Thank you for the great post!
It helped a lot to me and hw acceleration now works on my GPU also:
Intel® UHD Graphics 620 (verified on two different Intel CPUs)
Also, just to mention that for me I had to use the following arguments, maybe it helps to someone else also:

chromium --enable-features=VaapiVideoDecodeLinuxGL --disable-features=UseChromeOSDirectVideoDecoder --ignore-gpu-blacklist --enable-zero-copy

Question: do you maybe know when this change will land in the stable Chromium branch?
Thanks!

1 Like
45

Hi! Do we have any ETA for this coming to the stable channel?
Thanks!

46

Nope, sorry, I lost access to the testing server and my computer is sufficiently old to only support the i965 Intel driver. I’ll try to get that prerequisite solved. Meanwhile, keep on beta/edge for it.

1 Like
47

We’re still working on re-enabling the tests, unfortunately much went stale or updated and broke them.

But as mentioned before, Chromium already has most of this upstream so in stable it’s just a matter of passing the flags we use in edge and beta:

chromium --enable-features=VaapiVideoDecoder,VaapiVideoEncoder,VaapiVideoDecodeLinuxGL,UseChromeOSDirectVideoDecoder --enable-native-gpu-memory-buffers --ozone-platform-hint=auto
48

Hi there! The built-in intel’s media-driver (iHD) provided by the snap package does not seem to enable AV1 hardware decoding. Intel iGPUs (UHD7xx and Xe graphics) on 11th, 12th, 13th, 14th generation and Arc dGPUs are affected because the AV1 film grain kernel required for Intel’s AV1 hardware decoder is only available in the non-free variant package intel-media-va-driver-non-free. Please consider using it, otherwise playing AV1 videos on Youtube will still stress the CPU.

Here the error message on my i7-12700H, and it will fallback to use the software decoder:

[17702:17957:1120/224753.037142:ERROR:vaapi_wrapper.cc(3497)] : vaEndPicture failed, VA error: internal decoding error
[17702:17957:1120/224753.037238:ERROR:vaapi_video_decoder.cc(1225)] : error decoding stream
[17702:17848:1120/224832.297420:INFO:decoder.cc(56)] : VaapiVideoDecoder
[17702:18172:1120/224832.301497:ERROR:vaapi_wrapper.cc(3497)] : vaEndPicture failed, VA error: internal decoding error
[17702:18172:1120/224832.301614:ERROR:vaapi_video_decoder.cc(1225)] : error decoding stream
[17702:17848:1120/224834.998592:INFO:decoder.cc(56)] : VaapiVideoDecoder
[17702:18190:1120/224835.212927:ERROR:vaapi_wrapper.cc(3497)] : vaEndPicture failed, VA error: internal decoding error
[17702:18190:1120/224835.213039:ERROR:vaapi_video_decoder.cc(1225)] : error decoding stream
[17702:17848:1120/224850.523944:INFO:decoder.cc(56)] : VaapiVideoDecoder
[17702:18463:1120/224850.530875:ERROR:vaapi_wrapper.cc(3497)] : vaEndPicture failed, VA error: internal decoding error
[17702:18463:1120/224850.531026:ERROR:vaapi_video_decoder.cc(1225)] : error decoding stream

The iHD libraries provided by the snap pakcage:

/snap/mesa-2404/143/usr/lib/i386-linux-gnu/dri/iHD_drv_video.so
/snap/mesa-2404/143/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
/snap/chromium/2973/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

See also:

49

Thank you for bringing that to our attention. Per se, the question about the non-free driver is valid, though the idea was to move away from shipping that in each potential snap and instead consume from mesa-2404 or gpu-2404 (sorry, always forget the name).

In any case, the issues at hand are too recent, and even us on core24 cannot get such recent versions of the drivers in, because core24 is based in Ubuntu 24.04 and therefore uses the 24.04 archive which is won’t be new enough to contain those fixes. I’m sorry but as far as I can tell there is no a way beyond that, it’s the essentially the good old ‘stability vs new features’ thing at play.