Maybe a poorly worded question but I seem to recall some advances where framebuffering is being handled differently than my old way.
It could be typified by the kernel line used in grub.conf like this one: kernel /vmlinuz root=/dev/sdb3 vga=0x31A video=vesafb:mtrr,ywrap Or is that still a viable way to setup the framebuffer, and, of course, making the proper Vesa and /or Uvesa choices at compile time. OK, that leads into a second or related part to this question; I'm having a heck of a time finding the uvesa setting in menuconfig. A searched for 'vesa', using '/'. Output below. But I'm not finding anything about 'UVESA' at that location. I see, under the 'Type' line that they appear to either designate 'boolean' or 'Tristate' I know what boolean means in general but not how to apply it here... But have no idea what Type: 'Tristate' might mean. I've really scrutinized that area of menuconfig... but not finding any way to say 'y' to FB_UVESA │ Symbol: FB_VESA [=y] │ │ Type : boolean │ │ Prompt: VESA VGA graphics support │ │ Defined at drivers/video/Kconfig:755 │ │ Depends on: HAS_IOMEM [=y] && FB [=y]=y && X86 [=y] │ │ Location: │ │ -> Device Drivers │ │ -> Graphics support │ │ (1) -> Support for frame buffer devices (FB [=y]) │ │ Selects: FB_CFB_FILLRECT [=y] && FB_CFB_COPYAREA [=y] && | | FB_CFB_IMAGEBLIT [=y] && FB_BOOT_VE │ │ │ │ │ │ Symbol: FB_UVESA [=n] │ │ Type : tristate │ │ Prompt: Userspace VESA VGA graphics support │ │ Defined at drivers/video/Kconfig:737 │ │ Depends on: HAS_IOMEM [=y] && FB [=y] && CONNECTOR [=n] │ │ Location: │ │ -> Device Drivers │ │ -> Graphics support │ │ (2) -> Support for frame buffer devices (FB [=y]) │ │ Selects: FB_CFB_FILLRECT [=y] && FB_CFB_COPYAREA [=y] && | | FB_CFB_IMAGEBLIT [=y] && FB_MODE_HE │ │ │ │ │ │ Symbol: FB_BOOT_VESA_SUPPORT [=y] │ │ Type : boolean │ │ Selected by: FB_VESA [=y] && HAS_IOMEM [=y] && FB [=y]=y && | | X86 [=y] || FB_INTEL [=n] && HAS │
