[SOLVED] How to get proper TTY resolution?

[eeckwrk99]

I have an old kernel config file which would get me proper TTY resolution for my display (2560x1440), but I had performances issues with it so I started from scratch.

I'm generating kernels from sys-kernel/gentoo-sources, I use systemd. I have an NVIDIA GTX 970 with proprietary drivers.

GRUB has

Code: Select all

GRUB_GFXMODE=2560x1440x32

in

Code: Select all

/etc/default/grub

and is displayed with the correct resolution. After GRUB, it reverts to a smaller resolution.

I can get proper TTY resolution with a kernel generated with an old config file despite having

Code: Select all

#GRUB_GFXPAYLOAD_LINUX=

in /etc/default/grub. I tried using

Code: Select all

GRUB_GFXPAYLOAD_LINUX=keep

with the new config file but it doesn't make any difference.

I tried replicating these settings from my old config file (with only one framebuffer parameter enabled before each kernel compilation):

Code: Select all

Device Drivers --->
    Graphics support --->
        <*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --->
            [*] Enable legacy fbdev support for your modesetting driver
        Frame buffer Devices --->
            -*- Support for frame buffer devices --->
                [*] EFI-based Framebuffer Support
                [*] Simple framebuffer support
                [*] VESA VGA graphics support

, to no avail. I'm getting the exact same behavior with sys-kernel/gentoo-kernel-bin and stock config file.

Of course, some parameters have changed or have been removed between my old config file and the new one. I noticed some differences during the boot process.

When booting with a kernel generated from my old config file, the boot process is slightly verbose. Some harmless errors are printed before I'm prompted to enter my LUKS password, with elapsed time between brackets on the left. On the other hand, with the new config file (same with gentoo-kernel-bin), the boot process is completely silent. After GRUB, I'm only asked for my LUKS password and a success message like ">>LUKS device opened" appears before X starts.

Any idea what could be the issue?

My old config file with proper TTY
My new config file with wrong TTY

Thanks!

[NeddySeagoon]

eeckwrk99,

A few things.

The kernel built in fonts differ between kernels.

Code: Select all

CONFIG_FONT_SUPPORT=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

and

Code: Select all

CONFIG_FONT_SUPPORT=y
CONFIG_FONTS=y
# CONFIG_FONT_8x8 is not set
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_7x14 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_6x10 is not set
# CONFIG_FONT_10x18 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set
CONFIG_FONT_TER16x32=y
# CONFIG_FONT_6x8 is not set

I'm not sure if that matters or not.

Most (not Simple Framebuffer) framebuffer console drivers allow the video resolution to be set on the kernel command line.
I have

Code: Select all

vga=0x317 video=amdgpu:mtrr:3,ywrap 

but the origins of that are lost in the mists of time.
vga=0x317 sets the resolution. That much I remember.

[eeckwrk99]

@NeddySeagoon

Problem solved! Disabling

Code: Select all

Library routines --->
    [ ] Select compiled-in fonts

so that none of the the underlying font parameters are active did the trick.

Thank you so much for pointing me in the right direction!