Date: Thu, 12 Mar 2020 11:29:01 -0700 From: Pete Wright <pete@nomadlogic.org> To: Jan Beich <jbeich@FreeBSD.org> Cc: "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org> Subject: Re: xwayland issue with i965_dri.so Message-ID: <f026e50f-da42-3dca-8a34-ef6de1923ea9@nomadlogic.org> In-Reply-To: <3b0b4275-e2be-09f7-45b4-5a84f45f7636@nomadlogic.org> References: <7bfd39a6-3236-c0f9-04d9-e8ecaeb15ca5@nomadlogic.org> <ftee-m8ol-wny@FreeBSD.org> <3b0b4275-e2be-09f7-45b4-5a84f45f7636@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/12/20 8:54 AM, Pete Wright wrote: > > > On 2020-03-11 22:41, Jan Beich wrote: >> Pete Wright <pete@nomadlogic.org> writes: >> >>> hello - i've discussed this on irc but wanted to move it to email for >>> wider exposure (and also providing myself with notes i can refer to >>> later). >>> >>> i am able to launch sway on my i915 intel laptop running 12-STABLE >>> without any issues, and i am able to run xfce4-terminal in native >>> wayland more which is great! yet i notice this from the output from >>> sway: >>> >>> i965_dri.so does not support the 0xffffffff PCI ID. >> This error comes from Mesa. >> >>> Refusing to try glamor on llvmpipe >>> EGL setup failed, disabling glamor >>> Failed to initialize glamor, falling back to sw >>> >>> >>> i believe this is causing problems with starting Xorg apps via >>> xwayland, for example chrome and firefox crash on startup. i did some >>> googling and it looks like Jan ran into this problem a while back: >>> http://freebsd.1045724.x6.nabble.com/Xwayland-i965-dri-so-does-not-support-the-0xffffffff-PCI-ID-td6307408.html >>> >> I also had https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241821 >> which did reappear for some time but not anymore. >> >> What FreeBSD kernel are you running? Makes sure you have >> https://reviews.freebsd.org/D23846 as it may affect more than just >> Vulkan in Mesa. > Thanks for the tip on the outdated linux kernel, it does look like > kernel didn't have that patch for the linuxkpi - rebuilding now and > will update thread if this fixes things. > hrm unfortunately running latest kernel from the STABLE branch didn't fix this, nor did using the mesa-dri-19.0.x branch from the freebsddesktop-ports github repo. maybe someone who is more familiar with mesa can point me in the right direction to see why this bogus pciID is being passed? -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f026e50f-da42-3dca-8a34-ef6de1923ea9>