Bug 218825 – Boot flag vga=extended doesn't work (setting doesn't stay)

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 218825 - Boot flag vga=extended doesn't work (setting doesn't stay)

Summary:	Boot flag vga=extended doesn't work (setting doesn't stay)

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	initscripts (Show other bugs)
Sub Component:
Version:	6
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2006-12-07 13:25 EST by Bryan Christ
Modified:	2014-03-16 23:04 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-12-07 13:29:30 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Bryan Christ 2006-12-07 13:25:01 EST

Description of problem:

When the boot flag vga=extended is initially set, the console changes mode for a
brief moment and then reverts back to the standard 80x25 text mode.

Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:
1.  Modify the grub boot paramaters to add vga=extended and remove rhgb
2.  Boot image
3.
  
Actual results:

See description

Expected results:

Console permanently set to 80x50

Additional info:

Comment 1 Bill Nottingham 2006-12-07 13:29:30 EST

vga=ext merely sets a different vga font. To have it be permanent, put a
different font in /etc/sysconfig/i18n for sysfont (i.e., LatArCyrHeb-08 to run
in 80x50).

Comment 2 Bryan Christ 2006-12-07 13:33:10 EST

Thanks.  At least this is documented now.  Google turned up nothing on this.

Note You need to log in before you can comment on or make changes to this bug.