Console screen resolution
by Fission Chips from LinuxQuestions.org on (#4ZXGE)
I'm running Slackware64 on a computer hooked to my TV and the resolution is not detected correctly. In Lilo, most of the VGA options work fine but then as soon as the video controller starts (?) at "Console:Switching to colour frame buffer device", the resolution appears to be auto-deteted as 1920x1080 which ends up tiny and does not show me the whole screen. When I start KDE to change the resolution there, 1360x768 is the correct one.
I can override the problem on startup when I append "nomodeset" to the kernel and disable KMS, but then the resolutions don't work correctly in X, as predicted in some related threads I found:
https://www.linuxquestions.org/quest...33-smp-794283/
https://www.linuxquestions.org/quest...283/page2.html
I understand from here that KMS basically has the kernel set up the video card instead of X server so that switching between console and X using Ctrl+Alt+F1-F7 runs seamlessly, is that correct? How can I specify which resolution KSM uses instead of the native/auto-detected one? I also tried not using any VGA option at all in lilo.conf as suggested in the article on KMS, but that seems to be the same as vga=0.
FWIW, when I initialize runlevel 4, the resolution is still at 1920*1080 until I log on with the user, then it changes to the 768p I specified. Doesn't that mean that from that moment on, the X server controls the video card again contrary to what it says in the article on KMS I linked above? Also, I do get a flickering when I change to a console and back.
So most likely, KMS isn't working properly?
Also, considering all this, is there any use at all to the VGA settings in lilo.conf or are these relics from before KMS? It appears that they only affect the first part of the booting output on all my Slackware installs since at least a few years if I remember correctly, and after a short time during boot, the screen flickers and the video driver is loaded. Never a problem when KMS detects the right resolution, but in one of the related threads above, it's also called a bug...
I can override the problem on startup when I append "nomodeset" to the kernel and disable KMS, but then the resolutions don't work correctly in X, as predicted in some related threads I found:
https://www.linuxquestions.org/quest...33-smp-794283/
https://www.linuxquestions.org/quest...283/page2.html
I understand from here that KMS basically has the kernel set up the video card instead of X server so that switching between console and X using Ctrl+Alt+F1-F7 runs seamlessly, is that correct? How can I specify which resolution KSM uses instead of the native/auto-detected one? I also tried not using any VGA option at all in lilo.conf as suggested in the article on KMS, but that seems to be the same as vga=0.
FWIW, when I initialize runlevel 4, the resolution is still at 1920*1080 until I log on with the user, then it changes to the 768p I specified. Doesn't that mean that from that moment on, the X server controls the video card again contrary to what it says in the article on KMS I linked above? Also, I do get a flickering when I change to a console and back.
So most likely, KMS isn't working properly?
Also, considering all this, is there any use at all to the VGA settings in lilo.conf or are these relics from before KMS? It appears that they only affect the first part of the booting output on all my Slackware installs since at least a few years if I remember correctly, and after a short time during boot, the screen flickers and the video driver is loaded. Never a problem when KMS detects the right resolution, but in one of the related threads above, it's also called a bug...