Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 198674

Summary:	XFree86 wont start with mga or vesa driver
Product:	Red Hat Enterprise Linux 3	Reporter:	Sarah Prelutsky <sprelutsky>
Component:	XFree86	Assignee:	X/OpenGL Maintenance List <xgl-maint>
Status:	CLOSED WONTFIX	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-10-19 18:42:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sarah Prelutsky 2006-07-12 17:42:29 UTC

Description of problem: During installation the graphical install fails to
start. After installation startx or using init 5 fails to start.


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


How reproducible: All chassis with matrox g200 chipset


Steps to Reproduce: Install 3u7 or 3u8beta

  
Actual results: when you try to start xfree with the mga driver I get no screens
found. 

With vesa enabled i get

(EE) VESA(0): Set VBE Mode failed!

Fatal server error:
AddScreen/ScreenInit failed for driver 0


Expected results: xfree to start


Additional info: The only way i can get xfree to work is by using the vga driver
and setting the depth to 4 and i get a "usable" resolution.

Comment 1 Adam Jackson 2006-10-30 17:59:47 UTC

Please attach the /var/log/XFree86.0.log from an affected installation.

Comment 2 RHEL Program Management 2007-10-19 18:42:30 UTC

This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.