Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
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.
I recompiled my 2.6.4 kernel with console framebuffer support, installed id properly and modified grub.conf to add vga=791 as a parameter.
The problem is I see a 640x480 or something screen with the tux and a cursor moving as text should be running to the screen. I don't see any text, though.
I also tried with optional font support and a the first two fonts compiled inside the kernel. No change there.
Also after logging in, starting X and shutting X down the console is totally garbled with reddish nonsense (not even ASCII-garble).
I've got a GeForce 4 MX 440 and I've used the riva fb module. (Actually not as module but in the kernel.)
Any ideas how to at least see something more than a happy penguing in the console?
I think they wanted to confuse us, because you need the VESA VGA framebuffer driver instead of the Riva driver. Don't ask me why, but it works for me. As for no text, you did include the "append="splash=verbose"" line (if using LILO), right?
Thanks, really! That worked for these and even a boot-time hardware-related problem I'm having... Didn't even have to try verbosing.
An other issue came up:
Now the screen won't print out the way it should. All modes end up showing the upper side of each row - four times! The lower sides must have gone too close to /dev/null or something. Plus 640 & 800 modes have a misplacement (either left or right) for every row (and the 4 x multiplications).
I've tried all the reso-color combinations from 640x480x8b to 1024x768x24b and turning some BIOS AGP options off.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.