[solved] Boot stuck at black screen with after systemd

Erotaku · 2021-01-30 10:38:58

Hey everyone. I recently went through a fresh arch installation. Everything was going okay until I woke up to find the system not booting up after going through system.d. It's just a blank black screen with an underscore at the top left. It's not responsive to any key strokes, including ctrl+alt+F1-9 for a tty. It's not frozen either? Because when I physically shut down the PC, systemd stops back everything like normal.

Everything from here on was done through an arch live usb iso followed by chrooting in root.

Steps I have taken in an effort to fix this:

The last thing I had done before the system stopped booting up was installing and configuring systemd-resolved to get my VPN to work (and that did get it to work). So, I disabled systemd-resolved service. Then I pacman -Rns it to completely eliminate this potential cause out of the way.
After reading a bunch on google, I started suspecting that lightdm would be the next culprit. So, I disabled its service as well. Interestingly enough, the next boot showed the tty login text screen. Believing I found where the problem is coming from, I quickly discovered that it's not responsive either. I can not type anything to log in.
Bizarrely enough, I tried to acquire log files to provide you all with. But both journal logs are... like a matrix glitch? Take a look here. What is even more bizarre is that I had to reboot the live usb because that glitch carried on to everything I typed after...

As I have just proven, lightdm should not be the problem here... But here is its log file anyway:

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.30.0, UID=0 PID=433
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.00s] DEBUG: Monitoring logind for seats
[+0.00s] DEBUG: New seat added from logind: seat0
[+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.00s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.00s] DEBUG: Seat seat0: Starting
[+0.00s] DEBUG: Seat seat0: Creating user session
[+0.00s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+0.00s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.00s] DEBUG: User ero added
[+0.01s] DEBUG: Seat seat0: Creating display server of type wayland
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.01s] DEBUG: Session pid=450: Started with service 'lightdm-autologin', username 'ero'
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.02s] DEBUG: Session pid=450: Authentication complete with return value 0: Success
[+0.02s] DEBUG: Seat seat0: Session authenticated, running command
[+0.02s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+0.02s] DEBUG: Session pid=450: Running command /etc/lightdm/Xsession sway
[+0.02s] DEBUG: Creating shared data directory /var/lib/lightdm-data/ero
[+0.02s] DEBUG: Session pid=450: Logging to .xsession-errors
[+0.11s] DEBUG: Activating VT 7
[+0.11s] DEBUG: Activating login1 session 1
[+0.11s] DEBUG: Seat seat0 changes active session to 1
[+0.11s] DEBUG: Session 1 is already active
[+29.27s] DEBUG: Got signal 15 from process 1
[+29.27s] DEBUG: Caught Terminated signal, shutting down
[+29.27s] DEBUG: Stopping display manager
[+29.27s] DEBUG: Seat seat0: Stopping
[+29.27s] DEBUG: Seat seat0: Stopping display server
[+29.27s] DEBUG: Seat seat0: Display server stopped
[+29.27s] DEBUG: Seat seat0: Stopping session
[+29.27s] DEBUG: Terminating login1 session 1
[+29.28s] DEBUG: Session pid=450: Sending SIGTERM
[+29.28s] DEBUG: Session pid=450: Exited with return value 1
[+29.28s] DEBUG: Seat seat0: Session stopped
[+29.28s] DEBUG: Seat seat0: Stopped
[+29.28s] DEBUG: Display manager stopped
[+29.28s] DEBUG: Stopping daemon
[+29.28s] DEBUG: Releasing VT 7
[+29.28s] DEBUG: Exiting with return value 0

Things to note:

I am using sway/wayland. Trying to acquire a xorg log is not possible.
I am using systemd-boot as my boot loader. I enabled the editor in case you would like for me to pass any kernel parameters upon login.

Thank you to everyone who tries to help on this forum. You are the tech prophets of Linux :D

Last edited by Erotaku (2021-02-06 21:18:24)

loqs · 2021-01-30 11:42:28

