SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Nope, I can't get intel-media-22.3.0 to build, even using an edited slackbuild. It errors out at about 57% complete, just like when I did it by hand. Curiously, the error messages suggest actual errors in the code, undeclared variables and such-like.
How about version 21.3.5, did it build successfully?
Hi Hazel, when compiling that intel-media package I noticed it took quite a while and the end product is big:
Quote:
-rw-r--r-- 1 root root 10973939 Feb 22 22:22 intel-media-driver-22.6.6-x86_64-1ponce.tgz
Could it be that your 'tmp' space used for building gets filled up? Sometimes, when building something big and I don't clear my build-space the compiling falters without a clear reason.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Original Poster
Rep:
Quote:
Originally Posted by brobr
Hi Aeterna, thanks for this, now Brave can have hardware-acceleration set (with "brave://settings/system") without the fans coming on all the time ;-).
Some observations (with KabyLake, 9th generation; i7-7700HQ; pipewire; re-compiled ffmpeg, slackware64-current) when trying this out.
1. No Guc or HuC output in dmesg.
2. Testing with vlc (or QMplay2 with FFmpeg-VA-API Decoder) instead of mpv worked fine; gave "Video" output in 'intel-gpu-top' of ~7-11%.
Code:
bash-5.2$ cvlc Big_Buck_Bunny_1080_10s_5MB.mp4
VLC media player 3.0.17.3 Vetinari (revision 3.0.13-8-g41878ff4f2)
[0000000000b25c60] dummy interface: using the dummy interface module...
[00007ff630c138a0] avcodec decoder: Using OpenGL/VAAPI backend for VDPAU for hardware decoding
3. Brave leads to more "RENDER/3D" output (~20-25%, starting at ~39%) than Firefox (~8%, starting at 15%)(No "Video" output).
with "brave://gpu/" (colors from brave output):
4. FWIW (not being a versed ffmpeg user), the ffmpeg conversions falter at my end on:
Without the "-vf 'format=nv12,hwupload'" it worked (with "Big_Buck_Bunny_720_10s_2MB.mkv").
hth
1) this is what I see running cvlc (differences are hardware related, so all is fine):
Code:
cvlc Big_Buck_Bunny_1080_10s_1MB.mp4
VLC media player 3.0.17.4 Vetinari (revision 3.0.13-8-g41878ff4f2)
[0000000031b40dd0] dummy interface: using the dummy interface module...
TagLib: MP4: No audio tracks
[00006f6ab4c11100] avcodec decoder: Using Intel iHD driver for Intel(R) Gen Graphics - 22.6.6 () for hardware decoding
2) ffmgeg conversion (I am not versed in ffmpeg either) should confirm the use of VAAPI so as long as you see:
should be fine
3) never used brave
but I assume that
Code:
brave://flags
should work: search for specific options and enable what you want. Of course some options are specific for chrome only.
I would enable
Quote:
Raw Draw
you have it disabled (not possible to enable?)
A note regarding WebGPU:
Quote:
Enables access to the experimental WebGPU API. Warning: As GPU sandboxing isn't implemented yet for the WebGPU API, it is possible to read GPU data for other processes. – Mac, Windows, Linux, ChromeOS, Fuchsia, Lacros
..so I did not enable WebGPU in chrome
4) GuC and HuC
Based on Intel info
/etc/modprobe.d/i915.conf
options i915 enable_guc=3
options i915 enable_fbc=1
should be set 0 (zero)
this means that GuC and HuC are not available for Kabylake
Hi Hazel, when compiling that intel-media package I noticed it took quite a while and the end product is big:
Could it be that your 'tmp' space used for building gets filled up? Sometimes, when building something big and I don't clear my build-space the compiling falters without a clear reason.
hth
It's tmpfs so it should expand as required, shouldn't it? du shows 1.8G currently. Anyway, I've got -22.1 building now. It takes a very long time to get anywhere, and if it fails, it will be around the 57% mark.
update: 59% and still building!
update: crashed at 68%!
Code:
/tmp/SBo/media-driver-intel-media-21.3.5/media_driver/linux/common/ddi/media_libva.cpp: In function 'VAStatus DdiMedia_InitMediaContext(VADriverContextP, int32_t, int32_t*, int32_t*)':
/tmp/SBo/media-driver-intel-media-21.3.5/media_driver/linux/common/ddi/media_libva.cpp:1833:32: error: 'OpenGmm' was not declared in this scope
1833 | GMM_STATUS gmmStatus = OpenGmm(&mediaCtx->GmmFuncs);
| ^~~~~~~
make[2]: *** [media_driver/CMakeFiles/iHD_drv_video_OBJ.dir/build.make:8168: media_driver/CMakeFiles/iHD_drv_video_OBJ.dir/linux/common/ddi/media_libva.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:316: media_driver/CMakeFiles/iHD_drv_video_OBJ.dir/all] Error 2
make: *** [Makefile:156: all] Error 2
should work: search for specific options and enable what you want. Of course some options are specific for chrome only.
I would enable
you have it disabled (not possible to enable?)
Ha, never used "brave://flags"; Thanks. BTW, it was default; setting this to `enabled` does not, at least, change the 'Render/3D' levels
Quote:
Originally Posted by Aeterna
4) GuC and HuC
Based on Intel info
/etc/modprobe.d/i915.conf
options i915 enable_guc=3
options i915 enable_fbc=1
should be set 0 (zero)
this means that GuC and HuC are not available for Kabylake
hope this helps
Yes thanks; I had set "enable_guc=0" but left "enable_fbc=1", which seems to work with the 7th generation chip (I called it wrongly to be 9th generation; wishful thinking, haha ;-).
Yes, but it can be restricted; at my end it's set to 6G in the /etc/fstab
Code:
tmpfs /tmp tmpfs size=6G,mode=777
0 0
Maybe I should increase it ;-)
No, mine uses only the default options.
Just as an experiment I tried rebuilding the package with the -j1 make option. LFS recommends this as a thing to try when a multi-core build crashes. But it still crashed in the same place.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Original Poster
Rep:
@brobr
Quote:
Yes thanks; I had set "enable_guc=0" but left "enable_fbc=1", which seems to work with the 7th generation chip (I called it wrongly to be 9th generation; wishful thinking, haha ;-).
Sorry, I meant
Quote:
enable_guc=0
only.
Interesting link thank you. Unfortunately I am unable to edit my first post anymore otherwise I would include it for more reading for Slackware intel video users.
@lancsuk
Regarding Kaby Lake settings listed work. For some differences consult @brobr posts. I think that only GuC/HuC will not work so set enable_guc=0
Regarding HD Graphics 620, I am not sure to what extend will work. Maybe try and report back
which tests succeeded. Start with Kaby Lake as "positive control"
Max core profile version: 4.6
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL core profile version string: 4.6 (Core Profile) Mesa 21.3.5
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.3.5
eglinfo | grep version
Code:
EGL API version: 1.4
EGL version string: 1.4
EGL API version: 1.4
EGL version string: 1.4
EGL API version: 1.4
EGL version string: 1.4
Max core profile version: 4.6
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL core profile version string: 4.6 (Core Profile) Mesa 21.3.5
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.3.5
eglinfo | grep version
Code:
EGL API version: 1.4
EGL version string: 1.4
EGL API version: 1.4
EGL version string: 1.4
EGL API version: 1.4
EGL version string: 1.4
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.