Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 179888 - FEAT: RHEL3 U8: request updates to the ATI RN50 driver
FEAT: RHEL3 U8: request updates to the ATI RN50 driver
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: XFree86 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: X/OpenGL Maintenance List
David Lawrence
: FutureFeature, Reopened
: 179889 (view as bug list)
Depends On:
Blocks: 170417 193174
  Show dependency treegraph
Reported: 2006-02-03 12:03 EST by Issue Tracker
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-07-11 12:38:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Issue Tracker 2006-02-03 12:03:44 EST
Escalated to Bugzilla from IssueTracker
Comment 2 Ronald Pacheco 2006-02-03 12:08:58 EST
*** Bug 179889 has been marked as a duplicate of this bug. ***
Comment 3 Ernie Petrides 2006-02-03 19:10:13 EST
Ron, which rn50 driver version is needed and for what reason(s)?  Thanks.
Comment 4 Tom Coughlan 2006-02-06 10:13:19 EST
This is a video device. 
Comment 10 Mike A. Harris 2006-05-02 06:17:39 EDT
Issue has received a NACK from PM, and has not had any information provided
after multiple requests have been made.

Closing issue due to inactivity, and setting resolution to INSUFFICIENT_DATA
Comment 13 Chris Williams 2006-06-05 13:16:31 EDT
This is HP's complaint:

We're seeing a lot of unnecessary screen refreshing (blanking for a split second
type events) on boxes with the ATI RN50 video controller.  This wasn't happening
with RHEL3U7.  Perhaps something is awry with this video driver?

I had them downgrade to 4.3.0-98 (from U7) and they said all was well.

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