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.
I'm compiling a custom 2.6 kernel and I want the framebuffer. I've enabled it in kernel, including VESA, VGA, and RadeonFB all built-in - however, on boot shortly after it switches to the framebuffer the machine hard locks with no error message!
Am I doing something wrong here? I'll attach .config if necessary. Thanks!
Since you helped me a few times over at rage3d, if this is the same black hole sun, I'll attempt to help you since I had the exact same problem when I compiled my 2.6.9 in Slack 10. See this post...
[url]http://www.linuxquestions.org/questions/showthread.php?s=&threadid=127095&perpage=15
framebuffer seems to be only needed when using the cli and at boot and shutdown. In KDE the xorg drivers take over, so I don't see any advantage in getting it to work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.