efi_max_resolution
vbe_max_resolution
Specify the maximum desired resolution for the EFI or VBE
framebuffer console. The following values are accepted:
Value Resolution
480p 640x480
720p 1280x720
1080p 1920x1080
2160p 3840x2160
4k 3840x2160
5k 5120x2880
WidthxHeight WidthxHeight
I use uefi
I use uefi and the latest nvidia driver. I followed this tutorial:
screen.font is available on 13.0 and upwards, with a small set of fonts in /boot/fonts to choose from.
Indeed, but in case of
efi_max_resolution, it doesn't really make a difference.Agreed. In the likely case this is not yet 13, the magic of choosing a larger font won't be there yet, so he can just ignore what I wrote
So if i wanted to set a resolution of 1920x1080 on version 12, I would type what exactly for it to work on 12?Indeed, but in case ofefi_max_resolution, it doesn't really make a difference.
Agreed. In the likely case this is not yet 13, the magic of choosing a larger font won't be there yet, so he can just ignore what I wrote
I have set efi_max_resolution=“1920x1080” but it doesnt make any difference so i guess it was the same b4 i actually set it. But the text is really large. But i cant change that on 12? Can i upgrade to 13?Indeed, but in case ofefi_max_resolution, it doesn't really make a difference.
Agreed. In the likely case this is not yet 13, the magic of choosing a larger font won't be there yet, so he can just ignore what I wrote
I will run an x server. This is more aesthetic.... could i decrease the tty text size?
gomster : Have you tried the suggestion SirDice gave you? I.e. did you try setting
kern.vt.fb.default_mode?
I tried setting the resolution. However the text is still very large and i dont know how to decrease its size
Wouldn't the abysmal scroll speed be (quite) easy to fix by using the hardware scrolling of the CRTC?
vidcontrol() has some options afaik... didn't need yet to explore this, as I run still non-UEFI mode, and thus can use sc() in text mode.
What does
dmesg | grep 'VT(efifb)' return? Does the resolution show 1920x1080?
Wait, what?! Does that mean that 13.0 brings VBE support to vt(4)? Maybe there's still hope for my server console.
The mode is set by loader, but as a result, you have your console on some higher-resolution framebuffer even with legacy boot, yes. I tested it on my desktop and it was somewhat slow (EFI fb is faster here) and also broke compositing in X11 with radeonkms.ko, so I went back to classic VGA text console boot. And for my server, it's not interesting, this thing doesn't have any graphics
I'm not looking to run X11 on my server console, but the ability to use anything that gives more space for text than the 640x480x16 that vt_vga currently gives surely would be nice. Unfortunately Gigabyte did not feel the necessity to include a graphics port on that mainboard, so I had to go with 'what was available' and does not consume much power:The mode is set by loader, but as a result, you have your console on some higher-resolution framebuffer even with legacy boot, yes. I tested it on my desktop and it was somewhat slow (EFI fb is faster here) and also broke compositing in X11 with radeonkms.ko, so I went back to classic VGA text console boot. And for my server, it's not interesting, this thing doesn't have any graphics
vgapci0@pci0:3:5:0: class=0x030000 card=0x0100102b chip=0x051a102b rev=0x02 hdr=0x00
vendor = 'Matrox Electronics Systems Ltd.'
device = 'MGA 1064SG [Mystique]'
class = display
subclass = VGAYou also can try to use the graphical mode of sc().
Not sure whether you need a graphical mode, but sc(4) relies on vga(4) which seems to have optional support for VESA BIOS extensions (VBE) so you could probably go with any VESA text or graphics mode supported by the hardware. But going down that road would probably mean loosing unicode support and some other nice stuff that came with vt(4).
I have no plans on running Xorg on a server console that is solely used for maintenance, but it's good to know that it could work