can I use the display native resolution on vty0 as on any other vty's using KMS ?
nacho Lariguet
lariguet at gmail.com
Mon Aug 10 10:56:11 PDT 2020
On Mon, 10 Aug 2020 14:37:14 +0300
"karu.pruun" <karu.pruun at gmail.com> wrote:
> Hello
>
> I should clarify that when you load the drm driver (i915 or radeon, as
> root on the console using 'kldload i915' or 'kldload radeon') the
> initial buffer restriction does not apply any more. The drm drivers
> allocate their own framebuffers, so all ttyv-s will have the same
> column x row configuration.
Gotcha.
> In the pre-drm situation, as explained earlier, the system tries to
> work out an optimal column x row configuration based on the
> information it gets from BIOS or UEFI. In the case of BIOS, you get
> VGA modes; we don't have VESA at the moment, yet, if I'm correct. In
> the case of UEFI, the system gets the resolution from UEFI and then
> tries to work out the best column x row configuration under the
> restriction that it must be max 160 column x 50 rows, font width is 8
> and the final configuration must preserve font scaling. For instance,
> on my laptop this works out precisely as described:
>
> - UEFI tells the resolution is 1680x1050 (X x Y)
> - Font width is 8
> - 1680 / 8 = 210, too large
> - increase font width x 2
> - 1680 / 16 = 105, yes under 160
> - 1050 / 32 (font height is 16) = 32.8, round to nearest int, this is
> 32; yes it's under 50
> - final setup: 105x32
CRYSTAL CLEAR.
Is it possible right now to end up in a pre-DRM situation by default ?
IIRC kern.kms_console now defaults to 1 (don't know since when it does).
But for a moment suppose kern.kms_console still defaults to 0: if I boot
the liveCD via uEFI without changing anything I should end up in the
pre-DRM situation as following:
For the uEFI pre-DRM situation with no loader variables I should get:
uEFI @ 1920x1200 with font-size=8 -> 1920/8=240 -> 1920/16=120 -> 120x37
... which is under 160x50 but I'm still getting 80x25 on ttyv0 on 5.9.#
Back to 5.9.# defaults: The liveCD starts @ 1920x1200 without doing
anything before, so it is clear that uEFI is informing 1920x1200 right
now to begin with. Everything I do on the loader screen (ie: choosing a
boot mode, setting boot options, etc) is done at 1920x1200. It is after
the REGENTS jargon message that the resolution is lowered on ttyv0.
> The 105x32 is exactly what I get by default on my laptop if I set no
> loader variables.
>
> I am not sure what if anything has changed between DragonFly 5.4 and
> master. The syscons driver I believe is exactly the same. The BIOS and
> UEFI setups would give different results though.
>
> I suggest you try to calculate the column x row configuration as
> described above. In UEFI setup, you can see the modes as follows: at
> boot, go to boot prompt (press '9'), and then do 'gop list' to see
> what modes UEFI gives you. You can set the mode there too. (Give 'gop'
> to see the command.) Enter 'boot' to continue booting. I guess you can
> set the desired mode by default via a boot loader variable; but I
> don't know what it would be.
Will reboot tonight after finishing some installation/configuration
scripts I am currently at, and let you know what I get from gop.
Furthermore, this 'gop list' thing is something that I am eagerly to try
on my PowerEdge servers to see what's going on there in order to gather
what the hell is going on after the boot loader screen because I never
manage to see even the REGENTS message. It is like the servers are
booting the kernel but I can't manage to see the system console for
whatever reasons and I early interpreted this situation as panic which
obviously is not. But one step at a time. First I have to set this tiny
desktop running.
> The graphical target etc stuff is linux speak, and probably systemd;
> it has no relevance at all for DragonFly.
I was advised to use "isolate graphical.target as in CentOS" but I do
know (even with my bare knowledge on the nixes so far) that this fix
is totally out-of-scope. This fix is X-stack related.
> Hope this helps.
It helps ... a LOT.
Your reply was VERY informative.
Thanks very much for your time Peeter, I'll keep you posted :) !
> Peeter
>
> --
>
> On Mon, Aug 10, 2020 at 1:33 AM nacho Lariguet <lariguet at gmail.com> wrote:
> >
> > On Sun, 9 Aug 2020 13:53:22 -0700
> > Jonathan Engwall <engwalljonathanthereal at gmail.com> wrote:
> >
> > > On Sun, Aug 9, 2020, 12:00 PM <users-request at dragonflybsd.org> wrote:
> > >
> > > > Send Users mailing list submissions to
> > > > users at dragonflybsd.org
> > > >
> > > > To subscribe or unsubscribe via the World Wide Web, visit
> > > > http://lists.dragonflybsd.org/mailman/listinfo/users
> > > > or, via email, send a message with subject or body 'help' to
> > > > users-request at dragonflybsd.org
> > > >
> > > > You can reach the person managing the list at
> > > > users-owner at dragonflybsd.org
> > > >
> > > > When replying, please edit your Subject line so it is more specific
> > > > than "Re: Contents of Users digest..."
> > > >
> > > >
> > > > Today's Topics:
> > > >
> > > > 1. Re: can I use the display native resolution on vty0 as on any
> > > > other vty's using KMS ? (nacho Lariguet)
> > > > 2. how do I label (meaning adding a reminder caption) to any
> > > > given BSD slice ? (nacho Lariguet)
> > > >
> > > >
> > > > ----------------------------------------------------------------------
> > > >
> > > > Message: 1
> > > > Date: Sat, 8 Aug 2020 18:06:14 -0300
> > > > From: nacho Lariguet <lariguet at gmail.com>
> > > > To: users at dragonflybsd.org
> > > > Subject: Re: can I use the display native resolution on vty0 as on any
> > > > other vty's using KMS ?
> > > > Message-ID: <20200808180614.66f67761 at leonov>
> > > > Content-Type: text/plain; charset=US-ASCII
> > > >
> > > > On Sat, 8 Aug 2020 11:26:35 -0700
> > > > Jonathan Engwall <engwalljonathanthereal at gmail.com> wrote:
> > > >
> > > > > Your picture looks to me like the standard "UNIX multi-user mode" perhaps
> > > > > you should select a graphical target somehow. Are making a multi-head
> > > > boot,
> > > > > or bringing up each tty simultaneously?
> > > > > Jonathan Engwall
> > > >
> > > > ... standard "UNIX multi-user mode" ... sure: do I did try/ask for
> > > > anything else ?
> > > >
> > > > I'm afraid I'm not following
> > > >
> > >
> > > Your photo shows the BSD/UNIX default to boot to a root system
> > > administrator account. To change this you will need to boot to a graphical
> > > target, or launch a multi head, or something relevant to what you are doing.
> > > I don't know what you are doing. Maybe puppet would work for you?
> > > Jonathan Engwall
> >
> > OK. Let me be more clear.
> >
> > I want to start using dragonFly ... daily.
> >
> > So the first step is to install it on the hardware that for whatever reasons
> > I currently have, get it running without major issues, and last but not least,
> > set a working environment that suits my needs, which ends in the following fact:
> >
> > What I want is dragonFly running ... WITHOUT X11 !
> >
> > I just want to develop and work with/on the system console, which in our case,
> > happens to be syscons since we still don't have vt/wcons/whatever which means
> > no native UTF-8 console for the time being.
> >
> > I feel comfortable working/developing without a major stack like X because:
> >
> > - I'm learning BSD and the best way to learn something like this is bottom to top
> > not the other way around. This is exactly what I've done with arch-linux some years
> > ago, I just installed a barebones system and from then on I kept learning and
> > needless to say I learned a lot of thinks of linux inner workings which I doubt
> > I could have learned with the zillion packages required by X and any given desktop
> > environment with all their complexity and all the duplicacte functionality. Prior
> > to start using linux I developed for many many years on, yes, Microsoft products
> > and whatnot. Eventually moving to linux was so alien that I wanted to start, I say
> > it again: bottom to top, not the other way around.
> >
> > - That said, I eventually want to move my primary workstation to dragonFly and a
> > couple of servers, and I decided, wisely or not, that I want to move one server
> > first because the server won't need X etc etc and albeit being a file/web server
> > to begin with, it will give me a working environment so I can start coding in BSD,
> > meaning primarily C.
> >
> > - Everything I need to code do not requires X at all: just a working system console.
> > I learned to use VIM in the past few years and feels quite comfortably with it
> > meaning I totally customized it (even I coded many syntax files from scratch), and
> > in my arch linux console environment I have everything I want to.
> >
> > That will give you a detailed overview of what I am after with dragonFly.
> >
> > I need a couple of things:
> >
> > - digital video at max resolution: 1920x1200 in my case ... got it on my test-bed
> > desktop and will attempt to get it running on my PowerEdge servers in a couple of
> > days I guess.
> >
> > - a working US international keyboard layout (us-acentos) ... still not working
> >
> > - a UTF-8 native console ... I know I should give up on this if I want to use this OS
> >
> > - a custom script in CSH to execute after booting a liveCD that formats/installs/
> > configures everything as needed ... almost done, testing it right now.
> >
> > From there on I'm planing to use what for whatever reasons I am currently using in arch:
> >
> > - BIND
> > - nginx
> > - postgreSQL
> >
> > Nothing special, all are in dPorts and I can customize and recompile them as needed.
> >
> > WHEN I get this server working I will start fiddling with X11 on my future BSD workstation.
> >
> > Sorry if this answer was a bit long but I hope you'll understand where I am standing
> > right now.
> >
> > > I don't know what you are doing. Maybe puppet would work for you?
> >
> > I'll eventually get it running with/without your support.
> >
> > Thanks for your advice, and I mean it.
> >
> > PS: You will note that I am asking a lot of questions on the mailing list, I read the man
> > pages, always, that won't mean that some thing can goes unnoticed to me at any given time
> > or that simply I just forgot about some x detail I read before, there's a LOT to learn
> > and the fact that I am asking is because I am a NEWBIE to BSD in general and I want to
> > learn, nothing out of the ordinary I guess. If that irritates you just ignore me. I will
> > be fine.
> >
> > > >
> > > >
> > > > ------------------------------
> > > >
> > > > Message: 2
> > > > Date: Sun, 9 Aug 2020 15:04:42 -0300
> > > > From: nacho Lariguet <lariguet at gmail.com>
> > > > To: dragonFlyBSD user list <users at dragonflybsd.org>
> > > > Subject: how do I label (meaning adding a reminder caption) to any
> > > > given BSD slice ?
> > > > Message-ID: <20200809150442.7f5bc89d at leonov>
> > > > Content-Type: text/plain; charset=US-ASCII
> > > >
> > > > ie: the "label:" field shown under the "diskid:" one with disklabel64
> > > >
> > > > It seems there is no switch (maybe -l) on disklabel64 (when using -w) to
> > > > label a slice.
> > > >
> > > > eg:
> > > >
> > > > # /dev/da0s1:
> > > > #
> > > > # Calculated informational fields for the slice:
> > > > #
> > > > # boot space: 1044480 bytes
> > > > # data space: 175691776 blocks # 171574.00 MB (179908378624 bytes)
> > > > #
> > > > # NOTE: The partition data base and stop are physically
> > > > # aligned instead of slice-relative aligned.
> > > > #
> > > > # All byte equivalent offsets must be aligned.
> > > > #
> > > > diskid: af1b4686-d85d-11ea-9373-012324e2aca4
> > > > label: ... HOW TO SET THIS ONE ?
> > > > boot2 data base: 0x000000001000
> > > > partitions data base: 0x000000100000
> > > > partitions data stop: 0x0029e3700000
> > > > backup label: 0x0029e37ff000
> > > > total size: 0x0029e3800000 # 171576.00 MB
> > > > alignment: 4096
> > > > display block size: 1024 # for partition display and edit only
> > > >
> > > > 16 partitions:
> > > > # size offset fstype fsuuid
> > > > a: 1048576 0 4.2BSD # 1024.000MB
> > > > d: 33554432 1048576 HAMMER2 # 32768.000MB
> > > > e: 134217728 34603008 HAMMER2 # 131072.000MB
> > > > f: 6871040 168820736 HAMMER2 # 6710.000MB
> > > > a-stor_uuid: eb61372a-d85d-11ea-9373-012324e2aca4
> > > > d-stor_uuid: eb613733-d85d-11ea-9373-012324e2aca4
> > > > e-stor_uuid: eb613739-d85d-11ea-9373-012324e2aca4
> > > > f-stor_uuid: eb61373e-d85d-11ea-9373-012324e2aca4
> > > >
> > > >
> > > > ------------------------------
> > > >
> > > > Subject: Digest Footer
> > > >
> > > > _______________________________________________
> > > > Users mailing list
> > > > Users at dragonflybsd.org
> > > > http://lists.dragonflybsd.org/mailman/listinfo/users
> > > >
> > > >
> > > > ------------------------------
> > > >
> > > > End of Users Digest, Vol 96, Issue 10
> > > > *************************************
> > > >
> >
More information about the Users
mailing list