Skip to contentSkip to conversation

vgacon disable again

PATCH Gerd Hoffmann 2 participants 5 messages Feb 13, 2007 – Feb 14, 2007

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

Hi,

The much easier fix is this one ;)

cheers,
Gerd

Signature · 1 line
Gerd Hoffmann <[email protected]>
---
 drivers/video/console/vgacon.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/video/console/vgacon.c +2 -1
Index: paravirt-2.6.20-hg749/drivers/video/console/vgacon.c
===================================================================
@@ -372,7 +372,8 @@ static const char *vgacon_startup(void)
 	}
 
 	/* VGA16 modes are not handled by VGACON */
-	if ((ORIG_VIDEO_MODE == 0x0D) ||	/* 320x200/4 */
+	if ((ORIG_VIDEO_MODE == 0x00) ||	/* not set */
+	    (ORIG_VIDEO_MODE == 0x0D) ||	/* 320x200/4 */
 	    (ORIG_VIDEO_MODE == 0x0E) ||	/* 640x200/4 */
 	    (ORIG_VIDEO_MODE == 0x10) ||	/* 640x350/4 */
 	    (ORIG_VIDEO_MODE == 0x12) ||	/* 640x480/4 */

_______________________________________________
Virtualization mailing list
[email protected]
https://lists.osdl.org/mailman/listinfo/virtualization

#1 lore raw
Quoted 3 lines · Gerd Hoffmann

Hi,

The much easier fix is this one ;)

Oh, and it obsoletes vgacon-fix-zero-size.patch btw ...

cheers,
Gerd

Signature · 1 line
Gerd Hoffmann <[email protected]>
#2 lore raw
Quoted 2 lines · Gerd Hoffmann

Oh, and it obsoletes vgacon-fix-zero-size.patch btw ...

Well, I think the zero-size allocation oops is a bug anyway. But is it really necessary to disable VGA beyond that?

J

#3 lore raw
Quoted 6 lines · Jeremy Fitzhardinge
Quoted 2 lines · Gerd Hoffmann

Oh, and it obsoletes vgacon-fix-zero-size.patch btw ...

Well, I think the zero-size allocation oops is a bug anyway. But is it really necessary to disable VGA beyond that?

Yes, it is. Otherwise it oopses as soon as something is printed on /dev/tty<any>. Quite early at boot with "console=tty1", otherwise as soon as /sbin/getty starts on /dev/tty1. Oh, and the reason is it thinks it has an EGA card with 0 lines and 0 columns because we never ran the real-mode boot code and thus SCREEN_INFO isn't initialized. The 0x0 screen probably leads to the zero-sized buffer you are catching in that patch.

cheers,

Gerd

Signature · 1 line
Gerd Hoffmann <[email protected]>
#4 lore raw
Quoted 3 lines · Gerd Hoffmann

Yes, it is. Otherwise it oopses as soon as something is printed on /dev/tty<any>.

OK, I'll add your other patch to the series.

J