Date: Mon, 04 Feb 2019 20:10:13 +0300 From: Greg V <greg@unrelenting.technology> To: Phil Norman <philnorm@gmail.com> Cc: Pete Wright <pete@nomadlogic.org>, freebsd-x11@freebsd.org Subject: Re: System lockup on kldload amdgpu Message-ID: <1549300213.5098.0@smtp.migadu.com> In-Reply-To: <CAOa8eG5S5zydkfxjqKBXGJwWsnr1zEGo_eej-6vv_2-mgPNKBA@mail.gmail.com> References: <CAOa8eG5FQ4M=O-cqCnV5kq%2BdTSbF3fpjSQM-iyNZ84KSvTYsyw@mail.gmail.com> <1549052728.1799.0@smtp.migadu.com> <c46c7310-87f6-a624-9f93-b200c4b1b17f@nomadlogic.org> <CAOa8eG5S5zydkfxjqKBXGJwWsnr1zEGo_eej-6vv_2-mgPNKBA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 4, 2019 at 2:39 PM, Phil Norman <philnorm@gmail.com> wrote: > Hi. >=20 > Finally got around to trying this out. The interesting thing is that=20 > 'hw.syscons.disable=3D1' disables (as seems obvious from the name) the=20 > system console. That means after a few boot messages, I got nothing=20 > more from the console. However, I managed to login remotely and=20 > kldload amdgpu, which made the console work again (although it looks=20 > unusual). Yep, that's kinda the point =97 the problem it's fixing is that our=20 amdgpu for some reason conflicts with the EFI framebuffer. Now you just set up the rc.conf to autoload amdgpu, and it's all=20 "normal" =97 you see garbage in between the bootloader and amdgpu=20 loading of course :) =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1549300213.5098.0>