Date: Thu, 9 Dec 2021 13:29:19 -0500 From: Ed Maste <emaste@freebsd.org> To: Peter <pmc@citylink.dinoex.sub.org> Cc: freebsd-stable stable <freebsd-stable@freebsd.org> Subject: Re: 12.3: vt driver does not provide virtual console terminals Message-ID: <CAPyFy2DbWAxcy3cTtVG2jA7kAW-f=h5=yR=vCa0YMCtE9=3kgg@mail.gmail.com> In-Reply-To: <YauxafdwpxwHmaaU@gate.intra.daemon.contact> References: <YauxafdwpxwHmaaU@gate.intra.daemon.contact>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 4 Dec 2021 at 13:27, Peter <pmc@citylink.dinoex.sub.org> wrote: > > There is also this error reported: > > module_register_init: MOD_LOAD (vesa, 0xffffffff80e22c00, 0) error 19 Are you trying to load vesa.ko via /boot/loader.conf or /etc/rc.d kld_list, or is this observed without any vesa-specific configuration? > This one is widely discussed as currently not supported by vt driver, but > this should be related to higher resolution screen, and not virtual > terminals missing. Or has it something to do with each other, and is > it a known problem? It is not a known problem, and I believe it should be unrelated to the MOD_LOAD error. You can try running `pgrep -fl getty` to confirm that getty(8) is running on each of the vtys.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2DbWAxcy3cTtVG2jA7kAW-f=h5=yR=vCa0YMCtE9=3kgg>