Changing screen refresh rate for terminal (so not for a GUI terminal emulator but an actual terminal outside the GUI -> different TTY)

Does someone know how to change the refresh rate of the terminal? So, an actual terminal outside the GUI, not a terminal emulator within the GUI.

I regularly have to switch between the GUI and a terminal (so switching TTY with CTRL+ALT+F2 → F7), and I have my GUI set to 120 Hz, which my screen and obviously also my graphics driver support at the given resolution (it is supported on other resolutions too; no issue here). The default of the terminal is 60 Hz, which makes my screen to change its refresh rate condition each time I switch the TTY, which always takes several seconds and thus wastes a lot of my time. So the question is if I can switch it from 60 Hz in the terminal to 120 Hz, to have the same refresh rate in GUI and terminal.

Using a terminal emulator within the GUI is not acceptable for the given purpose. Switching GUI to 60 Hz is not an option as well.

It’s not a big thing and not worth much efforts, but maybe someone knows off the cuff :classic_smiley:

Can you do that with kernel mode setting?

1 Like

There is this proposal F44 Change Proposal: UseKmsconVTConsole [SystemWide].
Alison likely would know what is possible.

That’s realistic, but I prefer to not create self-made statics in the dynamic adjustments of the kernel space. I aim to keep the kernel space default and auto-adjust to changes of upstream/Fedora, as everything else can cause issues at some point, and they are sometimes not easily to identify (especially if much time has passed since a fixed/static customization). The kernel also acts as “issue mitigation”/“control instance” for user space, which I would bypass that way in this very area. So I would prefer a user space solution :frowning:

Hi @barryascott – this proposal is actually owned by @jfalempe and he should have the details you are looking for. I apologize for the confusion, I forgot to transfer ownership of the Discussion Post :slight_smile:

2 Likes

You can try kmscon.
By default, it will re-use the current mode, so it should stay at 120Hz.

You can try it with:

If there is still a flicker (unlikely), I’m currently updating kmscon to use atomic modesetting with:

And that should fix it.