[Bug 263099] vidcontrol(1) -p and -P does not work
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 263099] vidcontrol(1) -p and -P does not work"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 06 Apr 2022 21:33:05 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263099 Tomoaki AOKI <junchoon@dec.sakura.ne.jp> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |junchoon@dec.sakura.ne.jp --- Comment #6 from Tomoaki AOKI <junchoon@dec.sakura.ne.jp> --- (In reply to Chris Hutchinson from comment #5) Are you 100% sure all your hardwares are legacy (non-UEFI) booted? On UEFI, efifb (only usable via vt) is forced and sc is not emulated (by firmware) at all. So nothing can detect legacy (character based) frame buffer on UEFI-booted environment. (For UEFI-capable hardwares with legacy boot ennbled, CSM of UEFI firmware would take care of it, just stop hiding physical text frame buffer or emulate actually-nonexistent hardware, which would be dependent on hardware). It's a limitation of UEFI, not of FreeBSD. So kern.vty=sc on UEFI-booted environment would be ignored and forced vt. On vidcontrol side, discussions would be needed which to capture, graphical frame buffer or vt-internal text buffer. Someone would want images displayed to be captured, that means, texts are also captured as image, not as characters. But OTOH, others would want only texts to be captured as characters. This is like the behaviour with mice driven by moused. -- You are receiving this mail because: You are the assignee for the bug.