Re: Reasons for keeping sc(4) and libvgl ?

On Thu, Jun 23, 2022 at 1:44 AM Cejka Rudolf <cejkar@fit.vutbr.cz> wrote:

> Hello,
>   so is there any solution for problem below now?
>
> Cejka Rudolf wrote (2021/11/29):
> > Hello,
> >   I have one problem or two with VT in FreeBSD 12. I wrote a question in
> > freebsd-stable what to do, but without response, so I still have to
> > use SC. Please, could you look at it? There is not configured device
> > /dev/console without monitor after upgrade from 11 to 12 and device
> > /dev/kbdmux0 is busy using VT but not with SC.
> >
> > Subject: Unable to grab keyboard with VT on a headless node in stable/12
> >
> > Hello,
> >   I have a headless node without monitor and without keyboard. There
> > is just network and USB card reader in keyboard mode.
> >
> > In stable/11, there was no problem to disconnect USB card reader
> > from kbdmux using kbdcontrol -A ukbd0 < /dev/console and open
> > /dev/ukbd0 in a program.
> >
> > However, under stable/12 it works just with connected monitor.
> >
> > Without monitor, there is an error:
> >
> > # kbdcontrol < /dev/console
> > -bash: /dev/console: Device not configured
> >
> > Furthermore with default VT, it is also impossible to use /dev/kbdmux0:
> >
> > # kbdcontrol < /dev/kbdmux0
> > -bash: /dev/kbdmux0: Device busy
> >
> > I have found a workaround using SC, where it is possible to atleast
> > open /dev/kbdmux0 and use kbdcontrol -A ukbd0 < /dev/kbdmux0, but why
> > keyboard operation is now dependend on connected monitor? And why VT
> > does not allow to open /dev/kbdmux0?
> >
> > Thank you.
>

Have you filed a bug for this? This looks like a legit bug and one that
should be easy(ish) to reproduce.
Or at least it looks that way on the surface, there might be a pilot error
as well that just happened to
work before and needs a slightly different workaround to what you are
doing...

And it's an actual monitor connected that's the only difference? Or is this
some KVM switch that's
connected, so there's an atkbd in the mix somewhere? What's the difference
in dmesg between
these two boots? Is this with EFI or legacy BIOS boot?

'Not conifgured' is ENXIO which is returned when /dev/console isn't there
(eg, no /dev/console), which
seems weird in the extreme. And it's 'bash' that's giving the message,
which means kbdcontrol isn't
even getting invoked. A dmesg with bootverbose would be most enligtening.

And I'm also a little confused, detach ukbd0 from a usb card reader? That's
an interesting setup. While
it won't affect whether or not this is a bug, I'd be interested to know
more details there...

Warner