Date: Fri, 17 Nov 2017 18:19:18 -0800 From: "Chris H" <bsd-lists@bsdforge.com> To: freebsd-x11@FreeBSD.org, Alexey Dokuchaev <danfe@FreeBSD.org>, Andriy Gapon <avg@FreeBSD.org> Subject: Re: nvidia driver Message-ID: <ac46c81d91de4c65062315391a99c14d@ultimatedns.net> In-Reply-To: <aa478dad-b750-b976-852b-ac5b50877502@FreeBSD.org> References: <aa478dad-b750-b976-852b-ac5b50877502@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 17 Nov 2017 12:39:15 +0200 Andriy Gapon <avg@FreeBSD.org> wrote
> I would like to clarify a couple of things about x11/nvidia-driver, because
> they don't seem to be spelled out in the package documentation (pkg-message,
> etc).
>
> First, it seems that the driver requires that syscons (device sc) is compiled
> into the kernel.
That's not *entirely* true. On a new install, I always need to set
the following in loader.conf(5) :
kern.vty=sc
which seems to work. But don'even get me started about booting (u)efi. ;)
> Even if vt is actually used sc still must be present,
> because otherwise the module would fail to load:
> > link_elf_obj: symbol sc_get_softc undefined
>
> Also, from my experiments it seems that switching between X and text consoles
> works only with syscons.
Also been my experience.
> If vt is used then there is a garbage on the screen
> after switching to a text console.
> Is this true?
For me, as well.
>
> Finally, it seems that syscons should not use any VESA ("graphic") modes.
> On my system the screen becomes garbled and neither X nor text consoles are
> usable if I enabled any VESA mode via device hints.
>
> It would be nice to describe these things in pkg-message.
>
> Thanks!
>
> --
> Andriy Gapon
--Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ac46c81d91de4c65062315391a99c14d>