SlackwareThis Forum is for the discussion of Slackware Linux.
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.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hey all, long time. Just recompiled with 2.4.20 kernel. Updated NVIDIA drivers, PCMCIA (its a laptop), and my linux-wlan. Anyway, I noticed that there wasn't a menu config option for a framebuffer in the console drivers section. I enabled everything in the console drivers section anyway (VGA Console and Video Selection).
Now to the problem.
I have LILO configured for the framebuffer @ 1024x768 (256) but the resolution is irrelevant. Every time I reboot with the new kernel the framebuffer doesn't work. I just get a blank, black screen as the system boots. Nothing is halted, it is just that I get no image on the screen. I tried changing the resolution and color depth but the same thing happens.
Has anybody gotten framebuffer support working in 2.4.20?
You have probably enabled experimental frame buffers when you enabled all. Not a good idea if you ask me. Especially if it is experimental. Anyways, you are going to have to re-compile your kernel and do not enable the experimental fb drivers for high end cards (i.e. ATI, MATROX, NVIDIA, 3DFX, etc) and only keep low end drivers like vesa (default) and vga. Don't be tempted to use the NVidia frame buffer because you will be running into problems when XFree86 loads its NVidia drivers.
I figured the kernel tree maintainers would just get rid of them after a while, since they were included (mostly) for non-gui systems (small population target), such that you can still have most of the features of your popular video card within your vt consoles. However, I did not understand the theory behind it since real servers don't have high-end cards built in them and everyone else uses gui.
Besides, the idea for high-end fbs never caught on. An indicator is the last development date for those high-end cards listed. The fact is that most users would rather use the gui drivers, and would never have a need for them. Most end-users just fail to understand the purpose for those buffers (unless they are curious and compile them in their kernel -- an example is this post ). Thus learning about them the "curious-george" way. .
Probably they will be removed when version 2.6.X is released. . .
How about Console Drivers->Frame buffer when you select Prompt for development and/or incomplete code/drivers in Code maturity level options?
I have 2.4.20 with frame buffer support going on my slack install, none of a problem. Well, yes frame buffer was there for ages, and as I can understand it migrated from UNIX where there weren't any sofisticated video hardware at the times and luck of drivers.