You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
When installing a new nvidia driver (possibly others as well), the user is dropped to console upon reboot. Dmesg will show NVRM: Api mismatch. This is caused by the driver being of the old version, and the client being the newly updated version.
Cause:
initrd is not automaically updated after install of the nvidia driver. Manually regenerating the initrd by executing dracut --regenerate-all --force and manually copying the new initrd over the the one in /boot/efi/opensuse-tumbleweed/<kernel-version> will fix the problem and allow booting into the GUI once more
Solution:
Update initrd automatically as part of the post-install scripts for systemd-boot when a kernel module is updated. Ie adding kmp-* scripts currently not present under /usr/lib/module-init-tools/kernel-scriptlets may be all that is needed?
The text was updated successfully, but these errors were encountered:
Thanks, that's easier / quiker than dracut --regerenate-all --force and then copying over the original in /boot/efi/opensuse.../ what I was doing until now
.
Problem:
When installing a new nvidia driver (possibly others as well), the user is dropped to console upon reboot. Dmesg will show
NVRM: Api mismatch
. This is caused by the driver being of the old version, and the client being the newly updated version.Cause:
initrd is not automaically updated after install of the nvidia driver. Manually regenerating the initrd by executing
dracut --regenerate-all --force
and manually copying the new initrd over the the one in/boot/efi/opensuse-tumbleweed/<kernel-version>
will fix the problem and allow booting into the GUI once moreSolution:
Update initrd automatically as part of the post-install scripts for systemd-boot when a kernel module is updated. Ie adding kmp-* scripts currently not present under
/usr/lib/module-init-tools/kernel-scriptlets
may be all that is needed?The text was updated successfully, but these errors were encountered: