Comment 44 for bug 147623

Fabio,

I tend to agree with your synopsis. I haven't dived much into hunting down
the exact cause like you, but I did find this solution on the forums, which
relates to your post. Look at orange2k's solution.

http://ubuntuforums.org/showpost.php?p=3635667&postcount=9

On Dec 29, 2007 8:57 AM, Fabio Papa <email address hidden> wrote:

> Ok, I think I got what the problem is. And, unfortunately, I think the
> solution is out of reach, at least for me.
> It seems we x86_64 are simply short of a usable working vesa module!
> That's right, because:
>
> vesafb doesn't work with newer cards. The fact that with x86 it works,
> it's because it is, in reality, vesafb-tng, the newer release, which of
> course isn't availabe on x86_64.
> nvidiafb or ati equivalent doesn't work because thay won't work with the
> proprietary driver.
>
> There is an alternative: uvesafb
> (http://dev.gentoo.org/~spock/projects/uvesafb/<http://dev.gentoo.org/%7Espock/projects/uvesafb/>),
> which is the evolution
> of vesafb-tng. It works on every architecture and it's completely
> userland. It needs a kernel patch, though, and offer also some new
> features, like VESA 3.0 compatibility.
>
> If Ubuntu's folks can implement uvesafb, we should be set! ;)
>
> --
> [EM64T]When booting, screen stays black.
> https://bugs.launchpad.net/bugs/147623
> You received this bug notification because you are a direct subscriber
> of the bug.
>