On Tue, 18 Mar 2008 17:38:26 -0000
"mirko.quaglio" <email address hidden> wrote:
> Same problem using vesafb.
> I've commented blacklisted-framebuffer #vesafb (and #vga16fb) and loaded fbcon and vesafb modules in initramfs. I've tried various vga= options and the result was always the same: framebuffer seems to work but when I switch between ttys (ALT+right, ALT+left) all becomes black except the blinking cursor.
This is exactly what happens here with the most recent kernel. The frame
buffer appears to work for example on tty1, but switching to another tty
results in a blank screen. This is not recoverable.
In addition, even to get this much functionality the initramfs and modules
hacks are still required. This bug is *still not fixed*, and should be
so marked.
On Tue, 18 Mar 2008 17:38:26 -0000
"mirko.quaglio" <email address hidden> wrote:
> Same problem using vesafb. framebuffer #vesafb (and #vga16fb) and loaded fbcon and vesafb modules in initramfs. I've tried various vga= options and the result was always the same: framebuffer seems to work but when I switch between ttys (ALT+right, ALT+left) all becomes black except the blinking cursor.
> I've commented blacklisted-
This is exactly what happens here with the most recent kernel. The frame
buffer appears to work for example on tty1, but switching to another tty
results in a blank screen. This is not recoverable.
In addition, even to get this much functionality the initramfs and modules
hacks are still required. This bug is *still not fixed*, and should be
so marked.