Comment 13 for bug 2026790

ok, SUPER interesting -- when I force the intel profile to be PRIME, then I can safely boot with the enclosure attached(!), the systems gets through gdm, and I can login no problem.

I suspect there is a driver problem we are chasing, and PRIME was just selecting the NVIDIA GPU for some reason and flailing ..'

Hmm running into a bit of a snag :

beadon@semiauto:~$ sudo nvidia-settings
[sudo] password for beadon:

ERROR: NVIDIA driver is not loaded

(nvidia-settings:3802): GLib-GObject-CRITICAL **: 14:38:11.591: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

** (nvidia-settings:3802): CRITICAL **: 14:38:11.592: ctk_powermode_new: assertion '(ctrl_target != NULL) && (ctrl_target->h != NULL)' failed

ERROR: nvidia-settings could not find the registry key file or the X server is not accessible.
       This file should have been installed along with this driver at
       /usr/share/nvidia/nvidia-application-profiles-key-documentation. The application
       profiles will continue to work, but values cannot be prepopulated or validated, and
       will not be listed in the help text. Please see the README for possible values and
       descriptions.

** Message: 14:38:11.616: PRIME: Requires offloading
** Message: 14:38:11.616: PRIME: is it supported? yes
** Message: 14:38:11.637: PRIME: Usage: /usr/bin/prime-select nvidia|intel|on-demand|query
** Message: 14:38:11.637: PRIME: on-demand mode: "1"
** Message: 14:38:11.637: PRIME: is "on-demand" mode supported? yes