System lockup on kldload amdgpu

Greg V greg at unrelenting.technology
Mon Feb 4 17:10:17 UTC 2019



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