| 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.
 |
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. |
|
|
By rickh at 2006-10-03 09:55
|
|
Seems that nowadays most distros use a splash screen to cover up all the system messages that scroll across the screen during boot-up. You usually get an option to see the detail by hitting some key or other. I'm an old man, and get some kind of comfort from watching those lines fly by, and sometimes it's very helpful.
The problem is that the default screen density at that point is something like 640x480. The lines wrap, and you can only see about 20 at a time even when they're not wrapping. It's very difficult to see a line that you're particularly watching for. You can change that screen density by modifying the framebuffer resolution, but if you try googling for information about how to do that, you will quickly be discouraged unless you're the type of person who builds his own kernels, enjoys hexadecimal numbers, and is generally smarter than me.
Fortunately, there is an easy way to do it if only you could find it. You've come to the right place.
You need to edit your "menu.lst" file. Some hand-holding distros don't think you'll be able to remember that name, so they have set you up a link named "grub.conf." Whichever you use, you need to add a kernel option.
If your menu.lst file has a line that starts out: that's the one you want. Otherwise look for a line something like:
Code:
kernel /boot/vmlinuz-2.6.17-2-k7 root=/dev/hda1 ro
To set the screen resolution to 1024x768, insert into the appropriate line: "vga=791"
Some common frambuffer resolutions are:
640x480 - 785
800x600 - 788
1024x768 - 791
1152x864 - 355
1280x1024 - 794
1600x1200 - 798
Isn't that nice?
|
|
|
|
All times are GMT -5. The time now is 07:05 AM.
|
|
|
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
|
|
/me pulls up google, types in, "Framebuffer resolution codes," hits "I'm feeling lucky," and is immediately dropped onto a page with a chart of resolutions and color depths with all the codes listed...
Who exactly has a problem finding and configuring this?!?!?! It's not rocket science to find the codes!
/me pulls up google, types in, "Framebuffer resolution codes," hits "I'm feeling lucky," and is immediately dropped onto a page with a chart of resolutions and color depths with all the codes listed...
Who exactly has a problem finding and configuring this?!?!?! It's not rocket science to find the codes!
How have you contributed to add knowledge of many of the readers who might have come across this post.
About as much as digging up 3 year old posts contributes.... whoooooo