You are not logged in.
Pages: 1
Hello,
After an Upgrade (Pacman -Syu) Arch boots perfectly until the TTY login prompt should appear. But in this moment it freezes. I can't even change to another TTY with CTRL+ALT+F1/2/3/4. Only thing I can do is CTRL+ALT+DEL to reboot.
Booting in an Arch session with a Live USB Stick, mounting the broken Arch partition and booting in it via systemd-nspawn works well. It starts an older kernel version (5.1.15 - the most recent one is 5.2.1 and I already upgraded the system), but I can login into the broken Arch instance. I don't know why it starts an older kernel version here, but at this point I don't really care. Maybe this is relevant though ...
Inside of the session I see the following:
$ systemctl status getty@tty1.service ◀
● getty@tty1.service - Getty on tty1
Loaded: loaded (/lib/systemd/system/getty@.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Condition: start condition failed at SAT 2019-07-20 13:36:32 URC; 2min ago
└─ ConditionPathExists=/dev/tty0 was not met
Docs: man:agetty(8)
man:systemd-getty-generator(8)
http://0pointer.de/blog/projects/serial-console.html
Jul 20 13:30:57 archaic systemd[1]: Condition check resulted in Getty on tty0 being skipped.
Jul 20 13:36:52 archaic systemd[1]: Condition check resulted in Getty on tty0 being skipped.What does "/dev/tty0 was not met" mean?
Do you need more logs?
I hope for help,
maikeloni
Last edited by maikeloni (2019-07-20 13:02:42)
Offline
So if you can login into your broken Arch instance, then try to post journalctl log of failed system start with 5.2 kernel (with command journalctl -b-n where n=1,2,3,..n), and journalctl log of successfully started session.
Offline
Hi,
thanks for the reply.
Here is the "journalctl -b" output of the successful boot in kernel 5.1.15 via systemd-nspawn:
https://pastebin.com/G1Bg8gbM
Here the "journalctl -b-1" output of the unsuccessful boot in kernel 5.2.1:
https://pastebin.com/Km1S0dzG
Best regards
maikeloni
Last edited by maikeloni (2019-07-20 14:21:27)
Offline
Have you worked through the issues on https://bugs.archlinux.org/ caused by the 5.2 kernel update?
For example have you tried the workaround or patch from https://bugs.archlinux.org/task/63159 ?
Offline
Thanks, I haven't been aware of those issues. I will work through it.
Offline
Pages: 1