Date: Tue, 10 Oct 2017 14:46:33 -0700 From: Pete Wright <pete@nomadlogic.org> To: tbr@acm.org Cc: freebsd-x11@freebsd.org Subject: Re: intro Message-ID: <f259004e-d5b2-0fc4-44d8-23d556fdc7de@nomadlogic.org> In-Reply-To: <c4b3bff7-12a9-c772-7ffa-41710a74e403@gmail.com> References: <f0fb13d6-1d4e-2de8-f3cb-c6976f57fc9f@gmail.com> <696fb5ea-e1bf-d7c2-004a-eb4eb2af43d7@nomadlogic.org> <c4b3bff7-12a9-c772-7ffa-41710a74e403@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f259004e-d5b2-0fc4-44d8-23d556fdc7de>