Re: vesa display codes (Etch Xorg memory leak?)
On Sat, May 19, 2007 at 07:33:51PM EDT, Owen Heisler wrote:
> On Sat, 2007-05-19 at 19:10 -0400, Greg Folkert wrote:
> > On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote:
> > > On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote:
> > > > On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote:
> > > > > http://www.gregfolkert.net/info/vesa-display-codes.html
> > > >
> > > > Very helpful! Although no 1280x960 (grr) unfortunately. Is there any
> > > > way to get that?
> > >
> > > vbetool is supposed to do it.
> > >
> > > Or "hwinfo --vbe"
> > >
> > > But they aren't exactly 100%, as I haven't been able to get the info out
> > > of the hardware yet.
> >
> > FYI, I've updated the page and now lists a few things to get other
> > modes. Though the framebuffer howtos have not really been updated since
> > 2000 or 2001.
>
> video=<>:xres:<>,yres:<>,depth:<>,left:<>,right:<>,hslen:<>,upper:<>,lower:<>,vslen:<>
>
> It looks like I need something like this:
> Modeline "1280x1024" DCF HR SH1 SH2 HFL VR SV1 SV2 VFL
>
> Is there some way to get that from xorg?
>
> And what do I use for the framebuffer device (video=<>)?
I missed the earlier posts on this thread so this is a bit of a shot in
the dark.
Please ignore if this is .. er .. "off topic" :-)
I believe video= is card-specific and you need to specify the name of
the kernel "video" driver that supports your card .. if there is one,
that is.
I have an antique laptop with an ATI Mach64 card which is fully
supported by the "atyfb" driver.
So I specify this in my grub menu file:
kernel /boot/vmlinuz-2.4.27.041213.2 root=/dev/hda11 ro video=atyfb:1400x1050
In other words, I do not use the generic vga/vesa driver .. the one that
has the vga=791 .. etc. syntax .. but rather one that's specific to my
hardware. The reason I use it rather than the generic is that among
other things it lets me run a 1400x1050 linux console which happens to
be the native mode of my laptop's panel, taking care of the blurred
fonts I was getting with other modes available with the generic driver
such as 1024x768 .. Makes a huge difference. It also gives me twice the
real-estate ~1.4M vs. ~0.7M pixels or so .. while maintaining the
correct 4:3 ratio as opposed to the wide-screen mode of 1280x1024 that I
used for a while with the generic driver.
In order to get this to work I had to do a bit of kernel configuration
to enable support for my card .. add the 1400x1050 mode to some file or
other in the ../drivers/ sub-directory of the kernel source tree .. I
think this file is common to all the different drivers .. and naturally
build a custom kernel. Depending on your card .. which kernel you are
using .. who built it .. whether he enabled the driver that you need ..
the mode you plan to use .. all the above may not even be necessary.
And then again your particular card may not be supported .. in which
case you're out of luck and will have to stick with the generic driver
until someone adds support for your particular hardware.
Unfortunately, I don't know of a site that has the list of currently
supported cards and which particular module supports each of them.
In any case, the semi-obsolete framebuffer console HOWTO is worth a
read.
Other places to look for additional info:
$ man fbset
$ man 5 fb.modes
You probably need to do an "apt-get install fbset" of similar to have
access to these documents on your machine.
HTH
Thanks,
cga
Reply to: