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

Greg, thanks for the wonderful suggestion. Where should I put this line: "
hw.syscons.disable=1 "
I tried it in /etc/rc.conf and it booted into the console as usual with
repeated messages:
/etc/rc.conf  hw.syscons.disable=1: not found
I could login to the console as usual, but trying to run startx (as user)
still fails. Maybe there is some boot config file this goes in?

Thanks
Clay

On Sat, Aug 24, 2019 at 3:29 AM Greg V <greg_at_unrelenting.technology> wrote:

> 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.
>