Date: Sun, 19 Oct 2014 20:37:34 +0200 From: =?windows-1252?Q?Jean-S=E9bastien_P=E9dron?= <dumbbell@FreeBSD.org> To: freebsd-stable@freebsd.org Subject: Re: vt(4) "newcons" and 80x25 vty? (tested: 10.1-BETA2) Message-ID: <544404EE.6070609@FreeBSD.org> In-Reply-To: <2ac3ccbb9ede61a99b0306107ad3846b.squirrel@s4bysmmsnraf7eut.onion> References: <4490c8c4d489370c7617c0ace9e773be.squirrel@s4bysmmsnraf7eut.onion> <op.xmq3dipokndu52@82-171-231-144.ip.telfort.nl> <3d80542ccc73686094ddde4e18465e4a.squirrel@s4bysmmsnraf7eut.onion> <2ac3ccbb9ede61a99b0306107ad3846b.squirrel@s4bysmmsnraf7eut.onion>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --a509DLANpDlBRteA30Qk9iBIOhUmfLCJr Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi! On 29.09.2014 06:20, beeessdee@ruggedinbox.com wrote: > * hw.vga.textmode=3D1 not affect situation with kms driver loaded: Tin= y > characters, much too many lines/cols. Correct: loading a video driver changes the video mode to the "preferred" mode (usually the screen native resolution). > * VT in VGA textmode fonts loading broken (tested 10.1-BETA2). Tried > vidfont(1) and also vidcontrol -f [size] [filename]. For loading "VGA"= > fonts, screen weird/unusable (see below). For loading Gallant (12x22),= > the virtual terminal freeze (both other vty still ok). Still correct: there's a bug here. In VGA text mode, loading a font should be rejected. The purpose of text mode is to let the video card draw the text itself. > Obvious the 12x22 font (as gallant) will not expect working in > "textmode". And does not work (hangs vty). As stated in previous mail= , > with kms driver vidfont(1) has bug prevent gallant load (but vidcontrol= > -f works). I didn't know this vidfont(1) tool and obviously never tested it. This tools must be revisited for vt(4). Regarding your initial problem, yes, we still have work to do to allow a user to configure a readable font. This is known issue. Unfortunately, it won't make it to 10.1-RELEASE as you mentionned. --=20 Jean-S=E9bastien P=E9dron --a509DLANpDlBRteA30Qk9iBIOhUmfLCJr Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJURATyXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NzA4N0ZEMUFFQUUwRTEyREJDNkE2RjAz OUU5OTc2MUE1RkQ5NENDAAoJEDnpl2Gl/ZTM/CsQAJ0kpXcVd+GOfe54Mmk9TBj0 pWC+BQDOwm2lecx+EmpR66a7DriJ47mO3YaQvTnDhKAMVJ6f1IYCLU2E5WlDM2eM +HaG75+rs4Pm+knTcmwphLCMwH8CdYfvYHW68DJ8B2MNHUudrE288zymmpYgVlYh 2t8d6TJEbU2M13LkfOht+0NX6LMIvUCN37rRhyYFKdueLcZEJL9Myy091/Rb3dfz W4n4xax0k0FfGEFrzu8cmlY+WhUrMqMuEolznqnA7xzZFaAQiR1Z8ZI2RgGTQiLw zJSJc9PJgTRaADQ5FJYydD27EezZ1koicqstoE6jm5IpXv3dnN15cZdt832bDeqK xZ3GiD9eJqN87pQdaii3BRvoRaYn+/Wq11OnGdGQwBLZUhyt662UAIVwPKNecElM V7SEC3eC8FpT2NyNbnRRBN0GghL+B7A3U5jhS7DGm8itLlyezCHciRnL+H5oG9+r 1go7zV7eTpTxlc5HmjP+MBOiPVjXqA4pGAWrhNd80bG72zEj08CckYAjytrH2Udd Xk6kCcnGYW1M97nSjldsleYSbKXcEl4tQUqeFmICnlSOwyCK2oZeQO8acF3gcFBi wrjSLICMSLBUQgqa5I/Y8zpzWVt9ToeByIQsa1k3TVWHMH5mc5sNq6lqUbR666Kg GaYiiyn+HOczBw570n/3 =epcM -----END PGP SIGNATURE----- --a509DLANpDlBRteA30Qk9iBIOhUmfLCJr--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?544404EE.6070609>