open grub customizer > appearance settings > check custom resolution > select your prefer resolution and save.
Yes, but (confusingly) immediately after displaying the boot menu and accepting input for boot parameters, grub's job is done.
A few seconds into the boot process, KMS driver takes over, overriding any selected custom grub resolution.
During init, the specified console font size and fontface are read from /etc/default/console-setup
Quite a variety of fonts are pre-installed (ref: all/console-data/filelist
and to change the configured default selection, instead of hand-editing /etc/default/console-setup
debian would have us perform font selection by running a command like "setfont /usr/share/consolefonts/Lat7-Terminus28x14.psf"
sudo dpkg-reconfigure -plow console-setup (ref: https://sources.debian.org/src/console- ... etup.5.txt
As a convenience, the antiX/MX init (live init, at least) recognizes a conwidth=
I didn't find a wiki description to link here, but specifying conwidth=120 instructs "given the current display resolution, I want the font to be appropriately sized so that 120 character columns fill the width of the display". Choosing a larger value (e.g. 140) yields a smaller font face.
The right answer is related to conwidth option from within LiveBoot menu,
which I can't find right now how to apply/adjust after installation. (MX/antiX wiki?)
From a console prompt, we have 2 antiX/MX utilities available. Someone can followup to mention if they are also accessible via controlcentre or menu.
note: neither of these attempts to modify the actual "display resolution"
enables selection of an alternative fontface for the console font and IIRC the selection is "remembered", per user, across sessions.
Using sudo console-width-select
to set a new default width selection relieves the need to specify conwidth= bootline parameter.