You are not logged in.
Hey there,
I updated my secure boot system yesterday with yay and it said shim-signed couldn't be downloaded. Didn't make too much of it and rebooted.
Now, at boot, refind (or shim or my bios, I don't know) complains about tempering with my system / boot / firmware (red warning) and won't boot.
I tried chrooting to retry the update, but shim-signed won't update in the chrooted environment & complains about the system not being booted with systemd (usb stick boot before chrooting).
Any solution to this mess?
Thanks.
Last edited by SneakyLittleman (2024-04-01 16:13:49)
Offline
https://aur.archlinux.org/packages/shim-signed lists 2 sources and the first one return 404, perhaps yay isn't picking up the second one
https://ugjka.net
paru > yay | vesktop > discord
pacman -S spotify-launcher
mount /dev/disk/by-...
Offline
yes, and the comments don't look good. Something is wrong with this package & breaks systems. I'll try to downgrade.
Offline
It's fixed today (April 10) : the package shim-signed has been updated. Fixing my system was a bit of a pain, though:
- Disable secure boot in bios
- Boot an arch USB boot disk
- connect to the net
- mount / & /boot
- arch-chroot into the broken system
- su to normal user (can't yay as root)
- yay to update everything
- reboot
- enable secure boot in bios
- Profit
Last edited by SneakyLittleman (2024-04-09 15:07:38)
Offline