adsldude
always learning
Premium,Ex-Mod 2003-9
join:2000-11-10
Colorado
1 edit | Framebuffer 1680x1050
Hi folks!
I've been searching for a couple days and finding very little on how to solve my framebuffer issue. I just picked up a new Samsung SyncMaster 225BW monitor from NewEgg with 1680x1050 native resolution which is not supported by LILO in Slackware 12. The monitor is awesome but that's another topic! I currently have the framebuffer set in LILO at 1280x1024x256 which is acceptable. I would prefer full resolution using LILO, not Grub, to do it. BTW, my nVidia 7600GS card does just fine with 1680x1050 in the X server thanks to the nVidia X Server applet added to my KDE menus.
The 1680x1050 resolution is not one of the selections for LILO so how would I go about adding it? Do I put a new entry in the /etc/fb.mode file for LILO to find? If that is the solution how would I determine what the fb.mode entry values should be?
This has me stumped and I'm hoping someone has "been there, done that" and can provide guidance. TIA! |
|
firephoto
KDE
Premium
join:2003-03-18
 ·Verizon west (ex G..
2 edits | 1440x900 is a valid frame buffer size and it's the same ratio as yours so maybe that would be a close compromise?
»en.wikipedia.org/wiki/VESA_BIOS_Extensions
*edit
Looks at this too, maybe you can just calculate and use the proper number for your resolution. |
|
adsldude
always learning
Premium,Ex-Mod 2003-9
join:2000-11-10
Colorado
| Thanks for your reply. I found the same Wikipedia entry and it helped me realize that this was somehow possible but didn't give me enough to actually do it. The Gentoo splash link also confirms it's possible.
I still think this has to do with the /etc/fb.modes entries which I'm clueless on how to generate the proper values for the 1680x1050x256 mode. Here is a sample of a mode listed in my /etc/fb.modes file:
Clear as mud to me! |
|
benyto
Premium
join:2000-07-09
Chico, CA | There is a man page for fb.modes. I'm not trying to be snide, just pointing it out in case you didn't realize it existed. The man page may give you more insight on how to create your own entry. |
|
adsldude
always learning
Premium,Ex-Mod 2003-9
join:2000-11-10
Colorado | No offense taken. I had not looked at that man page but I had looked at "man fbset" which near the top declared to be "out of date". I'll look into the rest of the fb man pages and see if they help me piece this mystery together. Thanks! |
|
firephoto
KDE
Premium
join:2003-03-18
·Verizon west (ex G..
| You should just be able to give the kernel the boot option vga=865 or vga=0x361 for 1680x1050x246.
I see you're trying to get lilo not the boot at this res. This would have to be a lilo specific config I guess? The lilo.conf should take the vga=865 line to set the default resolution for lilo. I think it uses vga=normal by default. |
|
adsldude
always learning
Premium,Ex-Mod 2003-9
join:2000-11-10
Colorado
| said by firephoto  :You should just be able to give the kernel the boot option vga=865 or vga=0x361 for 1680x1050x246. I see you're trying to get lilo not the boot at this res. This would have to be a lilo specific config I guess? The lilo.conf should take the vga=865 line to set the default resolution for lilo. I think it uses vga=normal by default. That's what I thought in the beginning too. I entered vga=865 in my lilo.conf and reinstalled LILO only to have framebuffer freak out and ask me to choose from the available resolutions. The choices framebuffer gave me matched the values in the /etc/fb.modes file.
I believe I need to create a new entry in /etc/fb.modes like my earlier post with the specific settings for 1680x1050x256. Then I should be able to pass vga=865 to the framebuffer. I might be going about this all wrong but I'm surprised that others haven't run across this before with their wide screen displays. |
|
adsldude
always learning
Premium,Ex-Mod 2003-9
join:2000-11-10
Colorado
| reply to adsldude
Here's a cool command that might get me a little closer. It helps me figure out what values would need to go into an entry in /etc/fb.modes. How I reference it with a vga= line in lilo.conf is beyond me at the moment.
|
|
