Description of problem: When the monitor (iiyama) attached via Displayport is turned off and on again, it only says "no signal". When the display(s) are rearranged in the Displays Preferences, the display works again. Version-Release number of selected component (if applicable): x11-server-1.16.4-2.mga5.src.rpm x11-driver-video-ati-7.5.0-3.mga5 How reproducible: Always Steps to Reproduce: 1. Configure (dual) display on Displayport (iiyama) 2. Power cycle the monitor. 3. To recover, goto Displays Preferences -> "Arrange Combined Displays", move the displays around, apply and wait to timeout. Despite nothing changed, all windows will move to new locations (might be a separate bug in gnome-shell). Reproducible: Steps to Reproduce:
I've been told such behaviour is a feature of DisplayPorts, I hope that information was wrong! CC'ing some people with more knowledge. Anyway: Is this bug still valid? If not, please close it :-) If still valid: * What is the output of: lspcidrake -v | grep Card * If you switch to a text tty before turning your iiyama off, do you then get the "no signal" message, too, when you turn it back on? Please do also: * reboot * reproduce this bug * then run, as root: journalctl -ab > output.txt * and then attach output.txt to this bug report * and please do also attach /etc/X11/xorg.config
Keywords: (none) => NEEDINFOCC: (none) => gnome, kernel, marja11, thierry.vignaud
Hey Marja! Hard to tell. As you can imagine, it wasn't an acceptable situation and certainly not for a year or more, so I soon replaced Xorg and the radeon driver with a newer version, which works reasonably fine (minor issues with tearing but hey, it doesn't require a reboot when the monitor suspends :). So I have no idea how the current Mageia 5 packages would perform. Best, Herbert
CC: (none) => herbert
(In reply to Herbert Poetzl from comment #2) > > So I have no idea how the current Mageia 5 packages would perform. > Thanks for the feedback, Herbert. Setting to unconfirmed, then, since we cannot investigate this further without similar hardware, and because no one else reported this. @ anyone hitting this bug in Mageia 5 and/or cauldron: Please change the Status of this bug back to NEW, and do also answer the questions in comment 1 :-)
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
(In reply to Marja van Waes from comment #3) > (In reply to Herbert Poetzl from comment #2) > > > > > So I have no idea how the current Mageia 5 packages would perform. > > > > > Thanks for the feedback, Herbert. > > Setting to unconfirmed, then, since we cannot investigate this further > without similar hardware, and because no one else reported this. > Closing as OLD, now, because no one else reported or confirmed this issue, and it is already two years ago that Herbert hit it.
Resolution: (none) => OLDStatus: UNCONFIRMED => RESOLVED