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
As of right now method 2/3 is working for gamescope session under steamos like OSes such as bazzite/nobara/chimeraOS while method 1 is not (according to my experience with Ayaneo geek 1s and ho elitebook 1030g3). Unfortunately by doing so the internal display stays on during boot. Would it beneficial to run an export-gpu command after it? Maybe adding an entry point for custom command would cut it? I was experiencing with something along the lines of "if egpu is connected then run this script" but I had no success with a systemd service.
The text was updated successfully, but these errors were encountered:
As of right now method 2/3 is working for gamescope session under steamos like OSes such as bazzite/nobara/chimeraOS while method 1 is not (according to my experience with Ayaneo geek 1s and ho elitebook 1030g3). Unfortunately by doing so the internal display stays on during boot. Would it beneficial to run an export-gpu command after it? Maybe adding an entry point for custom command would cut it? I was experiencing with something along the lines of "if egpu is connected then run this script" but I had no success with a systemd service.
The text was updated successfully, but these errors were encountered: