You are not logged in.
Hi all,
pacman -Syu hard-hung the system while running hooks, so I had to power off with hardware button.
Problems after reboot (using rEFInd to boot, linux-lts and generating UKI via mkinitcpio):
If choosing plain Linux image to boot (/boot/vmlinuz-linux-lts) systemd fails at switch-root target. Booting both UKI options (regular and fallback) works fine.
Sway starts from tty as usual (simply running from tty), but doesn't display the bar and not reacting to keybinds.
Suspicious stuff in sway's log:
Could not find config for output <output name>
Line 277 Failed to parse get BlockInhibited property: Invalid argument
<a bunch of lines removing devices>
[ERROR] connector <output name>: Failed to disable CRTC 56Fontconfig warnings by mpv (running it in plain console works fine, auto-chooses gpu vo), complaining about files in /etc/fonts.d/*.conf (invalid attribute names etc). Worked around by moving all /etc/fonts.d/*.conf symlinks elsewhere.
Tried reinstalling linux-lts, intel-ucode (Intel CPU), mesa, mkinitcpio, libdrm, sway, kmod, fontconfig, all installed fonts. Pacman hooks work fine (generating initrd etc) - didn't help.
Last edited by nesk (Today 07:21:23)
Offline
You should have looked at the wiki first , Fixing an unbootable system caused by an interrupted upgrade , the procedure listed there may no longer work.
Moderator Note
moving to Pacman & Package Upgrade Issues
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Fixing an unbootable system caused by an interrupted upgrade , the procedure listed there may no longer work.
Thanks for the link. After reinstalling all pkgs from failed upgrade sway started working.
pacma -Qkk lists only the usual changes to /etc/passwd and the like.
Other problems listed there are N/A.
Booting plain kernel (not UKI image) still doesn't work. I can live with that but would like to fix it, maybe uncover more unsolved problems in the process. pacman -Syu mkinitcpio systemd linux-lts didn't fix it.
Last edited by nesk (Today 12:43:41)
Offline
\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Emboldened the unsolved part, apparently it wasn't clear.
Offline
Did you mount the /boot partition before re-installing the kernel?
Are there mkinitcpio errors when re-installing the kernel?
What are the error messages when the root switch fails?
Offline
Did you mount the /boot partition before re-installing the kernel?
Yes.
Are there mkinitcpio errors when re-installing the kernel?
No, just the usual warnings about possibly missing modules.
What are the error messages when the root switch fails?
Starting Switch Root...
Failed to start Switch Root.
See 'systemctl status initrd-switch-root.service' for details.
You are in emergency mode.
Cannot open access to console, the root account is locked.
Press Enter to continue.
<Enter or Ctrl-D>
Reloading system manager configuration.
Starting initrd.target
You are in emergency mode.
Cannot open access to console, the root account is locked.
Press Enter to continue.Offline
Remove any "quiet" parameters, in doubt see https://wiki.archlinux.org/title/Genera … l_messages
There're likely error messages ahead of that.
In case: your phone has a camera that can read faster than you ![]()
(Use a tripod, in doubt makeshift one out of two books: -\_ )
Are there kernel and/or initramfs in the mountpoint of the boot partition (ie. the /boot path on the root partition)?
Offline