Bug 86104 - ati radeon mobility 9000 fails to recover from normal blanking
ati radeon mobility 9000 fails to recover from normal blanking
Product: Red Hat Public Beta
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-03-13 19:06 EST by Eric Bourque
Modified: 2007-04-18 12:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-03-16 16:52:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
XF86Config file (3.26 KB, text/plain)
2003-03-13 19:07 EST, Eric Bourque
no flags Details
xdpyinfo output (4.01 KB, text/plain)
2003-03-13 19:09 EST, Eric Bourque
no flags Details
XFree86 log (42.78 KB, text/plain)
2003-03-14 00:15 EST, Eric Bourque
no flags Details

  None (edit)
Description Eric Bourque 2003-03-13 19:06:11 EST
I have a radeon mobility 9000 and 4.3.0-2.1. The radeon driver doesn't seem
to recover properly from screen blanking (there are several horizontal
white bars with spurious activity around them). It recovers fine from a
suspend however, so I find this strange.

This is on a Dell Inspiron 8200, so after going to a console, and using
Fn-D (blank screen) and waking it up a few times (almost always twice), the
display recovers, and I can go back into X.

I'm not using DRI if it makes a difference.
Comment 1 Eric Bourque 2003-03-13 19:07:44 EST
Created attachment 90588 [details]
XF86Config file
Comment 2 Eric Bourque 2003-03-13 19:09:24 EST
Created attachment 90589 [details]
xdpyinfo output
Comment 3 Mike A. Harris 2003-03-13 23:11:51 EST
Please attach X log file from a problem run.
Comment 4 Eric Bourque 2003-03-14 00:15:48 EST
Created attachment 90595 [details]
XFree86 log

During the run represented in this log, there were several suspend/resume
cycles which went fine and seem to be in the log, but I don't see anything from
when the screen blanks due to a (hardware) timeout. I believe the blank is
triggered from BIOS, not from dpms. In fact, I just tried 'xset dpms force off'
and it was fine.

Oddly, when I was running the vesa driver with 4.2.x in RH8, this problem
didn't exist.
Comment 5 Eric Bourque 2003-03-16 15:41:03 EST
I tried a boot without apmd, acpi, or bios related blanking, and there were no
problems. It really seems that this is a problem when recovering from a bios
blanking since dpms blanking works fine, as does a recover from suspend.
Comment 6 Mike A. Harris 2003-03-16 16:52:42 EST
Closing bug as NOTABUG, problem resolved as hardware having a buggy BIOS.

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