Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
There are less than 24 hours left to vote in the 2011 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Distribution: Slackware current, FreeBSD 4.10, 5.4, 6.2, Debian, RedHat, CentOS, Sun Cobalt OS
Posts: 66
Rep:
Frame Buffer Problem !!!
I gave up on this one already. I was searching for a solutions but seems like i cannot find any so i decided to post this thread and ask for suggestions. I've checked every possible HOWTO but still nothing. Here is the situation.
Everything worked just fine 15mins total kernel config+compile+tune up-=> voila everything's working just fine, BUT something is bothering me and i cannot fix it. The frame buffer resolution is working on "640x480-60" which is i suppose the lowest standard. It's kinda ugly to leave the resolution in console that low and i wanted to higher it a lil bit maybe up to 1024x768-70 but nope it didn't work. I've tried every single option in /etc/fb.mode but nothing. What i get after running fbset is:
I believe that this is best done in your lilo.conf. See below:
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
You *should* have somethign that looks like the above in your lilo.conf. Just uncomment the line that matches the resolution that you want your frame buffer console to use, rerun lilo (i.e. type lilo as root) and restart.
Distribution: Slackware current, FreeBSD 4.10, 5.4, 6.2, Debian, RedHat, CentOS, Sun Cobalt OS
Posts: 66
Original Poster
Rep:
it should but it does not work -=> the only option that works is @ 640x480 for some reason. I was thinking maybe it's a hardware issue -=> i was told that i810 and the frame buffer don't work that well but i don't know, actually i was told that it doesn't work at all -=> still researching though so let's see
It is very possible that maybe that particular video adapter does not support frame buffers..... I don't know much about the i810 but I do know some adapters, especially on board adapters, do not include frame buffer support.
Please do not post the same thread in more than one forum. Picking the most relevant forum and posting it once there makes it easier for other members to help you and keeps the discussion all in one place.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.