From owner-freebsd-x11@freebsd.org Tue Oct 10 21:46:35 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 DA5D3E3E38B for ; Tue, 10 Oct 2017 21:46:35 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [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 BD0626E884 for ; Tue, 10 Oct 2017 21:46:35 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [10.44.139.75] (nat-192-187-90-114.nat.tribpub.com [192.187.90.114]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id e483a0df TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 10 Oct 2017 14:46:35 -0700 (PDT) Subject: Re: intro To: tbr@acm.org Cc: freebsd-x11@freebsd.org References: <696fb5ea-e1bf-d7c2-004a-eb4eb2af43d7@nomadlogic.org> From: Pete Wright Message-ID: Date: Tue, 10 Oct 2017 14:46:33 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.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-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, 10 Oct 2017 21:46:36 -0000 On 10/10/2017 14:34, Tom Rushworth wrote: > >> >> If you are wanting to run vanilla FreeBSD and don't mind periodic >> instability you can also run 12-CURRENT and install the "drm-next-kmod" >> pkg.  Although depending on how much time you want to put into hacking >> on things TrueOS may be an easier entry point for you. > > I don't mind CURRENT as long as the parts I'm using work :).  Doug > Kirk also pointed me at the graphics/drm-next-kmod port, which I'd > guess needs something close to CURRENT as well. > > I'll give both suggestions a try over the weekend and report back. i can verify that drm-next-kmod works on CURRENT as I'm dog-fooding it right now on a kabylake laptop and skylake desktop system :) i've been suggesting people give TrueOS a spin first to verify their gfx hardware is supported and working as expected. one of the nice things with both TrueOS and CURRENT is that once Xorg and drm-next-kmod is installed you don't need to configure xorg.conf - autodetection "just works" afaict. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA