Date: Sun, 15 Sep 2019 19:15:51 -0700 From: Pete Wright <pete@nomadlogic.org> To: CSO@riseup.net, "Clay Daniels Jr." <clay.daniels.jr@gmail.com> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: AMD & 13.0 Current Message-ID: <8a8de0ac-ad49-3ce6-65f5-ddcbdf6a658f@nomadlogic.org> In-Reply-To: <20190915231435.GA27796@whitehouse.gov> References: <CAGLDxTWQeAj_m1kgrCCG1HpnkHR9wVNFDVBUE3q5d9zwu0cMHw@mail.gmail.com> <20190915231435.GA27796@whitehouse.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/15/19 4:14 PM, CSO@riseup.net wrote: > >> The other thing to note, is that for 13.0 Current they both need a line in >> /boot/loader.conf: >> hw.syscons..disable=1 > Why is this line needed and for what purposes? This issue, and the one it links to, go a bit towards describing the issue: https://github.com/FreeBSDDesktop/kms-drm/issues/127 I have to use the workaround as well, which isn't ideal to be honest, but i just think due to the other higher priority tasks it hasn't been addressed yet. > > Does the new hardware in this new build also work well in FreeBSD 12 > stable branch? The FreeBSD current is for testing purposes so we are > very interested in how it the above mentioned new hardware work on > stable or production version. I run both CURRENT and 12.0-RELEASE on Ryzen with amdgpu graphics and they work fine. I actually use AWS instances that have the AMD Epyc CPU installed and those work great as well - so i def feel like AMD is becoming relevant again on both desktop and servers :) -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8a8de0ac-ad49-3ce6-65f5-ddcbdf6a658f>