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
My laptop has an iGPU and dGPU, and I switch between them via a MUX Switch in BIOS. This switches the connected on a hardware level, rather than a software level, which leads to outputs having different namings.
When running solely on the dGPU my outputs are listed as:
DP-0
DP-1
HDMI-0
DP-2
Where DP-2 is my laptop monitor. Do note that it's missing the common eDP name. This makes autorandr unable to track if the lid is closed or not due to the following RegEx:
Would it be possible to track this in some other way?
The text was updated successfully, but these errors were encountered:
sQVe
changed the title
Unable to save lid state when using NVIDIA GPU
Unable to save lid state when using NVIDIA GPU (no eDP / LVDS output)
Nov 10, 2023
I'm experiencing the same issue with autorandr failing to detect the lid status due to the RegEx used for identifying the internal display. One potential solution could be to allow users to explicitly specify the name of the internal display in the ~/.config/autorandr/settings.ini file. Alternatively, adding a new option like --internal <output> to autorandr would enable users to manually set the display name.
Hey,
My laptop has an iGPU and dGPU, and I switch between them via a MUX Switch in BIOS. This switches the connected on a hardware level, rather than a software level, which leads to outputs having different namings.
When running solely on the dGPU my outputs are listed as:
Where
DP-2
is my laptop monitor. Do note that it's missing the commoneDP
name. This makesautorandr
unable to track if the lid is closed or not due to the following RegEx:autorandr/autorandr.py
Lines 150 to 152 in bb98da7
Would it be possible to track this in some other way?
The text was updated successfully, but these errors were encountered: