> > Strange that CONFIG_VT would get set to no. Another huge issue is that
> > people are configuring several framebuffer drivers to run the same piece
> > of hardware.
> A number of people seem to be seeing regressions with vesafb too.
> Configs that worked with 2.4 give a blank screen, and lock up under 2.5
> I believe vga=791 was one such option.
They are forgetting to set CONFIG_FRAMEBUFFER_CONSOLE.
I have had VESA compiled without framebuffer console but with mdacon
instead. If they would log in a do a cat /dev/urandom > /dev/fb0 they
would see that the VESA fbdev driver is functional.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jul 23 2003 - 22:00:30 EST