Andre,
Your problem is most likely due to using incorrect modes on the kernel
parameter line, and not a confirmation of the bug. The documentation in
the kernel describes the correct method (Documentation/fb/uvesafb.txt):
video=uvesafb:1024x768-32,mtrr:3,ywrap
The specific mode that you use would depend on your hardware and
supported modes. On an Inspiron 1420 with integrated Nvidia 8400M GS
graphics this mode works like a champ:
video=uvesafb:1440x900,mtrr:3,ywrap
The documentation also describes how you may determine supported modes,
note that v86d must be properly installed and the uvesafb module loaded:
$ less /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
If the uvesafb.0 directory is not present, then you can assume that you
have not properly installed v86d and/or loaded the uvesafb module.
Once you have the correct mode, and v86d is installed and you are still
having problems at boot, then you should suspect a problem with the
initramfs. At this point I would guess the v86d executable is probably
missing from the initramfs.
In the last case, I would return and report the issue.
Thanks,
Harvey
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
