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
Great app. Works (almost) perfectly on my Ubuntu Gnome 15.04 install and happily switches between my Nvidia and Intel displays on my Dell XPS 15.
However, my issue is when I first boot and log in the indicator always shows the Nvidia icon despite the "Using: xxx" line in the popup showing it's using "Mesa DRI Intel(R) Haswell Mobile".
Then selecting "Quick switch graphics..." and logging out/in the icon is now the Intel icon and "Using:" is still "Mesa DRI Intel(R) Haswell Mobile".
Selecting "Quick switch graphics..." and logging out/in one more time finally gets me to my GeForce GT 750M graphics display.
Rebooting at this point puts me back on the Intel display (which is fine) and the process has to be started all over.
Not sure what's going on here. I'm happy to debug whatever/however is needed.
The text was updated successfully, but these errors were encountered:
JAZ-013
changed the title
Icon/state incorrect on log in.
Icon/state incorrect on boot and first log on.
Apr 28, 2015
Hello, JAZ-013. Do you happen to have Secure Boot turned ON? I've seen this issue when it's ON. It happens because NVIDIA's drivers aren't compatible with Secure Boot because of signing issues.
Great app. Works (almost) perfectly on my Ubuntu Gnome 15.04 install and happily switches between my Nvidia and Intel displays on my Dell XPS 15.
However, my issue is when I first boot and log in the indicator always shows the Nvidia icon despite the "Using: xxx" line in the popup showing it's using "Mesa DRI Intel(R) Haswell Mobile".
Then selecting "Quick switch graphics..." and logging out/in the icon is now the Intel icon and "Using:" is still "Mesa DRI Intel(R) Haswell Mobile".
Selecting "Quick switch graphics..." and logging out/in one more time finally gets me to my GeForce GT 750M graphics display.
Rebooting at this point puts me back on the Intel display (which is fine) and the process has to be started all over.
Not sure what's going on here. I'm happy to debug whatever/however is needed.
The text was updated successfully, but these errors were encountered: