Bug 42787 - Video flickers on X1200 / RS690 over DVI
Summary: Video flickers on X1200 / RS690 over DVI
Status: RESOLVED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-16 22:14 UTC by Stephan Diestelhorst
Modified: 2014-07-03 20:27 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.4.22
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg of flickering system (52.88 KB, application/octet-stream)
2012-12-26 12:40 UTC, Stephan Diestelhorst 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Stephan Diestelhorst 2012-02-16 22:14:02 UTC 
I still experience flickering on the DVI of my on-board graphics card if I set the mode to 1920x180 (ragrdless which timing 59.9 / 60 Hz).  Tried both KMS / UMS, no real difference.  AFAICS, all pathes in other bug reports should be picked up by now.  It seems that graphics activity (moving a translucent window) is more prone to blanking the display.

Killing upowerd does not help, so it is not a polling issue.  CPU is is not properly detected by the BIOS (too old, no upgrade available), so it may (?) be that some registers (MTRRs?) are not set up properly.

Reducing the resolution does seem to help.
Comment 1 Michel Dänzer 2012-02-17 13:01:31 UTC 
Let's focus on KMS here.

Please attach the dmesg output.

Does radeon.disp_priority=2 help, or forcing a reduced blanking mode?
Comment 2 Stephan Diestelhorst 2012-12-26 12:36:18 UTC 
Tried radeon.disp_priority=2 and video=1920x1080MR@60 and I can still see the flicker.  Will attach a dmesg.
Comment 3 Stephan Diestelhorst 2012-12-26 12:40:46 UTC 
Created attachment 89691 [details]
dmesg of flickering system
Comment 4 xerofoify 2014-06-25 02:15:32 UTC 
Please check if this bug is still on newer kernel releases.
Otherwise you should this bug as it's now fixed:)
Cheers Nick
Comment 5 Stephan Diestelhorst 2014-07-03 20:27:23 UTC 
Closing, since I do not own the hardware in question anymore.
Note You need to log in before you can comment on or make changes to this bug.