[Bug 108934] [Dualscreen] "No signal" issues when booting with DVI and HDMI screens both plugged in - bugzilla-daemon

From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108934] [Dualscreen] "No signal" issues when booting with DVI and HDMI screens both plugged in
Date: Mon, 03 Dec 2018 20:04:43 +0000	[thread overview]
Message-ID: <bug-108934-502@http.bugs.freedesktop.org/> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1737 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=108934

            Bug ID: 108934
           Summary: [Dualscreen] "No signal" issues when booting with DVI
                    and HDMI screens both plugged in
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: laurent.pointecouteau@gmail.com

I'm using a AMD R9 380 video card on Arch Linux (with kernel 4.19.4 and the
latest `mesa` package installed), and since several weeks, dualscreen has a
buggy behavior. My Samsung TV displays "no signal" after booting while plugged
in my computer (using a HDMI cable), and when trying to switch display modes
using the GNOME control center (or the Super+P shortcut), my Iiyama ProLite
B2475HDS DVI monitor gets randomly disabled and displays "no signal" too
without ever recovering, forcing me to hard reboot.

I've tried to apply a kernel patch as suggested in bug #108704, but it only
removed the amdgpu-related error messages from dmesg, without fixing the
dualscreen issues. Since then, I've found two workarounds:
 - putting the system to sleep then waking it up seems to restore normal
functionality;
 - when booting with the HDMI cable unplugged, after plugging it in, screen
switching is not buggy anymore.

My setup does not allow me to safely downgrade to an older kernel, but I can
confirm that the screen settings started to exhibit this buggy behaviour only
recently.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3266 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel