On Sun, 2007-09-23 at 14:54 +0000, Matthew Garrett wrote:
> No, that's not the problem. vgacon is statically linked in. We
> deliberately don't use vga16fb or vesafb by default.
vesafb+vgacon is ok during start-up but as soon as a graphics mode has
been activated (usplash or xorg) there is no VT console display.
With one of the VT consoles activated (by Ctrl+Alt+F1) all that is
apparent is the back-light glow.
Connecting via ssh from a remote PC and simply doing:
On Sun, 2007-09-23 at 14:54 +0000, Matthew Garrett wrote:
> No, that's not the problem. vgacon is statically linked in. We
> deliberately don't use vga16fb or vesafb by default.
vesafb+vgacon is ok during start-up but as soon as a graphics mode has
been activated (usplash or xorg) there is no VT console display.
With one of the VT consoles activated (by Ctrl+Alt+F1) all that is
apparent is the back-light glow.
Connecting via ssh from a remote PC and simply doing:
$ lsmod | egrep 'vga|fb'
fbcon 41760 72
tileblit 3584 1 fbcon
font 9344 1 fbcon
bitblit 6912 1 fbcon
$ sudo modprobe vga16fb
and the VT console text display instantly appears.
$ lsmod | egrep 'vga|fb'
vga16fb 15500 1
vgastate 11008 1 vga16fb
fbcon 41760 71
tileblit 3584 1 fbcon
font 9344 1 fbcon
bitblit 6912 1 fbcon