Ubuntu
v86d package

  1. Bug #189621
  2. Comment #10

Comment 10 for bug 189621

Revision history for this message
Evgeni Golov (evgeni) wrote : Re: [Bug 189621] Re: v86d missing, needed for uvesafb

Hi,

On Fri, 18 Jul 2008 07:58:52 -0000 Michael Sotnikov wrote:

> 1. with current interpid kernel (2.6.26-4) vesafb isn't possible - it's absent. It was replaced with uvesafb, which use another command (according to documents)
> In addition. After system load we can see that uvesafb was loaded (lsmod | grep uvesafb), but it doesn't work! Cause uvesafb should create some entries in /sys/class/graphics/fb0/.... which is absent at this moment. And if you restart uvesafb - they will be created.

So you have
CONFIG_FB_UVESA=y
CONFIG_FB_VESA=n
in your kernel config?
IMHO that's bad, as uvesafb should not be used as a complete
replacement for vesafb, but only in cases where vesafb fails due to
it's limitations.

Can you post a `dmesg |grep -i uvesa` after a fresh boot with uvesafb
not working correctly? I assume it just can't start v86d (as / is not
yet mounted). This should be solved by including v86d into the initrd.

> 2.I think this is right way - add uvesafb to initrd, but we need it
> working first.

It works fine as a module here for me, both with and without initrd.