Gutsy Gibbon poses problems unknown to Feisty Fawn
bmarsh at bmarsh.com
Tue Nov 6 17:38:32 UTC 2007
On Sunday 04 November 2007, sktsee wrote:
> > but even with un-blacklisting the FB doesn´t work (when i tested it)
> Gerald's suggestion isn't to un-blacklist the driver, but to include it
> in the initrd image.
> If you use the vesa framebuffer driver you would do the following:
> $ cd /lib/modules/`uname -r`/kernel/drivers/video
> $ sudo cp vesafb.ko /lib/modules/`uname -r`/initrd
> $ sudo update-initramfs -u
> $ sudo shutdown -r now
> If all goes well, vesafb gets loaded when the initrd image does, and
> fbcon (framebuffer console driver) has a framebuffer to work with.
> Interestingly enough, vesafb.ko is already present in the above
> mentioned initrd directory with feisty kernels, but isn't with gutsy
> kernels. Why the gutsy devs moved away from this workaround without
> first solving the original problem with initramfs' framebuffer handling
> is a mystery.
The above doesn't work for me....
I guess I am getting a little ticked as to why they can't solve a relatively
simple issue like this?
Is it more complex than I think it is?
More information about the ubuntu-users