Created attachment 57766 [details] [review] Xorg log with the disconnect event at the bottom My monitor is SyncMaster 305Tplus connected to a DP-DLDVI adapter, which is hooked to the dp port of my llano mb. The monitor won't accept any other resolution than 2560x1600 and 1280x800, but EDID doesn't find those. To compensate, I'm using these lines in my .xinitrc: xrandr --newmode 2560x1600 268.00 2560 2608 2640 2720 1600 1603 1609 1646 +hsync -vsync xrandr --addmode DisplayPort-0 2560x1600 xrandr --newmode "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync xrandr --addmode DisplayPort-0 "1280x800"x59.9 xrandr --output DisplayPort-0 --mode 2560x1600 xrandr --output DVI-0 --rotate left --auto --right-of DisplayPort-0 Today after closing a window, the monitor suddenly went dark. Xorg log seems to show almost like it was rediscovered, or something, but trying to reset the mode doesn't work: $ xrandr --newmode 2560x1600 268.00 2560 2608 2640 2720 1600 1603 1609 1646 +hsync -vsync X Error of failed request: BadName (named color or font does not exist) Major opcode of failed request: 150 (RANDR) Minor opcode of failed request: 16 (RRCreateMode) Serial number of failed request: 29 Current serial number in output stream: 29 Same with trying to add the 1280 mode. So I can't turn the monitor on without rebooting. Not sure what happened there...
Just wanted to clarify, that rebooting X was enough, didn't have to reboot the whole machine.
Are you using an active or passive DP to DVI adapter? Also please attach your dmesg output.
Does you monitor claim it is in power save when it goes dark? If so maybe the root cause is similar to my https://bugs.freedesktop.org/show_bug.cgi?id=46711.
Active, powered from USB.
Created attachment 57771 [details] dmesg
Yes, it went to powersave. In the desktop manager, before login (and thus before setting the right modes in .xinitrc), it shows primary colors which is the monitor's way of saying that it doesn't understand the signal.
This has happened several times more to me. It happens very often when watching a HD video, and some times when viewing photos. Hasn't happened in normal desktop use. I've also noticed that I can get it back on by forcing it off with xrandr, and then back on.
Seems like I can reproduce this every time I view a certain photo taken with my phone in feh...
Does booting with radeon.disp_priority=2 on the kernel command line in grub help?
Unfortunately not.
-- 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/252.
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.