Bug 249472 - Latest xorg updates break ATI Rage Pro video
Summary: Latest xorg updates break ATI Rage Pro video
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 7
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-24 21:14 UTC by Tom Wood
Modified: 2008-06-17 01:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-17 01:57:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
X server log (49.41 KB, text/plain)
2007-07-24 21:14 UTC, Tom Wood
no flags Details
xorg.conf (850 bytes, application/octet-stream)
2007-07-24 21:15 UTC, Tom Wood
no flags Details

Description Tom Wood 2007-07-24 21:14:31 UTC
Description of problem:
Latest updates broke X on ATI Rage Pro

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.3.0.0-9.fc7
xorg-x11-drv-ati-6.6.3-4.fc7

How reproducible: Every time


Steps to Reproduce:
1.  Do a fresh install of F7 onto old PC with ATI Rage onboard video;
2.  Reboot after install and watch X run perfectly;
3.  Run "yum -y update";
4.  Watch X no longer work;
5.  Frustrate yourself to no end running "system-config-display --reconfig" to
no avail.
  
Actual results:

No X
Expected results:

X
Additional info:

System is an old Dell.  Smolt ID is 4f3840c2-3916-4322-9de0-247ce8d286e6

Comment 1 Tom Wood 2007-07-24 21:14:32 UTC
Created attachment 159886 [details]
X server log

Comment 2 Tom Wood 2007-07-24 21:15:18 UTC
Created attachment 159887 [details]
xorg.conf

Comment 3 Adam Jackson 2007-07-27 21:26:56 UTC
Can you isolate whether it was 

Comment 4 Adam Jackson 2007-07-27 21:27:26 UTC
Can you isolate whether it was the ATI driver or the server update that caused
the problem?

Comment 5 Bug Zapper 2008-05-14 13:39:45 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
http://docs.fedoraproject.org/release-notes/

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2008-06-17 01:57:31 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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