You examine logs or at least provide them so that others can do it. Show full output of “journalctl -b” immediately after boot.
I just installed G06 from the repo. Anything that happened is a result of that. It automagically blacklists nouveau, though I can’t say what it does with initrd. I’ve been assuming that the installation sets up everything to run.
The output can be seen at SUSE Paste
Running my previous test late at night I forgot to disable the nvidia repo and it installed G05 for me. But this has, as previously, given the same results:
inxi -G
**Graphics:**
**Device-1:** NVIDIA GM204 [GeForce GTX 980] **driver:** N/A
**Display:** x11 **server:** X.Org **v:** 1.20.3 **with:** Xwayland
**driver:** **X:** **loaded:** nouveau
**unloaded:** fbdev,modesetting,vesa **failed:** nvidia
**gpu:** N/A **resolution:** 800x600~75Hz
**OpenGL:** **renderer:** llvmpipe (LLVM 11.0.1 256 bits)
**v:** 4.5 Mesa 20.2.4
Hopefully, someone can see something in the log that gives a clue to what’s going on. It’s getting very frustrating!
Apr 14 10:35:51 Adele kernel: Loading compiled-in X.509 certificates
Apr 14 10:35:51 Adele kernel: Loaded X.509 cert 'SUSE Linux Enterprise Secure Boot Signkey: 5a240449d29fd0d8a7a187e6fc0e26b95d1aa87b'
Apr 14 10:35:51 Adele kernel: integrity: Loading X.509 certificate: UEFI:db
Apr 14 10:35:51 Adele kernel: integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
Apr 14 10:35:51 Adele kernel: integrity: Loading X.509 certificate: UEFI:db
Apr 14 10:35:51 Adele kernel: integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
Apr 14 10:35:51 Adele kernel: integrity: Loading X.509 certificate: UEFI:MokListRT
Apr 14 10:35:51 Adele kernel: integrity: Loaded X.509 cert 'SUSE Linux Enterprise Secure Boot CA: ecab0d42c456cf770436b973993862965e87262f'
...
Apr 14 10:36:12 Adele systemd-udevd[649]: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service
On reboot after installing nvidia kernel drivers you should have seen MokManager screen asking you whether you want to enroll certificate used to sign nvidia modules. Either you need to enroll it or disable Secure Boot.
That solved the problem. I can now access my graphics card memory!
Graphics Card Vendor: NVIDIA CorporationGraphics Card: NVIDIA GeForce GTX 980/PCIe/SSE2
Graphics Card Memory: 4096 MB
Though I have to say that MokManager is not an easy thing to navigate. First of all, before arvidjaar’s post I was just ignoring that message and letting the machine boot. Once I tried to enroll the certificate I had to attempt twice before I provided the right answers to the questions. But at least it lets you attempt more than once. So not completely user-unfriendly.
So thank you for your intervention arvidjaar. And thanks to **malcolmlewis **for their initial response and sticking with me. And to **gogalthorp **for their good question, even though it turned out to be not relevant. All contributions were appreciated.
And now, just as we come to the long weekend, I can use my PC for fun as well as work!