You are not logged in.
After I updating my Arch Linux 2/3 days ago, my boot started to being stuck in "Starting Hostname Service". I tried to check hostnamectl and it was fine, and when I gone into hosts/hostname it was also fine. I have tried reinstalling grub and nothing. I have been unable to spot what is the root on the problem, and I still unable to boot my PC properly.
Offline
Are we sure it's "stuck" *there* or is that simply the last thing you see?
Can you boot the multi-user.target (2nd link below) in doubt along "nomodeset"?
Offline
Are we sure it's "stuck" *there* or is that simply the last thing you see?
Can you boot the multi-user.target (2nd link below) in doubt along "nomodeset"?
I managed to pass through Hostname Service, but I got in the terminal screen that I access with Alt + F2
Offline
What does that mean? Do you end up w/ a login prompt on the console?
What do you think the multi-user.target is?
Can you log in there?
Does it work w/o nomodeset?
(uname -a; pacman -Qs kernel) | curl -F 'f:1=<-' ix.ioOffline
What does that mean? Do you end up w/ a login prompt on the console?
What do you think the multi-user.target is?
Can you log in there?
Does it work w/o nomodeset?(uname -a; pacman -Qs kernel) | curl -F 'f:1=<-' ix.io
Yeah, I ended up in login prompt on console
I think multi-user.tager is for instead of just aiming to 1 default user, it also search for others availables and start one available. When I was with default, I think it might have stuck into one single user and that was why I couldn't get through Hostname Service; but I don't have absolute sure about that.
I can login
And it works without nomodeset
Offline
I think multi-user.tager is for instead of just aiming to 1 default user
No. It's to avoid the graphical.target
And it works without nomodeset
What means your system boots fine, you only have a problem w/ the graphical.target, from your description some autologin?
Elaborate on that.
Offline
I think multi-user.tager is for instead of just aiming to 1 default user
No. It's to avoid the graphical.target
And it works without nomodeset
What means your system boots fine, you only have a problem w/ the graphical.target, from your description some autologin?
Elaborate on that.
As far as I see, it looks to be the case the issue being on graphical.target; I checked to see what dependencies required to graphical.target work, and some of these dependencies was disabled/grey. One that catched my attention was "systemd-firstboot.service" that one of it's functions is to initialize hostname.
Offline
The ones who was disabled/grey:
ldconfig.service
systemd-ask-password-console.path
systemd-boot-random-seed.service
systemd-firstboot.service
systemd-hwdb-update.service
systemd-journal-catalog-update.service
systemd-pcrmachine.service
systemd-pcrphase.service
systemd-repart.service
systemd-sysusers.service
systemd-update-done.service
systemd-fsck-root.service
Offline
Wtf are you talking about?
What /is/ your graphical.target? display-manager.service?
What /is/ your display manager?
GDM? SDDM? …
Do you use X11 or wayland?
…
From the multi-user.target
- post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st- post the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f | curl -F 'file=@-' 0x0.stOffline