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. 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. You can also check if the LIBVA_DRIVER setting is correct with; $ vainfo 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] 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 HTHs. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃\/彡 ┗━━┛ "Companies have come to view generative AI as a kind of monster that must be fed at all costs―even if it isn’t always clear what exactly that data is needed for or what those future AI systems might end up doing." -- Generative AI Is Making Companies Even More Thirsty for Your Data --