I should have noted that I'm aware vesafb is compiled into the kernel.
For some reason, no matter what combination of modes are put on the
kernel command-line, it doesn't help the virtual consoles.
With just vesafb+fbcon I tried vga=0x317 (1024 x 768 x 16) and 0x318
(1024 x 768 x 24) and they
No, that's not the problem. vgacon is statically linked in. We
deliberately don't use vga16fb or vesafb by default.
--
Gutsy Alternate - no console video driver installed
https://bugs.launchpad.net/bugs/144178
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Sun, 2007-09-23 at 14:54 +, 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
** Changed in: xserver-xorg-video-siliconmotion (Ubuntu)
Sourcepackagename: linux-source-2.6.22 = xserver-xorg-video-siliconmotion
** Summary changed:
- Gutsy Alternate - no console video driver installed
+ Silicon Motion X driver fails to correctly restore text mode
--
Silicon Motion X driver
This might be related to the other Silicon Motion issue I've found in
bug #144182 Gutsy - Silicon Motion video driver freezes, corruption,
and error reports.
--
Silicon Motion X driver fails to correctly restore text mode
https://bugs.launchpad.net/bugs/144178
You received this bug notification
From a remote ssh session, whilst at the GDM greeter page:
[EMAIL PROTECTED]:~$ sudo vbetool vbemode get
3
After switching to VT console 1 using Ctrl+Alt+F1:
[EMAIL PROTECTED]:~$ sudo vbetool vbemode get
3
[EMAIL PROTECTED]:~$ lsmod | egrep 'vga|fb'
fbcon 41760 0
tileblit
