From owner-freebsd-x11@freebsd.org Sat Jan 12 15:31:25 2019 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 4470E14956EE for ; Sat, 12 Jan 2019 15:31:25 +0000 (UTC) (envelope-from greg@unrelenting.technology) 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 651568AFD2 for ; Sat, 12 Jan 2019 15:31:24 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: by mailman.ysv.freebsd.org (Postfix) id 2376C14956ED; Sat, 12 Jan 2019 15:31:24 +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 11E7C14956EC for ; Sat, 12 Jan 2019 15:31:24 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out.migadu.com (out.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.migadu.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 60F2B8AFCA for ; Sat, 12 Jan 2019 15:31:22 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: (Migadu outbound); Sat, 12 Jan 2019 15:31:15 +0000 Received: from [192.168.1.141] ([62.122.208.146]) by out.migadu.com (Haraka/2.8.16) with ESMTPSA id 16D1CBC1-B6FC-41EE-A0EA-231603C62975.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 verify=FAIL); Sat, 12 Jan 2019 15:31:13 +0000 Date: Sat, 12 Jan 2019 18:31:14 +0300 From: Greg V Subject: Re: Xwayland: i965_dri.so does not support the 0xffffffff PCI ID To: Jan Beich Cc: x11@freebsd.org Message-Id: <1547307074.35085.0@smtp.migadu.com> In-Reply-To: References: X-Mailer: geary/lite-gnome~g3766af013824-dirty MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; bh=qoStAimTo6xHxRI66QTxbXQ/XIT8/KzbBYcp89XVO68=; c=relaxed/simple; d=unrelenting.technology; h=from:subject:date:to; s=default; b=Nsg3saHnGjegwGNKD6VuuwypTED8ts1vQ3FraWV6eX7LBiaHdFkRRUy8RQV+QlbWqIaf/jdyXN7cr8npc/7I8xrbQfmptdbn0vJ/ODSC39J+NJHlGCbdd+ZkTWhFz9MKlJJIff6eCFqyab7m2OCV80ogMvnzxolC3kqXwOnEiS4= X-Rspamd-Queue-Id: 60F2B8AFCA X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.97)[-0.966,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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, 12 Jan 2019 15:31:25 -0000 On Sat, Jan 12, 2019 at 2:36 PM, Jan Beich wrote: > I'm new to Wayland. As some applications either don't support Wayland=20 > or > have bugs I'm relying on Xwayland. Unfortunately, Xwayland fails to=20 > pass > device information to Mesa for hardware to be recognized. Any clues? [=85] > [xwayland/xwayland.c:103] WAYLAND_SOCKET=3D18 Xwayland :1 -rootless=20 > -terminate -listen 16 -listen 17 -wm 60 > i965_dri.so does not support the 0xffffffff PCI ID. > Refusing to try glamor on llvmpipe > EGL setup failed, disabling glamor > Failed to initialize glamor, falling back to sw That's weird, I don't remember that kind of issue=85 Driver name detection was fixed in=20 https://gitlab.freedesktop.org/mesa/mesa/commit/db8519a369261cdedda50852fac= c45616d4eba28=20 a long time ago, but that used to happen in the clients and you have=20 i965 detected correctly anyway, it's i965 itself complaining. I used to need to 'export LIBGL_DRI3_ENABLE=3D1' for Xwayland apps to=20 work (not sure why I don't anymore, maybe because my build of Mesa=20 doesn't have the patch from ports that shuffles some DRI3 defaults=20 around, if that patch is still there). But again, that's for apps =97 I=20 don't think driver loading ever failed in the Xwayland server itself. There's a permissions bug in drm-kmod that results in Xwayland windows=20 being invisible for me: https://github.com/FreeBSDDesktop/kms-drm/issues/33 but it affects=20 AMDGPU and is not the same kind of problem. I recently saw the exact "ffffffff" message in=20 https://github.com/libretro/RetroArch/issues/7953 (on Linux) =97 the=20 issue was just starting a KMS application inside a Wayland compositor=20 (i.e. a DRM master already existed). Not what's happening here though=85 Google also finds that message in=20 https://github.com/letoram/arcan/issues/129 (but looks like there the=20 compositor itself was failing, not Xwayland) and=20 https://lists.freedesktop.org/archives/wayland-devel/2017-July/034404.html=20 =97 as a workaround you can try the PCI ID override environment=20 variable from that link. =