Created attachment 60820 [details] dmesg output Radeon HD 7870 mesa 8.0.2 Kernel 3.4-rc5 X.Org X Server 1.12.0 xf86-video-modesetting 0.2.0 * Monitor is a DVI monitor connected to an active mini-displayport to DVI adaptor. * Output to all three screens functions in Windows. * dmesg output and xrandr output are able to see the display and print out the correct supported resolutions * HDMI and DVI output are functioning correctly on the card. * Using xrandr I'm able to get the X server to think that the display is present and functioning. (I can place windows and the cursor on the screen) * The display is in power-saving mode from the moment that the framebuffer console initializes. I'm not able to get any image on it.
I got tired of only being able to use ⅔ of my monitors, so I tried using the integrated graphics (Intel hd4000 / ivy bridge) to power them. (Motherboard has VGA, DVI, HDMI and full-size Displayport). The odd thing I discovered is that the same monitor continues to not work. I've eliminated the possibility of it being the DVI cable as I've tried two of them. It's not the adaptor because the motherboard takes a full-size Displayport adaptor and the HD7870 takes a mini-displayport. Is there some code that is shared between the intel and radeon mode setting drivers?
Does the monitor come up at all? E.g., is the bios able to light it up at boot on either card?
Yes. The system dual-boots Windows. During boot the first kernel messages show up on both the HDMI monitor and the Displayport monitor, nothing on the DVI. As soon as KMS kicks in, there's the expected 1920x1080 on the DVI and the HDMI, but the Displayport goes black.
Still present in kernel 3.5-rc1
Still present in kernels 3.19.0-031900rc4 3.13.0-44 3.13.0-43 3.13.0-30 3.13.0-29 Also happens with just the DVI-D connector as well. Black screen only way out is with ALT+SysReq+REISUB You can't even switch to TTY1-6 with CTRL+ALT+F1-F6
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/265.
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.