From owner-freebsd-x11@freebsd.org Sat Dec 8 21:38:02 2018 Return-Path: Delivered-To: freebsd-x11@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 D72C71329F4F for ; Sat, 8 Dec 2018 21:38:01 +0000 (UTC) (envelope-from jbeich@freebsd.org) 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 7801969F9E for ; Sat, 8 Dec 2018 21:38:01 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3B54F1329F4E; Sat, 8 Dec 2018 21:38:01 +0000 (UTC) Delivered-To: x11@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 29B6A1329F4D for ; Sat, 8 Dec 2018 21:38:01 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C4E4069F9C; Sat, 8 Dec 2018 21:38:00 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id B45CE34CB; Sat, 8 Dec 2018 21:38:00 +0000 (UTC) From: Jan Beich To: Kevin Oberman Cc: greg@unrelenting.technology, yuripv@yuripv.net, "freebsd-x11\@freebsd.org" Subject: Re: [CFT] Mesa 18.3.0 update (mesa-libs, mesa-dri, libosmesa, clover) References: <790ba1cb-7251-e8b3-f7a3-6de3cdee9958@yuripv.net> <8t11-v5xg-wny@FreeBSD.org> <1544292716.1907.0@smtp.migadu.com> Date: Sat, 08 Dec 2018 22:37:53 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: 7801969F9E X-Spamd-Result: default: False [-2.91 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; NEURAL_HAM_SHORT(-0.94)[-0.945,0]; ASN(0.00)[asn:10310, ipnet:2001:1900:2254::/48, country:US]; NEURAL_HAM_LONG(-0.97)[-0.970,0] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Dec 2018 21:38:02 -0000 Kevin Oberman writes: > As far as firefox is concerned, I tried running it with the "MOZ" variables > Jan listed, but I still got the same status message in about:support. I > also looked though about:config for relevant settings, but came up blank. That's expected. Environment variables override hardware qualifications. Whether WebRender is actually in-use is decided by Compositing field. WebRender (like WebGL 2) requires OpenGL 3.2+ which SandyBridge supports. If it fails you'd see "unavailable by runtime: WebRender initialization failed". $ MOZ_ACCELERATED=1 MOZ_WEBRENDER=1 firefox --new-instance --profile $(mktemp -dt ffprofile) about:support [...] Features ------------------------------------------------------------------------------ Compositing WebRender ------------------------------------------------------------------------------ WebGL 2 Driver Renderer Intel Open Source Technology Center -- Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) ------------------------------------------------------------------------------ WebGL 2 Driver Version 4.5 (Core Profile) Mesa 18.3.0 ------------------------------------------------------------------------------ [...] Decision Log ------------------------------------------------------------------------------ HW_COMPOSITING blocked by default: Acceleration blocked by platform available by user: Enabled by envvar ------------------------------------------------------------------------------ WEBRENDER opt-in by default: WebRender is an opt-in feature available by user: Force enabled by envvar ------------------------------------------------------------------------------ WEBRENDER_QUALIFIED blocked by env: No qualified hardware ------------------------------------------------------------------------------ If you're curious how fast WebRender is try toggling gfx.webrender.debug.profiler which would enable profiling overlay that shows FPS, CPU/GPU usage, etc.