Did you access one of the journal files directly instead of using journalctl to produce the image?

Erotaku · 2021-01-30 11:55:20

That is indeed what I did, yes. I have no access to shell to execute any commands.

loqs · 2021-01-30 11:56:37

You can not run journalctl after chrooting in from the live media?

Erotaku · 2021-01-30 12:52:25

Initially I thought that the command would only show details relevant to the live usb boot. Upon further reading from arch wiki, I can actually specify the boot with the --list-boot option. I then chose the boot I had tried from my actual system, and there you go: http://codepad.org/2T6axolZ

Last edited by Erotaku (2021-01-30 12:53:16)

loqs · 2021-01-30 13:09:23

I think the end of the journal might have been trimmed from the pastebin or was the following really the end?

Jan 30 13:30:24 arch kernel: tsc: Refined TSC clocksource calibration: 3999.997 MHz
Jan 30 13:3

Erotaku · 2021-01-30 14:10:43

Eh, I tried avoiding using pastebin... but I might as well. Here is the full log: https://pastebin.com/FCsevMQy

Sorry about that!

loqs · 2021-01-30 14:32:57

mullvad-daemon is failing, if you disable that service can you reach a prompt?

Erotaku · 2021-01-30 15:20:27

I went and disabled the mullvad service, and even disabled it from being auto started as well. There is no change whatsoever though. Maybe the daemon was failing because there was no internet connection? Oh well, it doesn't matter.

Here is the latest boot attempt's journal after disabling the daemon: https://pastebin.com/cyH4ugMb

loqs · 2021-01-30 15:40:55

Did you just re-enable lightdm? That was not in the previous journal or it might have been blocked by mullvad-daemon. lightdm succeeds in autlogging in a user but that would be to a blank screen?
Edit:
What is the contents of /var/log/Xorg.0.log ?

Last edited by loqs (2021-01-30 15:54:08)

Erotaku · 2021-01-30 15:59:41

Ah, that's what I forgot to mention in my last post. I did re-enable lightdm, yes. Since I was able to get the journalctl logs, I thought I should probably include it to see where the problem is coming from.

Yes. Systemd does all the usual start up initializatio , then an responsive black screen appears. I assume that happens after lightdm?

I am also using SwayWM/wayland. So, there are no xorg logs.

Last edited by Erotaku (2021-01-30 16:02:09)

loqs · 2021-01-30 16:03:44

There are two possibly related issues then, why the system does not reach a command prompt and why Wayland produces a blank screen?
Edit:
What GPU is in use, with what driver? Is early KMS in use? Why can X not be used?

Last edited by loqs (2021-01-30 16:05:46)

Erotaku · 2021-01-30 16:30:00

I am not sure I fully understand what you mean by the first issue. Regardless though, yeah I wonder too.

My graphics card is an AMD RX 5700xt. Normal drivers were installed; xf86-video-amdgpu, mesa and vulkan-radeon. I also just checked what KMS is. Yeah, I haven't done anything in that area. I am sure it's a no.

I am only interested in using SwayWM (and window managers too for that matter). X11 has a few limitations regarding the multihead/monitor setups, and a few freesync shenanigans. There are other reasons, but sway is generally a VERY solid and stable window manager used by many people. It can't be the reason, right?

Edit: This fresh arch installation worked flawlessly for a few days with absolutely no problem. Just throwing that out there.

Last edited by Erotaku (2021-01-30 16:33:09)

loqs · 2021-01-30 16:45:46

Before you re-enabled lightdm, when the system booted did you reach a login prompt?
Edit:

Jan 30 15:56:29 arch kernel: fbcon: Taking over console

No sign of the amdgpu module in the journal.

Last edited by loqs (2021-01-30 16:48:58)

Head_on_a_Stick · 2021-01-30 16:50:01

Try https://wiki.archlinux.org/index.php/Sy … _boot_into to see if that allows you to login at the TTY.

If it works then start sway from a console login like this to generate a log file:

sway > ~/sway.log 2>&1

Have you tried downgrading the kernel or booting with the LTS version?

Erotaku · 2021-01-30 17:20:25

loqs wrote:

Before you re-enabled lightdm, when the system booted did you reach a login prompt?
Edit:
Jan 30 15:56:29 arch kernel: fbcon: Taking over console
No sign of the amdgpu module in the journal.

Yeah, as I have mentioned prior, I did reach a login prompt in the tty after disabling lightdm. Everything seemed fine, but it was unresponsive. I was not able to type anything or change to a different tty. Which is odd because the underscore where I am supposed to type was blinking normally. It's clearly not crashed or frozen.

As for the lack of amdgpu module in the journal... That's another mystery

Head_on_a_Stick wrote:

Try https://wiki.archlinux.org/index.php/Sy … _boot_into to see if that allows you to login at the TTY.
If it works then start sway from a console login like this to generate a log file:
sway > ~/sway.log 2>&1
Have you tried downgrading the kernel or booting with the LTS version?

I have just finished trying the multi.target boot. I did reach a tty login screen, yes. It's the same scenario as what I just typed in the above quote. Unresponsive, but not frozen, with normally blinking underscore at the location of typing.

I forgot to mention. I have yet to try the LTS kernel. I still need to (and figure out from the wiki) add that as an entry to my systemd-boot. Gah, it's annoying how this boot loader doesn't do this automatically. I will get back to studying the wiki on this matter now.

Last edited by Erotaku (2021-01-30 17:27:07)

Erotaku · 2021-01-30 18:02:04

Ehh.. I finally gotten around figuring out and adding the LTS kernel entry to systemd-boot. I logged in there and there is no difference. Same old empty black screen.

loqs · 2021-01-30 18:13:13

Is the blinking underscore where the login prompt should be, after you entered the login name, or after you entered the password? If after the password is accepted have you tried logging in as a different user?
From the live media what is the output of `lspci -nnk`?
Edit:
If the login prompt never appears what is the output of:

stat /etc/systemd/system/getty.target.wants/getty@tty1.service

Also have you enabled auto-login at the console?

Last edited by loqs (2021-01-30 18:46:43)

Erotaku · 2021-01-30 20:02:59

loqs wrote:

Is the blinking underscore where the login prompt should be, after you entered the login name, or after you entered the password? If after the password is accepted have you tried logging in as a different user?
From the live media what is the output of `lspci -nnk`?
Edit:
If the login prompt never appears what is the output of:
stat /etc/systemd/system/getty.target.wants/getty@tty1.service
Also have you enabled auto-login at the console?

The tty login screen is unresponsive as soon as it appears. So, I am not able to type neither the user or password.

I think we will be able to tell where the problem is happening from that `lspci -nnk`. Because when I tried to outputting it to a file, I got the following error: 'lspci: Unable to load libkmod resources'. Anyway, I still got some output here:

00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex [1022:1450]
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b85]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit [1022:1451]
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b85]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453]
	Kernel driver in use: pcieport
00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453]
	Kernel driver in use: pcieport
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453]
	Kernel driver in use: pcieport
00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454]
	Kernel driver in use: pcieport
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454]
	Kernel driver in use: pcieport
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 59)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b85]
	Kernel driver in use: piix4_smbus
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b85]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1460]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1461]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1462]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1463]
	Kernel driver in use: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1464]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1465]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1466]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 [1022:1467]
01:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation E12 NVMe Controller [1987:5012] (rev 01)
	Subsystem: Phison Electronics Corporation E12 NVMe Controller [1987:5012]
	Kernel driver in use: nvme
03:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller [1022:43d5] (rev 01)
	Subsystem: ASMedia Technology Inc. Device [1b21:1142]
	Kernel driver in use: xhci_hcd
03:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller [1022:43c8] (rev 01)
	Subsystem: ASMedia Technology Inc. Device [1b21:1062]
	Kernel driver in use: ahci
03:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge [1022:43c6] (rev 01)
	Kernel driver in use: pcieport
20:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
	Kernel driver in use: pcieport
20:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
	Kernel driver in use: pcieport
20:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
	Kernel driver in use: pcieport
21:00.0 Network controller [0280]: Intel Corporation Wireless-AC 9260 [8086:2526] (rev 29)
	DeviceName: Broadcom 5762
	Subsystem: Intel Corporation Device [8086:0014]
	Kernel driver in use: iwlwifi
22:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b85]
	Kernel driver in use: igb
25:00.0 Non-Volatile memory controller [0108]: KIOXIA Corporation Device [1e0f:0009] (rev 01)
	Subsystem: KIOXIA Corporation Device [1e0f:0001]
	Kernel driver in use: nvme
26:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch [1002:1478] (rev c1)
	Kernel driver in use: pcieport
27:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch [1002:1479]
	Kernel driver in use: pcieport
28:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1)
	Subsystem: Sapphire Technology Limited Radeon RX 5600 XT [1da2:e411]
	Kernel driver in use: amdgpu
28:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio [1002:ab38]
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio [1002:ab38]
	Kernel driver in use: snd_hda_intel
29:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function [1022:145a]
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b85]
29:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor [1022:1456]
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b85]
	Kernel driver in use: ccp
29:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller [1022:145f]
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b85]
	Kernel driver in use: xhci_hcd
2a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function [1022:1455]
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b85]
2a:00.2 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b85]
	Kernel driver in use: ahci
2a:00.3 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller [1022:1457]
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:cb85]
	Kernel driver in use: snd_hda_intel

As for the stat command. I will assume it's okay to run from a chrooted environment? If so, then here you go:

  File: /etc/systemd/system/getty.target.wants/getty@tty1.service -> /usr/lib/systemd/system/getty@.service
  Size: 38        	Blocks: 0          IO Block: 4096   symbolic link
Device: 10303h/66307d	Inode: 1179674     Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2021-01-30 09:39:51.839209517 +0100
Modify: 2021-01-25 18:30:11.794226223 +0100
Change: 2021-01-25 18:30:11.794226223 +0100
 Birth: 2021-01-25 18:30:11.794226223 +0100

Lastly, I did create an autologin group during my arch installation for my lightdm. You are referring to that, right?

loqs · 2021-01-30 20:10:19

Getty#Automatic_login_to_virtual_console

Please post the journal for a boot with lightdm disabled. I want to see if any getty service is started.

Erotaku · 2021-01-30 20:54:01

loqs wrote:

Getty#Automatic_login_to_virtual_console
Please post the journal for a boot with lightdm disabled. I want to see if any getty service is started.

After reading this wiki page, I can safely say I have never done in thing in that area either. I also checked for relevant files similar to what the wiki showed, and I found none.

Here is the journal you asked for: https://pastebin.com/d24ynRVc

I have been reading more things on google about my weird issue. It seems like someone had a very similar issue and had to include sddm to the video groups or something? Could these groups affect my problem in anyway?:

groups ero
wheel audio storage video autologin ero

loqs · 2021-01-30 21:10:22

