Why did you use vesafb (instead of uvesafb)?
uvesafb supports more resolutions than vesafb - like 1280x800.
I realized a broken framebuffer after the update to Lucid Beta2.
So I have written a tutorial in the German ubuntuusers.de forum, how you install and use uvesafb and get plymouth (new boot screen) displayed at start up correctly.
The translation:
Add or replace in /etc/default/grub for 1280x1024 @ 32bit color range (replace with your favorite resolution)
Code:
GRUB_GFXPAYLOAD_LINUX=1280x1024x32
GRUB_CMDLINE_LINUX="video=uvesafb:mode_option=1280x1024-32"
. Then run
. In /etc/modprobe.d/blacklist-framebuffer.conf you add the line
and add in /etc/initramfs-tools/modules the line
. Finally run
Code:
update-initramfs -u
.
In some cases you need to install the package v86d from the repository.
A fix for get plymouth before the X server starts:
Code:
sudo su
echo FRAMEBUFFER=y > /etc/initramfs-tools/conf.d/splash
update-initramfs -u
exit
Without that fix you see plymouth only a few seconds and at the longest time a black screen.
PS: All commands needs root privileges (sudo) and
don't forget to save the changes!
Use your favorite text editor: gedit, vim, nano etc.
The changes will be activated at the next boot.
I hope you understand translation.
PPS: I don't know how often the nvidia-current package will be updated, but I think a stable and tested driver is better then a new and 'not tested' driver.
Bookmarks