nvidia konnte den Registry Key nicht finden

From Google Translate

Ubuntu 04/18/03
nvidia GTX 750Ti with the -390 driver
Kernel is 5.3.0-26

Last Sunday, when I rebooted the computer for the day, the monitor could no longer be identified and there was no profile in the graphic part nvidia-settings.

By entering

nvidia-settings

in the terminal I got an error message that the registry key could not be found. Since I lack the necessary programming knowledge for troubleshooting using the terminal, I decided to refer to Mastodon in a discussion

sudo apt purge * nvidia *

First of all, uninstall and clean everything nvidia-like, so that I can use the system for troubleshooting at first with the nouveau driver. For my own safety, I then checked the two hard drives that passed the test without errors.

So there has to be something in the software. I just don't know where to look. Of course I can reinstall the nvidia 390, but I don't want to shoot my system completely.

For reference here is the link to the discussion from Sunday: https://social.tchncs.de/web/statuses/103509858591103043

If you boot an older kernel, does it work OK?

I tried that, but it didn't solve the problem. Which is why I went back to nouveau for now.

The older kernel I tried with was 5.0.0-37. It still said it couldn't find the key

Does the nouveau driver work OK? Do you run games on the system?

I run games on the system, yes, which is why I _need_ the proprietary driver. The nouveau driver works ok, but I can't run the games I want with it - I need the nvidia one for that.

"Fehlermeldung, dass der Registry Key nicht gefunden werden konnte."
= "error message, that the registry key could not be found"

"Registry Key" is a word which I know only from Microsoft Windows.

What exactly was the error message and when was it shown?
Wie genau hat die Fehlermeldung gelautet and wann wurde sie angezeigt?

What I could imagine is that you are running Ubuntu in UEFI Secure Boot mode with module signature checking, and that the NVidia modules are not signed with a signature registered in your system and thus refuse to be loaded.

What output do you receive or the command

mokutil --sb-state

Aber warum hatte ich das Problem erst am Sonntag und vorher nie?
But why did I never have the same problem before Sunday?

Ich hattte auf Mastodon ein Foto gepostet, dass ich mit dem Handy gemacht hatte - direkter Link: https://social.tchncs.de/@Cedara/103510181232347745
I had posted a photo on Mastodon that I made with the mobile - direct link: https://social.tchncs.de/@Cedara/103510181232347745

Ref: Mokutil (was bedeutet dies? what does that do?)

Der Befehl 'mokutil' wurde nicht gefunden, kann aber installiert werden mit:

sudo apt install mokutil

This post here reads similar to mine, although the difference is that I installed my -390 via the additional drivers section:

https://askubuntu.com/questions/1204165/ubuntu-18-04-3-lts-and-nvidia-card-low-resolution/1204640#1204640

Also, I do still have a 5.0.0-37 and 4.15.0-74 listed in the old kernels that are not used.

The fellow there posted a remark that suggested to him the 5.3.xx kernel is incompatible with the 390 nvidia one. That the newer one should be used.

Those would either be for me the 430 or the 435, cause those are listed in the additional drivers section. The 435 has also a "tested"remark.

I think I just found the cause of the problem: Bug #1851162 "nvidia-drivers-390 fail to build with kernel 5.3"

A new version of the -390 version has been built a few hours ago and is already available on -proposed.

That is awesome.

When can I expect that to be in the normal packages, or do I have to add bionic-proposed?

Ack, I just realised I accidentally reopened it. I should have pressed comment instead. Dang. Sorry.

Current status is that the new package in bionic-proposed does not work (probably needs another patch for the 5.3 kernel).
I suggest that you wait for new information in the bug report.

But combining all available information, then selecting the older (5.0) kernel from the grub menu ("Advanced options ...") should have always worked. I do not know what there is different on your system that it didn't work for you.