2008/1/8, Bill Nottingham <notting(a)redhat.com&gt;: Well.. vesafb is also enabled with 'y' and because uvesafb is it's successor it seems logical to me that it also gets enabled with 'y' (not as a module but build in). Perhaps a good idea for fedora to add a anaconda installer option that allows you to set the boot resolution or add the option in the firstboot.

2008/1/8, Bill Nottingham <notting(a)redhat.com&gt;: uvesafb just got included in the 2.6.24 which isn't even final yet so it's not 'late'.. more early than late. To execute.. Quote from [1]: "add video=uvesafb:1024x768-32,mtrr:3,ywrap (or similar) to your kernel command line" About the question: "But who wwould maintain the v86d userspace code package if we enabled the driver?" I'm willing to give it a shot with the help of someone that has experience in making spec files. (i have the links to the (old) handbooks.. just not the experience) [1] http://dev.gentoo.org/~spock/projects/uvesafb/

The readme says: 4. Installation & Usage ----------------------- To configure, build and install v86d with the default settings, run: # ./configure --default # make # make install v86d isn't meant to be used in an interactive way. It should be started and called by the kernel. If you want to see it in action, build and load the uvesafb kernel module. If you want to include v86d into an initramfs image, misc/initramfs provides a minimal config parsable by gen_init_cpio. misc/initramfs says: dir /dev 0755 0 0 nod /dev/console 0600 0 0 c 5 1 nod /dev/tty1 0600 0 0 c 4 1 nod /dev/zero 0600 0 0 c 1 5 nod /dev/mem 0600 0 0 c 1 1 dir /root 0700 0 0 dir /sbin 0755 0 0 file /sbin/v86d /sbin/v86d 0755 0 0 I think the module simply has to be included with initramfs In general i'm not sure how this is supposed to work. only that it solves my widescreen issue and that it's less difficult to use than just vesafb (because that uses codes for the resolution while this one uses a readable text (like 1280x800))