#blake2b hash for URI 'boot():/.../linux/initramfs-linux' does not match!
1 messages · Page 1 of 1 (latest)
Hi, Do you manage to fix it without reinstalling?
I got the same error today, did you find any fix?
One of my machines is experiencing this as well. It was running (booting) without issue prior to the latest upgrade. I installed from USB stick created two or three weeks ago.
At the end of the upgrade, it reported non-fatal errors occurred during the upgrade, but no details were provided.
Is there a way to resolve it without a full re-install?
Since this is not my main machine and I'm able to reproduce the issue, I'm happy to try some troubleshooting.
UPDATE: Resolved?
I was able to find the correct path to the files by looking at limine.conf
Then I executed:
b2sum /boot/<some-unique-id>/linux/vmlinuz-linux
b2sum /boot/<some-unique-id>/linux/initramfs-linux
I then replaced the checksums in limine.conf with these values.
The message is no longer displayed at boot; however, I do not know if this is the best solution. "It works though"
RESOLVED: So had this happen or something similar on a second machine, tried the above but no good, but what i did was I went to Omarchy > Update > Channel > Edge then restart and all is good.
@idle flume@grizzled beacon@elder sun@maiden belfry
Then try pacman -Syu first
Isn't there an option for this in the Update menu section? I might be wrong.
Every time the kernel changes, its computed hash also changes. But not your limine.conf's hash
So one could also write a pacman hook for it that adds the hash
Maybe there already is one?
Also, you can just remove the lines from limine.conf
It is what happens when switching channels too
I basicly assumed as much which is why I tried that cause just doing update omarchy did not update the hashs
It could be that during install one needs a fresh update if a kernel version was updated somewhere in between
It hopefully is just this timing issue
The way to directly fix it is this anyhow
But a hook should do it