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
Title pretty much explains it. For the Kubuntu Focus machines, we have a script to completely power-off the Nvidia hardware if the Intel driver is selected. This wasn't a problem with nvidia-driver-455 and lower, but with 460 for some reason the menu no longer displays the Nvidia selections.
Granted, the system would have to be rebooted to get the Nvidia hardware back in this scenario (and we have a script injection in SDDM that does this exactly), but there's a pretty nasty inconvenience to our customers if they don't have the selection to begin with.
In order to take a sledgehammer approach to this, I had to remove line #115 from mate-optimus-applet: nvidia_detected(capability) and \
This produces the desired result. However, I'm sure there's a more graceful approach to this. In the meantime, unfortunately, I am in a position where I have to downstream patch this, but I'm reluctant to downstream patch in in Ubuntu (which I can) since this is a very quick and dirty approach.
The text was updated successfully, but these errors were encountered:
Title pretty much explains it. For the Kubuntu Focus machines, we have a script to completely power-off the Nvidia hardware if the Intel driver is selected. This wasn't a problem with nvidia-driver-455 and lower, but with 460 for some reason the menu no longer displays the Nvidia selections.
Granted, the system would have to be rebooted to get the Nvidia hardware back in this scenario (and we have a script injection in SDDM that does this exactly), but there's a pretty nasty inconvenience to our customers if they don't have the selection to begin with.
In order to take a sledgehammer approach to this, I had to remove line #115 from mate-optimus-applet:
nvidia_detected(capability) and \
This produces the desired result. However, I'm sure there's a more graceful approach to this. In the meantime, unfortunately, I am in a position where I have to downstream patch this, but I'm reluctant to downstream patch in in Ubuntu (which I can) since this is a very quick and dirty approach.
The text was updated successfully, but these errors were encountered: