From owner-freebsd-x11@freebsd.org Thu Mar 12 15:54:15 2020 Return-Path: Delivered-To: freebsd-x11@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 68E932643E3 for ; Thu, 12 Mar 2020 15:54:15 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48dYKd55Dqz3yp1; Thu, 12 Mar 2020 15:54:13 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.141] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id c8e62867 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Thu, 12 Mar 2020 15:54:11 +0000 (UTC) Subject: Re: xwayland issue with i965_dri.so To: Jan Beich Cc: "freebsd-x11@freebsd.org" References: <7bfd39a6-3236-c0f9-04d9-e8ecaeb15ca5@nomadlogic.org> From: Pete Wright Message-ID: <3b0b4275-e2be-09f7-45b4-5a84f45f7636@nomadlogic.org> Date: Thu, 12 Mar 2020 08:54:11 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 48dYKd55Dqz3yp1 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 174.136.98.114 as permitted sender) smtp.mailfrom=pete@nomadlogic.org X-Spamd-Result: default: False [-5.06 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RECEIVED_SPAMHAUS_PBL(0.00)[239.162.243.23.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; IP_SCORE(-2.76)[ip: (-9.30), ipnet: 174.136.96.0/20(-4.07), asn: 25795(-0.39), country: US(-0.05)]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-0.99)[-0.995,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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: Thu, 12 Mar 2020 15:54:15 -0000 On 2020-03-11 22:41, Jan Beich wrote: > Pete Wright 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. cheers! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA