Semenov How can I switch between drivers?

You can enable proprietary NVIDIA drivers by going to the Budgie Menu and opening Hardware Drivers.
If there are proprietary drivers that can be installed, they will show up in the box below the description. You can click the item you wish to install and click Install.
Jn the end, once installed, if you search for nvidia in the menu you will find this:

In addition from the terminal you will have something like this:

~ $ lsmod | grep nvidia
nvidia_uvm 1617920 0
nvidia_drm 90112 4
nvidia_modeset 1290240 8 nvidia_drm
nvidia 55844864 513 nvidia_uvm,nvidia_modeset
drm_kms_helper 249856 3 drm_display_helper,nvidia_drm,i915
drm 782336 13 drm_kms_helper,drm_display_helper,nvidia,drm_buddy,nvidia_drm,i915,ttm
video 65536 2 i915,nvidia_modeset

      FAb7D So that won't work because @Semenov is using a laptop that has a nvidia GPU that is simply too old for any of the driver packages we have in the repos. His only choice is to use the noveau driver built in to the kernel.

      @Semenov the nvidia package you saw is the modaliases package, which is used for hardware detection. It is installed even if you don't have the nvidia drivers installed (which again you can't do since your hardware is unsupported by any of the Solus ones).

          Addendum:
          "....Below are the legacy GPUs that are no longer supported in the unified driver. These GPUs will continue to be maintained through the special legacy NVIDIA GPU driver releases.
          The 390.xx driver supports the following set of GPUs:
          ........GeForce GT 220M 0649 1043 202D A
          .......
          GeForce GT 220M 0654 A....."
          ([https://download.nvidia.com/XFree86/Linux-x86_64/450.80.02/README/supportedchips.html](https://) )
          So, in your case the package maybe is nvidia-390-glx-driver-current.
          At worst-case you can try the run files installers Nvidia (but you risk breaking everything)(I've used them in the past on Suse and Slakware, never on Solus and recent kernels )
          [https://docs.nvidia.com/datacenter/tesla/tesla-installation-notes/index.html#runfile](https://)

            ReillyBrogan

            Would it perhaps be helpful if you could be very specific (in the copy-paste sense) with the commands you want to see the output from?

              ReillyBrogan So that won't work because @Semenov is using a laptop that has a nvidia GPU that is simply too old for any of the driver packages we have in the repos. His only choice is to use the noveau driver built in to the kernl

              But (why) the nvidia-390-glx-driver-current are not good?

              "....Below are the legacy GPUs that are no longer supported in the unified driver. These GPUs will continue to be maintained through the special legacy NVIDIA GPU driver releases.
              The 390.xx driver supports the following set of GPUs:
              ........GeForce GT 220M 0649 1043 202D A
              .......
              GeForce GT 220M 0654 A....."
              https://download.nvidia.com/XFree86/Linux-x86_64/450.80.02/README/supportedchips.html

              And try the run files installers Nvidia is not possible (safe-useful)?
              https://docs.nvidia.com/datacenter/tesla/tesla-installation-notes/index.html#runfile

                  FAb7D No, the last supported driver for the GT 220M was the 340 series. You can see that it's not on the supported hardware list here

                  To anyone encountering this issue, please run the following command to get the log from the previous boot.

                  sudo journalctl --boot=-1 > journal.log

                  Upload it to hastebin (or similar service) and share the link with the Phab issue. Someone more familiar with xorg will need to mention how to get that log.

                      ReillyBrogan No, the last supported driver for the GT 220M was the 340 series. You can see that it's not on the supported hardware list here

                      Ok, thanks

                        Any news?
                        I switched to Mint MATE. It works, but I don't like it. Solus is just better. And what about 4.4?

                          Perhaps you could install Solus on a USB drive or similar just to help us get the logs? Without those logs there's no chance we can debug this and you're pretty much just going to have to hope that a future package update randomly fixes this for you.

                            ReillyBrogan I can't do this untill 4.4 release. Old 4.3 will work fine. I can't update the sistem in live without reboot. So...

                              I think the issue got better with the sync before last, and seems to be gone with the sync today. If it happens again, I will log and post here. Thanks for your support