Created attachment 133251 [details] x log I am unable to make the dual monitor setup work. One screen is attached over HDMI, the other over DVI. Individually they both work fine. Once I attach the second screen (DVI), it does not get signal and the HDMI screen shows both screens in some weird squeezed format next to each other. Depending on the settings in display preferences, I get various other weird results when the desktop gets uncontrollable (does not react to mouse clicks and keyboard events) so I have to restart the machine. After restart only the HDMI screen appears, it shows content normally according to single screen setup. torel@tornanomachine:~$ sudo lshw -c video *-display description: VGA compatible controller product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:28 memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:f000(size=64) torel@tornanomachine:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial torel@tornanomachine:~$ uname -a Linux tornanomachine 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:38:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux torel@tornanomachine:~$ X -version X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-83-generic x86_64 Ubuntu Current Operating System: Linux tornanomachine 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:38:41 UTC 2017 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic root=UUID=ca9b58a4-570c-4d39-9e7b-f75131f395b4 ro quiet splash vt.handoff=7 Build Date: 17 July 2017 05:05:12PM xorg-server 2:1.18.4-0ubuntu0.3 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. torel@tornanomachine:~$ xrandr Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 32767 x 32767 DP1 connected 800x600+1920+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00 800x600 60.32* 56.25 848x480 60.00 640x480 59.94 HDMI1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 521mm x 293mm 1920x1080 60.00*+ 50.00 59.94 1680x1050 59.88 1600x900 60.00 1280x1024 75.02 60.02 1440x900 59.90 1280x800 59.91 1152x864 75.00 1280x720 60.00 50.00 59.94 1024x768 75.08 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 720x576 50.00 720x480 60.00 59.94 640x480 75.00 72.81 66.67 60.00 59.94 720x400 70.08 HDMI2 disconnected (normal left inverted right x axis y axis) HDMI3 disconnected (normal left inverted right x axis y axis) VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis)
a similar issue has been reported here: https://askubuntu.com/questions/845814/ubuntu-16-04-1-lts-with-dual-monitor-and-integrated-intel-graphics
Capturing the drm.debug=0xe dmesg from boot should help identify the paths used by the DVI/HDMI connectors. Are you using an external dongle, or just the connectors as exposed by the motherboard?
Created attachment 133256 [details] dmesg log with only the HDMI screen attached to the machine
Hi Chris, many thanks for the prompt reply. Unfortunately I only could capture the dmesg log with a single monitor attached. I wrote a small script that writes dmesg into a file: dmesg > /home/torel/DualScreenIssue/dmesg_`date "+%Y_%m_%d_%H_%M_%S"`.log I made this script run after gnome has started up (by adding it at gnome-session-properties). Once I rebooted the machine with _both_ monitors attached, I saw a dmesg capture file of length 0! And I could not do anything on the UI anymore - on the HDMI screen the cursor could move only on the left edge of the screen and no mouse clicks were accepted (thats why I had to make this script run automatically). Answer to your other question: I don't use any dongle, I attach the monitors via HDMI and DVI cables directly to the motherboard. thx for looking into this, Balazs
What happens if you boot with one, and hotplug the other once the system is up and running?
Created attachment 133278 [details] hotplugging the DVI screen
When hotplugging the DVI screen: 1. The DVI screen does not turn on. An additional lunchbar appeares on the HDMI screen, see attached pic "hotplugging the DVI screen". It looks like this lunchbar is the one of the DVI screen, it seems like the area supposed to appear on the DVI is attempted to be drawn onto the top right of the HDMI screen (this area looks like 800x600 the size of the DVI screen) Then, when unplugging the DVI screen: 1. The HDMI screen switches off too 2. After a minute or so, the HDMI screen switches on again automatically and the screen is back to normal single screen mode.
Created attachment 133279 [details] dmesg log when hotplugging DVI screen loog for "drm_fb_helper_hotplug_event" in the log file to spot the hotplug event
torel@tornanomachine:~/DualScreenIssue$ grep WARNING dmesg_hotplug.log [ 1548.065904] WARNING: CPU: 1 PID: 1079 at /build/linux-YaBj6t/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1326 drm_wait_one_vblank+0x1b5/0x1c0 [drm]() [ 1548.118283] WARNING: CPU: 1 PID: 1079 at /build/linux-YaBj6t/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12796 intel_modeset_check_state+0x49b/0x8a0 [i915]() [ 1548.118879] WARNING: CPU: 1 PID: 1079 at /build/linux-YaBj6t/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12824 intel_modeset_check_state+0x6a0/0x8a0 [i915]() [ 1715.705911] WARNING: CPU: 3 PID: 1079 at /build/linux-YaBj6t/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:3965 intel_crtc_wait_for_pending_flips+0x1e2/0x240 [i915]() [ 1715.706612] WARNING: CPU: 3 PID: 1079 at /build/linux-YaBj6t/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:3970 intel_crtc_wait_for_pending_flips+0x233/0x240 [i915]()
Adding tag into "Whiteboard" field - ReadyForDev *Status is correct *Platform is included *Feature is included *Priority and Severity correctly set *Logs included
(In reply to Balazs Torma from comment #4) > Hi Chris, > > many thanks for the prompt reply. Unfortunately I only could capture the > dmesg log with a single monitor attached... Maybe too late, but kern.log could store the information needed, just rm it and reboot so you get a clean one.
First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Closing, please re-open is issue still exists.
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.