Bug 46977

Summary: Unresolved symbols in Cirrus driver.
Product: [Retired] Red Hat Linux Reporter: william rose <wrose>
Component: XFree86Assignee: Mike A. Harris <mharris>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-07-11 17:16:36 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:
Attachments:
Description Flags
The X log file. none

Description william rose 2001-07-02 15:13:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Description of problem:
During the installation process when X is set up on an HP LPr with a 
Cirrus Logic GD544x, the screen starts to show the Gnome desktop so that 
you can confirm the settings, but then goes black. No alterations in the 
setup will allow it to be viewed more that 1 second or so. After finishing 
the installation, and trying 'startx' to run X, same thing. Looking at X's 
output on the console shows an error message that there are unresolved 
symbols in the Cirrus driver. This may be the fault of anaconda and not X, 
I'm not sure.

How reproducible:
Always

Steps to Reproduce:
1. Install on an HP LPr
2.
3.
	

Additional info:

Comment 1 Mike A. Harris 2001-07-03 01:25:46 UTC
No, this would be an X server bug, or a misconfiguration.  Most likely
a bug though.  Please attach your X server log, and config as separate
uncompressed files using the file attachment link below.  I have fixed
a bug similar to this, so it might be fixed already.  Once I see your logs,
etc. I can be more certain though.

Thanks.

Comment 2 william rose 2001-07-11 17:16:32 UTC
Created attachment 23312 [details]
The X log file.

Comment 3 Mike A. Harris 2001-07-17 15:19:02 UTC
Yes, this is fixed internally, in 4.0.3-22.5 and an errata will appear in
a future errata release.