[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: what happened to vesafb support in 2.6.13-1?



On Wed, Oct 12, 2005 at 03:31:18PM +0900, Horms wrote:
> On Sun, Oct 09, 2005 at 06:00:55PM +0200, Maximilian Attems wrote:
> > On Sun, Oct 09, 2005 at 05:14:06PM +0200, Willi Mann wrote:
> > > Hi!
> > > 
> > > Can someone please tell me what happened to vesafb support in 2.6.13-1? 
> > > (CONFIG_FB_VESA=m in 2.6.12-10 vs. "not set" in 2.6.13-1)
> > > I get a blank screen when booting with vga=791.
> > > 
> > > Willi
> > > 
> > 
> > the old legacy modular vesafb patch got dropped.
> > and it seems it was overlooked to set them to yes.
> 
> I think I might have made that change, and at the very least
> I remember discussing it. I think that the idea was that
> it has actually been superceeded by another module. However
> if this isn't the case, I guess setting it to yes is a good idea.
> Does anyone know what this might break?
> 
> -- 
> Horms

well the d-i guys should get a notice:
currently vesa failed by default so they dropped into vga16,
which is known not to work on a range of laptops.

it might be a fix for the strange red background item..

as background info the old half-baken vesa modular patch conflicts
with upstream fixes. hch, waldi and i decided that to be a good
time to drop it.

--
maks



Reply to: