You are not logged in.
I get this error on system startup after running
sudo pacman -Syu
rebootLast edited by uzuto (2022-12-24 17:55:56)
Offline
You're going to need to give more information than that. What's the context? Post the actual / complete log. The service description seems to identify this as pacman-init.service from the archiso package. But why is this enabled? Is this in the iso or an installed system? How did you install the system (which instructions did you follow)?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
1. This is an system installed with archinstall
2. Custom repos (exodia) are added in pacman mirrorlist and update
3. Installed exodia-bspwm and related packages from repo
4. updated again and rebooted
5. removed some unnecessary packages installed with exodia-bspwm (using pacman -Rdd)
6. what logs should I provide?
EDIT: Tried disabling pacman-init.service still can't boot (got no error)
Last edited by uzuto (2022-12-24 16:12:17)
Offline
Define
can't boot
Can you boot the multi-user.target? (2nd link below)
Can you boot when adding "nomodeset" to the kernel parameters?
Offline
Define
can't boot
Can you boot the multi-user.target? (2nd link below)
Can you boot when adding "nomodeset" to the kernel parameters?
Yes I am able to boot with multi.user.target and nomodeset
EDIT: I was able to start tty without these, if that matters
Last edited by uzuto (2022-12-24 16:11:43)
Offline
Yeah, that does matter, because it means you boot perfectly fine, but whatever your graphical target is fails.
Post a complete system journal
sudo journalctl -b | curl -F 'file=@-' 0x0.stOffline
Yeah, that does matter, because it means you boot perfectly fine, but whatever your graphical target is fails.
Post a complete system journalsudo journalctl -b | curl -F 'file=@-' 0x0.st
here it is https://0x0.st/o53g.txt
MORE INFO:
This is a archinstall in Virtualbox
intramfs build with ventoy vtoyboot to boot vdi file directly from grub using vdiskchain on real machine
currently running in Virtualbox
Last edited by uzuto (2022-12-24 17:14:51)
Offline
So disabling a service that should never have been enabled let alone installed solved the issue of this thread, right? That leaves the question of why it was installed / enabled in the first place - I'm pretty sure the archinstall script does not do that.
But the remaining issue is completely different, and can be summarized as a failure in software that you 1) installed from an unsupported third party repo, and 2) broke by removing dependencies with `pacman -Rdd`. Do I have that about right? Doesn't describing the problem point you to the solution options?
(and it looks like this was an X-Y problem from the start)
Last edited by Trilby (2022-12-24 18:07:35)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
SOLVED It.
All of it was because of a file /etc/X11/xorg.conf.d/20-amdgpu.conf that I created to fix screen tearing and It stopped Xserver from starting.
Offline