Created attachment 44876 [details] Xorg log file My setup: a hd5770 eyefinity5 powercolor card, with 5 mini display port ports. running Fedora 15 with (from Xorg.0.log) "X.Org X Server 1.10.0 Release Date: 2011-2-25" and radeon_drv.so 6.14.99, my card is recognized as a "Chipset: "ATI Radeon HD 5700 Series" (ChipID = 0x68b8)". I have 4 connected Samsung 2333 screens using the following conneectors: DisplayPort-0 mdp to dvi Screen 0 DisplayPort-1 mdp to dvi Screen 1 DisplayPort-2 mdp to dp + active dp to dvi Screen 2 DisplayPort-3 mdp to dp + active dp to dvi Screen 3 The connecetors are either passive (mdp to dvi and mdp to dp) or active (dp to dvi). The problems: occasionally all four screens will work fine. When they do, it will stay that way until I try to suspend the computer. After return from suspend, one of the screens does not come up (the same screen). This appeared to be related to the cable connected to it, but I also had a case (1) where I would get: [drm:atom_dp_get_link_status] *ERROR* displayport link status failed. And then by switching to another VT and back to X the display would come up. Other interesting messages: Whenever I switch VT's from Xorg to a non Xorg VT I get a bunch of these: [ 6672.850940] [drm] force priority to high Also: After that one screen doesn't come up, disconnecting the other three doesn't help. I couldn't figure out what causes it to come back yet, although playing with the cable seemed to help (but then I had case 1 mentioned above). Also: But using the same cable and adapter with a different screen does work. So it appears that the screen/card interaction is the problem after all. Which is why I'm filing this bug after all. To be clear: if "Screen 2" from above doesn't show a picture (btw it does notice there is termination, i.e. it doesn't present the 'cable not plugged' caption), and I replace Screen 2 and Screen 0, then change VT's twice (out and in to Xorg - this is required for some reason), then Screen 0 will show up fine, negating the option it is a cable/adapter issue (at least it isn't just that issue).
Created attachment 44877 [details] dmesg output grep for drm
(In reply to comment #1) > Created an attachment (id=44877) [details] > dmesg output > > grep for drm I did some more moving of cables around, it really looks like just one faulty cable (although it does work with it occasionally - but that is consistent with a loose connection somewhere), so I'm closing this.
(In reply to comment #2) > (In reply to comment #1) > > Created an attachment (id=44877) [details] [details] > > dmesg output > > > > grep for drm > > I did some more moving of cables around, it really looks like just one faulty > cable (although it does work with it occasionally - but that is consistent with > a loose connection somewhere), so I'm closing this. It was a faulty cable.
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.