Date: Sat, 12 Jan 2019 18:31:14 +0300 From: Greg V <greg@unrelenting.technology> To: Jan Beich <jbeich@FreeBSD.org> Cc: x11@freebsd.org Subject: Re: Xwayland: i965_dri.so does not support the 0xffffffff PCI ID Message-ID: <1547307074.35085.0@smtp.migadu.com> In-Reply-To: <zhs6-f6qn-wny@FreeBSD.org> References: <zhs6-f6qn-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 12, 2019 at 2:36 PM, Jan Beich <jbeich@FreeBSD.org> 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. =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1547307074.35085.0>