From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0055320345==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 99E3289E65 for ; Mon, 3 Dec 2018 20:04:43 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0055320345== Content-Type: multipart/alternative; boundary="15438674830.4043.10328" Content-Transfer-Encoding: 7bit --15438674830.4043.10328 Date: Mon, 3 Dec 2018 20:04:43 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D108934 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 plug= ged 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 on= ly recently. --=20 You are receiving this mail because: You are the assignee for the bug.= --15438674830.4043.10328 Date: Mon, 3 Dec 2018 20:04:43 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
Bug ID 108934
Summary [Dualscreen] "No signal" issues when booting with D= VI 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&qu=
ot; 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 on=
ly
recently.


You are receiving this mail because:
  • You are the assignee for the bug.
= --15438674830.4043.10328-- --===============0055320345== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0055320345==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 108934] [Dualscreen] "No signal" issues when booting with DVI and HDMI screens both plugged in Date: Tue, 04 Dec 2018 10:11:37 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1008475789==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 734076E13F for ; Tue, 4 Dec 2018 10:11:37 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1008475789== Content-Type: multipart/alternative; boundary="15439182971.15eA547.8767" Content-Transfer-Encoding: 7bit --15439182971.15eA547.8767 Date: Tue, 4 Dec 2018 10:11:37 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D108934 --- Comment #1 from Michel D=C3=A4nzer --- Please attach the corresponding output of dmesg, and the Xorg log file if you're using Xorg. --=20 You are receiving this mail because: You are the assignee for the bug.= --15439182971.15eA547.8767 Date: Tue, 4 Dec 2018 10:11:37 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 1 on bug 10893= 4 from Michel D=C3=A4nzer
Please attach the corresponding output of dmesg, and the Xorg =
log file if
you're using Xorg.


You are receiving this mail because:
  • You are the assignee for the bug.
= --15439182971.15eA547.8767-- --===============1008475789== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1008475789==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 108934] [Dualscreen] "No signal" issues when booting with DVI and HDMI screens both plugged in Date: Sat, 08 Dec 2018 12:15:52 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1602971430==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id D39606E923 for ; Sat, 8 Dec 2018 12:15:52 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1602971430== Content-Type: multipart/alternative; boundary="15442713520.e4ACFA.31949" Content-Transfer-Encoding: 7bit --15442713520.e4ACFA.31949 Date: Sat, 8 Dec 2018 12:15:52 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D108934 --- Comment #2 from Laurent Pointecouteau = --- Created attachment 142751 --> https://bugs.freedesktop.org/attachment.cgi?id=3D142751&action=3Dedit Boot log with suspend Hre is my boot log from my current session. The HDMI cable is plugged in du= ring boot and the HDMI TV displays "No signal". Around ~12:59, I've switched from the current "Split-screen" setting to "Single screen" (selecting my HDMI TV) with gnome-control-center, and the DVI screen went black with a "no signal" message, whereas the TV displays "Unsupported resolution" for a while, then goes back to "No signal". I've then pressed the Power button of my computer= in order to suspend it, then pressed the Enter touch of my keyboard in order to wake it up. The two screens then displayed the correct image according to t= he "Split-screen" initial setting. Switching to others settings in gnome-control-center works fine. --=20 You are receiving this mail because: You are the assignee for the bug.= --15442713520.e4ACFA.31949 Date: Sat, 8 Dec 2018 12:15:52 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 2 on bug 10893= 4 from Laurent Pointecou= teau
Created attachment 142751<=
/a> [details]
Boot log with suspend

Hre is my boot log from my current session. The HDMI cable is plugged in du=
ring
boot and the HDMI TV displays "No signal". Around ~12:59, I've sw=
itched from
the current "Split-screen" setting to "Single screen" (=
selecting my HDMI TV)
with gnome-control-center, and the DVI screen went black with a "no si=
gnal"
message, whereas the TV displays "Unsupported resolution" for a w=
hile, then
goes back to "No signal". I've then pressed the Power button of m=
y computer in
order to suspend it, then pressed the Enter touch of my keyboard in order to
wake it up. The two screens then displayed the correct image according to t=
he
"Split-screen" initial setting. Switching to others settings in
gnome-control-center works fine.


You are receiving this mail because:
  • You are the assignee for the bug.
= --15442713520.e4ACFA.31949-- --===============1602971430== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1602971430==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 108934] [Dualscreen] "No signal" issues when booting with DVI and HDMI screens both plugged in Date: Wed, 20 Nov 2019 07:51:17 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1610156322==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 1C5376E19A for ; Wed, 20 Nov 2019 07:51:17 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1610156322== Content-Type: multipart/alternative; boundary="15742362770.8dDD75894.1805" Content-Transfer-Encoding: 7bit --15742362770.8dDD75894.1805 Date: Wed, 20 Nov 2019 07:51:17 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D108934 Martin Peres changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #3 from Martin Peres --- -- 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/624. --=20 You are receiving this mail because: You are the assignee for the bug.= --15742362770.8dDD75894.1805 Date: Wed, 20 Nov 2019 07:51:17 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated <= span class=3D"fn">Martin Peres changed bug 10893= 4
What Removed Added
Resolution --- MOVED
Status NEW RESOLVED

Commen= t # 3 on bug 10893= 4 from Martin Peres
-- 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/624.


You are receiving this mail because:
  • You are the assignee for the bug.
= --15742362770.8dDD75894.1805-- --===============1610156322== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1610156322==--