System lockup on kldload amdgpu
Phil Norman
philnorm at gmail.com
Mon Feb 4 17:05:06 UTC 2019
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).
I'm now running X11 through my onboard amdgpu - so thanks a lot for helping
me get up and running :-)
And thanks Pete for fixing the wiki page.
Thanks,
Phil
On Fri, 1 Feb 2019 at 21:54, Pete Wright <pete at nomadlogic.org> wrote:
>
>
> On 2/1/19 12:25 PM, Greg V wrote:
> >
> >
> > On Thu, Jan 31, 2019 at 10:39 PM, Phil Norman <philnorm at gmail.com>
> wrote:
> >> Hi.
> >>
> >> I have a Ryzen 2400G (built-in Vega graphics), and am trying to get it
> >> working with x11 (on FreeBSD 12.0-STABLE r343112 GENERIC amd64). Pete
> >> Wright has been helping me out with instructions (over on
> >> freebsd-stable@),
> >> and so far I've got as far as installing drm-kmod, and setting
> >> 'hw.sysconf.disable=1' in /boot/loader.conf.
> >
> > syscons !!! not sysconF. I think I've seen that typo in the github
> > issue tracker before.
> >
> oh man that's a nasty typo - thanks for pointing it out! I've amended
> the Graphics wiki accordingly.
>
> cheers,
> -pete
>
> --
> Pete Wright
> pete at nomadlogic.org
> @nomadlogicLA
>
>
More information about the freebsd-x11
mailing list