-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong xrandr pattern match? #12
Comments
I had that problem too, until I created a file at
in it. Then I rebooted and |
I created that file, but it doesn't seem to have had an affect on my system. |
What driver are you using? |
NVidia 435.21 from Ubuntu 19.10. The driver appears to be working fine; it's just the optimus applet that would be nice to have. |
I see. I found this nice instruction, its for Mint actually, but works well for Ubuntu too. By following these instructions and also creating that file at |
I followed those instructions, I think.
Bad:
So, it seems like I can choose between full mode switching via the applet (if I patch it to allow I still think the applet needs to recognise both strings. |
@a-m-s thanks, good to know. Yes, I agree that applet needs to recognize both strings. |
The applet doesn't appear to work correctly for me. It shows the Prime Profile I currently have selected, but does not offer any others for me to switch to.
If I select On-demand mode in the NVidia X Server Settings, reboot, and then try offload-glx, it says
xrandr: NVIDIA GPU screen not detected.
I have an NVidia Quadro M3000M. It shows in xrandr --listproviders like this:
The problem seems to be that mate-optimus is expecting to find
NVIDIA-G
where I haveNVIDIA-0
.If I change the pattern match to
NVIDIA-0
, then both scripts function as expected (although I can't see any performance difference between on-demand and performance mode, but I don't think that's your fault as I still can't if I reboot into performance mode only.)The text was updated successfully, but these errors were encountered: