vt driver

when EFI booting my x250 Thinkpad into 14.3-RELEASE. I have the resolution during boot via /boot/loader.confexec="gop set 2" # during boot, 800x600x32 kern.vt.color.0.rgb="#303000" kern.vt.color.15.rgb="#00f000" kern.vt.fb.default_mode="640x480x16" # has no effect But not on the virtual...

When switching between vt terminals from X using Ctrl-Alt-F#, the keyboard partially locks up. Ctrl-Alt-F# and arrow keys still work, but terminal console input can't be typed in, unless, I switch from another terminal console first with Ctrl-Alt-F#. This has been an issue since from previous...

I've recently been bouncing between 14.3-RELEASE and 15.0-CURRENT BE's. It's pretty great. After my latest reboot my VT text is like...HUGE. It is HUGE before the boot menu and it's HUGE after (pic below). My logic holds that this can't be related to the kernel I'm using because this...

I'm playing around with Unicode and was wondering: Can the vt console handle Unicode combining characters? I did not find them mentioned in the man page, so I suspect the answer is "no". But maybe I'm missing something. Can anyone clarify?

When setting the resolution for two monitors to "1024x768" or to "1280x720" (720p) the desired effect takes place, /boot/loader.conf kern.vt.fb.default_mode="1280x720" but the following error message repeats, which can also be seen with dmesg: drmn0: [drm] User-defined mode not supported...

Hi folks, I have freebsd 14.2 installed on intel alderlake i5-12400 (integrated graphics). Recently I am keeping getting the below messages in dmesg drmn0: [drm] User-defined mode not supported: "1024x768": 75 78750 1024 1040 1136 1312 768 769 772 800 0x60 0x5 I have the below line in my...

Hello, I have a machine with 2 displays. When X session is not yet started, one of the displays remains inactive while the other shows a console. I use FreeBSD 10.3 with UEFI loader and vt console driver. It is smart enough to autodetect the display's native resolution (a line from dmesg)...

On 10.2-RELEASE, I quickly discovered that if I bring up X and want to go to a virtual console by pressing, say <Alt><F2>, I need to place into /boot/loader.conf: kern.vty=vtI discovered an unpleasant side effect, though. When I go from X to a virtual console, I don't get the old-fashioned...