<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Aug 11, 2020 at 11:26 AM <<a href="mailto:users-request@dragonflybsd.org">users-request@dragonflybsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send Users mailing list submissions to<br>
<a href="mailto:users@dragonflybsd.org" target="_blank">users@dragonflybsd.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.dragonflybsd.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.dragonflybsd.org/mailman/listinfo/users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:users-request@dragonflybsd.org" target="_blank">users-request@dragonflybsd.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:users-owner@dragonflybsd.org" target="_blank">users-owner@dragonflybsd.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: can I use the display native resolution on vty0 as on any<br>
other vty's using KMS ? (karu.pruun)<br>
2. Re: can I use the display native resolution on vty0 as on any<br>
other vty's using KMS ? (Jasse Jansson)<br>
3. Re: can I use the display native resolution on vty0 as on any<br>
other vty's using KMS ? (nacho Lariguet)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 11 Aug 2020 11:18:34 +0300<br>
From: "karu.pruun" <<a href="mailto:karu.pruun@gmail.com" target="_blank">karu.pruun@gmail.com</a>><br>
To: nacho Lariguet <<a href="mailto:lariguet@gmail.com" target="_blank">lariguet@gmail.com</a>><br>
Cc: dragonFlyBSD user list <<a href="mailto:users@dragonflybsd.org" target="_blank">users@dragonflybsd.org</a>><br>
Subject: Re: can I use the display native resolution on vty0 as on any<br>
other vty's using KMS ?<br>
Message-ID:<br>
<CADdF=MK=<a href="mailto:ZCY4U-v6wj0JZ842QFNdBtQQXqCP3Z1RHdfr7roKrQ@mail.gmail.com" target="_blank">ZCY4U-v6wj0JZ842QFNdBtQQXqCP3Z1RHdfr7roKrQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
Hello<br>
<br>
> Is it possible right now to end up in a pre-DRM situation by default ?<br>
> IIRC kern.kms_console now defaults to 1 (don't know since when it does).<br>
<br>
The terminology here is a little confusing. I used pre-drm to mean<br>
"until a drm driver (i915 or radeon) is loaded". Let me try to clarify<br>
booting.<br>
<br>
The first screen with the boot menu is displayed by the loader. The<br>
kernel modules to load by the loader are given in<br>
<br>
/boot/loader.conf<br>
<br>
However, the official advice is that the loader load the absolute<br>
required minimum of kernel modules. For instance, my loader.conf has<br>
no modules. This is because memory is tight at that early stage. If<br>
you include, e.g. a drm driver, i915 or radeon, then the kernel will<br>
most likely crash at boot.<br>
<br>
The official advice is to load modules later by placing them in<br>
/etc/rc.conf, for instance,<br>
<br>
i915_load="YES"<br>
<br>
I have all the required wlan, drm etc there. And you can also load the<br>
drm modules manually on console using 'kldload i915'.<br>
<br>
This means that, for instance, if I choose to load the drm driver<br>
manually then I'm in the pre-drm stage until I will have kldloaded it,<br>
say, on console, manually. The copyright note (the "Regents" screen<br>
you mention), this is the kernel starting to load. This is pre-drm,<br>
there is no drm driver anywhere. This is either VGA or the UEFI<br>
display. The terminology "kms_columns" is misleading; that variable is<br>
read by the system to try to figure out column x row configuration,<br>
but there is no drm driver anywhere. That same "kms_columns" is also<br>
read later by the drm driver to set the column x row configuration.<br>
<br>
So long story short: it is all pre-drm until the drm driver is<br>
literally kldloaded.<br>
<br>
The screen change you see when going from loader to kernel loading<br>
(the copyright, "Regents" note), there is no resolution change. The<br>
resolution is the same as on the loader screen, it has been set by<br>
UEFI. What you notice though is the change of font size. Between these<br>
two screens, the system has done the calculation described in the<br>
previous email, set the new column x row configuration, which is<br>
larger than what you have in the UEFI screen; but there is no change<br>
in resolution. Or perhaps there is slight change since it tries to<br>
allocate a buffer that covers most of the screen.<br>
<br>
I may have missed details, maybe someone can clarify more.<br>
<br>
Cheers<br>
<br>
Peeter<br>
<br>
--<br>
<br>
On Tue, Aug 11, 2020 at 1:41 AM nacho Lariguet <<a href="mailto:lariguet@gmail.com" target="_blank">lariguet@gmail.com</a>> wrote:<br>
><br>
> On Mon, 10 Aug 2020 14:37:14 +0300<br>
> "karu.pruun" <<a href="mailto:karu.pruun@gmail.com" target="_blank">karu.pruun@gmail.com</a>> wrote:<br>
><br>
> I'm attaching the output of "gop list" as mentioned before.<br>
><br>
> You can clearly see that it boots straight to 1920x1200 right from the<br>
> liveCD. So uEFI is informing 1920x1200 capability without any doubt.<br>
><br>
> When it gets to the REGENTS message, it switches to a lower resolution.<br>
><br>
> PS: I keep forgetting to CC the users list: sorry to reply twice Peeter<br>
><br>
> > Hello<br>
> ><br>
> > I should clarify that when you load the drm driver (i915 or radeon, as<br>
> > root on the console using 'kldload i915' or 'kldload radeon') the<br>
> > initial buffer restriction does not apply any more. The drm drivers<br>
> > allocate their own framebuffers, so all ttyv-s will have the same<br>
> > column x row configuration.<br>
> ><br>
> > In the pre-drm situation, as explained earlier, the system tries to<br>
> > work out an optimal column x row configuration based on the<br>
> > information it gets from BIOS or UEFI. In the case of BIOS, you get<br>
> > VGA modes; we don't have VESA at the moment, yet, if I'm correct. In<br>
> > the case of UEFI, the system gets the resolution from UEFI and then<br>
> > tries to work out the best column x row configuration under the<br>
> > restriction that it must be max 160 column x 50 rows, font width is 8<br>
> > and the final configuration must preserve font scaling. For instance,<br>
> > on my laptop this works out precisely as described:<br>
> ><br>
> > - UEFI tells the resolution is 1680x1050 (X x Y)<br>
> > - Font width is 8<br>
> > - 1680 / 8 = 210, too large<br>
> > - increase font width x 2<br>
> > - 1680 / 16 = 105, yes under 160<br>
> > - 1050 / 32 (font height is 16) = 32.8, round to nearest int, this is<br>
> > 32; yes it's under 50<br>
> > - final setup: 105x32<br>
> ><br>
> > The 105x32 is exactly what I get by default on my laptop if I set no<br>
> > loader variables.<br>
> ><br>
> > I am not sure what if anything has changed between DragonFly 5.4 and<br>
> > master. The syscons driver I believe is exactly the same. The BIOS and<br>
> > UEFI setups would give different results though.<br>
> ><br>
> > I suggest you try to calculate the column x row configuration as<br>
> > described above. In UEFI setup, you can see the modes as follows: at<br>
> > boot, go to boot prompt (press '9'), and then do 'gop list' to see<br>
> > what modes UEFI gives you. You can set the mode there too. (Give 'gop'<br>
> > to see the command.) Enter 'boot' to continue booting. I guess you can<br>
> > set the desired mode by default via a boot loader variable; but I<br>
> > don't know what it would be.<br>
> ><br>
> > The graphical target etc stuff is linux speak, and probably systemd;<br>
> > it has no relevance at all for DragonFly.<br>
> ><br>
> > Hope this helps.<br>
> ><br>
> > Peeter<br>
> ><br>
> > --<br>
> ><br>
> > On Mon, Aug 10, 2020 at 1:33 AM nacho Lariguet <<a href="mailto:lariguet@gmail.com" target="_blank">lariguet@gmail.com</a>> wrote:<br>
> > ><br>
> > > On Sun, 9 Aug 2020 13:53:22 -0700<br>
> > > Jonathan Engwall <<a href="mailto:engwalljonathanthereal@gmail.com" target="_blank">engwalljonathanthereal@gmail.com</a>> wrote:<br>
> > ><br>
> > > > On Sun, Aug 9, 2020, 12:00 PM <<a href="mailto:users-request@dragonflybsd.org" target="_blank">users-request@dragonflybsd.org</a>> wrote:<br>
> > > ><br>
> > > > > Send Users mailing list submissions to<br>
> > > > > <a href="mailto:users@dragonflybsd.org" target="_blank">users@dragonflybsd.org</a><br>
> > > > ><br>
> > > > > To subscribe or unsubscribe via the World Wide Web, visit<br>
> > > > > <a href="http://lists.dragonflybsd.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.dragonflybsd.org/mailman/listinfo/users</a><br>
> > > > > or, via email, send a message with subject or body 'help' to<br>
> > > > > <a href="mailto:users-request@dragonflybsd.org" target="_blank">users-request@dragonflybsd.org</a><br>
> > > > ><br>
> > > > > You can reach the person managing the list at<br>
> > > > > <a href="mailto:users-owner@dragonflybsd.org" target="_blank">users-owner@dragonflybsd.org</a><br>
> > > > ><br>
> > > > > When replying, please edit your Subject line so it is more specific<br>
> > > > > than "Re: Contents of Users digest..."<br>
> > > > ><br>
> > > > ><br>
> > > > > Today's Topics:<br>
> > > > ><br>
> > > > > 1. Re: can I use the display native resolution on vty0 as on any<br>
> > > > > other vty's using KMS ? (nacho Lariguet)<br>
> > > > > 2. how do I label (meaning adding a reminder caption) to any<br>
> > > > > given BSD slice ? (nacho Lariguet)<br>
> > > > ><br>
> > > > ><br>
> > > > > ----------------------------------------------------------------------<br>
> > > > ><br>
> > > > > Message: 1<br>
> > > > > Date: Sat, 8 Aug 2020 18:06:14 -0300<br>
> > > > > From: nacho Lariguet <<a href="mailto:lariguet@gmail.com" target="_blank">lariguet@gmail.com</a>><br>
> > > > > To: <a href="mailto:users@dragonflybsd.org" target="_blank">users@dragonflybsd.org</a><br>
> > > > > Subject: Re: can I use the display native resolution on vty0 as on any<br>
> > > > > other vty's using KMS ?<br>
> > > > > Message-ID: <20200808180614.66f67761@leonov><br>
> > > > > Content-Type: text/plain; charset=US-ASCII<br>
> > > > ><br>
> > > > > On Sat, 8 Aug 2020 11:26:35 -0700<br>
> > > > > Jonathan Engwall <<a href="mailto:engwalljonathanthereal@gmail.com" target="_blank">engwalljonathanthereal@gmail.com</a>> wrote:<br>
> > > > ><br>
> > > > > > Your picture looks to me like the standard "UNIX multi-user mode" perhaps<br>
> > > > > > you should select a graphical target somehow. Are making a multi-head<br>
> > > > > boot,<br>
> > > > > > or bringing up each tty simultaneously?<br>
> > > > > > Jonathan Engwall<br>
> > > > ><br>
> > > > > ... standard "UNIX multi-user mode" ... sure: do I did try/ask for<br>
> > > > > anything else ?<br>
> > > > ><br>
> > > > > I'm afraid I'm not following<br>
> > > > ><br>
> > > ><br>
> > > > Your photo shows the BSD/UNIX default to boot to a root system<br>
> > > > administrator account. To change this you will need to boot to a graphical<br>
> > > > target, or launch a multi head, or something relevant to what you are doing.<br>
> > > > I don't know what you are doing. Maybe puppet would work for you?<br>
> > > > Jonathan Engwall<br>
> > ><br>
> > > OK. Let me be more clear.<br>
> > ><br>
> > > I want to start using dragonFly ... daily.<br>
> > ><br>
> > > So the first step is to install it on the hardware that for whatever reasons<br>
> > > I currently have, get it running without major issues, and last but not least,<br>
> > > set a working environment that suits my needs, which ends in the following fact:<br>
> > ><br>
> > > What I want is dragonFly running ... WITHOUT X11 !<br>
> > ><br>
> > > I just want to develop and work with/on the system console, which in our case,<br>
> > > happens to be syscons since we still don't have vt/wcons/whatever which means<br>
> > > no native UTF-8 console for the time being.<br>
> > ><br>
> > > I feel comfortable working/developing without a major stack like X because:<br>
> > ><br>
> > > - I'm learning BSD and the best way to learn something like this is bottom to top<br>
> > > not the other way around. This is exactly what I've done with arch-linux some years<br>
> > > ago, I just installed a barebones system and from then on I kept learning and<br>
> > > needless to say I learned a lot of thinks of linux inner workings which I doubt<br>
> > > I could have learned with the zillion packages required by X and any given desktop<br>
> > > environment with all their complexity and all the duplicacte functionality. Prior<br>
> > > to start using linux I developed for many many years on, yes, Microsoft products<br>
> > > and whatnot. Eventually moving to linux was so alien that I wanted to start, I say<br>
> > > it again: bottom to top, not the other way around.<br>
> > ><br>
> > > - That said, I eventually want to move my primary workstation to dragonFly and a<br>
> > > couple of servers, and I decided, wisely or not, that I want to move one server<br>
> > > first because the server won't need X etc etc and albeit being a file/web server<br>
> > > to begin with, it will give me a working environment so I can start coding in BSD,<br>
> > > meaning primarily C.<br>
> > ><br>
> > > - Everything I need to code do not requires X at all: just a working system console.<br>
> > > I learned to use VIM in the past few years and feels quite comfortably with it<br>
> > > meaning I totally customized it (even I coded many syntax files from scratch), and<br>
> > > in my arch linux console environment I have everything I want to.<br>
> > ><br>
> > > That will give you a detailed overview of what I am after with dragonFly.<br>
> > ><br>
> > > I need a couple of things:<br>
> > ><br>
> > > - digital video at max resolution: 1920x1200 in my case ... got it on my test-bed<br>
> > > desktop and will attempt to get it running on my PowerEdge servers in a couple of<br>
> > > days I guess.<br>
> > ><br>
> > > - a working US international keyboard layout (us-acentos) ... still not working<br>
> > ><br>
> > > - a UTF-8 native console ... I know I should give up on this if I want to use this OS<br>
> > ><br>
> > > - a custom script in CSH to execute after booting a liveCD that formats/installs/<br>
> > > configures everything as needed ... almost done, testing it right now.<br>
> > ><br>
> > > From there on I'm planing to use what for whatever reasons I am currently using in arch:<br>
> > ><br>
> > > - BIND<br>
> > > - nginx<br>
> > > - postgreSQL<br>
> > ><br>
> > > Nothing special, all are in dPorts and I can customize and recompile them as needed.<br>
> > ><br>
> > > WHEN I get this server working I will start fiddling with X11 on my future BSD workstation.<br>
> > ><br>
> > > Sorry if this answer was a bit long but I hope you'll understand where I am standing<br>
> > > right now.<br>
> > ><br>
> > > > I don't know what you are doing. Maybe puppet would work for you?<br>
> > ><br>
> > > I'll eventually get it running with/without your support.<br>
> > ><br>
> > > Thanks for your advice, and I mean it.<br>
> > ><br>
> > > PS: You will note that I am asking a lot of questions on the mailing list, I read the man<br>
> > > pages, always, that won't mean that some thing can goes unnoticed to me at any given time<br>
> > > or that simply I just forgot about some x detail I read before, there's a LOT to learn<br>
> > > and the fact that I am asking is because I am a NEWBIE to BSD in general and I want to<br>
> > > learn, nothing out of the ordinary I guess. If that irritates you just ignore me. I will<br>
> > > be fine.<br>
> > ><br>
> > > > ><br>
> > > > ><br>
> > > > > ------------------------------<br>
> > > > ><br>
> > > > > Message: 2<br>
> > > > > Date: Sun, 9 Aug 2020 15:04:42 -0300<br>
> > > > > From: nacho Lariguet <<a href="mailto:lariguet@gmail.com" target="_blank">lariguet@gmail.com</a>><br>
> > > > > To: dragonFlyBSD user list <<a href="mailto:users@dragonflybsd.org" target="_blank">users@dragonflybsd.org</a>><br>
> > > > > Subject: how do I label (meaning adding a reminder caption) to any<br>
> > > > > given BSD slice ?<br>
> > > > > Message-ID: <20200809150442.7f5bc89d@leonov><br>
> > > > > Content-Type: text/plain; charset=US-ASCII<br>
> > > > ><br>
> > > > > ie: the "label:" field shown under the "diskid:" one with disklabel64<br>
> > > > ><br>
> > > > > It seems there is no switch (maybe -l) on disklabel64 (when using -w) to<br>
> > > > > label a slice.<br>
> > > > ><br>
> > > > > eg:<br>
> > > > ><br>
> > > > > # /dev/da0s1:<br>
> > > > > #<br>
> > > > > # Calculated informational fields for the slice:<br>
> > > > > #<br>
> > > > > # boot space: 1044480 bytes<br>
> > > > > # data space: 175691776 blocks # 171574.00 MB (179908378624 bytes)<br>
> > > > > #<br>
> > > > > # NOTE: The partition data base and stop are physically<br>
> > > > > # aligned instead of slice-relative aligned.<br>
> > > > > #<br>
> > > > > # All byte equivalent offsets must be aligned.<br>
> > > > > #<br>
> > > > > diskid: af1b4686-d85d-11ea-9373-012324e2aca4<br>
> > > > > label: ... HOW TO SET THIS ONE ?<br>
> > > > > boot2 data base: 0x000000001000<br>
> > > > > partitions data base: 0x000000100000<br>
> > > > > partitions data stop: 0x0029e3700000<br>
> > > > > backup label: 0x0029e37ff000<br>
> > > > > total size: 0x0029e3800000 # 171576.00 MB<br>
> > > > > alignment: 4096<br>
> > > > > display block size: 1024 # for partition display and edit only<br>
> > > > ><br>
> > > > > 16 partitions:<br>
> > > > > # size offset fstype fsuuid<br>
> > > > > a: 1048576 0 4.2BSD # 1024.000MB<br>
> > > > > d: 33554432 1048576 HAMMER2 # 32768.000MB<br>
> > > > > e: 134217728 34603008 HAMMER2 # 131072.000MB<br>
> > > > > f: 6871040 168820736 HAMMER2 # 6710.000MB<br>
> > > > > a-stor_uuid: eb61372a-d85d-11ea-9373-012324e2aca4<br>
> > > > > d-stor_uuid: eb613733-d85d-11ea-9373-012324e2aca4<br>
> > > > > e-stor_uuid: eb613739-d85d-11ea-9373-012324e2aca4<br>
> > > > > f-stor_uuid: eb61373e-d85d-11ea-9373-012324e2aca4<br>
> > > > ><br>
> > > > ><br>
> > > > > ------------------------------<br>
> > > > ><br>
> > > > > Subject: Digest Footer<br>
> > > > ><br>
> > > > > _______________________________________________<br>
> > > > > Users mailing list<br>
> > > > > <a href="mailto:Users@dragonflybsd.org" target="_blank">Users@dragonflybsd.org</a><br>
> > > > > <a href="http://lists.dragonflybsd.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.dragonflybsd.org/mailman/listinfo/users</a><br>
> > > > ><br>
> > > > ><br>
> > > > > ------------------------------<br>
> > > > ><br>
> > > > > End of Users Digest, Vol 96, Issue 10<br>
> > > > > *************************************<br>
> > > > ><br>
> > ><br>
><br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 11 Aug 2020 16:47:49 +0200<br>
From: Jasse Jansson <<a href="mailto:jasse@yberwaffe.com" target="_blank">jasse@yberwaffe.com</a>><br>
To: <a href="mailto:users@dragonflybsd.org" target="_blank">users@dragonflybsd.org</a><br>
Subject: Re: can I use the display native resolution on vty0 as on any<br>
other vty's using KMS ?<br>
Message-ID: <<a href="mailto:ee7bfe84-4c7c-e729-742d-59072fc612d5@yberwaffe.com" target="_blank">ee7bfe84-4c7c-e729-742d-59072fc612d5@yberwaffe.com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
<br>
On 2020-08-11 10:18, karu.pruun wrote:<br>
> Hello<br>
><br>
>> Is it possible right now to end up in a pre-DRM situation by default ?<br>
>> IIRC kern.kms_console now defaults to 1 (don't know since when it does).<br>
> The terminology here is a little confusing. I used pre-drm to mean<br>
> "until a drm driver (i915 or radeon) is loaded". Let me try to clarify<br>
> booting.<br>
><br>
> The first screen with the boot menu is displayed by the loader. The<br>
> kernel modules to load by the loader are given in<br>
><br>
> /boot/loader.conf<br>
><br>
> However, the official advice is that the loader load the absolute<br>
> required minimum of kernel modules. For instance, my loader.conf has<br>
> no modules. This is because memory is tight at that early stage. If<br>
> you include, e.g. a drm driver, i915 or radeon, then the kernel will<br>
> most likely crash at boot.<br>
><br>
> The official advice is to load modules later by placing them in<br>
> /etc/rc.conf, for instance,<br>
><br>
> i915_load="YES"<br>
><br>
> I have all the required wlan, drm etc there. And you can also load the<br>
> drm modules manually on console using 'kldload i915'.<br>
><br>
> This means that, for instance, if I choose to load the drm driver<br>
> manually then I'm in the pre-drm stage until I will have kldloaded it,<br>
> say, on console, manually. The copyright note (the "Regents" screen<br>
> you mention), this is the kernel starting to load. This is pre-drm,<br>
> there is no drm driver anywhere. This is either VGA or the UEFI<br>
> display. The terminology "kms_columns" is misleading; that variable is<br>
> read by the system to try to figure out column x row configuration,<br>
> but there is no drm driver anywhere. That same "kms_columns" is also<br>
> read later by the drm driver to set the column x row configuration.<br>
><br>
> So long story short: it is all pre-drm until the drm driver is<br>
> literally kldloaded.<br>
><br>
> The screen change you see when going from loader to kernel loading<br>
> (the copyright, "Regents" note), there is no resolution change. The<br>
> resolution is the same as on the loader screen, it has been set by<br>
> UEFI. What you notice though is the change of font size. Between these<br>
> two screens, the system has done the calculation described in the<br>
> previous email, set the new column x row configuration, which is<br>
> larger than what you have in the UEFI screen; but there is no change<br>
> in resolution. Or perhaps there is slight change since it tries to<br>
> allocate a buffer that covers most of the screen.<br>
><br>
> I may have missed details, maybe someone can clarify more.<br>
><br>
> Cheers<br>
><br>
> Peeter<br>
<br>
Things like this ought to be be added somewhere in the dragonfly wiki.<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 11 Aug 2020 15:26:38 -0300<br>
From: nacho Lariguet <<a href="mailto:lariguet@gmail.com" target="_blank">lariguet@gmail.com</a>><br>
To: Peeter <<a href="mailto:karu.pruun@gmail.com" target="_blank">karu.pruun@gmail.com</a>><br>
Cc: dragonFlyBSD user list <<a href="mailto:users@dragonflybsd.org" target="_blank">users@dragonflybsd.org</a>><br>
Subject: Re: can I use the display native resolution on vty0 as on any<br>
other vty's using KMS ?<br>
Message-ID: <20200811152638.6addf9bd@leonov><br>
Content-Type: text/plain; charset=US-ASCII<br>
<br>
On Tue, 11 Aug 2020 11:18:34 +0300<br>
"karu.pruun" <<a href="mailto:karu.pruun@gmail.com" target="_blank">karu.pruun@gmail.com</a>> wrote:<br>
<br>
> Hello<br>
> <br>
> > Is it possible right now to end up in a pre-DRM situation by default ?<br>
> > IIRC kern.kms_console now defaults to 1 (don't know since when it does). <br>
> <br>
> The terminology here is a little confusing. I used pre-drm to mean<br>
> "until a drm driver (i915 or radeon) is loaded". Let me try to clarify<br>
> booting.<br>
<br>
OK. Now it is crystal-clear what pre-DRM is. My guess was pre-DRM meaned<br>
before we (I mean dragonFly) started using kms_console by default.<br>
<br>
> The first screen with the boot menu is displayed by the loader. The<br>
> kernel modules to load by the loader are given in<br>
> <br>
> /boot/loader.conf<br>
<br>
Right. The only thing I always added there is kern.kms_columns=-1<br>
<br>
> However, the official advice is that the loader load the absolute<br>
> required minimum of kernel modules. For instance, my loader.conf has<br>
> no modules. This is because memory is tight at that early stage. If<br>
> you include, e.g. a drm driver, i915 or radeon, then the kernel will<br>
> most likely crash at boot.<br>
> <br>
> The official advice is to load modules later by placing them in<br>
> /etc/rc.conf, for instance,<br>
> <br>
> i915_load="YES"<br>
<br>
Right. Mine (rc.conf) has drm_load="yes" and radeon_load="yes". The<br>
first is supposed to be automatically loaded by the second but I leave<br>
it there to remind me of the process because it won't hurt at all.<br>
<br>
> I have all the required wlan, drm etc there.<br>
<br>
Me too.<br>
<br>
> And you can also load the drm modules manually on console using<br>
> 'kldload i915'.<br>
<br>
Right.<br>
<br>
> This means that, for instance, if I choose to load the drm driver<br>
> manually then I'm in the pre-drm stage until I will have kldloaded it,<br>
> say, on console, manually. The copyright note (the "Regents" screen<br>
> you mention), this is the kernel starting to load. This is pre-drm,<br>
> there is no drm driver anywhere. This is either VGA or the UEFI<br>
> display. The terminology "kms_columns" is misleading; that variable is<br>
> read by the system to try to figure out column x row configuration,<br>
> but there is no drm driver anywhere. That same "kms_columns" is also<br>
> read later by the drm driver to set the column x row configuration.<br>
<br>
That's what mesmerizing me; suppose the following:<br>
<br>
I am booting @ 1920x1200 as set by the uEFI framebuffer code and then<br>
while booting the kernel the REGENTS message follows (and seems lower<br>
resolution due to the font scaling you mention but actually is at<br>
1920x1200) and then I end up at the root prompt still at 1920x1200 with<br>
font scaling enabled @ 80x25 characters and without any drm driver at<br>
all because when I booted I did not instructed the loader to use<br>
anything out of the ordinary as advised by the man pages and/or the<br>
handbook and/or whatever, and then, and only then I manually load the<br>
DRM drivers with kldload drm and kldload radeon and when I issue<br>
kldstat it shows them correctly loaded and then I do vidcontrol -i mode<br>
on ttyv0 and it shows ONLY 80x25 while ttyv>=1 shows 240x75. In this<br>
case I did not booted with the DRM drivers but I am still ending with<br>
ttyv0 limited to less characters on the screen than the ones available<br>
AFTER DRM was loaded post-boot the way is advised/intended to.<br>
<br>
Summarizing:<br>
<br>
- I boot the liveCD via uEFI without touching the boot loader options<br>
<br>
- kldload drm;<br>
- kldload radeon;<br>
- kldstat; ### shows radeon loaded and '[DRM] radeon' shows up in dmesg<br>
<br>
- vidcontrol -f 8x16 iso15-thin-8x16;<br>
- vidcontrol -i mode; ### shows 80x25<br>
<br>
- sysctl kern.kms_console; ### not found<br>
- sysctl kern.kms_columns; ### not found<br>
### they are not even mentioned in the syscontrol man page<br>
- sysctl kern.kms_columns=-1; ### unable to: unknown OID<br>
<br>
So, how do I instruct a running OS to switch to max columns now ?<br>
<br>
> So long story short: it is all pre-drm until the drm driver is<br>
> literally kldloaded.<br>
> <br>
> The screen change you see when going from loader to kernel loading<br>
> (the copyright, "Regents" note), there is no resolution change. The<br>
> resolution is the same as on the loader screen, it has been set by<br>
> UEFI. What you notice though is the change of font size. Between these<br>
> two screens, the system has done the calculation described in the<br>
> previous email, set the new column x row configuration, which is<br>
> larger than what you have in the UEFI screen; but there is no change<br>
> in resolution. Or perhaps there is slight change since it tries to<br>
> allocate a buffer that covers most of the screen.<br>
> <br>
> I may have missed details, maybe someone can clarify more.<br>
<br>
I do really appreciate (your time and) your replies because they have a<br>
lot of content to begin with.<br>
<br>
I also have to state that, what I was previously doing fiddling with the<br>
boot loader options in order to get early-KMS start (as it is called in<br>
linux) is because it didn't occurred to me I was ending in a 80x25 console<br>
at 1920x1200 with font scaling enabled, to me it seemed like a standard<br>
VGA screen, my fault, absolutely my fault. Although it will be nice to<br>
have dragonFly (or for the matter whatever OS for instance) booting at<br>
the best possible resolution (because it is far easy to read the kernel<br>
messages this way) I do not need/require early-KMS at all, I am really<br>
fine booting as it is intended to without DRM ... PROVIDED I can later<br>
change to max characters after loading everything DRM-related via rc.conf<br>
<br>
I think the only thing I need to accomplish this right now is to find a<br>
way of setting:<br>
<br>
sysctl kern.kms_columns=-1;<br></blockquote><div>that would evaluate to -1, I think you mean:</div><div>sysctl kern.kms_columns -= 1;<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Am I right ?<br>
<br>
> Cheers<br>
> <br>
> Peeter<br>
> <br>
> --<br>
> <br>
> On Tue, Aug 11, 2020 at 1:41 AM nacho Lariguet <<a href="mailto:lariguet@gmail.com" target="_blank">lariguet@gmail.com</a>> wrote:<br>
> ><br>
> > On Mon, 10 Aug 2020 14:37:14 +0300<br>
> > "karu.pruun" <<a href="mailto:karu.pruun@gmail.com" target="_blank">karu.pruun@gmail.com</a>> wrote:<br>
> ><br>
> > I'm attaching the output of "gop list" as mentioned before.<br>
> ><br>
> > You can clearly see that it boots straight to 1920x1200 right from the<br>
> > liveCD. So uEFI is informing 1920x1200 capability without any doubt.<br>
> ><br>
> > When it gets to the REGENTS message, it switches to a lower resolution.<br>
> ><br>
> > PS: I keep forgetting to CC the users list: sorry to reply twice Peeter<br>
> > <br>
> > > Hello<br>
> > ><br>
> > > I should clarify that when you load the drm driver (i915 or radeon, as<br>
> > > root on the console using 'kldload i915' or 'kldload radeon') the<br>
> > > initial buffer restriction does not apply any more. The drm drivers<br>
> > > allocate their own framebuffers, so all ttyv-s will have the same<br>
> > > column x row configuration.<br>
> > ><br>
> > > In the pre-drm situation, as explained earlier, the system tries to<br>
> > > work out an optimal column x row configuration based on the<br>
> > > information it gets from BIOS or UEFI. In the case of BIOS, you get<br>
> > > VGA modes; we don't have VESA at the moment, yet, if I'm correct. In<br>
> > > the case of UEFI, the system gets the resolution from UEFI and then<br>
> > > tries to work out the best column x row configuration under the<br>
> > > restriction that it must be max 160 column x 50 rows, font width is 8<br>
> > > and the final configuration must preserve font scaling. For instance,<br>
> > > on my laptop this works out precisely as described:<br>
> > ><br>
> > > - UEFI tells the resolution is 1680x1050 (X x Y)<br>
> > > - Font width is 8<br>
> > > - 1680 / 8 = 210, too large<br>
> > > - increase font width x 2<br>
> > > - 1680 / 16 = 105, yes under 160<br>
> > > - 1050 / 32 (font height is 16) = 32.8, round to nearest int, this is<br>
> > > 32; yes it's under 50<br>
> > > - final setup: 105x32<br>
> > ><br>
> > > The 105x32 is exactly what I get by default on my laptop if I set no<br>
> > > loader variables.<br>
> > ><br>
> > > I am not sure what if anything has changed between DragonFly 5.4 and<br>
> > > master. The syscons driver I believe is exactly the same. The BIOS and<br>
> > > UEFI setups would give different results though.<br>
> > ><br>
> > > I suggest you try to calculate the column x row configuration as<br>
> > > described above. In UEFI setup, you can see the modes as follows: at<br>
> > > boot, go to boot prompt (press '9'), and then do 'gop list' to see<br>
> > > what modes UEFI gives you. You can set the mode there too. (Give 'gop'<br>
> > > to see the command.) Enter 'boot' to continue booting. I guess you can<br>
> > > set the desired mode by default via a boot loader variable; but I<br>
> > > don't know what it would be.<br>
> > ><br>
> > > The graphical target etc stuff is linux speak, and probably systemd;<br>
> > > it has no relevance at all for DragonFly.<br>
> > ><br>
> > > Hope this helps.<br>
> > ><br>
> > > Peeter<br>
> > ><br>
> > > --<br>
> > ><br>
> > > On Mon, Aug 10, 2020 at 1:33 AM nacho Lariguet <<a href="mailto:lariguet@gmail.com" target="_blank">lariguet@gmail.com</a>> wrote: <br>
> > > ><br>
> > > > On Sun, 9 Aug 2020 13:53:22 -0700<br>
> > > > Jonathan Engwall <<a href="mailto:engwalljonathanthereal@gmail.com" target="_blank">engwalljonathanthereal@gmail.com</a>> wrote:<br>
> > > > <br>
> > > > > On Sun, Aug 9, 2020, 12:00 PM <<a href="mailto:users-request@dragonflybsd.org" target="_blank">users-request@dragonflybsd.org</a>> wrote:<br>
> > > > > <br>
> > > > > > Send Users mailing list submissions to<br>
> > > > > > <a href="mailto:users@dragonflybsd.org" target="_blank">users@dragonflybsd.org</a><br>
> > > > > ><br>
> > > > > > To subscribe or unsubscribe via the World Wide Web, visit<br>
> > > > > > <a href="http://lists.dragonflybsd.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.dragonflybsd.org/mailman/listinfo/users</a><br>
> > > > > > or, via email, send a message with subject or body 'help' to<br>
> > > > > > <a href="mailto:users-request@dragonflybsd.org" target="_blank">users-request@dragonflybsd.org</a><br>
> > > > > ><br>
> > > > > > You can reach the person managing the list at<br>
> > > > > > <a href="mailto:users-owner@dragonflybsd.org" target="_blank">users-owner@dragonflybsd.org</a><br>
> > > > > ><br>
> > > > > > When replying, please edit your Subject line so it is more specific<br>
> > > > > > than "Re: Contents of Users digest..."<br>
> > > > > ><br>
> > > > > ><br>
> > > > > > Today's Topics:<br>
> > > > > ><br>
> > > > > > 1. Re: can I use the display native resolution on vty0 as on any<br>
> > > > > > other vty's using KMS ? (nacho Lariguet)<br>
> > > > > > 2. how do I label (meaning adding a reminder caption) to any<br>
> > > > > > given BSD slice ? (nacho Lariguet)<br>
> > > > > ><br>
> > > > > ><br>
> > > > > > ----------------------------------------------------------------------<br>
> > > > > ><br>
> > > > > > Message: 1<br>
> > > > > > Date: Sat, 8 Aug 2020 18:06:14 -0300<br>
> > > > > > From: nacho Lariguet <<a href="mailto:lariguet@gmail.com" target="_blank">lariguet@gmail.com</a>><br>
> > > > > > To: <a href="mailto:users@dragonflybsd.org" target="_blank">users@dragonflybsd.org</a><br>
> > > > > > Subject: Re: can I use the display native resolution on vty0 as on any<br>
> > > > > > other vty's using KMS ?<br>
> > > > > > Message-ID: <20200808180614.66f67761@leonov><br>
> > > > > > Content-Type: text/plain; charset=US-ASCII<br>
> > > > > ><br>
> > > > > > On Sat, 8 Aug 2020 11:26:35 -0700<br>
> > > > > > Jonathan Engwall <<a href="mailto:engwalljonathanthereal@gmail.com" target="_blank">engwalljonathanthereal@gmail.com</a>> wrote:<br>
> > > > > > <br>
> > > > > > > Your picture looks to me like the standard "UNIX multi-user mode" perhaps<br>
> > > > > > > you should select a graphical target somehow. Are making a multi-head <br>
> > > > > > boot, <br>
> > > > > > > or bringing up each tty simultaneously?<br>
> > > > > > > Jonathan Engwall <br>
> > > > > ><br>
> > > > > > ... standard "UNIX multi-user mode" ... sure: do I did try/ask for<br>
> > > > > > anything else ?<br>
> > > > > ><br>
> > > > > > I'm afraid I'm not following<br>
> > > > > > <br>
> > > > ><br>
> > > > > Your photo shows the BSD/UNIX default to boot to a root system<br>
> > > > > administrator account. To change this you will need to boot to a graphical<br>
> > > > > target, or launch a multi head, or something relevant to what you are doing.<br>
> > > > > I don't know what you are doing. Maybe puppet would work for you?<br>
> > > > > Jonathan Engwall <br>
> > > ><br>
> > > > OK. Let me be more clear.<br>
> > > ><br>
> > > > I want to start using dragonFly ... daily.<br>
> > > ><br>
> > > > So the first step is to install it on the hardware that for whatever reasons<br>
> > > > I currently have, get it running without major issues, and last but not least,<br>
> > > > set a working environment that suits my needs, which ends in the following fact:<br>
> > > ><br>
> > > > What I want is dragonFly running ... WITHOUT X11 !<br>
> > > ><br>
> > > > I just want to develop and work with/on the system console, which in our case,<br>
> > > > happens to be syscons since we still don't have vt/wcons/whatever which means<br>
> > > > no native UTF-8 console for the time being.<br>
> > > ><br>
> > > > I feel comfortable working/developing without a major stack like X because:<br>
> > > ><br>
> > > > - I'm learning BSD and the best way to learn something like this is bottom to top<br>
> > > > not the other way around. This is exactly what I've done with arch-linux some years<br>
> > > > ago, I just installed a barebones system and from then on I kept learning and<br>
> > > > needless to say I learned a lot of thinks of linux inner workings which I doubt<br>
> > > > I could have learned with the zillion packages required by X and any given desktop<br>
> > > > environment with all their complexity and all the duplicacte functionality. Prior<br>
> > > > to start using linux I developed for many many years on, yes, Microsoft products<br>
> > > > and whatnot. Eventually moving to linux was so alien that I wanted to start, I say<br>
> > > > it again: bottom to top, not the other way around.<br>
> > > ><br>
> > > > - That said, I eventually want to move my primary workstation to dragonFly and a<br>
> > > > couple of servers, and I decided, wisely or not, that I want to move one server<br>
> > > > first because the server won't need X etc etc and albeit being a file/web server<br>
> > > > to begin with, it will give me a working environment so I can start coding in BSD,<br>
> > > > meaning primarily C.<br>
> > > ><br>
> > > > - Everything I need to code do not requires X at all: just a working system console.<br>
> > > > I learned to use VIM in the past few years and feels quite comfortably with it<br>
> > > > meaning I totally customized it (even I coded many syntax files from scratch), and<br>
> > > > in my arch linux console environment I have everything I want to.<br>
> > > ><br>
> > > > That will give you a detailed overview of what I am after with dragonFly.<br>
> > > ><br>
> > > > I need a couple of things:<br>
> > > ><br>
> > > > - digital video at max resolution: 1920x1200 in my case ... got it on my test-bed<br>
> > > > desktop and will attempt to get it running on my PowerEdge servers in a couple of<br>
> > > > days I guess.<br>
> > > ><br>
> > > > - a working US international keyboard layout (us-acentos) ... still not working<br>
> > > ><br>
> > > > - a UTF-8 native console ... I know I should give up on this if I want to use this OS<br>
> > > ><br>
> > > > - a custom script in CSH to execute after booting a liveCD that formats/installs/<br>
> > > > configures everything as needed ... almost done, testing it right now.<br>
> > > ><br>
> > > > From there on I'm planing to use what for whatever reasons I am currently using in arch:<br>
> > > ><br>
> > > > - BIND<br>
> > > > - nginx<br>
> > > > - postgreSQL<br>
> > > ><br>
> > > > Nothing special, all are in dPorts and I can customize and recompile them as needed.<br>
> > > ><br>
> > > > WHEN I get this server working I will start fiddling with X11 on my future BSD workstation.<br>
> > > ><br>
> > > > Sorry if this answer was a bit long but I hope you'll understand where I am standing<br>
> > > > right now.<br>
> > > > <br>
> > > > > I don't know what you are doing. Maybe puppet would work for you? <br>
> > > ><br>
> > > > I'll eventually get it running with/without your support.<br>
> > > ><br>
> > > > Thanks for your advice, and I mean it.<br>
> > > ><br>
> > > > PS: You will note that I am asking a lot of questions on the mailing list, I read the man<br>
> > > > pages, always, that won't mean that some thing can goes unnoticed to me at any given time<br>
> > > > or that simply I just forgot about some x detail I read before, there's a LOT to learn<br>
> > > > and the fact that I am asking is because I am a NEWBIE to BSD in general and I want to<br>
> > > > learn, nothing out of the ordinary I guess. If that irritates you just ignore me. I will<br>
> > > > be fine.<br>
> > > > <br>
> > > > > ><br>
> > > > > ><br>
> > > > > > ------------------------------<br>
> > > > > ><br>
> > > > > > Message: 2<br>
> > > > > > Date: Sun, 9 Aug 2020 15:04:42 -0300<br>
> > > > > > From: nacho Lariguet <<a href="mailto:lariguet@gmail.com" target="_blank">lariguet@gmail.com</a>><br>
> > > > > > To: dragonFlyBSD user list <<a href="mailto:users@dragonflybsd.org" target="_blank">users@dragonflybsd.org</a>><br>
> > > > > > Subject: how do I label (meaning adding a reminder caption) to any<br>
> > > > > > given BSD slice ?<br>
> > > > > > Message-ID: <20200809150442.7f5bc89d@leonov><br>
> > > > > > Content-Type: text/plain; charset=US-ASCII<br>
> > > > > ><br>
> > > > > > ie: the "label:" field shown under the "diskid:" one with disklabel64<br>
> > > > > ><br>
> > > > > > It seems there is no switch (maybe -l) on disklabel64 (when using -w) to<br>
> > > > > > label a slice.<br>
> > > > > ><br>
> > > > > > eg:<br>
> > > > > ><br>
> > > > > > # /dev/da0s1:<br>
> > > > > > #<br>
> > > > > > # Calculated informational fields for the slice:<br>
> > > > > > #<br>
> > > > > > # boot space: 1044480 bytes<br>
> > > > > > # data space: 175691776 blocks # 171574.00 MB (179908378624 bytes)<br>
> > > > > > #<br>
> > > > > > # NOTE: The partition data base and stop are physically<br>
> > > > > > # aligned instead of slice-relative aligned.<br>
> > > > > > #<br>
> > > > > > # All byte equivalent offsets must be aligned.<br>
> > > > > > #<br>
> > > > > > diskid: af1b4686-d85d-11ea-9373-012324e2aca4<br>
> > > > > > label: ... HOW TO SET THIS ONE ?<br>
> > > > > > boot2 data base: 0x000000001000<br>
> > > > > > partitions data base: 0x000000100000<br>
> > > > > > partitions data stop: 0x0029e3700000<br>
> > > > > > backup label: 0x0029e37ff000<br>
> > > > > > total size: 0x0029e3800000 # 171576.00 MB<br>
> > > > > > alignment: 4096<br>
> > > > > > display block size: 1024 # for partition display and edit only<br>
> > > > > ><br>
> > > > > > 16 partitions:<br>
> > > > > > # size offset fstype fsuuid<br>
> > > > > > a: 1048576 0 4.2BSD # 1024.000MB<br>
> > > > > > d: 33554432 1048576 HAMMER2 # 32768.000MB<br>
> > > > > > e: 134217728 34603008 HAMMER2 # 131072.000MB<br>
> > > > > > f: 6871040 168820736 HAMMER2 # 6710.000MB<br>
> > > > > > a-stor_uuid: eb61372a-d85d-11ea-9373-012324e2aca4<br>
> > > > > > d-stor_uuid: eb613733-d85d-11ea-9373-012324e2aca4<br>
> > > > > > e-stor_uuid: eb613739-d85d-11ea-9373-012324e2aca4<br>
> > > > > > f-stor_uuid: eb61373e-d85d-11ea-9373-012324e2aca4<br>
> > > > > ><br>
> > > > > ><br>
> > > > > > ------------------------------<br>
> > > > > ><br>
> > > > > > Subject: Digest Footer<br>
> > > > > ><br>
> > > > > > _______________________________________________<br>
> > > > > > Users mailing list<br>
> > > > > > <a href="mailto:Users@dragonflybsd.org" target="_blank">Users@dragonflybsd.org</a><br>
> > > > > > <a href="http://lists.dragonflybsd.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.dragonflybsd.org/mailman/listinfo/users</a><br>
> > > > > ><br>
> > > > > ><br>
> > > > > > ------------------------------<br>
> > > > > ><br>
> > > > > > End of Users Digest, Vol 96, Issue 10<br>
> > > > > > *************************************<br>
> > > > > > <br>
> > > > <br>
> > <br>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@dragonflybsd.org" target="_blank">Users@dragonflybsd.org</a><br>
<a href="http://lists.dragonflybsd.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.dragonflybsd.org/mailman/listinfo/users</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Users Digest, Vol 96, Issue 16<br>
*************************************<br>
</blockquote></div></div>