Control: tag -1 + moreinfo On 2019-03-10 19:47:02, Steinar H. Gunderson wrote: > Package: intel-media-va-driver > Version: 18.4.0+dfsg1-1 > Severity: important > > Hi, > > I've been trying the intel-media-va-driver package on my Coffee Lake, > where the old driver works fine. It seems I can't get H.264 encoding > to work: As far as I understand the feature matrices of 18.4.x and 19.2.x, the open source build supports H.264 and JPEG encoding for Coffee Lake only as of the 19.2.x. This version is now available in unstable. Could you try it again with the new version? Cheers > > gruessi:~> export LIBVA_DRIVER_NAME=iHD > gruessi:~> nageru > No --va-display was given, and the X11 display did not expose a VA-API H.264 encoder. > DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument > Assuming 131072kB available aperture size. > May lead to reduced performance or incorrect rendering. > get chip id failed: -1 [22] > param: 4, val: 0 > No suitable VA-API H.264 encoders were found in /dev/dri; giving up. > Note that if you are using an Intel CPU with an external GPU, > you may need to enable the integrated Intel GPU in your BIOS > to expose Quick Sync. Alternatively, you can use --record-x264-video > to use software instead of hardware H.264 encoding, at the expense > of increased CPU usage and possibly bit rate. > > I've also tried JPEG decoding: > > gruessi:~> wget https://storage.sesse.net/trondisk2018-semifinal-multicam-mjpeg.mkv > [you don't need the entire file, Ctrl-C after ~50 MB is fine] > gruessi:~> futatabi --slow-down-input trondisk2018-semifinal-multicam-mjpeg.mkv > gruessi:~/dev/nageru/obj> futatabi --slow-down-input trondisk2018-semifinal-multicam-mjpeg.mkv > > VA-API JPEG decoding initialized. > decode_jpeg_vaapi:383 (vaCreateBuffer) failed with 5 > VA-API hardware decoding failed; falling back to software. > decode_jpeg_vaapi:383 (vaCreateBuffer) failed with 5 > VA-API hardware decoding failed; falling back to software. > decode_jpeg_vaapi:383 (vaCreateBuffer) failed with 5 > > In short, I can't get the driver to work at all, whereas the old driver > (no LIBVA_DRIVER_NAME set) works fine. I haven't tried JPEG encoding, > since I need working H.264 encoding before Nageru will allow me to try > that, but I wouldn't be surprised if that is broken, too. :-) > > This is a Core i5-8400 (Coffee Lake). > > 00:02.0 Display controller: Intel Corporation UHD Graphics 630 (Desktop) > 01:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2070] (rev a1) > > -- System Information: > Debian Release: buster/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386, armhf > > Kernel: Linux 4.19.0-3-amd64 (SMP w/6 CPU cores) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=nb_NO.utf8, LC_CTYPE=nb_NO.utf8 (charmap=UTF-8), LANGUAGE=nb_NO.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages intel-media-va-driver depends on: > ii libc6 2.28-8 > ii libgcc1 1:8.3.0-2 > ii libigdgmm5 18.4.1+ds1-1 > ii libpciaccess0 0.14-1 > ii libstdc++6 8.3.0-2 > ii libva2 [libva-driver-abi-1.4] 2.4.0-1 > > intel-media-va-driver recommends no packages. > > intel-media-va-driver suggests no packages. > > -- no debconf information > -- Sebastian Ramacher
Attachment:
signature.asc
Description: PGP signature