Bug 166423 – vesa driver mode

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 166423 - vesa driver mode

Summary:	vesa driver mode

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	initscripts (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All 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:	2005-08-20 17:09 EDT by Rahul Sundaram
Modified:	2014-03-16 22:55 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-10-03 17:32:42 EDT
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 Rahul Sundaram 2005-08-20 17:09:34 EDT

Description of problem:

We do not provide an easy way for the user currently to recover from a broken X
configuration other than system-config-display


Expected results:

A init script enhancement to provide a Windows like safe modem would be nice. A
potential implementation could be 

Press "F1"  to boot into safe mode which will boot into the Xorg Vesa driver
using the current configuration otherwise merely changing the driver only saving
for the current session


Additional info:

Such a implementation is not likely to work across all architectures and
displays according to mharris but I consider it worth a try if we push it in
rawhide quickly and ask for feedback to see how well it performs in the
development tree and enable it later on FC5 or a later relaase depending on
feedback.

Comment 1 Bill Nottingham 2005-10-03 17:32:42 EDT

Adding code to initscripts to edit the X config file seems rather impractical,
especially since with split X it may be likely that the vesa driver isn't even
installed.

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