On Friday 26 February 2021, Peter Suetterlin wrote:
Michael Hamilton wrote:
I don't know why it would work for some and not others. If "their scripted install" does not mean Yast, perhaps that's a factor.
AFAIK, the nvidia kmp package has a dependency on kernel-default-devel, and that one has a trigger script to (re)compile the module on install. This is what I see in my (zypper) log file:
# 2021-02-24 14:04:46 kernel-default-devel-5.10.16-1.3.x86_64.rpm installed ok # Additional rpm output: .... and then follows the compile log
I'm updating via 'zypper dup', not yast - maybe that's the difference for succeeds and fails?
I apologise, I should have said the original update was via zypper dup. From /var/log/zypp/history it does appear that the dup compiled the nvidia module for 5.10.16-1-default. Perhaps the module wasn't picked up for the initrd because no nvidia messages can be found in the journalctl output for the subsequent reboot into 5.10.16-1. There don't appear to be any relevant error message in any logs, even sddm didn't error, it just did not find any displays to manage. It was after this dup mystery that I used a yast to re-update the nvidia packages and that worked. I've not really had any unexpected issues with previous recent updates, it will be interesting to see what happens next time. For me, this is not really a big deal, I just wanted to confirm that Daniele's experience was not a lone occurrence. Michael