From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 111228] PRIME output screen stays black on 1002:15d8 with 128MB
VRAM
Date: Wed, 02 Oct 2019 07:44:19 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1735738264=="
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 5C9616E8D5
for ; Wed, 2 Oct 2019 07:44:19 +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
--===============1735738264==
Content-Type: multipart/alternative; boundary="15700022591.C5dFc.30383"
Content-Transfer-Encoding: 7bit
--15700022591.C5dFc.30383
Date: Wed, 2 Oct 2019 07:44:19 +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=3D111228
--- Comment #7 from Maik Freudenberg ---
Updating with info from other users with the same amd gpu with 128MB VRAM:
- one user was able to switch to VT and start a second Xserver which then
worked fine.
- another user found out that connecting an external monitor would work, was
able to log into gnome and in the monitor manager, the internal display sho=
wed
as disabled. So he could simply enable it and started working.
So this seems to be failing on xrandr --auto, not correctly adding the inte=
rnal
display to the config. Looking what Ubuntu does:
# Pass provider or sink and source
xrandr --setprovideroutputsource "$sink" "$src"
# Make sure xrandr sees all the outputs
xrandr --auto
# Do not move up. Only now xrandr shows the outputs
lvds=3D$(xrandr | grep -i -e "lvds" -e "edp" | head -n1 |cut -d " " -f 1)
xrandr --output "$lvds" --off
xrandr --output "$lvds" --auto
So it already disables and enables the internal display as a workaround for
something but this still isn't enough in this case.
Maybe this is some timing problem so that adding a "sleep 2" either before =
or
after xrandr --auto would make that work?
Doesn't explain why this is only happening on this specific model, though.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15700022591.C5dFc.30383
Date: Wed, 2 Oct 2019 07:44:19 +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 # 7
on bug 11122=
8
from =
Maik Freudenberg
Updating with info from other users with the same amd gpu with=
128MB VRAM:
- one user was able to switch to VT and start a second Xserver which then
worked fine.
- another user found out that connecting an external monitor would work, was
able to log into gnome and in the monitor manager, the internal display sho=
wed
as disabled. So he could simply enable it and started working.
So this seems to be failing on xrandr --auto, not correctly adding the inte=
rnal
display to the config. Looking what Ubuntu does:
# Pass provider or sink and source
xrandr --setprovideroutputsource "$sink" "$src"
# Make sure xrandr sees all the outputs
xrandr --auto
# Do not move up. Only now xrandr shows the outputs
lvds=3D$(xrandr | grep -i -e "lvds" -e "edp" | head -n1=
|cut -d " " -f 1)
xrandr --output "$lvds" --off
xrandr --output "$lvds" --auto
So it already disables and enables the internal display as a workaround for
something but this still isn't enough in this case.
Maybe this is some timing problem so that adding a "sleep 2" eith=
er before or
after xrandr --auto would make that work?
Doesn't explain why this is only happening on this specific model, though.<=
/pre>
You are receiving this mail because:
- You are the assignee for the bug.
=
--15700022591.C5dFc.30383--
--===============1735738264==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs
--===============1735738264==--