My computer (not the one I’m writing from) whenever turned on boots onto hardware log. It’s updates when USB devices are connected/disconnected.
Because other tty’s are available I’ve confirmed that the computer still connects to Ethernet, and that files appear to be intact. It does not seem to be a problem with the hard drive as I ran a smartctl test and from what I could decern there were no reported issues.
commands like poweroff and ‘shutdown’ do not work properly, they just seem to turn off the ttys instead of the main screen with the hardware log. In order to actually turn off the computer, a long-press on the power buttion to force a shutdown is needed.
Sorry that I can’t give any more details as I’m not really sure what other tools are available for diagnostics
I’m not able to give the raw output as I can’t copy-paste from there
CPU is: quad core Intel Core i7-4790 (-MT MCP-)
GPU is: AMD Navi 24 [Radeon RX 6400/6500 XT/6500M]
Primary drive is LITE-ON IT model LCS-256L9S-11 SSD
but mhwd-kernel shows 5.15.118-1-MANJARO
mhwd: video-linux version 2018.05.04
waiting for X server to begin accepting connections
..
..
..
and so on until it gets to
xinit: giving up
xinit: unable to connect to X server: connection refused
waiting for X server to shut down ...........
xinit: X server slow to shut down, sending KILL signal
waiting for server to die...
xinit: X server refuses to die
might be relevant, that i was previously fiddling with a game (Vintage Story) which refused to exit properly and required SIGKILL to actually end the process
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it under the
# terms of the GNU Lesser General Public License as published by the Free
# Software Foundation; either version 2.1 of the License, or (at your option)
# any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file, or by creating "drop-ins" in
# the journald.conf.d/ subdirectory. The latter is generally recommended.
# Defaults can be restored by simply deleting this file and all drop-ins.
#
# Use 'systemd-analyze cat-config systemd/journald.conf' to display the full config.
#
# See journald.conf(5) for details.
[Journal]
#Storage=auto
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=10000
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMaxFiles=100
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMaxFiles=100
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=no
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
#LineMax=48K
#ReadKMsg=yes
#Audit=yes
GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet apparmor=1 security=apparmor udev.log_priority=3"
GRUB_CMDLINE_LINUX=""
# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true
# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true
In /etc/systemd/journald.conf, change these lines…
#ForwardToConsole=no
#TTYPath=/dev/console
… into…
ForwardToConsole=yes
TTYPath=/dev/tty12
… and issue…
sudo systemctl daemon-reload.
This will route the system log output to tty12 so that you can watch it in real-time by switching to that console via Alt+F12.
Do however bear in mind that this is only part of the troubleshooting process. Your issue is that for some reason, the X server dies while trying to start. And barring any serious misconfiguration, this is usually the result of graphics driver issues.
You did however say that this problem started after running a game, and it is possible that this game has messed up your graphics configuration. Normally it shouldn’t be able to do that, unless of course you were running the game as root, because only the root account has write access to the system-wide configuration, and in Manjaro, the X11 server does itself not run with root privileges.
It does in many if not most environments - Gnome/GDM is a notable exception.
(If a number of criteria are met - namely kernel mode setting)
SDDM for example cannot launch X rootless unless you have a newer version, ex: sddm-git.
With kernel mode-setting and systemd, the X11 server only runs with root privileges for running the display manager session — this is necessary because the display manager has to be able to read /etc/shadow — but as soon as the user has logged in, the user session starts X11 under the user’s own UID, and the root-owned session with the display manager exits.
I’m not sure this is the case … at least not in all circumstances.
See for example:
ps -o user= -C Xorg
If rootless then it will display your user.
I contend this is not the case by default in many if not most manjaro editions … I can specifically speak to KDE. As this is technically more on the display manager I guess I should say I can speak to SDDM … I am relatively sure lightdm cannot launch X rootless either.
I mentioned the game because I repeatedly had to SIGKILL and figured there might be some issues with that.
for some reason I’m only able to get up to tty6 so I routed the output to there instead of tty12, beyond that there doesn’t seem to give any output to there on reloading the daemon.
It could just be graphics drivers but there’s also the issue of shutdown not turning the system off properly, which by my very limited understanding would be quite strange for that to be a graphics issue.
This has gotten rather OT … but … I dont follow how that shows X running rootless.
It shows your user starting sddm. ok.
I dont understand how the steps outlined in Archwiki are refuted … if you run the above command … it will tell you if X is running rootless or not.
$ ps -o user= -C Xorg
USER
If I do follow your logic … I get expectedly different output from yours:
I never said that it did. In fact, I contended (and still contend) that the display manager runs a root-owned X11 session because it needs to be able to read /etc/shadow.
But as you say, this is off-topic, so let’s just drop it.
e[32mCurrently running:e[0m 5.15.118-1-MANJARO (linux515)
The following kernels are installed in your system:
* linux515
sudo mhwd -li output
e[1me[31m> e[mInstalled PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
e[1me[31mWarning: e[mNo installed USB configs!
