In Ubuntu 8.04 and earlier, things worked as follows:
- vesafb.ko is included in the initramfs and conf/modules by virtue of being in /lib/modules/x/initrd/
- If vga= or similar is passed on the kernel command line, vesafb is loaded with the appropriate parameters
(/usr/share/initramfs-tools/scripts/init-top/framebuffer)
- the initramfs init script will try to load it again via conf/modules, but it's already loaded (harmless)
- thus, all that is needed to enable vesafb is passing a kernel parameter
In Intrepid, it now works as follows:
- vesafb is gone, and we have uvesafb.ko
- uvesafb.ko is included in the initramfs and conf/modules by virtue of being in /lib/modules/x/initrd/
- initramfs-tools has no smarts for uvesafb, so it gets loaded via conf/modules
- I see no way to pass parameters to the module as was done with vesafb
- it's impossible to do anything with the module without manually installing v86d
This should be made to work similarly to how it did with vesafb. If an additional package is required by a kernel module, it should have a dependency relationship (recommends?) with the kernel package.
In Ubuntu 8.04 and earlier, things worked as follows:
- vesafb.ko is included in the initramfs and conf/modules by virtue of being in /lib/modules/ x/initrd/ share/initramfs -tools/ scripts/ init-top/ framebuffer)
- If vga= or similar is passed on the kernel command line, vesafb is loaded with the appropriate parameters
(/usr/
- the initramfs init script will try to load it again via conf/modules, but it's already loaded (harmless)
- thus, all that is needed to enable vesafb is passing a kernel parameter
In Intrepid, it now works as follows: x/initrd/
- vesafb is gone, and we have uvesafb.ko
- uvesafb.ko is included in the initramfs and conf/modules by virtue of being in /lib/modules/
- initramfs-tools has no smarts for uvesafb, so it gets loaded via conf/modules
- I see no way to pass parameters to the module as was done with vesafb
- it's impossible to do anything with the module without manually installing v86d
This should be made to work similarly to how it did with vesafb. If an additional package is required by a kernel module, it should have a dependency relationship (recommends?) with the kernel package.