Re: Can't view videos in firefox: VA-API test failed
On 26/01/2024 07:09, Stefan Monnier wrote:
systemctl --user status pipewire{,-pulse} wireplumber
which shows that `wireplumber` failed to start.
I was assuming that
systemctl --user --failed
journalctl --user --boot
and as root
systemctl --failed
journalctl --boot
were first that you tried facing an issue. After replacing pulseaudio by
pipewire, I faced some issue with systemd unit, but I have not figured
out what have happened. Despite what Debian wiki states, no additional
configuration was required. That is why I can not tell if recipes from
Arch wiki are helpful.
Re: Can't view videos in firefox: VA-API test failed
> The problem might be in between of
>
> lspci -vnn
Spews out a lot of stuff, the relevant part being presumably:
00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD
Audio Controller [8086:284b] (rev 03)
Subsystem: Lenovo ThinkPad T61/R61 [17aa:20ac]
Flags: bus master, fast devsel, latency 0, IRQ 30
Memory at fe02 (64-bit, non-prefetchable) [size=16K]
Capabilities:
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
> and
>
> pactl list
> pactl list sinks
Here the sinks say just:
% pactl list cards
% pactl list sinks
Sink #33
State: SUSPENDED
Name: auto_null
Description: Dummy Output
Driver: PipeWire
Sample Specification: float32le 2ch 48000Hz
Channel Map: front-left,front-right
Owner Module: 4294967295
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 /
100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: auto_null.monitor
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY
Properties:
node.name = "auto_null"
device.description = "Dummy Output"
audio.rate = "48000"
audio.channels = "2"
audio.position = "FL,FR"
media.class = "Audio/Sink"
factory.name = "support.null-audio-sink"
node.virtual = "true"
monitor.channel-volumes = "true"
factory.id = "17"
clock.quantum-limit = "8192"
client.id = "30"
node.driver = "true"
factory.mode = "merge"
audio.adapt.follower = ""
library.name = "audioconvert/libspa-audioconvert"
object.id = "31"
object.serial = "33"
Formats:
pcm
%
> Perhaps troubleshooting sections in wikis may tell more. There is a chance
> that lsof may find another process holding audio devices.
Hmm... this time a web search lead me to
systemctl --user status pipewire{,-pulse} wireplumber
which shows that `wireplumber` failed to start.
Thanks. Haven't found the actual problem nor a fix, but I have
some leads.
Stay tuned, I'll be back with the results :-)
Stefan
Re: Can't view videos in firefox: VA-API test failed
On 24/01/2024 04:28, Stefan Monnier wrote: But since `pactl` seems to still be useful for Pipewire, I tried `pavucontrol` and it shows me no device from which to select in the "Output Devices". Now, how do I figure out why that is? The problem might be in between of lspci -vnn and pactl list pactl list sinks Perhaps troubleshooting sections in wikis may tell more. There is a chance that lsof may find another process holding audio devices.
Re: Can't view videos in firefox: VA-API test failed
> But since `pactl` seems to still be useful for Pipewire, I tried > `pavucontrol` and it shows me no device from which to select in the > "Output Devices". Hmm... actually, not quite: there is one output device, called "Dummy Output". And there is similarly just one input device listed, called "Monitor of Dummy Input". Stefan
Re: Can't view videos in firefox: VA-API test failed
>> Server Version: 15.0.0 >> Default Sample Specification: float32le 2ch 48000Hz >> Default Channel Map: front-left,front-right >> Default Sink: @DEFAULT_SINK@ >> Default Source: @DEFAULT_SOURCE@ >> Cookie: 40db:2cde >> % >> >> Not sure what the `Cookie` does and even less whether those @DEFAULT_SINK@ >> thingies are normal, tho a quick `grep` indicates at least `zsh` >> completion for `wpctl` finds them normal: >> >> /usr/share/zsh/site-functions/_wpctl: >> 'pw-defaults:defaults:(@DEFAULT_SINK@ @DEFAULT_SOURCE@)' \ > > I would set them explicitly and see if things get better. I don't really know how to set them. But since `pactl` seems to still be useful for Pipewire, I tried `pavucontrol` and it shows me no device from which to select in the "Output Devices". Now, how do I figure out why that is? Stefan
Re: Can't view videos in firefox: VA-API test failed
Stefan Monnier wrote: > Server Version: 15.0.0 > Default Sample Specification: float32le 2ch 48000Hz > Default Channel Map: front-left,front-right > Default Sink: @DEFAULT_SINK@ > Default Source: @DEFAULT_SOURCE@ > Cookie: 40db:2cde > % > > Not sure what the `Cookie` does and even less whether those @DEFAULT_SINK@ > thingies are normal, tho a quick `grep` indicates at least `zsh` > completion for `wpctl` finds them normal: > > /usr/share/zsh/site-functions/_wpctl: > 'pw-defaults:defaults:(@DEFAULT_SINK@ @DEFAULT_SOURCE@)' \ I would set them explicitly and see if things get better. -dsr-
Re: Can't view videos in firefox: VA-API test failed
> OK. First diagnostic: `pactl info`. > > On my bookworm desktop, I get this: > > $ pactl info > Server String: /run/user/1042/pulse/native > Library Protocol Version: 35 > Server Protocol Version: 35 > Is Local: yes > Client Index: 13692 > Tile Size: 65472 > User Name: dsr > Host Name: spike > Server Name: PulseAudio (on PipeWire 0.3.65) > Server Version: 15.0.0 > Default Sample Specification: float32le 2ch 48000Hz > Default Channel Map: front-left,front-right > Default Sink: PulseEffects_apps > Default Source: > alsa_input.usb-Blue_Microphones_Yeti_Stereo_Microphone_REV8-00.analog-stereo % pactl info Server String: /run/user/20848/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 138 Tile Size: 65496 User Name: monnier Host Name: alfajor Server Name: PulseAudio (on PipeWire 1.0.1) Server Version: 15.0.0 Default Sample Specification: float32le 2ch 48000Hz Default Channel Map: front-left,front-right Default Sink: @DEFAULT_SINK@ Default Source: @DEFAULT_SOURCE@ Cookie: 40db:2cde % Not sure what the `Cookie` does and even less whether those @DEFAULT_SINK@ thingies are normal, tho a quick `grep` indicates at least `zsh` completion for `wpctl` finds them normal: /usr/share/zsh/site-functions/_wpctl: 'pw-defaults:defaults:(@DEFAULT_SINK@ @DEFAULT_SOURCE@)' \ Stefan
Re: Can't view videos in firefox: VA-API test failed
Stefan Monnier wrote: > > Does mplayer give any more interesting errors? > > Oh, I didn't notice it at first, but now that you ask, yes it does: > after something like a timeout period it says: > > AO: [pulse] Init failed: Timeout > Failed to initialize audio driver 'pulse' > > And lo and behold if I start it with `mplayer -ao none `, the > video plays just fine (whether Theora, MPEG2, or H.264). > > So maybe I was barking up the wrong tree and the problem was on the > audio side all this time. Well, yes and no. I think we've established that there's no hardware support for decoding anything except MPEG2, but also that the machine is capable of doing most decoding in software. Sound problems are... excessive amounts of fun. > This machine is running Debian testing, > which seems to have selected Pipewire for me. > > % ps auxw|grep pipewire > monnier 1810 0.0 0.1 46096 9396 ?Ssl jan18 0:00 > /usr/bin/pipewire > monnier 1813 0.0 0.0 34436 6412 ?Ssl jan18 0:00 > /usr/bin/pipewire -c filter-chain.conf > monnier 1818 0.0 0.1 41540 10460 ?Ssl jan18 0:00 > /usr/bin/pipewire-pulse > monnier 7472 0.0 0.0 8276 2304 pts/6SN+ 16:40 0:00 grep > pipewire OK. First diagnostic: `pactl info`. On my bookworm desktop, I get this: $ pactl info Server String: /run/user/1042/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 13692 Tile Size: 65472 User Name: dsr Host Name: spike Server Name: PulseAudio (on PipeWire 0.3.65) Server Version: 15.0.0 Default Sample Specification: float32le 2ch 48000Hz Default Channel Map: front-left,front-right Default Sink: PulseEffects_apps Default Source: alsa_input.usb-Blue_Microphones_Yeti_Stereo_Microphone_REV8-00.analog-stereo Which says the things I expect: pulseaudio's interface is being supplied by pipewire, it's configured for 2 channel stereo, there's a USB microphone available and the output is being filtered through PulseEffects (which is doing equalization for me.) -dsr-
Re: Can't view videos in firefox: VA-API test failed
On 22/01/2024 04:26, Charles Curley wrote: You and I seem to be having similar problems. No, you don't. Charles, your graphics adapter is supported by i965, but not iHD and vainfo reports a number of profiles https://lists.debian.org/msgid-search/20240113101948.0a880f26@hawk.localdomain Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so Sat, 13 Jan 2024 10:19:48 -0700 A message related to iHD is a routine attempt to load the driver. In the case of Stefan neither iHD nor i965 support that graphics adapter. Perhaps mesa really has dropped it.
Re: Can't view videos in firefox: VA-API test failed
> Does mplayer give any more interesting errors? Oh, I didn't notice it at first, but now that you ask, yes it does: after something like a timeout period it says: AO: [pulse] Init failed: Timeout Failed to initialize audio driver 'pulse' And lo and behold if I start it with `mplayer -ao none `, the video plays just fine (whether Theora, MPEG2, or H.264). So maybe I was barking up the wrong tree and the problem was on the audio side all this time. This machine is running Debian testing, which seems to have selected Pipewire for me. % ps auxw|grep pipewire monnier 1810 0.0 0.1 46096 9396 ?Ssl jan18 0:00 /usr/bin/pipewire monnier 1813 0.0 0.0 34436 6412 ?Ssl jan18 0:00 /usr/bin/pipewire -c filter-chain.conf monnier 1818 0.0 0.1 41540 10460 ?Ssl jan18 0:00 /usr/bin/pipewire-pulse monnier 7472 0.0 0.0 8276 2304 pts/6SN+ 16:40 0:00 grep pipewire % IIUC `pipewire-pulse` is the daemon which should let PulseAudio client connect to Pipewire, so I don't know why mplayer's `pulse` backend is not happy. I know very little about Pipewire (or GNU/Linux audio in general for that matter), so I'd welcome help diagnosing this part as well. I tried to use `mplayer -ao alsa ` but it ends up just sitting there, without any output nor error after the first few information lines (which are always the same): % mplayer -ao alsa icfp23-explicit-refinement-types.mkv MPlayer 1.5+svn38446-1 (Debian)do_connect: could not connect to socket connect: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing icfp23-explicit-refinement-types.mkv. libavformat version 60.16.100 (external) libavformat file format detected. [lavf] stream 0: video (h264), -vid 0 [lavf] stream 1: audio (opus), -aid 0, -alang eng VIDEO: [H264] 1280x720 0bpp 30.000 fps0.0 kbps ( 0.0 kbyte/s) libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib/i386-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva error: /usr/lib/i386-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/i386-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_8 libva error: /usr/lib/i386-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 == Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family libavcodec version 60.31.102 (external) Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264) == Clip info: COMPATIBLE_BRANDS: iso6avc1mp41 MAJOR_BRAND: dash MINOR_VERSION: 0 ENCODER: Lavf60.16.100 Load subtitles in ./ == Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders [opus @ 0xf6d9bb80]Could not update timestamps for skipped samples. AUDIO: 48000 Hz, 2 ch, floatle, 0.0 kbit/0.00% (ratio: 0->384000) Selected audio codec: [ffopus] afm: ffmpeg (FFmpeg opus) == My best guess is that it's waiting for Pipewire to release the audio device? With `ao oss`, it goes a bit further (i.e. it opens up the actual window where the window should be played) but still ends up sitting there waiting for something and not playing anything. Stefan
Re: Can't view videos in firefox: VA-API test failed
On Sat, 20 Jan 2024 18:51:17 -0500 Stefan Monnier wrote: > So, IIUC the problem is that the hardware video decoder drivers aren't > found for some reason. I checked my VA-related packages and they seem > to be installed: > > # aptitude search '\' | grep '^i' > i A i965-va-driver - VAAPI driver for Intel G45 & HD Graphics > family i intel-media-va-driver - VAAPI driver for the Intel GEN8+ > Graphics family i A libvdpau-va-gl1 - VDPAU driver with OpenGL/VAAPI > backend i A mesa-va-drivers - Mesa VA-API video acceleration drivers > i va-driver-all - API de Video Acceleration (VA) – métapaquet de > pilotes i A vdpau-va-driver - VDPAU-based backend for VA API > # > > I tried to install `intel-media-va-driver-non-free` to see if that's > the problem, but it did not make any difference. You and I seem to be having similar problems. I suspect that it has to do with drivers initializing properly, not our respective browsers. I can run Firefox just fine, but not chromium. root@jhegaala:~# pre '\' i965-va-driver 2.4.1+dfsg1-1 amd64 intel-media-va-driver 23.1.1+dfsg1-1 amd64 libvdpau-va-gl1 0.4.2-1+b1 amd64 mesa-va-drivers 22.3.6-1+deb12u1amd64 va-driver-all 2.17.0-1amd64 root@jhegaala:~# I seem to be missing vdpau-va-driver, but it does not seem to be available for me (bookworm): root@jhegaala:~# apt install vdpau-va-driver Reading package lists... Done Building dependency tree... Done Reading state information... Done Package vdpau-va-driver is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: mesa-va-drivers E: Package 'vdpau-va-driver' has no installation candidate root@jhegaala:~# I've documented what I have so far in a thread with the subject "Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so" root@jhegaala:~# lspci -vs 2.0 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T520 Flags: bus master, fast devsel, latency 0, IRQ 28, IOMMU group 0 Memory at f000 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 6000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 root@jhegaala:~# VLC also plays MP4 movies just fine. It reports: charles@jhegaala:~/ogg$ VLC media player 3.0.20 Vetinari (revision 3.0.20-0-g6f0d0ab126b) [55febf968d30] [http] lua interface: Lua HTTP interface [55febf882550] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. [7f76bc0042f0] gl gl: Initialized libplacebo v4.208.0 (API v208) libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_17 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_8 libva info: va_openDriver() returns 0 [7f76bc0042f0] gl gl: Initialized libplacebo v4.208.0 (API v208) libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_17 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_8 libva info: va_openDriver() returns 0 [7f76d4c18c50] avcodec decoder: Using OpenGL/VAAPI backend for VDPAU for hardware decoding -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Can't view videos in firefox: VA-API test failed
On 2024-01-20 18:51 -0500, Stefan Monnier wrote: > Whenever I try to view videos in Firefox in my trusty Thinkpad T61, > Firefox just eats up the CPU but doesn't actually show the video. > > At startup I get the following message: > > [GFX1-]: vaapitest: VA-API test failed: failed to initialise VAAPI > connection. > > So, IIUC the problem is that the hardware video decoder drivers aren't > found for some reason. I checked my VA-related packages and they seem > to be installed: > > # aptitude search '\' | grep '^i' > i A i965-va-driver - VAAPI driver for Intel G45 & HD Graphics family > i intel-media-va-driver - VAAPI driver for the Intel GEN8+ Graphics > family > i A libvdpau-va-gl1 - VDPAU driver with OpenGL/VAAPI backend > i A mesa-va-drivers - Mesa VA-API video acceleration drivers > i va-driver-all - API de Video Acceleration (VA) – métapaquet de pilotes > i A vdpau-va-driver - VDPAU-based backend for VA API > # > > I tried to install `intel-media-va-driver-non-free` to see if that's the > problem, but it did not make any difference. > > I understand that my machine is fairly old, but it used to be able to > play youtube videos just fine without eating all my CPU time (i.e. using > hardware video decoding from its GM965/GL960 Intel integrated graphcs). > > Any idea what might be going on? It is probably due to the removal of old drivers, including i915 and i965, in Mesa 22.0. There is a separate branch for the old drivers called "Mesa Amber" but unfortunately no packages have appeared in Debian yet[1,2,3], and honestly I do not think they ever will. :-( > Any hint how I could diagnose the problem? Look for "swrast" in ~/.local/share/xorg/Xorg.0.log. If it is mentioned there, you are likely using software rendering. Cheers, Sven 1. https://bugs.debian.org/1006202 2. https://lists.debian.org/debian-x/2022/06/msg00041.html 3. https://lists.debian.org/debian-x/2023/08/msg00138.html
Re: Can't view videos in firefox: VA-API test failed
Stefan Monnier wrote: > > This should be the Intel 4500 integrated gpu, which is part of > > the i915/i965 family. It needs: > > > > - an intel kernel module > > According to `lsmod | grep '^i'` I have `i915` loaded. Is that the one? Yes. > > - X11 running the intel video driver > > Interesting. I was using the `modesetting` driver. > So I installed `xserver-xorg-video-intel` and then put > > % cat /etc/X11/xorg.conf > Section "Device" > Identifier "Intel Corporation 965GM" > Driver "intel" > EndSection > % > > to force Xorg to use that `intel` driver (since apparently by default > nowadays it tries only `vesa`, `fbdev`, and `modestting`). Yup. > > It will support MPEG2 accelerated decoding but not H264, H265 or > > any of the newer codecs -- and Youtube may not be supplying old > > codecs these days. > > That might be part of the problem, indeed. > Tho the `vainfo` failure suggests that even MPEG2 isn't working. > > I tried to view an MPEG2 video with totem/xine/mplayer and that didn't > work either (it doesn't eat up all the CPU, instead they just "sit > there", sometimes emitting the same kind of VA errors as shown earlier). Does mplayer give any more interesting errors? -dsr-
Re: Can't view videos in firefox: VA-API test failed
> This should be the Intel 4500 integrated gpu, which is part of > the i915/i965 family. It needs: > > - an intel kernel module According to `lsmod | grep '^i'` I have `i915` loaded. Is that the one? > - X11 running the intel video driver Interesting. I was using the `modesetting` driver. So I installed `xserver-xorg-video-intel` and then put % cat /etc/X11/xorg.conf Section "Device" Identifier "Intel Corporation 965GM" Driver "intel" EndSection % to force Xorg to use that `intel` driver (since apparently by default nowadays it tries only `vesa`, `fbdev`, and `modestting`). The end result appears to be the same, tho :-( At least, all the error messages I get are the same. > - libva-drm2 > - libva-x11-2 > - libva2 > - i965-va-driver Check! > It will support MPEG2 accelerated decoding but not H264, H265 or > any of the newer codecs -- and Youtube may not be supplying old > codecs these days. That might be part of the problem, indeed. Tho the `vainfo` failure suggests that even MPEG2 isn't working. I tried to view an MPEG2 video with totem/xine/mplayer and that didn't work either (it doesn't eat up all the CPU, instead they just "sit there", sometimes emitting the same kind of VA errors as shown earlier). Stefan
Re: Can't view videos in firefox: VA-API test failed
Stefan Monnier wrote: > Whenever I try to view videos in Firefox in my trusty Thinkpad T61, > Firefox just eats up the CPU but doesn't actually show the video. > > At startup I get the following message: > > [GFX1-]: vaapitest: VA-API test failed: failed to initialise VAAPI > connection. ... > I understand that my machine is fairly old, but it used to be able to > play youtube videos just fine without eating all my CPU time (i.e. using > hardware video decoding from its GM965/GL960 Intel integrated graphcs). > > Any idea what might be going on? Any hint how I could diagnose the problem? This should be the Intel 4500 integrated gpu, which is part of the i915/i965 family. It needs: - an intel kernel module - X11 running the intel video driver - libva-drm2 - libva-x11-2 - libva2 - i965-va-driver It will support MPEG2 accelerated decoding but not H264, H265 or any of the newer codecs -- and Youtube may not be supplying old codecs these days. -dsr-
Re: Can't view videos in firefox: VA-API test failed
Max Nikulin [2024-01-21 10:51:36] wrote: > On 21/01/2024 06:51, Stefan Monnier wrote: >> [GFX1-]: vaapitest: VA-API test failed: failed to initialise VAAPI >> connection. > [...] >> Any idea what might be going on? Any hint how I could diagnose the problem? > I would start from comparison of "vainfo" output and related sections in > about:support. Thanks, I didn't know about either of those :-) Sadly, `vainfo` doesn't tell me much more info than that it fails: % vainfo libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib/i386-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva error: /usr/lib/i386-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/i386-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_8 libva error: /usr/lib/i386-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 % But at least, it seems to indicate that my problems don't have to do with Firefox. > Internally Firefox likely uses a test like > > /usr/lib/firefox-esr/vaapitest -d /dev/dri/renderD128 > > https://searchfox.org/mozilla-central/source/widget/gtk/GfxInfo.cpp#line-649 Indeed that gives me the same error message: % /usr/lib/firefox-esr/vaapitest -d /dev/dri/renderD128 ERROR VA-API test failed: failed to initialise VAAPI connection. % I can't see any "verbose" option for those so I tried `strace`: % strace vainfo [...] write(2, "libva info: Found init function __vaDriverInit_1_20", 52) = 52 openat(AT_FDCWD, "/etc/igfx_user_feature_next.txt", O_RDONLY|O_LARGEFILE) = -1 ENOENT (Aucun fichier ou dossier de ce type) openat(AT_FDCWD, "/etc/igfx_user_feature.txt", O_RDONLY|O_LARGEFILE) = -1 ENOENT (Aucun fichier ou dossier de ce type) openat(AT_FDCWD, "/dev/shm/GFX_MEDIA_TRACE", O_RDONLY|O_LARGEFILE) = -1 ENOENT (Aucun fichier ou dossier de ce type) getpid()= 14840 ioctl(4, DRM_IOCTL_VERSION, 0xffdde780) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde780) = 0 ioctl(4, DRM_IOCTL_VERSION, 0xffdde820) = 0 ioctl(4, DRM_IOCTL_I915_GEM_GET_APERTURE, 0xffdde7e8) = 0 geteuid32() = 20848 getuid32() = 20848 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde820) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7e0) = 0 ioctl(4, DRM_IOCTL_I915_GEM_CONTEXT_GETPARAM, 0xffdde808) = 0 ioctl(4, DRM_IOCTL_I915_QUERY, 0xffdde7f8) = 0 ioctl(4, DRM_IOCTL_I915_QUERY, 0xffdde7f8) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7a4) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7a4) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7a4) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7a4) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7a4) = -1 ENODEV (Aucun périphérique de ce type) ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7a4) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7a4) = 0 ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7a4) = -1 ENODEV (Aucun périphérique de ce type) ioctl(4, DRM_IOCTL_I915_GETPARAM or DRM_IOCTL_TEGRA_CLOSE_CHANNEL, 0xffdde7a4) = -1 ENODEV (Aucun périphérique de ce type)
Re: Can't view videos in firefox: VA-API test failed
On 21/01/2024 06:51, Stefan Monnier wrote: [GFX1-]: vaapitest: VA-API test failed: failed to initialise VAAPI connection. [...] Any idea what might be going on? Any hint how I could diagnose the problem? I would start from comparison of "vainfo" output and related sections in about:support. ArchLinux and Debian wiki may give some troubleshooting hints https://wiki.debian.org/Firefox#Hardware_Video_Acceleration Internally Firefox likely uses a test like /usr/lib/firefox-esr/vaapitest -d /dev/dri/renderD128 https://searchfox.org/mozilla-central/source/widget/gtk/GfxInfo.cpp#line-649
Can't view videos in firefox: VA-API test failed
Whenever I try to view videos in Firefox in my trusty Thinkpad T61, Firefox just eats up the CPU but doesn't actually show the video. At startup I get the following message: [GFX1-]: vaapitest: VA-API test failed: failed to initialise VAAPI connection. So, IIUC the problem is that the hardware video decoder drivers aren't found for some reason. I checked my VA-related packages and they seem to be installed: # aptitude search '\' | grep '^i' i A i965-va-driver - VAAPI driver for Intel G45 & HD Graphics family i intel-media-va-driver - VAAPI driver for the Intel GEN8+ Graphics family i A libvdpau-va-gl1 - VDPAU driver with OpenGL/VAAPI backend i A mesa-va-drivers - Mesa VA-API video acceleration drivers i va-driver-all - API de Video Acceleration (VA) – métapaquet de pilotes i A vdpau-va-driver - VDPAU-based backend for VA API # I tried to install `intel-media-va-driver-non-free` to see if that's the problem, but it did not make any difference. I understand that my machine is fairly old, but it used to be able to play youtube videos just fine without eating all my CPU time (i.e. using hardware video decoding from its GM965/GL960 Intel integrated graphcs). Any idea what might be going on? Any hint how I could diagnose the problem? Stefan
