Re: 2.6.25 + vga=791
> On Mon, May 12, 2008 at 08:39:20PM +0200, Gilles Mocellin wrote:
> > Le Monday 12 May 2008 15:52:15 Hugo Vanwoerkom, vous avez écrit :
> > > Hi,
> > >
> > > In installing linux-image-2.6.25-1-686 I find I can no longer use
> > > vga=791 on the kernel commandline. I get "undefined videomode number:
> > > 317" that's 791 hex.
> > >
> > > I've been using vga=791 on kernels since time immemorial, what's wrong
> > > with it now?
> > >
> > > There is an alternative to that parameter:
> > >
> > > http://dev.gentoo.org/~spock/projects/uvesafb/
> > >
> > > but I'd like to know if anybody else using 2.6.25 has had problems with
> > > the vga= parameter, before I go into unknown territory...
> > >
> > > Hugo
> >
> > Same problem here.
> > I don't know the good solution.
> does this mean they have removed vesfb and moved to uvesafb ?
If I could pitch in my two cents here:
I have been using UVESA FB on an AMD64 machine since the beginning of the year -- it allows me to get my virtual terminals to run at 60 Hz, where VESA FB will only allow me to use 75 Hz. (Viewsonic recommends that my LCD monitor use a vert. refresh of 60 Hz at 1280x1024 in order to extend the life of the device.)
The Debian Kernel Team has certainly NOT moved to UVESA FB at all:
$ grep -i vesa /boot/config-2.6.25-1-amd64
# CONFIG_FB_UVESA is not set
CONFIG_FB_VESA=y
Usage of UVESA FB requires that 'klibc' (packaged for Debian under the names 'libklibc', 'klibc-utils', and 'libklibc-dev') be compiled against kernel sources that have been built with UVESA FB enabled; and it requires an "early userspace" helper program, 'v86d', that has not even been packaged for Debian.
If the kernel boot parameter "vga=791" is not working for someone, I would ask them for three pieces of information first, to rule out silly problems:
1. Have you changed your monitor to one that does not support the desired resolution?
2. Does your kernel configuration have the VESA framebuffer enabled?
3. If you use an initrd, is the VESA FB module present in it?
Only after determining whether the monitor supports the resolution, whether VESA FB is enabled in the kernel, and whether VESA FB is present in the initrd would I move on to deeper troubleshooting.
HTH,
Dave Witbrodt
Reply to: