Re: 12.3: vt driver does not provide virtual console terminals

On Thu, Dec 09, 2021 at 01:29:19PM -0500, Ed Maste wrote:
! 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?

I verified now:

I can reproduce the message with GENERIC 12.3 (id 70cb68e7a00,
local patches removed), and no loader.conf. It appears before
filesytems are mounted, so /etc/rc.d is irrelevant.

Trying to load vesa.ko from loader.conf or from the loader prompt
produces the same error message and then fails to boot with "vesa not
found".

A kernel with "device vesa" added does boot, but also produces the
message.

Doing "kldload vesa.ko" in single-user gives the same error message,
and additionally:
> sysctl_unregister_oid: failed(22) to unregister sysctl(vesa)

! > 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.

Yes they are running. I can also redirect output to the ttyv*, and
that works, only the output does not appear on the screens.


cheerio,
PMc