Created attachment 37311 [details]
digicam picture of both monitors
After resuming a previous (via pm-suspend) suspended system
the second monitor only shows a garbled picture.
Running xrandr to switch resolution seems to work, but
the picture still ist truncated.
This is a kms/multihead configuration.
latest xf86-video-ati from git
latest libdrm from git
latest mesa from git
Created attachment 37312 [details]
Created attachment 37313 [details]
Created attachment 37314 [details] [review]
Created attachment 37315 [details]
Does the other monitor work properly if you turn it off and then re-enable it with xrandr (e.g., --off, followed by --auto)?
Does doing a VT switch before suspend help?
No / No.
It even doesn't seem to work after a warm reboot.
I only get a test picture (as if there was no
connection between monitor and graphic card)
when the bios boots up.
I had to hard reset the computer
to get a working second monitor again.
Does the second monitor enable properly if you cold boot without it attached and then attach it after X has started?
If i run 'xrandr --output DVI-1 --off' followed by
'xrandr --output DVI-1 --auto' the second monitor switches off
and then on again (garbled screen).
Now if i run 'xrandr --output DVI-0 --auto' (happend accidentally first time),
monitor one switches to off and the second monitor shows
a correct piture again. Huh?!
Running 'xrandr --output DVI-0 --auto' afterwards makes
monitor one work and monitor two have a garbled picture again.
Will now try that cold boot thing.
Created attachment 37316 [details]
digicam picture of console after resume and vt switch
(In reply to comment #8)
> Does the second monitor enable properly if you cold boot without it attached
> and then attach it after X has started?
I think Yes.
I have to run 'xrandr --output DVI-1 --auto' to
get my desktop back, though.
Enabling "Repost Video On S3 Resume" in BIOS seems
to help a lot. I've send my computer into sleepmode
for a couple of times now and the second monitor has
always been working fine after resuming.
I actually dunno what this BIOS option does,
but it seems to be a solution.
-- 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/144.