Messages in this thread | | | Date | Thu, 23 Oct 2008 04:21:09 -0700 | From | "Robert Moss" <> | Subject | Re: Framebuffer issues in 2.6.26 with uvesafb and vesafb. Linux is about choice! |
| |
I also want to note, that I downloaded 2.6.27.3 and compiled, with CONFIG_FB_VESA=Y, and still get excactly the same response as from 2.6.26
Thank you for the quick reply, I'm glad to hear that everything is still supposed to work ^_^. Ok on both 2.6.24 AND 2.6.26, i get the same thing from vga=ask then scan, 0 F00 80x25 1 F01 80x50 2 F02 80x43 3 F03 80x28 4 F05 80x36 5 F06 80x36 6 F07 80x60
Please select a number
and on 2.6.26 with vga=791 it says
Screen unavailable [or not found, im not sure] 317. (which i believe is 0x317 = 791)
On Thu, Oct 23, 2008 at 1:04 AM, Samuel Thibault <samuel.thibault@ens-lyon.org> wrote: > Robert Moss, le Thu 23 Oct 2008 00:54:56 -0700, a écrit : >> Anyhow, I noticed that vesafb is no longer a part of the kernel. > > That's not true. It works nicely on my laptop (though I don't get > the native 1280x800 resolution). > >> vga=791 still gave a mode not found. > > Then that's a bug, which is a completely different thing. Could you > check that the output of vga=ask and typing scan at the boot prompt is > the same between 2.6.24 and 2.6.25/26 ? > > Samuel, who may want to try 2.6.24 to get his native resolution. > -- 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/
| |