Date: Wed, 6 Feb 2019 23:30:38 +0100 From: Phil Norman <philnorm@gmail.com> To: Greg V <greg@unrelenting.technology> Cc: Pete Wright <pete@nomadlogic.org>, freebsd-x11@freebsd.org Subject: Re: System lockup on kldload amdgpu Message-ID: <CAOa8eG6r_0n=V_8PU=8=kaWttdB%2BcELSyCnJwJASzZsCnnL-Ag@mail.gmail.com> In-Reply-To: <1549300213.5098.0@smtp.migadu.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> <1549300213.5098.0@smtp.migadu.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@unrelenting.technology> wrote: > > > On Mon, Feb 4, 2019 at 2:39 PM, Phil Norman <philnorm@gmail.com> wrote: > > Hi. > > > > Finally got around to trying this out. The interesting thing is that > > 'hw.syscons.disable=3D1' 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 =E2=80=94 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" =E2=80=94 you see garbage in between the bootloader and amdgpu > loading of course :) > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOa8eG6r_0n=V_8PU=8=kaWttdB%2BcELSyCnJwJASzZsCnnL-Ag>