can I use the display native resolution on vty0 as on any other vty's using KMS ?

nacho Lariguet lariguet at gmail.com
Sat Aug 8 10:41:44 PDT 2020


On Sat, 8 Aug 2020 10:19:41 +0300
"karu.pruun" <karu.pruun at gmail.com> wrote:

> Hello
> 
> The restriction of ttyv0 to max 160 columns is inherent in the
> syscons(4) driver. The man page syscons(4) says this:
> 
> ---
> Please note that ttyv0 is restricted to 160 columns and any setting of
> kern.kms_columns resulting in a higher number of columns will be
> ignored for ttyv0, but applied to other virtual terminals.
> ---
> 
> The reason is that at early boot, memory is tight so ttyv0 is given a
> buffer of certain max size. The size of this buffer is not updated
> afterwards. The other ttyv-s are initialized later, they can allocate
> more memory. Hence the difference between ttyv0 and other ttyv-s.
> 
> I suppose allocating initially a buffer of fixed max size is not
> uncommon at early boot. If I'm seeing it right, FreeBSD restricts
> initial width to max 200 characters, which is possibly updated later.
> DragonFly does not update the ttyv0 buffer; so in principle there is
> room to extend the code to do this.
> 
> Cheers

Thanks for your reply Peeter :) !

I forgot about this one, but now that you are showing it to me again,
I remember seeing this a couple of years ago while testing/installing
free/openBSD and dragonFly. 

I didn't think back then that it was still relevant, since dragonFly
5.4.1 RELEASE was doing fine @ 1920x1200 on ttyv0 on my laptop with
the radeon[kms] driver. I am attaching pictures of this laptop taken
today. Please, check them and let me know what you think about it.

> Peeter
> 
> --
> 
> On Fri, Aug 7, 2020 at 2:15 AM nacho Lariguet <lariguet at gmail.com> wrote:
> >
> > On Thu, 6 Aug 2020 19:28:46 -0300
> > nacho Lariguet <lariguet at gmail.com> wrote:
> >  
> > > On Thu, 6 Aug 2020 18:49:39 -0300
> > > nacho Lariguet <lariguet at gmail.com> wrote:
> > >  
> > > > On Wed, 5 Aug 2020 23:17:37 -0300
> > > > nacho Lariguet <lariguet at gmail.com> wrote:
> > > >  
> > > > > On Sun, 2 Aug 2020 22:43:29 -0300
> > > > > nacho Lariguet <lariguet at gmail.com> wrote:
> > > > >  
> > > > > > With the following configuration
> > > > > > on a Lenovo ThinkCentre Tiny M715q
> > > > > > with an AMD Pro A10/R7 APU installed
> > > > > > hooked through DP to a HP Z-24i LCD (1920x1200 native)
> > > > > > I successfully got 240x75 characters on all virtual terminals
> > > > > > except on vty0 which is stuck at 80x25 (@ 640x480 I guess):
> > > > > >
> > > > > > ... in /boot/loader.conf:
> > > > > >
> > > > > > kern.kms_console=1
> > > > > > kern.kms_columns=-1
> > > > > >
> > > > > > ... in /etc/rc.conf:
> > > > > >
> > > > > > drm_load="yes"
> > > > > > radeon_load="yes"
> > > > > >
> > > > > > allscreens_flags="-t 1800 -h 100 -f 8x16 iso15-thin-8x16 -m off"
> > > > > > allscreens_kbdflags="-l us.iso -r 250.34 -b off"  
> > > > >
> > > > > This is a follow-up:
> > > > >
> > > > > Today I fired-up once again the laptop I last used to check dragonFly (a test-bed) before attempting to install it on the PowerEdge servers.
> > > > >
> > > > > Although it runs 5.4.1-RELEASE it has the same configuration I am running in the newer Lenovo regarding this post, except for the fact that the laptop is booting through BIOS (no uEFI at all) while the Lenovo is booting through uEFI.
> > > > >
> > > > > The laptop has a Radeon video card and loads the radeon[kms] driver as well.
> > > > >
> > > > > - 5.4.1 on the laptop gets me ttyv0 @ 1920x1200 by default
> > > > > - 5.9.# on the Lenovo gets me standard VGA only
> > > > >
> > > > > Obviously something changed between 5.4.1 and 5.9.# because I am now sure not to be configuring anything different.  
> > > >
> > > > This is another follow up:
> > > >
> > > > I think that vty0 is running @ 1920x1200 but not honoring kern.kms_columns=-1 as honored by all other vty's.
> > > > In other words: it seems font scaling is going on on vty0 regardless my setting giving me the impression that is running @ 640x480 or similar. Could it be the case on 5.9.# ?  
> > >
> > > And the last follow up:
> > >
> > > Definitely.
> > > Booting once again with the live image (loading radeon and KMS) gives me 80x25.
> > > But when logged out as root and logged in as intaller I get 240x75.
> > > So it is not a resolution problem; it is already @ 1920x1200 on vty0.
> > > It is root (or any other user I presume) logging in on vty0 and getting 80x25 instead of 240x75 no matter what.  
> >
> > I suspect what I said on my last post is wrong:
> >
> > Examining the installer script (installer.sh):
> >
> >         # Console start sequence:
> >         # - Backend (and all other logging) goes to console (ttyv0)
> >         # - curses frontend starts on ttyv1.
> >         # - Uses vidcontrol -s 2 to switch to ttyv1 once the frontend is up.  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 17104.jpeg
Type: image/jpeg
Size: 1255967 bytes
Desc: not available
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20200808/1e31b16d/attachment-0002.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 17105.jpeg
Type: image/jpeg
Size: 1743201 bytes
Desc: not available
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20200808/1e31b16d/attachment-0003.jpeg>


More information about the Users mailing list