Bug 60231

Summary:	DisplayPort monitor not detected on PowerColor Radeon HD 4850
Product:	Drivers	Reporter:	prettyvanilla
Component:	Video(DRI - non Intel)	Assignee:	drivers_video-dri
Status:	NEW ---
Severity:	normal	CC:	alexdeucher, szg00000
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	3.10	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	dmesg output with dvi and displayport connected (drm.debug=0xE) dmesg output with dvi and displayport connected (drm.debug=0xE) xrandr --verbose Xorg.0.log

Description prettyvanilla 2013-06-29 20:58:25 UTC

Created attachment 106381 [details]
dmesg output with dvi and displayport connected (drm.debug=0xE)

I have a dual-monitor setup via my PowerColor Radeon HD 4850 - one monitor is connected via DVI, the other (main) one via DisplayPort.
While I was using fglrx that setup worked fine, with the radeon driver/module though only the dvi monitor is detected. DisplayPort is always reported as disconnected, no matter whether it is the only connected monitor at boot or is hotplugged later.

The monitors in question are a Samsung SyncMaster 970P via DVI and a Eizo FlexScan EV2333WH via DisplayPort. The Eizo does still work fine via DVI.

I'm currently running a 3.10 mainline kernel (+ radeon dpm patches) on Arch Linux. I remember trying this about 2 years ago I think, when it didn't work as well. Trying the 3.0 lts-kernel yields the same results, 3.10 mainline without dpm patches ditto.

I've attached the dmesg output with drm.debug=0xE set as kernel parameter.

I have found another bug report at launchpad that seems to describe the same issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1035556
Since that bug also happens on a PowerColor card, it seems likely to be a brand-/model-specific issue.

Comment 1 Alex Deucher 2013-08-20 13:08:09 UTC

Possibly related to bug 60639.  Can you try the patch on that bug?

Comment 2 prettyvanilla 2013-08-20 21:52:57 UTC

Created attachment 107258 [details]
dmesg output with dvi and displayport connected (drm.debug=0xE)

Comment 3 prettyvanilla 2013-08-20 21:53:33 UTC

Created attachment 107259 [details]
xrandr --verbose

Comment 4 prettyvanilla 2013-08-20 21:54:02 UTC

Created attachment 107260 [details]
Xorg.0.log

Comment 5 prettyvanilla 2013-08-20 21:58:36 UTC

I am running a current mainline kernel until dpm stabilises, so I am on 3.11rc6 currently, which has the patch mentioned already applied. Sadly, no change in behaviour.
I updated the dmesg output attachment and added xrandr and X.org log output.
Anything in particular I should look for to get to the root of the problem?