Date: Sat, 24 Aug 2019 11:29:50 +0300 From: Greg V <greg@unrelenting.technology> To: freebsd-current@freebsd.org, "Clay Daniels Jr." <clay.daniels.jr@gmail.com>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: "amdgpu and radeonkms are known to fail with EFI Boot" Message-ID: <F131C0ED-A0F1-45CA-AFA4-CBC516C96607@unrelenting.technology> In-Reply-To: <CAGLDxTW8mKUhQZwtamFZ5SNULPPSqAB9CE7QumHE4EUc%2Bfk5yw@mail.gmail.com> References: <CAGLDxTW8mKUhQZwtamFZ5SNULPPSqAB9CE7QumHE4EUc%2Bfk5yw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On August 24, 2019 10:15:22 AM GMT+03:00, "Clay Daniels Jr=2E" <clay=2Edani= els=2Ejr@gmail=2Ecom> wrote: >From the kmod ports, dated 20190814 > > >/usr/ports/graphics/drm-current-kmod/pkg-descr > >"amdgpu and radeonkms are known to fail with EFI Boot" > > >/usr/ports/graphics/drm-current-kmod/pkg-message > >"some positive reports if EFI is not enabled" > > >Any practical suggestions on getting drm-current-kmod to work on an AMD >machine, including how to NOT enable EFI? I did not see that option on >the >install menu=2E "Not enabling" EFI means booting the installer in legacy more (CSM)=2E Ins= taller images are universal, so you'd have to instruct the firmware to igno= re the EFI loader on there=2E Deleting the EFI partition might work I guess= =2E rEFInd can force CSM boot a USB drive=2E I do not recommend this=2E Instead, there is a workaround for the EFI fram= ebuffer conflict=2E If you have it (i=2Ee=2E amdgpu fails to load, or hangs= when starting GUI), boot with hw=2Esyscons=2Edisable=3D1=2E You won't see = anything on the screen after the boot loader and before loading the driver = :) but that's not a big deal when the driver autoloads successfully=2E
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F131C0ED-A0F1-45CA-AFA4-CBC516C96607>