Re: Framebuffer issues in 2.6.26 with uvesafb and vesafb. Linux is about choice!

From: Alistair John Strachan
Date: Thu Oct 23 2008 - 08:22:33 EST

On Thursday 23 October 2008 12:21:09 Robert Moss wrote:
> I also want to note, that I downloaded and compiled, with
> CONFIG_FB_VESA=Y, and still get excactly the same response as from
> 2.6.26

Useful info, and I checked your configs and they enable the right options.
Looks like you've found a real bug.

IIRC, a lot of real mode assembler (including the x86 vga/vesa stuff, iirc)
was rewritten a year or so ago, in C. This might have been the time that this
bug was introduced. I've added hpa to CC since I believe he was the author of
these changes.

(Summary of the original report is that vga= vesa mode selection seems to have
broken for Robert since at least 2.6.26, and after 2.6.24. From what I can see
he has the right vesafb options enabled.)

> Screen unavailable [or not found, im not sure] 317. (which i believe
> is 0x317 = 791)

I grepped the tree for "Screen unavailable" and "Screen not found" and found
nothing. Could you please reproduce the message and confirm which exactly it

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at