Restore Nvidia Drivers

[Cori Lenon]

NextI manually installed the nvidia drivers from the repository which successfully installed the nvidia driver, but the Ubuntu desktop does not function; no launcher, no menu bar, no windows. (Gnome seems to work though).

You did not mention your GPU. If you've had that problem on a laptop, I'd suggest its because of the so-called "Fusion" system (which uses your integrated GPU in lieu of discrete one when you don't need it).

Background: I've been running Ubuntu for years (started at 16.04, now at 20.04), and been constantly fighting with NVIDA drivers which I need as I use CUDA. As recently as yesterday, my NVIDIA 460 drivers were working fine, and an apt upgrade broke them again: Ubuntu 20.4 update broke my Nvidia 460 driver config

Restore point containing kernel+modules: is it possible to create (if so how), or am I simply misunderstanding how kernels & modules are managed on linux (ie a kernel wouldn't include the nvidia drivers) ?

Restoring from grub: It seems /etc/grub.d/40_custom is the file I want to modify as it's designed specifically for custom menu entries. Do you confirm this is the intended way of booting custom kernels or should I be looking at another file?

The package for the linux kernel is separate from the nvidia drivers. But each kernel version has its corresponding drivers.If you had the nvidia drivers installed for, say, 4.10.0-28, then booting that kernel should use the corresponding drivers.

So you should already have your "restore point"s, and you can use them via grub, as you show.As for the custom entries in grub, you don't need that for older kernel versions, those are added automatically when updating.You might need that if you want other customization, though.

There is no need to update kernel chain until hardware newer than the kernel chain is installed. The disadvantage is you need to occasionally update the kernel (on the same chain) if your system crashes and you don't know why.

It's not what I would call a "custom" kernel but many will call it such. When you upgrade within the same kernel chain, say 4.14.188 to 4.14.216 like I did last month grub doesn't automatically make it the new default on the main menu:

DKMS should be installed automatically once you install the nvidia driver using Software&Updates or using apt. Installing the non-dkms driver version requires manual intervention. Please post the output of

dkms status

Otherwise, it might be that the nvidia driver is installed but not added to the initrd:

-mint-nvidia-driver-loads-with-startx-but-not-on-initial-startup/168262/2

I re-checked ubuntu packaging and seems I missed that tey now switched to using pre-compiled, signed modules instead of dkms when using the third party software option or drivers autoinstall. So the modules are now in the packages

I was having a similar issue on my debian machine. Whenever the kernel is updated, the nvidia driver fails to load. I created a script that automates the process of downloading the latest driver and installing it afterwards. You can find it here: GitHub - BdN3504/nvidia-driver-update

I do a lot of video conferencing on jitsi and skype and the screen sharing had issues last year on wayland with my nvidia system (clients couldnt see my screen and vica versa), I switched to x11 and it didnt happen

If you not really need the power of Nvidia for Gaming and or extreme Graphic specific apps, I propose you to use hardware who works with opensource drivers. This definitely gives you more peace with your Fedora Linux experience alias Linux in general.

It seems to me that both gnome software and discover may update flatpaks while dnf does not.

If that is the issue then the extra updates are likely related to whatever flatpak software you may have installed.

Reinstalling them isn't going to do anything. I can't read your mind, please describe EXACTLY what you did. EVERYTHING. Including where you got the commands you ran from or how you installed them in general.

At first i tried to install the drivers from the nvidia script (from their official website) and it complained about the open-source drivers being installed. I then had to "try" to uninstall the open-source drivers. I didn't try.

I later went into the Garuda Hardware Manager to install the proprietary drivers and the hardware manager complained about conflicts with "nvidia-something-470xx". So i went in and manually deleted the conflicts since I wanted the drivers installed. Then after it "installed" without errors it now doesn't work. Just a black screen when i boot the machine.

Welp, I'm not close to that machine's monitor right now. But I'm pretty sure I had the open-source drivers since the garuda hardware manager told me I had. And the Nvidia script told me i had and then had to uninstall the open-source drivers.

I want to connect the Quest 2 via Air Link. So I installed the Oculus-App. Now my PC restarts or hang-up. And I have to use a restore-point to get the PC normal working again. But at a point, I can't restore it. So had to reinstall the complete PC. Now I have installed all, the oculus-app, too. But not the nvidia drivers. The PC runs fine. But if I want now to install the drivers. Because I need them, for games. Now it hangs up and that's it. I have to use a restore point, to let the PC run again.

@TheBlackGoddess I suggest you use DDU in Safe mode to properly uninstall your nvidia driver (google how to do this) then reinstall the latest nvidia driver (527.56 is working very well with my 3090 gpu). Also, like support mentioned, downloading the Oculus desktop pc app and running a Repair may also help. Also, check your win10 device manager usb to make sure you've disabled any power saving options. I've also found it best with win10 to disable hardware acceleration graphics (hags) and turn Game mode off. Hope this helps.

Hey there, @TheBlackGoddess! We're glad to hear that you've fixed it! If there's ever anything else we can help out with or if you have any questions that we could answer, please feel free to contact us again!

Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.

I'm using KDE Plasma on X11, SDDM and the standard and LTS kernels. I have an NVIDIA RTX 3080 GPU, of which I am using the two HDMI ports for my two screens since my mobo doesn't have on-board graphics. I'm using the proprietary nvidia drivers.

I'm wondering how I can figure out what the root cause of this issue might be (kernel, nvidia drivers, something X related or something plasma/Qt related), whether anyone else has experienced similar issues, and whether there is a fix.

I'm coming from Mac and am very much used to a "never power off my computer" workflow, so the inability to reliably put my computer to sleep is bothering me quite a bit.

Thanks, I looked over that part in the wiki it seems! Also good to know it must be a directory, I will add this to the wiki as it's not entirely clear from the text. I tried the steps but it still doesn't work, now the computer doesn't even go to sleep anymore; the screen immediately wakes back up. I'll have to dig a bit deeper now that I know that it's probably NVIDIA related, this page gives a pretty nice overview of what to try: Also seems compositing is disabled, I get a warning that "OpenGL compositing (the default) has crashed KWin in the past." and the suggestion to use XRender. If all else fails, I guess I'll have to go with plasmashell --replace and hope a better solution comes along at some point.

Over a year ago I installed Elementary OS on an old Macbook Air from circa 2011. It worked fine, albeit slowly, for a couple of weeks until I performed a suggested nvidia driver update.I read similar stack exchange questions from time to time but none of the suggestions worked.

I am confronted to an infinite log-in loop: the system recognises my password, then goes blank a moment, only to return to the log-in screen. I consulted I am unable to login "infinite login loop" andCan't login after upgradewithout being able to solve the problem

If you want to double check the existence of .Xauthority run ls -la for the $HOME directory which includes options to show hidden files and will let you confirm whether or not the .Xauthority file is there are not.

For below, in case you can't reach a console from normal boot as aforementioned using keyboard combinations, then boot into recovery mode, enable networking, and then select the option for dropping to root. This is suggested because you're going to need to install software and aside from the obvious, enabling networking will automatically remount your primary disk with read/write permissions as necessary.

Alternatively, the answer provided here explains when troubleshooting using nvidia drivers in the case of Ubuntu, that you need to exit the Xserver display before installing the nvidia drivers and after you've stopped lightdm by switching to a virtual terminal (The tty console) where instead, after arriving at the console

As one further alternative to blacklisting the nouveau driver and trying to get the two drivers to play nice together, don't do any of the above and simply try changing this in your grub configuration:

Then to ensure the system loads, we will re-install the elementary desktop, a helpful Ubuntu package, remove any xorg configurations that may have been previously set when nvidia drivers were installed and then manually re-add the open source nouveau drive back to be loaded, all before updating initramfs and rebooting

As I understand it, with Secure Boot enabled, the Lockdown kernel module requires all driver modules to be signed by a key enrolled in the MOK. The nvidia-driver-G06-kmp-default package includes a %post scriptlet for enrolling an included MOK public key as part of the installation of the drivers, though it requires physical presence at the machine on the subsequent boot to manually enroll the key. Once enrolled however, drivers signed by the associated private key should pass inspection and be loadable.

3a8082e126