Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
|
03-09-2010, 01:10 PM
|
#1
|
|
Member
Registered: May 2007
Distribution: Slackware
Posts: 281
Rep: 
|
console:switching to colour frame buffer device 128x48 while kernel boot 2.6.33-smp
hi!
in lilo.conf i do have specified vga normal
but while booting the system screen resolution changes and it says
Code:
Console:Switching to colour frame buffer device 128x48
what is causing this? how can i prevent this from happening again?
this only happens when i do have 2.6.33 predefined kernels installed.
Thanks alot!
|
|
|
|
03-10-2010, 01:33 AM
|
#2
|
|
Member
Registered: Feb 2007
Location: Belgium
Distribution: Slackware
Posts: 37
Rep:
|
hi,
Are you running slackware-current?
Blacklisting the nouveau driver (and using the nvidia driver) solved the problem for me.
|
|
|
|
03-10-2010, 03:01 AM
|
#3
|
|
Senior Member
Registered: Apr 2003
Location: Germany
Distribution: openSuSE 12.3_64-KDE, Ubuntu 12.04, Fedora 17, Mint 14, Chakra
Posts: 3,516
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...
|
|
|
|
03-10-2010, 04:39 AM
|
#4
|
|
Member
Registered: May 2007
Distribution: Slackware
Posts: 281
Original Poster
Rep: 
|
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.
|
|
|
|
03-10-2010, 08:01 AM
|
#5
|
|
Senior Member
Registered: May 2006
Posts: 3,012
|
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:
http://www.linuxquestions.org/questi...normal-792873/
Last edited by adamk75; 03-10-2010 at 08:19 AM.
|
|
|
|
03-10-2010, 08:09 AM
|
#6
|
|
Senior Member
Registered: Apr 2003
Location: Germany
Distribution: openSuSE 12.3_64-KDE, Ubuntu 12.04, Fedora 17, Mint 14, Chakra
Posts: 3,516
Rep: 
|
Quote:
Originally Posted by adamk75
...KMS (not KBM)...
|
Darned acronyms
Thanks for the correction.
|
|
|
|
03-10-2010, 05:21 PM
|
#7
|
|
Member
Registered: May 2007
Distribution: Slackware
Posts: 281
Original Poster
Rep: 
|
@JZL240I-U and adam yes that fixes the problem.
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:
/usr/lib/xorg/modules/intel_drv.so: undefined symbol: resVgaShared
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?
thanks guys
|
|
|
|
03-11-2010, 06:24 AM
|
#8
|
|
Senior Member
Registered: Apr 2003
Location: Germany
Distribution: openSuSE 12.3_64-KDE, Ubuntu 12.04, Fedora 17, Mint 14, Chakra
Posts: 3,516
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)
http://kember.net/articles/231/reisu...-linux-restart
http://www.definition-of.com/REISUB
For this the SysRq feature must be turned on, i.e. "cat /proc/sys/kernel/sysrq" issues "1".
Quote:
Originally Posted by matters
...thats why i would like to know how xorgsetup operate when detecting hardware through hal...
|
I have no answer for this, sorry.
Last edited by JZL240I-U; 03-11-2010 at 06:30 AM.
|
|
|
|
03-11-2010, 07:00 AM
|
#9
|
|
Senior Member
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware-14.0 on a Lenovo T61 6457-4XG
Posts: 2,784
|
If I wouldn't want frame buffer I'd just blacklist the relevant module; lsmod|grep fb would tell me which one.
|
|
|
|
03-11-2010, 08:44 AM
|
#10
|
|
Member
Registered: May 2007
Distribution: Slackware
Posts: 281
Original Poster
Rep: 
|
@jzl sysrq codes works perfecly. thanks for info!
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?
|
|
|
|
03-11-2010, 12:08 PM
|
#11
|
|
Member
Registered: Mar 2009
Location: Bulgaria
Distribution: Slackware
Posts: 103
Rep:
|
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?
|
|
|
|
03-11-2010, 12:55 PM
|
#12
|
|
Member
Registered: May 2007
Distribution: Slackware
Posts: 281
Original Poster
Rep: 
|
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,
thanks guys
|
|
|
|
03-11-2010, 02:22 PM
|
#13
|
|
Member
Registered: Mar 2009
Location: Bulgaria
Distribution: Slackware
Posts: 103
Rep:
|
I have installed only libdrm, but as I said I don't use any drivers, but if I remove libdrm? This will break anything...
|
|
|
|
03-11-2010, 02:42 PM
|
#14
|
|
Senior Member
Registered: May 2006
Posts: 3,012
|
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.
Adam
|
|
|
|
03-11-2010, 03:27 PM
|
#15
|
|
Member
Registered: May 2007
Distribution: Slackware
Posts: 281
Original Poster
Rep: 
|
to turn off kms in /etc/lilo.conf add the line
Code:
append = "nomodeset"
save /etc/lilo.conf,
then do :
and reboot.thats how resolution came back to normal for me on 865g chipset.
if u want to turn on kms back just comment the line to be like this:
Code:
#append = "nomodeset"
save lilo.conf and start lilo with and reboot.
im wondering when i will get the answer on my questions 
Last edited by matters; 03-11-2010 at 03:35 PM.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 04:05 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|