From owner-freebsd-multimedia@freebsd.org Sat Oct 6 17:48:55 2018 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB28B10C1425 for ; Sat, 6 Oct 2018 17:48:54 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 55AA47CAE5 for ; Sat, 6 Oct 2018 17:48:54 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 198B210C1423; Sat, 6 Oct 2018 17:48:54 +0000 (UTC) Delivered-To: multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBAF510C1422 for ; Sat, 6 Oct 2018 17:48:53 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 866947CAE4 for ; Sat, 6 Oct 2018 17:48:53 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ot1-x332.google.com with SMTP id j9-v6so15828727otl.2 for ; Sat, 06 Oct 2018 10:48:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=G0ZpjuAzwGZRN8Fyftv0LQo7/U0Od3hs2Wwe+1WxXks=; b=lFVZ9jik1YEJBHSJgAsTF4mWT91J6GLy/mb2tPsAsCEm0ymJ+nLESK4gbYZUl/w+ov KXVmDbsFDQCUvri5qnIwiBoS36dDc7saXFLofBmzQIMy3fY6SPFARY5DkGYD5nqvl4D6 WU9DpsXVImB32OOx0HjQBvjAEArZeIE4/PSJjLiWXO0AXIEjb0oCLEregSBnK//E13MK 4kK6FRJOkUljYh9DH1iaHgXz0uWwKO2yZlw9ZULiFvNwN2kpSOCIQ/2CGrePgQ+FWQND zSepX1sHoZs74f40RckLbwq8nnaP3ExZbNpUwKgDjoiPiQbCRzU6oa+pzmN7soiodtym xAig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=G0ZpjuAzwGZRN8Fyftv0LQo7/U0Od3hs2Wwe+1WxXks=; b=so+ycpY3TZNNmwaR9pRkOVC9wy2v6eFjWA8JyXto7qPwBUNZHVWq96PJrM6DuMPAhf JUiyIQEweeUmUfL/M7hitavUHYBAfXCHi82nmWFUDBZeSSt8PZoVKDH+XOrprq0RgMfJ 6cvpJGFhsE6ztIgx43yQoutmgiIs1sV33fxuCnNH6BA1XlIrin1zUy1U/EyhoPK6GIVX rTGCxMKrHp+NxuNpseXD4+3Lv/2DqO/hc3qiFk2CVP2sOK8SQiW158HvlRqTudxmkrhz IuTK3oDs0dCRxxm7KQmr+pJFQRbDR0Jjy6IyCm3i3wH7aJVGW6xnhZ/FCGdDRjSbV9TP +Gqw== X-Gm-Message-State: ABuFfohIDCxksCA77dxRO8QLPQCJ/rnDlKRmGH3Wsfp8WJWooy/JCZO9 NhCagnSibTGXhG8Jx5UAExaojnpD7bfSNyOCpOzf5AMi X-Google-Smtp-Source: ACcGV6193h0Tf7Ni1DDEN8z65reEk4Xp/Cp7gjHSTEhaaPNwcOdGOD+RG0VRbg05iwUTiTGa2Srzlh2lf2ldDK1BXnU= X-Received: by 2002:a9d:40f4:: with SMTP id t49mr6784129oti.210.1538848132487; Sat, 06 Oct 2018 10:48:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kevin Oberman Date: Sat, 6 Oct 2018 10:48:35 -0700 Message-ID: Subject: Re: VAAPI not working with latest updates To: multimedia@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Oct 2018 17:48:55 -0000 On Fri, Oct 5, 2018 at 1:19 PM Kevin Oberman wrote: > I'll start by admitting that I am not sure where to look about this, bu > after the last week's massive updates, all of my video players are failing. > I have tried mplayer, totem, mpv, xine and vlc. None work. > > vlc give the most detailed error message (more than one line): > libva info: VA-API version 1.2.0 > libva info: va_getDriverName() returns 0 > libva info: Trying to open /usr/local/lib/dri/i965_drv_video.so > libva info: Found init function __vaDriverInit_1_2 > libva info: va_openDriver() returns 0 > i965: Failed to submit batchbuffer: Input/output error > QObject::~QObject: Timers cannot be stopped from another thread > > All others just show the i965 line. > > I am assuming that VAAPI is the problem as I can use avidemux3_qt4 without > any problem and, as far as I can tell, it does not use VAAPI. > > Running 11.2-stable r338990 and drm-stable-kmod. All ports are current as > of last night. GPU is Sandy Bridge. > > I have not tried to play a video since 28-Sept. and a LOT of ports have > been touched since then, so VAPI may not be at issue, it just looks very > suspicious. I have tried rolling back libva and libva-intel-driver, to > 2.2.0 but that did not help. > > Any suggestions on what I might look at? I'm not happy about opening a PR > with so little to go by. > Found the problem... py-mako was not installed. Oddly, though the Makefile for mesa-dri clearly lists it as BUILD_DEPENDS and it is pulled in when I build the port, it is not listed as a dependency by "pkg info". It appears that build dependencies are not listed in the pkg database... only runtime dependencies, but, typically, things that are both run and build dependencies are only defined as BUILD_DEPENDS. After all, they are installed to build, so they will still be there to run the program. THIS IS BROKEN! In any case, there is no real issue with the port and certainly with VAAPI. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683