You are not logged in.
https://bbs.archlinux.org/viewtopic.php … 2#p2162662
How "reliably"? (if the answer is "100%", that's obviously a very good test case)
Can you impact this by
a) blacklisting nvidia_uvm
b)
sudo touch /etc/systemd/do-not-udevadm-trigger-on-update
Offline
Since I added the file it has not happened again. But I do not know if this is directly related or not.
Offline
Ok, keep an eye on it and please keep us informed if it happens again (anything including a systemd update is more prone to cause this now since the udev hook gets ignored)
Offline
Hey, so this happened again. I have tried to follow the same procedure as before, but now when using the live USB medium and running
pacman --root /mnt -Qnq | pacman --cachedir /mnt/var/cache/pacman/pkg --root /mnt -S --dbonly -
I get the error
error: glib2: singature from ... is invalid
:: FIle /mnt/var/cache/pacman/pkg/glib2....pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature))
Do you want to delete it? [Y/n]
And so on for many packages. Should I delete them all of them? If doing so, wouldnt they not be available in cache anymore so reinstall would not work?
Also here is "how bad it is": http://0x0.st/X8L9.txt (seems very bad indeed)
Offline
warning: archlinux-keyring: /mnt/var/lib/pacman/local/archlinux-keyring-20240429-1/install (MD5 checksum mismatch)
warning: archlinux-keyring: /mnt/usr/bin/archlinux-keyring-wkd-sync (MD5 checksum mismatch)
warning: archlinux-keyring: /mnt/usr/lib/systemd/system/archlinux-keyring-wkd-sync.service (MD5 checksum mismatch)
warning: archlinux-keyring: /mnt/usr/lib/systemd/system/archlinux-keyring-wkd-sync.timer (MD5 checksum mismatch)
warning: archlinux-keyring: /mnt/usr/share/pacman/keyrings/archlinux-revoked (MD5 checksum mismatch)
warning: archlinux-keyring: /mnt/usr/share/pacman/keyrings/archlinux-trusted (MD5 checksum mismatch)
warning: archlinux-keyring: /mnt/usr/share/pacman/keyrings/archlinux.gpg (MD5 checksum mismatch)
archlinux-keyring: 17 total files, 7 altered files
Is the iso you're operating from somewhat up-to-date? Are there trust "issues"?
https://bbs.archlinux.org/viewtopic.php … 9#p2168299
It's not unlikely though that you've a bunch of corrupted packages in the cache. The list list of broken files is humongous.
https://wiki.archlinux.org/title/Pacman … ure_errors
=> Delete the package cache first.
Offline
Yes, the iso is a few months old now. I will update it and try again. You mean to remove the system pacman cache right?
rm -r /mnt/var/cache/pacman/pkg/*
Offline
Right, but first see whether you get away w/ the newer install iso.
Offline
With the new image, and after having cleaning up and downloading all the packages again, I am getting the following error after the first step (--dbonly) to reinstall all packages (an right after "loading package files")
call to execv failed (exec format error)
And if I try to chroot (arch-chroot /mnt), I get the following error
chroot: failed to run command #/bin/bash#: Input/output error
Offline
If the "call to execv failed (exec format error)" errors are fmr ALPM hooks after the installation just ignore them and proceed w/ the 2nd pass to actually fix the files on disk.
Chrooting won't work until then either.
Offline
Got it working again. Many thanks, again!
For the moment I will change the nvidia driver to 535.171.04 which they say that it should work better for kernel 6.8.
Offline