From nobody Wed Jun 23 08:17:32 2021 X-Original-To: freebsd-x11@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 49C5311CFE9B for ; Wed, 23 Jun 2021 08:17:49 +0000 (UTC) (envelope-from evgeniy@khramtsov.org) Received: from mxa.khramtsov.org (mxa.khramtsov.org [IPv6:2a0a:e5c0:2:10f::f]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4G8x310vP9z3mlJ for ; Wed, 23 Jun 2021 08:17:48 +0000 (UTC) (envelope-from evgeniy@khramtsov.org) Received: from mxa.khramtsov.org (mxa.khramtsov.org [IPv6:2a0a:e5c0:2:10f::f]) by mxa.khramtsov.org (Postfix) with ESMTP id 2FF5F125EC1; Wed, 23 Jun 2021 08:14:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=khramtsov.org; s=rsa; t=1624436042; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=3qA5Lymk41seqKb4SJUDRy0uBgCjHAOlca0EqSd9KAc=; b=A22upciY9gV6LedrLeSA9kYox5cvEc8MSb7S4pDUJlh2aufUMQ9GupUKQftjyDF8+Grbg3 Uf7ULr4CO8WFwwrgx1IR8gFNwk4bx/aM42e8iduK85oviBucEXbxd6Gk9YC3bEgIWEGZ+a fcEeSHjAnILKmFxbXspBmvLlSFn6um0hGN65kguHEyyMUXGJ9BybB1wb12+gM1hQ2IUeL0 xMb0SjSDKralsSNq0Sqzx0jql2CczAy59pDHZhgNgaGIaPlPcEX4pbD9cLX5A+r+3a6Jkr HV6a24lhGxgnK083kTEu1UIOj5cGN6SjDJGTzx+i2l4OlWk2h6xkhGc0WhsaEA== Date: Wed, 23 Jun 2021 11:17:32 +0300 To: Kevin Oberman , freebsd-x11@freebsd.org Subject: Re: Correct libva driver for Intel Comet Lake Message-ID: References: List-Id: X11 List-Archive: https://lists.freebsd.org/archives/freebsd-x11 List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4G8x310vP9z3mlJ X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Reply-To: evgeniy@khramtsov.org From: Evgeniy Khramtsov via freebsd-x11 X-Original-From: Evgeniy Khramtsov X-ThisMailContainsUnwantedMimeParts: N "libva-media-driver" does not exist as a $PORTNAME. There are: libva-intel-driver: for Intel GMA 4500 to UHD 630 libva-intel-hybrid-driver: Haswell to Braswell Hybrid VP{8,9} {en,de}decoder. The two above are legacy drivers and were superseded by libva-intel-media-driver: https://github.com/intel/intel-vaapi-driver/issues/499#issuecomment-638556599 intel-media-driver should support Comet Lake starting from tag intel-media-19.2.pre1: https://github.com/intel/media-driver/commit/44ea2083b8f6c0afd6b7ee6b204a6017d1b67448 https://github.com/intel/media-driver/issues/771#issuecomment-769842424 Remove the legacy drivers if you have them installed, then install libva-intel-media-driver, libva-utils (for vainfo) and mpv (for test). See if you have VA-API profiles (example for Comet Lake ES that reports as Coffee Lake 0x3E9B): $ vainfo libva info: VA-API version 1.12.0 libva info: Trying to open /usr/local/lib/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_12 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.12 (libva 2.12.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 21.2.2 (intel-media-21.2.2) vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc VAProfileNone : VAEntrypointStats VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointFEI VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointFEI VAProfileH264High : VAEntrypointEncSliceLP VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointFEI VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile2 : VAEntrypointVLD Then try hardware VA-API decoding using mpv: $ mpv --no-config --msg-level=vo/gpu=v,vd=v --hwdec=vaapi --vo=gpu \ https://base-n.de/webm/out9.webm Check for: [vd] Selected codec: vp9 (Google VP9) [vd] Pixel formats supported by decoder: vaapi_vld yuv420p [vd] Codec profile: Profile 0 (0x0) [vd] Requesting pixfmt 'vaapi_vld' from decoder. Using hardware decoding (vaapi).