From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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 [thread overview]
Message-ID: <bug-111228-502-zonX9THVuc@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111228-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1378 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111228
--- Comment #7 from Maik Freudenberg <hhfeuer@gmx.de> ---
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 showed
as disabled. So he could simply enable it and started working.
So this seems to be failing on xrandr --auto, not correctly adding the internal
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=$(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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2262 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-10-02 7:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 1:43 [Bug 111228] PRIME output screen satys black on 1002:15d8 with 128MB VRAM bugzilla-daemon
2019-07-27 2:36 ` bugzilla-daemon
2019-07-27 2:37 ` bugzilla-daemon
2019-07-29 9:15 ` bugzilla-daemon
2019-07-29 9:26 ` bugzilla-daemon
2019-07-29 9:37 ` [Bug 111228] PRIME output screen stays " bugzilla-daemon
2019-08-06 10:42 ` bugzilla-daemon
2019-08-06 10:45 ` bugzilla-daemon
2019-10-02 7:44 ` bugzilla-daemon [this message]
2019-10-02 8:08 ` bugzilla-daemon
2019-11-19 9:37 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-111228-502-zonX9THVuc@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox