Bug 53339 - xf86cfg constructs broken XF86Config-4 for Matrox G450
xf86cfg constructs broken XF86Config-4 for Matrox G450
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
7.3
i386 Linux
low Severity low
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-09-06 17:45 EDT by David Lawrence
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-10-11 15:41:12 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)
Broken XF86Config-4 (1.03 KB, text/plain)
2001-09-06 17:46 EDT, David Lawrence
no flags Details
Output showing error generated. (4.15 KB, text/plain)
2001-09-06 17:46 EDT, David Lawrence
no flags Details

  None (edit)
Description David Lawrence 2001-09-06 17:45:53 EDT
Description of Problem:
When using xf86cfg to configure XFree86 4.1 with a Matrox G450, it adds a
line called ChipSet which generates an error when starting X. If you
comment the line out then X starts properly. Also the files section is not
getting generated properly when starting with a blank configuration. I am
attaching the relevant output.

Version-Release number of selected component (if applicable):
XFree86-xf86cfg-4.1.0-2
Comment 1 David Lawrence 2001-09-06 17:46:26 EDT
Created attachment 31174 [details]
Broken XF86Config-4
Comment 2 David Lawrence 2001-09-06 17:46:57 EDT
Created attachment 31175 [details]
Output showing error generated.
Comment 3 Mike A. Harris 2001-11-01 07:25:30 EST
Preston has closed many bugs against xf86cfg in the past as
"we do not support xf86cfg", so I am sending this upstream as
well, and closing it for now.  I'm sure if the problem still
exists, it stands a better chance of getting fixed that way.

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