Hi all.
...
:: Running post-transaction hooks...
(1/5) Updating module dependencies...
(2/5) Install DKMS modules
==> dkms install --no-depmod vboxhost/6.1.34_OSE -k 5.15.52-1-lts
/usr/bin/dkms: line 1033: sha512: command not found
/usr/bin/dkms: line 1033: sha512: command not found
/usr/bin/dkms: line 1033: sha512: command not found
==> dkms install --no-depmod nvidia/515.57 -k 5.15.52-1-lts
/usr/bin/dkms: line 1033: sha512: command not found
/usr/bin/dkms: line 1033: sha512: command not found
/usr/bin/dkms: line 1033: sha512: command not found
/usr/bin/dkms: line 1033: sha512: command not found
/usr/bin/dkms: line 1033: sha512: command not found
...
Instead, I have /usr/bin/sha512sum on my system.
UPD. After that mkinitcpio gives me this warning I haven't seen before, maybe related to the error above:
==> Generating module dependencies
depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio.TeVOOF/root/lib/modules/5.15.52-1-lts: No such file or directory
So I cloned the dkms sources and did a
grep -r sha512 . and got this output:
./dkms.in: kmodsign sha512 $mok_signing_key $mok_certificate "$built_module"
./dkms.in: eval $sign_file sha512 $mok_signing_key $mok_certificate "$built_module"
I do not know if
sha512 is an internal command of dkms or an external program, but my guess would be to change
sha512 to
sha512sum and see if it gets fixed.
Yes. Replacing sha512 for sha512sum should fix it.
dkms is just verifying the integrity (https://man.archlinux.org/man/sha512sum.1) of the keys and it's certificate before signing it.
known issue in arch linux upstream https://github.com/dell/dkms/issues/229
world/dkms 3.0.5-1.1 is good, thank you! :)
// Although mkinitcpio's depmod warning is still there, but it's likely unrelated then.
Apparently people at Arch had the same problem too:
https://bbs.archlinux.org/viewtopic.php?pid=2044391
the mkinitcpio warning was also fixed today with mkinitcpio 31-3