Re: vesafb not working in later 2.4.x kernels?

Change Ling (change@wesecurethe.net)
Sun, 24 Mar 2002 09:58:39 -0800 (PST)


I guess I jumped the gun, and have proven that vesafb support is still in the
latest stable. My bad.

I'm using LILO version 21.7-5 as a boot loader. Much to my chagrin I was
finally able to get vesafb support on a machine running a RedHat 7.2 default
lilo version(can't get at that machine at the moment to obtain the version
diff).

I'm using the above mentioned version of lilo specifically for graphical boot
time splash screen support.

I now need to determine if this lilo version supports some other method of
manipulating video modes. Which I guess no longer belongs in this forum.

thanks,

William

Quoting Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>:

> On 22 March 2002 16:04, Change Ling wrote:
> > I have been trying to build the vesafb under the 2.4.18 kernel for use
> in
> > my work on the biatchux bootable cdrom distribution, but the frame
> buffer
> > never seems to initialize at boot with the vga=791 kernel argument.
> >
> > It is as though the Video select option isn't handling the kernel
> arg,
> > since vga=ask doesn't present my with a selection menu either.
> >
> > Has vesafb or Video_select support somehow been dropped in the
> latest
> > stable kernel???
>
> It is working here in 2.4.18.
>
> IIRC vga=XXX isn't a kernel option, it is handled by kernel loader.
> Kernel loader parse vga=xxx and pass it to real-mode part of kernel init
>
> code. That code switch display to specified video mode via VESA before
> it
> enters 32-bit mode.
>
> Since even vga=ask does not work for you it seems your kernel loader
> does not
> handle vga=xxx parameter correctly. What loader do you use?
> --
> vda
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/