brent I use the 390's but what happens to me when they drop support in 2023? Go back to Nouveau? Buy a new one? Sorry I'm pestering, I know you're busy.

We'll have to see. Even if they don't continue support after 2022 there will probably be third-party patches to keep the drivers compatible with new kernel versions. But at some point I'm afraid we'll actually have to retire that driver series and then it'll mean back to nouveau. We'll burn that bridge when we get to it (as my favorite malaphor goes ^^).

Btw @everyone, please try to keep this thread mostly on topic from here on out. While it is about Nvidia phasing out support for some products, discussions about this practice are more at home in a separate thread. This one is about our particular driver packages and related support.

In related news, info for users of the Unstable repository: It will still be a bit until I actually switch the driver series for thenvidia-glx-driver packages. Due to the GCC 12 toolchain update I can't build the packages until the kernel has been updated/rebuilt (I was too slow to get it done before that). The plan still stands though.

      Staudey brent

      I'm cautiously optimistic that the new open-source kernel modules will help with longer-term kernel compatibility issues, so long as Nvidia's closed stuff stays compatible with user space. We've had good luck with the Nvidia long-term releases. 340 only had to be retired because it was no longer compatible with Xorg.

          Staudey Thank you very much for the info, and for the instructions to switch to the legacy Nvidia 470 drivers. I switched to the legacy drivers and my machine (GeForce GT 710) rebooted without any issue.

          I guess this issue is what is delaying this week's update, am I right?

              I have a Geforce GTX 680. I installed everything matching "nvidia-470*". And then did a "sudo eopkg update". Now I have a no signal situation. Please advice?

              Message sent from Windows 10.

                Jumpy I'm back in Solus. I added " single " to the boot parameters after pressing e-key on the systemd boot menu. Then wrote "exit" to the command prompt and Solus Budgie opened up. Then uninstalled everything matching "nvidia-470*".

                My GTX680 seem to work with just these installed for now:
                $ eopkg li | grep nvidia
                nvidia-390-glx-driver-modaliases
                nvidia-glx-driver-modaliases

                I don't really know what I'm doing. According to this output above, I have no nvidia drivers installed just some "modalias" files.

                How can I check which drivers are currently in use?

                    Jumpy Now you have no proprietary Nvidia driver installed and your system uses nouveau (the open source driver).
                    What you need to do is use one of the commands I posted at the start of the thread. It sounds like you installed ALL of the nvidia-470-* driver packages, which will include both the modules for the current and LTS kernel, which I think (without testing) will cause issues.

                    So if you use the linux-current kernel (i.e. the default, if you haven't manually switched to LTS), use the following to install the drivers:

                    sudo eopkg it nvidia-470-glx-driver-current

                    (and make sure your system has all updates installed too, to avoid a mismatch between driver and kernel)

                      joluveba I guess this issue is what is delaying this week's update, am I right?

                      Funnily enough that's just a coincidence, and the sync is being held up mostly for different reasons.

                          Staudey Funnily enough that's just a coincidence, and the sync is being held up mostly for different reasons.

                          May I ask the reason? It's just curiosity.

                              What about DoFlicky, Will it be able to detect that system is using older drivers and configure 4xx drivers on those system, or do we have to do it manually still?

                                joluveba May I ask the reason? It's just curiosity.

                                Mainly the mesalib update, kernel update and LSI issue(s)

                                Abhinav1217 What about DoFlicky, Will it be able to detect that system is using older drivers and configure 4xx drivers on those system, or do we have to do it manually still?

                                Yes, after this PR is merged and commited to our repository, DoFlicky will detect the correct driver branch for such cards.
                                But it will not automatically warn or notify you in any way if you're on the wrong driver branch. User intervention is required in any case.

                                      Staudey Mainly the mesalib update, kernel update and LSI issue(s)

                                      Is the next sync officially postponed until next Friday? I've been checking for a refreshed repository 8 or 10 times a day since last Friday, and I won't continue that if it's simply been postponed a week.

                                        8 days later

                                        Guys, I use Asus N61 with nVidia GeForce GT220M. I did not install any additional drivers, only your ISO. Should I be worried about this?

                                        P.S. Results:

                                        • nvidia-390-glx-driver-modaliases
                                        • nvidia-glx-driver-modaliases
                                          17 days later

                                          This post surely helped me install the correct drivers upon just installing Solus Gnome. I've a Kepler card -- the GT 720, and I need to use the latest 470.xxx driver. For some reason, when I used the distro's tool to install my driver, it read "390.xxx" for some reason.

                                            D-Smithee There are still a few things to be adjusted here and there, for the detection to work right from the start (mainly an update to doflicky aka "Hardware Drivers")

                                                Staudey That would be most welcome. When I first tried Solus a few months ago, it was Budgie and it did read the correct driver.

                                                  6 days later
                                                  Staudey unstickied the discussion .