Date: Sun, 28 Nov 2021 11:43:44 -0500 From: Ed Maste <emaste@freebsd.org> To: FreeBSD Hackers <freebsd-hackers@freebsd.org> Cc: Emmanuel Vadot <manu@bidouilliste.com>, Stefan Blachmann <sblachmann@gmail.com> Subject: Re: Reasons for keeping sc(4) and libvgl ? Message-ID: <CAPyFy2DVuWQ==9yaYuMZoEqTVTK7vr_PvtKVqGHcJAvnBS5gqQ@mail.gmail.com> In-Reply-To: <CACc-My0%2B5zi9bsMpLWsOMmP8uiatTCBiJcvkOAS_3%2BXfrNWMvQ@mail.gmail.com> References: <20211126160454.3eb827365a02103169ab9adc@bidouilliste.com> <CACc-My0%2B5zi9bsMpLWsOMmP8uiatTCBiJcvkOAS_3%2BXfrNWMvQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 26 Nov 2021 at 10:45, Stefan Blachmann <sblachmann@gmail.com> wrote: > > Main technical reasons why I consider sc(4) essential: > > - vt/vesa.ko break suspend/resume on nvidia cards. To make > suspend/resume work on computers with nvidia, it is necessary to build > a kernel *without* vt/vesa modules. See > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253733 To wrap up this one - this is an issue with `options VESA` / vesa.ko. It is not related to vt(4), which does not use that VESA driver. I have removed `options VESA` from GENERIC now in b8cf1c5c30a5. It serves no purpose when vt(4) is in use, and the kernel module is still available for sc(4) users who want to set a VBE mode. As an aside, the loader can set a VBE mode and vt(4) will make use of that, it just does not support mode changing after boot.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2DVuWQ==9yaYuMZoEqTVTK7vr_PvtKVqGHcJAvnBS5gqQ>