Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Aug 2019 14:55:14 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        "Clay Daniels Jr." <clay.daniels.jr@gmail.com>
Cc:        Greg V <greg@unrelenting.technology>,  "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject:   Re: "amdgpu and radeonkms are known to fail with EFI Boot"
Message-ID:  <CANCZdfqap-a8MEuDgQQnCVEM=HR%2B8V6iZttKhO2OzFhfLBk26A@mail.gmail.com>
In-Reply-To: <CAGLDxTVv8psVGeKzWJzp-tHvxkX34sdEPqzAUOJhxNx%2BvGHsFA@mail.gmail.com>
References:  <CAGLDxTW8mKUhQZwtamFZ5SNULPPSqAB9CE7QumHE4EUc%2Bfk5yw@mail.gmail.com> <F131C0ED-A0F1-45CA-AFA4-CBC516C96607@unrelenting.technology> <CAGLDxTVv8psVGeKzWJzp-tHvxkX34sdEPqzAUOJhxNx%2BvGHsFA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Aug 24, 2019 at 2:06 PM Clay Daniels Jr. <clay.daniels.jr@gmail.com>
wrote:

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

Two places: (1) /boot/loader.conf (2) where-ever the docs say there is a
conflict with EFI :)

Warner


> Thanks
> Clay
>
> On Sat, Aug 24, 2019 at 3:29 AM Greg V <greg@unrelenting.technology>
> wrote:
>
> > On August 24, 2019 10:15:22 AM GMT+03:00, "Clay Daniels Jr." <
> > clay.daniels.jr@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.
> >
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqap-a8MEuDgQQnCVEM=HR%2B8V6iZttKhO2OzFhfLBk26A>