You are not logged in.
I use systemd-boot. My ESP is located at the default path. After a pacman update that includes systemd, I manually run the following command:
bootctl updateI did this today. There were zero problems from the pacman update. And the output of `bootctl update` was normal:
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/BOOT/BOOTX64.EFI".However, now my system will not boot. The BIOS screen comes up as normal, but at the instant the boot process is handed off to systemd-boot I get nothing but a black screen. There is no error message, no prompt, nothing.
I did some troubleshooting and was able to copy old versions of "/boot/EFI/systemd/systemd-bootx64.efi" and "/boot/EFI/BOOT/BOOTX64.EFI" into place. This resolved the issue and the system would boot again. However, even after carefully checking every step, as soon as I run `bootctl update` again, the problem comes back and the system will not boot.
This is a ThinkPad w550s. So it is a couple years old model. Any thoughts about how to resolve this, or even what might be causing it? Is anyone else seeing anything similar? I never had any problem with `bootctl update` before this current update.
Last edited by MountainX (2018-03-20 19:42:24)
Offline
Which package version provided the problematic efi and which version provided the older working efi?
Offline
Which package version provided the problematic efi and which version provided the older working efi?
The problematic efi is from systemd-238.0-3-x86_64.pkg.tar.xz
My previous working package was:
systemd-237.64-1-x86_64.pkg.tar.xz
Offline
Would check upstream if there are any bug reports about such as issue, if not
git clone git://git.archlinux.org/svntogit/packages.git --single-branch --branch "packages/systemd"
cp -r packages/trunk/ systemd
cd systemd
makepkg -Codd
cd src/systemd-stable
git cherry-pick -n 848e863acc51ecfb0f3955c498874588201d9130 #needed to make systemd build https://github.com/systemd/systemd/pull/8456
cd ../.. #edit PKGBUILD line 206 change rm to rm -f so the rm will not fail if the links are missing (links were added between 237 and 238)
makepkg -ersi # build and install locally v238 and check it is broken (ensure you have the two signing keys installed)cd systemd/src/systemd-stable
git reset --hard
git checkout v237
git cherry-pick -n 848e863acc51ecfb0f3955c498874588201d9130
cd ../..
makepkg -ersi # build and install locally v237 and check it is not brokencd systemd/src/systemd-stable
git reset --hard
git bisect start
git bisect good v237
git bisect bad 738ab7502afb7663d9aacdd73e79025aa7cd0a9b #the commit id arch is using for v238
Bisecting: 259 revisions left to test after this (roughly 8 steps)
[4cac89bd7c449dad262e4b306b76611b80fb51cc] test: add tests for TemporaryFileSystem=
git cherry-pick -n 848e863acc51ecfb0f3955c498874588201d9130
$ cd ../..
makepkg -ersi #build and install bisected commit and check result
cd systemd/src/systemd-stable
git reset --hard
git cherry-pick -n 848e863acc51ecfb0f3955c498874588201d9130
git bisect $RESULT # where result is good or bad
$ cd ../..
makepkg -ersi #build and install bisected commit and check result (repeat last six lines until git bisect has found the commit)Offline
Thank you. Here's an update. On one system where I had the problem, it was resolved by updating the BIOS. On the other system, there is no newer BIOS update available. So I will investigate your suggested steps.
Offline