Jan 30 21:41:05 arch systemd[1]: Started Getty on tty1.
Jan 30 21:41:05 arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 30 21:41:05 arch systemd[1]: Reached target Login Prompts.
Jan 30 21:41:05 arch systemd-logind[422]: Watching system buttons on /dev/input/event1 (Power Button)
Jan 30 21:41:05 arch systemd-logind[422]: Watching system buttons on /dev/input/event0 (Power Button)
Jan 30 21:41:05 arch systemd-logind[422]: New seat seat0.
Jan 30 21:41:05 arch systemd[1]: Started User Login Management.
Jan 30 21:41:05 arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 30 21:41:05 arch systemd[1]: Reached target Multi-User System.
Jan 30 21:41:05 arch systemd[1]: Reached target Graphical Interface.
Jan 30 21:41:05 arch dbus-daemon[420]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jan 30 21:41:05 arch systemd[1]: Started Hostname Service.
Jan 30 21:41:05 arch systemd[1]: Startup finished in 17.722s (firmware) + 3.656s (loader) + 2.014s (kernel) + 746ms (userspace) = 24.140s.
Jan 30 21:41:05 arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8309] hostname: hostname: using hostnamed
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8309] hostname: hostname changed from (none) to "arch"
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8312] dns-mgr[0x5627927f2220]: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
Jan 30 21:41:05 arch kernel: usb 1-6: new full-speed USB device number 3 using xhci_hcd
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8341] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.28.1dev+7+g3f5df3cdc6-1/libnm-device-plugin-ovs.so)
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8357] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.28.1dev+7+g3f5df3cdc6-1/libnm-device-plugin-bluetooth.so)
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8361] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.28.1dev+7+g3f5df3cdc6-1/libnm-device-plugin-adsl.so)
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8398] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.28.1dev+7+g3f5df3cdc6-1/libnm-device-plugin-team.so)
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8404] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.28.1dev+7+g3f5df3cdc6-1/libnm-device-plugin-wifi.so)
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8407] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.28.1dev+7+g3f5df3cdc6-1/libnm-device-plugin-wwan.so)
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8409] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8409] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8410] manager: Networking is enabled by state file
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8413] dhcp-init: Using DHCP client 'internal'
Jan 30 21:41:05 arch dbus-daemon[420]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.2' (uid=0 pid=421 comm="/usr/bin/NetworkManager --no-daemon ")
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8416] settings: Loaded settings plugin: keyfile (internal)
Jan 30 21:41:05 arch systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8426] device (lo): carrier: link connected
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8428] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8444] ovsdb: Could not connect: No such file or directory
Jan 30 21:41:05 arch NetworkManager[421]: <info>  [1612039265.8450] manager: startup complete
Jan 30 21:41:05 arch dbus-daemon[420]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 30 21:41:05 arch systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 30 21:41:05 arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 30 21:41:05 arch kernel: usb 3-3: new full-speed USB device number 4 using xhci_hcd
Jan 30 21:41:06 arch kernel: usb 3-3: New USB device found, idVendor=1462, idProduct=7b85, bcdDevice= 0.01
Jan 30 21:41:06 arch kernel: usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 30 21:41:06 arch kernel: usb 3-3: Product: PRO CARBON   
Jan 30 21:41:06 arch kernel: usb 3-3: Manufacturer: MSI
Jan 30 21:41:06 arch kernel: usb 3-3: SerialNumber: A02018070613
Jan 30 21:41:06 arch kernel: usb 1-6: New USB device found, idVendor=1b1c, idProduct=0c1a, bcdDevice= 0.09
Jan 30 21:41:06 arch kernel: usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 30 21:41:06 arch kernel: usb 1-6: Product: CORSAIR Lighting Node CORE
Jan 30 21:41:06 arch kernel: usb 1-6: Manufacturer: Corsair
Jan 30 21:41:06 arch kernel: usb 1-6: SerialNumber: 1510020AE00445AFF23A055CC61B00F5
Jan 30 21:41:06 arch kernel: usb 3-4: new full-speed USB device number 5 using xhci_hcd
Jan 30 21:41:06 arch kernel: usb 3-4: New USB device found, idVendor=8087, idProduct=0025, bcdDevice= 0.02
Jan 30 21:41:06 arch kernel: usb 3-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 30 21:41:16 arch systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan 30 21:41:16 arch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 30 21:41:16 arch kernel: kauditd_printk_skb: 21 callbacks suppressed
Jan 30 21:41:16 arch kernel: audit: type=1131 audit(1612039276.081:32): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 30 21:41:27 arch systemd-logind[422]: Power key pressed.
Jan 30 21:41:27 arch systemd-logind[422]: Powering Off...
Jan 30 21:41:27 arch systemd-logind[422]: System is powering down.

