<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - PRIME output screen stays black on 1002:15d8 with 128MB VRAM" href="https://bugs.freedesktop.org/show_bug.cgi?id=111228#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - PRIME output screen stays black on 1002:15d8 with 128MB VRAM" href="https://bugs.freedesktop.org/show_bug.cgi?id=111228">bug 111228</a> from <a class="email" href="mailto:hhfeuer@gmx.de" title="Maik Freudenberg <hhfeuer@gmx.de>"> Maik Freudenberg</a> <pre>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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>