From owner-freebsd-x11@freebsd.org Tue Jan 24 21:07:42 2017 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1423BCBD3D2 for ; Tue, 24 Jan 2017 21:07:42 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E400D330 for ; Tue, 24 Jan 2017 21:07:41 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [IPv6:2605:e000:1313:b3:223:24ff:fea8:4fb5] (2605:e000:1313:b3:223:24ff:fea8:4fb5 [IPv6:2605:e000:1313:b3:223:24ff:fea8:4fb5]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 42278362 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Tue, 24 Jan 2017 13:07:40 -0800 (PST) Subject: Re: CFT upgrade to xorg 1.18.4 and newer intel/ati DDX To: freebsd-x11@freebsd.org References: <20170123235516.o5lvu3sfwq5r5tsq@ivaldir.etoilebsd.net> <20170124095555.13772b01@freedom.alkumuna.eu> <20170124202627.268bdaa0@freedom.alkumuna.eu> <219ebae8-5fa4-fe9c-9746-06132a4f5af7@nomadlogic.org> From: Pete Wright Message-ID: <1ef21ded-b5f3-efdf-61de-f33007dbc23a@nomadlogic.org> Date: Tue, 24 Jan 2017 13:07:35 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <219ebae8-5fa4-fe9c-9746-06132a4f5af7@nomadlogic.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2017 21:07:42 -0000 On 01/24/2017 11:31, Pete Wright wrote: > > > On 01/24/2017 11:26, Matthieu Volat wrote: >> On Tue, 24 Jan 2017 11:12:56 -0800 >> Pete Wright wrote: >> >>> On 01/24/2017 00:55, Matthieu Volat wrote: >>>> On Tue, 24 Jan 2017 00:55:16 +0100 >>>> Baptiste Daroussin wrote: >>>> >>>>> Hi all, >>>>> >>>>> This is a call for testing for newer Xorg along with newer >>>>> drivers: intel and >>>>> ati. >>>>> >>>>> The patch against the head ports: >>>>> https://people.freebsd.org/~bapt/newxorg.diff >>>>> >>>>> Note that you would need to rebuild all the xf86-* packages to >>>>> work with that >>>>> newer xorg (hence the bump of the revision) >>>>> >>>>> Do not expect newer gpu supported as this is not the kernel part. >>>>> >>>>> If you experience any issue with intel or radeon driver please try >>>>> to use the >>>>> new modesetting driver provided by xorg directly (note that fedora >>>>> and debian >>>>> recommands to use that new driver instead of the ati/intel one) >>>>> >>>>> To use that driver: >>>>> >>>>> cat /usr/local/etc/xorg.conf.d/modesetting.conf >>>>> Section "Device" >>>>> Identifier "Card0" >>>>> Driver "modesetting" >>>>> EndSection >>>>> >>>>> You need to first load the kms driver eiter via loader.conf or >>>>> manually via >>>>> kldload >>>>> >>>>> Best regards, >>>>> Bapt of behalf of the X11 team >>>> Looks good with x11/nvidia driver! >>> Hi Matthieu - did you run into any issues building components from >>> x11-drivers? specifically i'm running into this error when attempting >>> to build x11-drivers/xf86-input-mouse x11-drivers/xf86-video-vesa >>> (among >>> others): >>> >>> from vesa build log: >>> >>> checking if DPMSExtension is defined... yes >>> checking for XORG... no >>> configure: error: Package requirements (xorg-server >= 1.6 xproto >>> fontsproto randrproto renderproto xextproto) were not met: >>> >>> Package dri3proto was not found in the pkg-config search path. >>> Perhaps you should add the directory containing `dri3proto.pc' >>> to the PKG_CONFIG_PATH environment variable >>> Package 'dri3proto', required by 'xorg-server', not found >>> >>> >>> Consider adjusting the PKG_CONFIG_PATH environment variable if you >>> installed software in a non-standard prefix. >>> >>> >>> It's odd because xorg-server built fine as did dri3proto - so I'm not >>> sure why its not being picked up by poudriere when i attempt to build >>> these packages. >>> >>> Cheers! >>> -pete >>> >> Hmm, I did not have the issue when I rebuilt ports, but you're right: >> it seems that dri3proto should be added to ${PORTSDIR}/Mk/bsd.xorg.mk >> line 61 USE_XORG flags... >> >> I think I missed the problem since xorg-server must have brought the >> dependancy that was not removed from my system until I ran "pkg >> autoremove". > > hey thanks for getting back to me, and teaching me a bit more about > our ports infrastructure :) > > that def seemed to fix 'er up - here is a diff: > > $ diff -u bsd.xorg.mk.bak bsd.xorg.mk > --- bsd.xorg.mk.bak 2017-01-24 11:27:44.998639000 -0800 > +++ bsd.xorg.mk 2017-01-24 11:28:16.089046000 -0800 > @@ -59,8 +59,8 @@ > > . if ${XORG_CAT} == "driver" > USE_XORG+= xorg-server xproto randrproto xi renderproto xextproto \ > - inputproto kbproto fontsproto videoproto dri2proto > xf86driproto \ > - presentproto glproto xineramaproto resourceproto > scrnsaverproto > + inputproto kbproto fontsproto videoproto dri2proto > dri3proto xf86driproto \ > + presentproto glproto xineramaproto resourceproto > scrnsaverproto > # work around a llvm bug on i386, llvm bug #15806 > # reproduced with clang 3.2 (current release) and 3.1 > . if ${ARCH} == i386 to close the loop on this. after applying the above patch all dependencies compiled without issue on my end. i have upgraded xorg to 1.18.4 on my end against the drm-next branch and it's working pretty good. my hardware is an intel Skylake with Intel HD Graphics 530. I am seeing acceleration using modesetting + glamor which was not working for me with earlier releases, although there seems to be font corruption issue I'll need to chase down. I am also able to use the xf86-video-intel driver and that does not cause font corruption using SNA. I will dogfood intel+SNA for a bit then try to see if I can isolate the font corruption issue with glamor. Cheers! -pete