Date: Thu, 28 Jan 2021 09:33:52 +0200 From: Toomas Soome <tsoome@me.com> To: Jesper Schmitz Mouridsen <jsm@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: vidcontrol < /dev/console -i active ioctl error Message-ID: <C9F632C5-F1A9-4AF8-8163-EA08C848B94A@me.com> In-Reply-To: <e94429f7-efd1-80a1-7541-78a0b67a156b@FreeBSD.org> References: <e94429f7-efd1-80a1-7541-78a0b67a156b@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 28. Jan 2021, at 01:35, Jesper Schmitz Mouridsen <jsm@FreeBSD.org> = wrote: >=20 > FreeBSD build.freebsd.lan 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #0 = main-c255938-g7ae27c2d6c4: Thu Jan 14 06:29:55 UTC 2021 = root@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC = amd64 > jesper@build:~ $ su > Password: > root@build:~ # vidcontrol < /dev/console -i active > vidcontrol: getting active vty: Inappropriate ioctl for device >=20 > build is virtualized in bhyve, it happens as well on my pinebook pro. >=20 > This is annoying to sysutils/consolekit2 >=20 > on 12.2 it works (not tested on same HW) >=20 it should work for local console: root@freebsd:/usr/src # vidcontrol -i active < /dev/console 1 may it be your =E2=80=9Cprimary=E2=80=9D is actually serial console? rgds, toomas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C9F632C5-F1A9-4AF8-8163-EA08C848B94A>