[SOLVED] console:switching to colour frame buffer device 128x48 while kernel boot 2.6.33-smp
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,634
Rep:
As I understand it, something was changed in the KBM (kernel based mode setting), that thingy which prevents flickering of the display during boot and changes of resolution. Maybe it is just a side effect...
yes slackware-current.im using intel 865g onboard chipset i tried blacklisting by specifying blacklist nouveau anyway to see no matter because its nvidia and no joy for me.
If it is related to KMS (not KBM), you can disable it at boot by passing the 'nomodeset' option to the kernel. Mind you, I doubt X will start on intel GPUs without KMS enabled :-)
EDIT: Alright, so X will still work if you disable KMS on Slackware 13.0. What I've heard, though, is that it will not work on -current. I can't confirm this personally, though:
jzl where did you get the info from that its about kms ?
when i disable kms while in X windows i can change console with ctrl+alt+f1-f6 no problem but if kms is enabled then when i try to switch back to consoles with ctrl+alt+f1-f6 it gives black screen and i cant use ctrl+alt+backspace no more.
also xorgsetup when trying to detect hardware gives black screen no matter if kms is enabled or disabled. im wondering what cause that it gives black screen?, im wondering how xorgsetup operate? does it operate in a way that its trying to start a xorg server when detecting hardware?
i saved xorg.conf from previous xorg server from slack13
and tried to start x to see what happens.
i get this:
because at the moment im unable to get proper resolution in X windows. i see that many ppls say that driver that i have installed is conflict with x-org server or does not support xorg server that im running, so i will see about it.
thats why i would like to know how xorgsetup operate when detecting hardware through hal?
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,634
Rep:
Quote:
Originally Posted by matters
...jzl where did you get the info from that its about kms ? ...
That was a guess founded on your description of the problem.
Quote:
Originally Posted by matters
...if kms is enabled then when i try to switch back to consoles with ctrl+alt+f1-f6 it gives black screen and i cant use ctrl+alt+backspace no more....
For a controlled reboot use <Alt> + <SysReq> + REISUB (typing the (small) characters in this sequence)
lets wait and see that someone reply whys that happening when kms is enabled and while in X windows when switching to consoles ctrl+alt+f1-f6 gives black screen? what causes that?
and no matter if kms is enabled or disabled in lilo xorgsetup gives black screen while trying to detect hardware ? what causes this?
wondering how xorgsetup operate when trying to detect hardware?
another thing about inteldrmfb would like to know how its related to kms?
And I have that problem, but I am not using any drivers for the video card. So, before slackware start on the lilo prompt to type nomodeset, and I should turn off kms from lilo.conf? But after that X may not work?
im speaking in the name of intel chipset 865g, if you have slackware-current installed libdrm and xf86-video-intel-2.10 installed you can start X windows no matter if kms is enabled or disabled, but resolution wont be properly displayed, as i described earlier. however im still waiting for peoples to answer on my questions that i posted,
What do you mean by "I am not using any drivers for the video card." ? Are you saying that you're not using Xorg? Because if you are using Xorg, then you're using drivers for your video card.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.