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.
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.
|
 |
07-16-2005, 10:37 AM
|
#1
|
Member
Registered: Jun 2004
Location: Potsdam, NY
Distribution: Fedora Core 6
Posts: 201
Rep:
|
Console Framebuffer
I am having a bit of trouble figuring out why my console, at boot, does't have the tux logo in it. Instead I get a really large font an no graphics at all. I am running the 2.6.12.2 kernel and I did build support for the framebuffer. Here is a section from my .config:. Th
Code:
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=m
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
I must have forgot something, but I don't know what. Thanks for any help.
UPDATE: I just followed what this thread said to do and everything worked out.
Last edited by darkarcon2015; 07-16-2005 at 01:39 PM.
|
|
|
07-16-2005, 10:50 AM
|
#2
|
Member
Registered: Jan 2005
Location: Boston
Distribution: slackware
Posts: 502
Rep:
|
looks like you compiled support for all three options of the bootup logo in menuconfig and it's defaulting to the standard black and white one. To fix this you could recompile with only the 16-colour or 224-colour options enabled, but there may be an easier fix that I don't know about.
Cheers
|
|
|
07-16-2005, 10:53 AM
|
#3
|
Member
Registered: Jun 2004
Location: Potsdam, NY
Distribution: Fedora Core 6
Posts: 201
Original Poster
Rep:
|
Heh, I try to be safe and I still mess something up.
|
|
|
07-16-2005, 11:12 AM
|
#4
|
Member
Registered: Sep 2003
Distribution: Slackware
Posts: 626
Rep:
|
You have framebuffer support set as a module, so first check with lsmod to see if the module is loaded, but I think the problem is connected to the bootloader.
If you're using lilo, check in lilo.conf, in the global section, which line is uncommented in the " VESA framebuffer console" part. It's probably set to 640x480.
Mine is set to 1024x768x256 (vga = 773) and tux puts in an appearance at the top.
|
|
|
07-16-2005, 11:21 AM
|
#5
|
Member
Registered: Jun 2004
Location: Potsdam, NY
Distribution: Fedora Core 6
Posts: 201
Original Poster
Rep:
|
It's not a LILO problem because I have the tux logo appear when I boot the 2.4.29 kernel. I checked `lsmod` and I don't see framebuffer. What would I type in to get it loaded? `modprobe framebuffer` didn't work.
|
|
|
07-16-2005, 12:17 PM
|
#6
|
Member
Registered: Aug 2004
Location: BR - Floripa
Distribution: Ubuntu 9.10 - 2.6.x.x
Posts: 661
Rep:
|
|
|
|
07-16-2005, 12:30 PM
|
#7
|
Member
Registered: Jun 2004
Location: Potsdam, NY
Distribution: Fedora Core 6
Posts: 201
Original Poster
Rep:
|
Thanks, I'll try that.
|
|
|
07-16-2005, 01:35 PM
|
#8
|
Senior Member
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721
Rep:
|
you must compile frame buffer support, and vesa framebuffer support,
into the kernel.
not as module.
also don't compile other fb support like ati or so.
vesa is what's used in the standard Slackware kernels.
egag
|
|
|
07-16-2005, 01:37 PM
|
#9
|
Member
Registered: Jun 2004
Location: Potsdam, NY
Distribution: Fedora Core 6
Posts: 201
Original Poster
Rep:
|
Okay, I just followed what that post said and everything works now. Thanks a lot everyone.
|
|
|
07-16-2005, 05:24 PM
|
#10
|
Member
Registered: Jun 2005
Location: Florida, USA
Distribution: ~~~Slackware~~~
Posts: 86
Rep:
|
Note: You only get the pretty logo if you have the framebuffer. You won't get it if you use agpgart, also if you include support for the VGA text console your screen will be black and won't display nothing until you xserver starts(either from text mode or from entering run level 5 from an init script). Read the tips/comments you get at config time for the kernel.
I am a Jedi in training, Padwon Troye. You will register with the Linux Counter at counter.li.org. You will give me your highend graphics card. You will clean my toilet bowl.
|
|
|
All times are GMT -5. The time now is 03:15 PM.
|
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
|
|