VESA framebuffer in 2.6.16.16 compile - what am I doing wrong?
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.
VESA framebuffer in 2.6.16.16 compile - what am I doing wrong?
I just compiled my own kernel for the first time this past Saturday to use with my Slackware 10.2 installation. I downloaded the 2.6.16.16 source, went through all the steps, and was surprised that my first effort worked. I did notice that I lost the penguin logo on bootup, and my boot text and shell font for the CTL-ALT-F1 - CTL-ALT-F6 sessions is larger.
I did a good bit of searching and found several sources that said to enable VESA framebuffer in the kernel. I did this, and even noted that the VESA framebuffer help in menuconfig states that it would give a penguin logo at no cost. I recompiled, installed the new kernel and System.map, ran lilo, then rebooted. Nothing changed, except that my kernel size is a little bigger. Am I missing something obvious?
Look around under "Console display driver support" and "Logo configuration". They're under "Device Drivers -> Graphics support". From there you can choose fonts and make sure you enable the bootup logo. You'll probably want to enable video mode selection support (if you haven't already done so) so you're not stuck with an 80x24 display.
Look around under "Console display driver support" and "Logo configuration". They're under "Device Drivers -> Graphics support". From there you can choose fonts and make sure you enable the bootup logo. You'll probably want to enable video mode selection support (if you haven't already done so) so you're not stuck with an 80x24 display.
-elyk
Thanks, I didn't do the bootup logo. I'll do that when I get home.
Quote:
Originally Posted by masonm
If you did enable everything in the kernel config and recompiled, did you tell lilo to use it?
I'm having a similar problem with enabling the framebuffer. I've gone to the console display driver support menu in menuconfig, but I can't seem to enable anything. I can select the various options, I just can't change them.
I recompiled with the bootup logo and the video mode selection support, and now I have the penguin, but my text is still pretty big compared to the text size from the generic 2.6.13 kernel. If I issue the
fbset
command, it reports that it is using 640x480-60 mode. I haven't had time, but I assume if I do:
fbset -n 1024x768-60
it will change, but does that make the mode setting permanent? Or am I even on the right track?
Look in your lilo.conf file. Mine has a commented list of video modes to use for console and tells what resolution each is. Mine, if I remember, is set to video=773 for 1024x768x256. If you can't set it there you can add it to the append line under the kernel or pass it as a parameter at boot time.
Look in your lilo.conf file. Mine has a commented list of video modes to use for console and tells what resolution each is. Mine, if I remember, is set to video=773 for 1024x768x256. If you can't set it there you can add it to the append line under the kernel or pass it as a parameter at boot time.
Mine is set exactly like your is. I haven't modified it, it's been that way since I first installed Slack. For some reason even though that is in lilo, it seems that it is being ignored, but only in the kernel I compiled.
The whole time I've been trying to get all of the VESA stuff working, I hadn't gone into X. I tried starting X for the first time since enabling the VESA framebuffer settings, and as soon as I do, I get "Scan out of range" on my monitor.
I recompiled without any of the extra Video settings, and I'm going to re-add them one by one until I figure out which one is causing this new problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.