Bug 102351 - Radeon R9 270: Flickering Screen (Dual Monitor setup)
Summary: Radeon R9 270: Flickering Screen (Dual Monitor setup)
Status: RESOLVED INVALID
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: 2015-08-05 20:39 UTC by beta992
Modified: 2015-08-29 17:29 UTC (History)
1 user (show)

See Also:
Kernel Version: Linux desktop1 4.2.0-1-mainline #1 SMP PREEMPT Thu Jul 30 19:02:38 CEST 2015 x86_64 GNU/Linux
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Samsung Monitor setup (361 bytes, text/plain)
2015-08-05 20:39 UTC, beta992 		Details
dmesg (69.44 KB, application/octet-stream)
2015-08-05 20:55 UTC, beta992 		Details
xorg log (54.84 KB, text/plain)
2015-08-05 20:56 UTC, beta992 		Details
Add an attachment (proposed patch, testcase, etc.)

Description beta992 2015-08-05 20:39:59 UTC 
Created attachment 184471 [details]
Samsung Monitor setup

Hardware Setup:
- ASUS P8H67-M Pro B3
- Club 3D Radeon R9 270 royalQueen:
*DP => works without any issues (DELL U2312HM)
*DVI => flickering, on/off (Samsung 2253LW)

Booting with the following parameters reduces the flickering, but still it keeps happening: radeon.audio=0 radeon.bapm=1 radeon.disp_priority=2 radeon.hw_i2c=1 radeon.msi=1 radeon.mst=1 radeon.tv=0

In Windows 8.1 this also happens, but less frequent then in Linux.

The Samsung monitor seems to be working fine (pretty old), but I think this could be a DVI issue (has only VGA/DVI-output), but can't test on HDMI.


Thanks and please let me know if more debug info is needed.
Comment 1 Alex Deucher 2015-08-05 20:48:49 UTC 
Please attach your xorg log and dmesg output.
Comment 2 beta992 2015-08-05 20:55:34 UTC 
Created attachment 184481 [details]
dmesg

dmesg output
Comment 3 beta992 2015-08-05 20:56:16 UTC 
Created attachment 184491 [details]
xorg log
Comment 4 beta992 2015-08-29 17:29:30 UTC 
After upgrading the drivers, replacing cables, etc. The issue seems to be fixed. Sorry about the incomplete & mixed message. :)
Note You need to log in before you can comment on or make changes to this bug.