Re: vesafb no longer works on 2.5.50/51

• Next message: Patrick Petermair: "Re: vt8235 fix, hopefully last variant"
• Previous message: george anzinger: "Re: [PATCH]Timer list init is done AFTER use"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> On one of my machines, vesafb no longer works in 2.5.51 (other machine
> is okay?!).
>
> Everything is okay, except I can not see anything on the display.
>
> 2.4. (vesafb works):
> vesafb: framebuffer at 0xee000000, mapped to 0xd080d000, size 8192k
> vesafb: mode is 1024x768x16, linelength=2048, pages=4
> vesafb: protected mode interface info at c000:7652
> vesafb: scrolling: redraw
> vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
>
> 2.5.51 (vesafb does not work):
> vesafb: framebuffer at 0xee000000, mapped to 0xd0815000, size 8192k
> vesafb: mode is 1024x768x16, linelength=2048, pages=4
> vesafb: protected mode interface info at c000:7652
> vesafb: scrolling: redraw
> vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0

Can you try my patch to cfbimgblt.c in another post to see if that fixes
teh problem.

-
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/

• Next message: Patrick Petermair: "Re: vt8235 fix, hopefully last variant"
• Previous message: george anzinger: "Re: [PATCH]Timer list init is done AFTER use"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Dec 23 2002 - 22:00:27 EST