Perhaps the issue is the display as the getty was started. Can you login blind at the console and then shutdown the system by calling `poweroff`?

Erotaku · 2021-01-30 21:21:39

loqs wrote:

Perhaps the issue is the display as the getty was started. Can you login blind at the console and then shutdown the system by calling `poweroff`?

You mean like still type the command 'poweroff" at the tty blind? No, that does not work. I even restarted my PC just to make sure in case I was mistaken. Typing my username or poweroff blind do not work. It does not respond to any keyboard strokes. Yes, I attempted to mash all my keyboard keys to no avail...

seth · 2021-01-30 23:28:04

The photo looks like something is creating garbage input…

Try to remove all the fancy g4m0rz stuff: the mouse, the headset, the LED (detaching the usb will do) and probably the keyboard (notably everything on the usb, could also be a webcam)
Then boot the multi-user.target w/ nothing but a $5 wired keyboard and see what happens.

Erotaku · 2021-01-31 09:38:29

seth wrote:

The photo looks like something is creating garbage input…
Try to remove all the fancy g4m0rz stuff: the mouse, the headset, the LED (detaching the usb will do) and probably the keyboard (notably everything on the usb, could also be a webcam)
Then boot the multi-user.target w/ nothing but a $5 wired keyboard and see what happens.

I just finished attempting what you asked for... Except that last part, because I only have one keyboard, unfortunately. My keyboard is vanilla though. It does not have any bells and whistles of any sorts. Regardless, nothing changed and I still could not type anything in.

Arch Linux

#1 2021-01-30 10:38:58

[solved] Boot stuck at black screen with after systemd

#2 2021-01-30 11:42:28

Re: [solved] Boot stuck at black screen with after systemd

#3 2021-01-30 11:55:20

Re: [solved] Boot stuck at black screen with after systemd

#4 2021-01-30 11:56:37

Re: [solved] Boot stuck at black screen with after systemd

#5 2021-01-30 12:52:25

Re: [solved] Boot stuck at black screen with after systemd

#6 2021-01-30 13:09:23

Re: [solved] Boot stuck at black screen with after systemd

#7 2021-01-30 14:10:43

Re: [solved] Boot stuck at black screen with after systemd

#8 2021-01-30 14:32:57

Re: [solved] Boot stuck at black screen with after systemd

#9 2021-01-30 15:20:27

Re: [solved] Boot stuck at black screen with after systemd

#10 2021-01-30 15:40:55

Re: [solved] Boot stuck at black screen with after systemd

#11 2021-01-30 15:59:41

Re: [solved] Boot stuck at black screen with after systemd

#12 2021-01-30 16:03:44

Re: [solved] Boot stuck at black screen with after systemd

#13 2021-01-30 16:30:00

Re: [solved] Boot stuck at black screen with after systemd

#14 2021-01-30 16:45:46

Re: [solved] Boot stuck at black screen with after systemd

#15 2021-01-30 16:50:01

Re: [solved] Boot stuck at black screen with after systemd

#16 2021-01-30 17:20:25

Re: [solved] Boot stuck at black screen with after systemd

#17 2021-01-30 18:02:04

Re: [solved] Boot stuck at black screen with after systemd

#18 2021-01-30 18:13:13

Re: [solved] Boot stuck at black screen with after systemd

#19 2021-01-30 20:02:59

Re: [solved] Boot stuck at black screen with after systemd

#20 2021-01-30 20:10:19

Re: [solved] Boot stuck at black screen with after systemd

#21 2021-01-30 20:54:01

Re: [solved] Boot stuck at black screen with after systemd

#22 2021-01-30 21:10:22

Re: [solved] Boot stuck at black screen with after systemd

#23 2021-01-30 21:21:39

Re: [solved] Boot stuck at black screen with after systemd

#24 2021-01-30 23:28:04

Re: [solved] Boot stuck at black screen with after systemd

#25 2021-01-31 09:38:29

Re: [solved] Boot stuck at black screen with after systemd

Board footer