Re: "amdgpu and radeonkms are known to fail with EFI Boot"

From: Greg V <greg_at_unrelenting.technology>
Date: Sat, 24 Aug 2019 11:29:50 +0300
On August 24, 2019 10:15:22 AM GMT+03:00, "Clay Daniels Jr." <clay.daniels.jr_at_gmail.com> 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.

"Not enabling" EFI means booting the installer in legacy more (CSM). Installer images are universal, so you'd have to instruct the firmware to ignore the EFI loader on there. Deleting the EFI partition might work I guess. rEFInd can force CSM boot a USB drive.

I do not recommend this. Instead, there is a workaround for the EFI framebuffer conflict. If you have it (i.e. amdgpu fails to load, or hangs when starting GUI), boot with hw.syscons.disable=1. 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.
Received on Sat Aug 24 2019 - 06:29:59 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:21 UTC