On 2024-03-30 04:31, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: [oS-en] Problem with VLC on Intel machines. Message-ID : <20240329162926.19a5d073@acer-suse.fritz.box> Date & Time: Fri, 29 Mar 2024 16:29:26 +0000
[DH] == Dave Howorth <dave@howorth.org.uk> has written:
DH> On Fri, 29 Mar 2024 21:34:28 +0900 DH> Masaru Nomiya <nomiya@lake.dti.ne.jp> wrote:
MN>> Now it's my turn to sleep.
DH> Is one of those businesses called "Sleep Hygiene" and is one part of DH> that stopping using TV and computer screens two hours before you go to DH> bed? (hint: the answer is yes)
DH> And are you?
It's entirely correct.
In Japan, people are actively telling not to use their phones before going to bed because of sleep problems.
I don't own a TV or a smartphone, but I understand that screens are bad for your eyes and even your brain.
Sorry for Off-topic、all．
Ok :-)
Anyway, I'll try to be more precise.
[...] Isengard:~ # grep -iE 'vdpau | dri driver' /var/log/Xorg.0.log [ 201.567] (II) intel(0): [DRI2] DRI driver: iris [ 201.567] (II) intel(0): [DRI2] VDPAU driver: va_gl Isengard:~ # [...]
Anyway, I'm going to write more precisely because it is important to use vlc.
The message 'VDPAU driver: va_gl' in the second line appears when the libva driver is incorrectly configured, and does not appear when the configuration is correct.
You can find out how it is configured with;
$ env | grep LIBVA_DRIVER.
Isengard:~ # env | grep LIBVA_DRIVER Isengard:~ #
You can also check if the LIBVA_DRIVER setting is correct with;
$ vainfo
Isengard:~ # vainfo If 'vainfo' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf vainfo Isengard:~ # Isengard:~ # zypper install libva-utils ... Isengard:~ # logout Connection to isengard.valinor closed. cer@Telcontar:~> ssh -X cer@isengard.valinor Last login: Wed Mar 27 21:45:27 2024 from 79.151.89.236 Have a lot of fun... cer@Isengard:~> tmux attach Isengard:~ # vainfo error: XDG_RUNTIME_DIR is invalid or not set in the environment. libva info: VA-API version 1.16.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_16 libva error: /usr/lib64/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_13 failed to open /usr/lib64/dri/hybrid_drv_video.so Not using hybrid_drv_video.so libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.16 (libva 2.15.0) vainfo: Driver version: Intel i965 driver for Intel(R) CherryView - 2.4.1 ... Isengard:~ # It doesn't like execution via ssh, trying locally and pasting to a file. cer@Isengard:~/tmp> vainfo libva info: VA-API version 1.16.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_16 libva error: /usr/lib64/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_13 failed to open /usr/lib64/dri/hybrid_drv_video.so Not using hybrid_drv_video.so libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.16 (libva 2.15.0) vainfo: Driver version: Intel i965 driver for Intel(R) CherryView - 2.4.1 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD You have new mail in /var/spool/mail/cer cer@Isengard:~/tmp>
If the setting is correct, the following result is displayed.
$ vainfo
Trying display: wayland Trying display: x11 libva info: VA-API version 1.21.0 libva error: vaGetDriverNames() failed with unknown libva error libva info: User environment variable requested driver 'nvidia libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 vainfo:: Found init function __vaDriverInit_1_20 VA-API version: 1.21 (libva 2.20.0) vainfo: va_openDriverInit_1_20 Driver version: 1.21 (libva 2.20.0) Splitted-Desktop Systems VDPAU backend for VA-API - 0.7.4 vainfo: Driver version: Splitted-Desktop Systems Supported profiles and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG4Simple : VAEntrypointVLD VAProfileMPEG4AdvancedSimple : VAEntrypointVLD <unknown profile> : VAEntrypointVLD VAProfileH264Main : VAEntrypointVLD VAProfileH264High : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD
If the setting is not correct, it will look like this;
$ vainfo Trying display: wayland Trying display: x11 libva info: VA-API version 1.21.0 libva error: vaGetDriverNames() failed with unknown libva error libva info: User environment variable requested driver 'i950 libva info: Trying to open /usr/lib64/dri/i950_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit
If the configuration is incorrect, you must add the followings to the .profile;
export LIBVA_DRIVERS_PATH=/usr/lib64/dri export LIBVA_DRIVER_NAME=[correct driver name]
And what is the correct driver name? :-?
If it is correct, you do not need to do anything.
As can be inferred from the above, for example, whether iHD_drv_video.so can be used as a libva driver can be determined by executing;
$ LIBVA_DRIVER_NAME=iHD vainfo
cer@Isengard:~/tmp> LIBVA_DRIVER_NAME=iHD vainfo libva info: VA-API version 1.16.0 libva info: User environment variable requested driver 'iHD' libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_16 libva error: /usr/lib64/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 vaInitialize failed with error code 1 (operation failed),exit cer@Isengard:~/tmp> -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)