Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 49633 - More display resolutions for vesa framebuffer after boot
Summary: More display resolutions for vesa framebuffer after boot
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Michal Januszewski (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-01 12:00 UTC by Sebastian
Modified: 2004-06-15 07:11 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian 2004-05-01 12:00:59 UTC
Hello,

can you guys try to add more possible resolutions to the framebuffer driver? More and more often people buy flatpanels or even notebooks instead of tube monitors. And these sometimes have different resolutions. Now that the 16:10 panels hit the market resolutions of 1280x800 and higher enter the game. Conventional flatpanels are set to 1400x1050 or else. These differ from the possible resolutions in GNU. You can run other resolutions like 1024x768 instead of 1280x800 but it just doesn't look right.
Is there a way you can put new resolutions into the kernel or wherever it's needed (lilo, grub?).

Thanks!

Sebastian

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Michal Januszewski (RETIRED) gentoo-dev 2004-05-08 10:42:29 UTC
As crazy as it may sound, this is already being worked on ;) I'm reassinging this bug to myself to take care of it as a part of the vesafb-tng project. 
Comment 2 Michal Januszewski (RETIRED) gentoo-dev 2004-06-13 07:24:06 UTC
Please try the new vesafb-tng driver. You can find more info and instructions how to install it on http://dev.gentoo.org/~spock/#vesafb-tng

The driver will let you view all available VESA modes (/proc/fb0/modes). It's theoretically possible to set modes that are not officially supported by your VBE, but I haven't checked it out. Please let me know if this solves your vesafb problems.
Comment 3 Sebastian 2004-06-14 00:02:14 UTC
Hello,

I tried the patch with gentoo-dev-sources 2.6.5 (which I currently use only) and it threw a lot of failed hunks at me. Best part was it didn't even save the .rej(ects). So that's a no go for me at the moment. I could update to 2.6.7-r2, but my kernel is really working great for me right now so you can see my point why I don't want to. I am also having no troubles with the display resolution right now, because I use the new radeon-framebuffer module which sets the mode right. I couldn't use that together with the ATI binary X driver (switching back to console crashed my box) but I found out some time ago that I can use the xorg radeon driver for 2D accel and the kernel DRI driver for 3D accel and that this setup doesn't interfere with the radeonfb module. So I'm very happy right now (because a) I have no resolution problems and b) I don't have to use any binary software on my laptop). 
Anyway, I believe that the tng project is the right way to go and I will check it out when I see fit.

Thanks for the tip in the right direction!
Sebastian
Comment 4 Michal Januszewski (RETIRED) gentoo-dev 2004-06-15 07:11:32 UTC
I'm closing this as fixed, since there's nothing more to be done here and since vesafb-tng should solve all similar problems.