System lockup on kldload amdgpu
Phil Norman
philnorm at gmail.com
Wed Feb 6 22:30:53 UTC 2019
Just to follow up for the record: I now have amdgpu being loaded from
/etc/rc.conf, and it seems to be running stably so far. Thanks for the help.
On Mon, 4 Feb 2019 at 18:10, Greg V <greg at unrelenting.technology> wrote:
>
>
> On Mon, Feb 4, 2019 at 2:39 PM, Phil Norman <philnorm at gmail.com> wrote:
> > Hi.
> >
> > Finally got around to trying this out. The interesting thing is that
> > 'hw.syscons.disable=1' disables (as seems obvious from the name) the
> > system console. That means after a few boot messages, I got nothing
> > more from the console. However, I managed to login remotely and
> > kldload amdgpu, which made the console work again (although it looks
> > unusual).
>
> Yep, that's kinda the point — the problem it's fixing is that our
> amdgpu for some reason conflicts with the EFI framebuffer.
>
> Now you just set up the rc.conf to autoload amdgpu, and it's all
> "normal" — you see garbage in between the bootloader and amdgpu
> loading of course :)
>
>
>
More information about the freebsd-x11
mailing list