You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. Ever since using gamescope with the changes introduced in the new-color-toys branch, i've found that gamescope consistently fails to load when attempting to start a SteamOS session, either through Tty2, or on startup with a dedicated session through gamescope-session. I updated to the latest kernel supplied through the linux-hdr kernel pkgbuild prior to attempting to use gamescope updated as well.
The error that appears in the log when launching is xwm: We failed our modeset and have no mode to fall back to! (Initial modeset failed?): Invalid argument. The last working commit on my end is 1310315
The text was updated successfully, but these errors were encountered:
isaboll1
changed the title
Issue launching gamescope with HDR enabled using latest commits.
Issue launching gamescope/steamos-session with HDR enabled using latest commits.
Apr 30, 2023
As an update, it appears using the launch option --disable-color-management allows gamescope to be used with HDR monitors and not crash. It likely could be that the methods for acquiring MDR metadata from the monitor, might run into issues depending on the edid of the monitor, causing gamescope to crash.
Hello. Ever since using gamescope with the changes introduced in the new-color-toys branch, i've found that gamescope consistently fails to load when attempting to start a SteamOS session, either through Tty2, or on startup with a dedicated session through gamescope-session. I updated to the latest kernel supplied through the linux-hdr kernel pkgbuild prior to attempting to use gamescope updated as well.
The error that appears in the log when launching is
xwm: We failed our modeset and have no mode to fall back to! (Initial modeset failed?): Invalid argument
. The last working commit on my end is 1310315gamescope-stdout.log
modes.cfg.txt
patched_edid.bin.zip
The text was updated successfully, but these errors were encountered: