http://bugzilla.opensuse.org/show_bug.cgi?id=1100233 Chris Puttick changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.opensuse.o | |rg/show_bug.cgi?id=1079547 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1100233 http://bugzilla.opensuse.org/show_bug.cgi?id=1100233#c2 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chris@twoten.is Flags| |needinfo?(chris@twoten.is) --- Comment #2 from Stefan Dirsch --- Does xrandr --auto help to detect the native resolution of the monitors? Please attach also /var/log/Xorg.0.log. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1100233 http://bugzilla.opensuse.org/show_bug.cgi?id=1100233#c4 --- Comment #4 from Chris Puttick --- Created attachment 776325 --> http://bugzilla.opensuse.org/attachment.cgi?id=776325&action=edit Xorg.0.log attached. This is after a fresh boot, with one monitor having been turned off and on again to reproduce the issue. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1100233 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #776325|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1100233 http://bugzilla.opensuse.org/show_bug.cgi?id=1100233#c7 --- Comment #7 from Felix Miata --- (In reply to Chris Puttick from comment #0)

both 1080HD capable

Exactly what does this mean? Some "monitors" that "support" 1080 are actually 1366x768 TV screens intended to support 1080 TV programming and do not behave well connected to a PC. In attempting to reproduce this with Intel 630 video on my only native 1366x768 display, a Samsung TV, I had no problem getting Xorg into 1920x1080 by booting with TV on, or keeping it in 1920x1080 after cycling the TV power. With [AMD/ATI] RV610 [Radeon HD 2400 PRO], which only has DVI and DisplayPorts and requires a DisplayPort to HDMI adapter to connect to the Samsung, I have yet to find a way to get the TV into any 1920x1080 mode. Does using modesetting driver instead of amdgpu change anything? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1100233 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |CONFIRMED -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1100233 http://bugzilla.opensuse.org/show_bug.cgi?id=1100233#c10 --- Comment #10 from Chris Puttick --- Ok, adding Section "Device" Identifier "Default Device" Driver "modesetting" EndSection into 50-device.conf certainly altered the behaviour. Turning off the monitor connected by DP (the Dell) caused the HDMI connected monitor to switch to a lower resolution, turning back on caused both to return to the correct (desired, previously selected) 1920*1080. Turning off the HDMI connected one caused odd behaviour; the Dell retained correct resolution, but when the HDMI one was turned back on it all got weird - couldn't enable both monitors anymore, and once I managed to switch to the AOC/HDMI, the highest resolution options showing in Displays were in 5 figures and I couldn't choose anything less (click on it in dropdown, jumped to the max in the list. Had to reboot to get expected behaviour (sleep/resume didn't resume either display). The boot session with drm.debug=0xfe should be with 50-device.conf returned to defaults? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1100233 http://bugzilla.opensuse.org/show_bug.cgi?id=1100233#c13 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |NORESPONSE --- Comment #13 from Stefan Dirsch ---

Additionally please try to boot with drm.debug=0xfe parameter, reproduce the issue and attach kernel log.

Still open. We're still waiting for a response for more than two months now. Please reopen once you can provide the requested feedback. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.