Bug#439846: framebuffer script badly interprets modedb boot parameter

[trosos <trosos@seznam.cz>]

Package: initramfs-tools
Version: 0.85h

The init-top/framebuffer script should use "mode_option" (according
to the documentation) as a fb module parameter for setting the video
mode, instead of "mode".

The Linux documentation uses "mode_option" argument:

 $ zcat /usr/share/doc/linux-doc-2.6.18/Documentation/fb/modedb.txt.gz
 ...
 Valid mode specifiers (mode_option argument):
 
     <xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m]
     <name>[-<bpp>][@<refresh>]
 ...

But the framebuffer script uses "mode" argument:

 $ cat /usr/share/initramfs-tools/scripts/init-top/framebuffer
 ...
 # When the options are used with modules, they need to be space-separated
 ...
 #       <modevalue>   -> mode=<modevalue>
 ...

As a consequence, if I specify eg. "video=aty128fb:1024x768-16" as
a kernel boot parameter, the framebuffer script uses a "mode" module
parameter (instead of "mode_option"), which will not be understood by
the module.

I tried aty128fb and nvidiafb modules, and both accept "video_mode"
option, and don't accept "mode" option. With other fb modules I would
expect similar behavior.

One can use "video=foofb:mode_option=1024x768..." as a workaround,
but the documented behavior will not work.

If no fb driver uses the "mode" parameter, I suggest to change the
init-top/framebuffer script in order to use the "mode_option"
parameter.

---

$ uname -r
2.6.18


Tomas "trosos" Tintera