Bug 1398 - DRI resume garbles screen on Dell Latitude D600 Radeon 9000 M9
Summary: DRI resume garbles screen on Dell Latitude D600 Radeon 9000 M9
Status: RESOLVED DUPLICATE of bug 1220
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 6.8.0
Hardware: Other Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-16 00:15 UTC by Giridhar Pemmasani
Modified: 2004-09-28 10:49 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Giridhar Pemmasani 2004-09-16 00:15:09 UTC
I have Dell Latitude D600 laptop with Radeon R250 Lf (Radeon Mobility 9000 M9) 
rev 01 card. This card works fine with XFree86 with suspend+resume both S3 and 
S4. However, Xorg (I have tried 6.8.0 as well as a few CVS versions in the 
past couple of weeks), without DRI, it resumes fine, but of course, X is too 
slow. With DRI, right after switching to VT 7, the screen is garbled (white 
pixels whizz around and nothing that was there before suspend can be seen). 
With a bit of trail and error, found out that the following statement  
   
_ret = drmCommandNone(info->drmFD, DRM_RADEON_CP_RESUME); 
 
in DRIResume function causes this problem. If I put a return statement right 
before the above statement, screen is restored with some ghosting, although X 
hangs. 
 
I also need to use a patch to POST the card during resume, otherwise X hangs. 
There are couple of patches for this: see 
http://www.loria.fr/~thome/d600/index.php
Comment 1 Karol Kozimor 2004-09-21 00:28:27 UTC
This is a duplicate of #1220. 
Comment 2 Giridhar Pemmasani 2004-09-29 03:49:27 UTC
This indeed is same as bug #1220. In fact, the fix there also fixes the 
problem with this setup, so please consider this bug as resolved. 

*** This bug has been marked as a duplicate of 1220 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.