Hello,
Lately, I was installing some updates and left the laptop, when I came back screen was locked, and when I tried to login it kept saying password was wrong, while I was sure it was correct. Forced shutdown and since then it boots and is stuck on hp logo.
Tried “ctrl + alt + f2” to access the terminal, but the screen shows the terminal and prompts login details but for some reason I can’t type anything in it.
Tried chroot from live USB to update all packages but no luck.
Any ideas what could be the fix?
Thanks,
Hi @usef ,
Welcome back to the forum.
Could you please read the following post in order to solve your problem?
‘GRUB/Restore the GRUB Bootloader - Manjaro ’
I suggest you to restore the grub bootloader first.
Hope this help, regards
Hello @usef
I would rather suggest to remove quiet
from the grub kernel parameter and see where it hangs.
You can do this at boot time on the menu by editing the menu and at /etc/default/grub
and sudo update-grub
.
It is stuck after Finished TLP system startup/shutdown
Tried restoring grub, but no luck with that.
ok. So I assume the display-manager launched already.
This is the log when using Gnome3:
Mai 15 13:23:39 manjaro systemd[1]: Starting GNOME Display Manager...
Mai 15 13:23:39 manjaro systemd[1]: Starting Accounts Service...
Mai 15 13:23:39 manjaro systemd[1]: Starting Network Manager Script Dispatcher Service...
Mai 15 13:23:39 manjaro systemd[1]: Starting User Runtime Directory /run/user/120...
Mai 15 13:23:39 manjaro systemd[1]: Starting User Manager for UID 120...
Mai 15 13:23:40 manjaro systemd[1]: Starting cpupower-gui system helper...
Mai 15 13:23:41 manjaro systemd[1]: Starting TLP system startup/shutdown...
Did you try restarting the display-manager?
sudo systemctl restart display-manager
Also what is the status? Any error?
sudo systemctl status display-manager
Sorry, but where should I run those commands?
As when using the live USB and in chroot, I get
Running in chroot, ignoring command 'restart'
and as mentioned before I can’t write anything in the tty.
Ah ok, thought you can use the TTY, but cant type into the sddm display-manager to login. Got it. I read it again.
Well then it must be the journal:
journalctl -b1 --unit=sddm
This is what I get when running the journalctl command
-- Journal begins at Sat 2021-01-02 15:23:46 EET, ends at Sat 2021-05-15 17:26:33 EET. --
Jan 02 15:24:00 yousef-pavilion systemd[1]: Started Simple Desktop Display Manager.
Jan 02 15:24:03 yousef-pavilion sddm[528]: Initializing...
Jan 02 15:24:03 yousef-pavilion sddm[528]: Starting...
Jan 02 15:24:03 yousef-pavilion sddm[528]: Logind interface found
Jan 02 15:24:03 yousef-pavilion sddm[528]: Adding new display on vt 1 ...
Jan 02 15:24:03 yousef-pavilion sddm[528]: Loading theme configuration from ""
Jan 02 15:24:03 yousef-pavilion sddm[528]: Display server starting...
Jan 02 15:24:03 yousef-pavilion sddm[528]: Adding cookie to "/var/run/sddm/{b46b5618-f422-4382-91b7-00d9fa583c25}"
Jan 02 15:24:04 yousef-pavilion sddm[528]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{b46b5618-f422-438>
Jan 02 15:24:25 yousef-pavilion sddm[528]: Setting default cursor
Jan 02 15:24:25 yousef-pavilion sddm[528]: Running display setup script "/usr/share/sddm/scripts/Xsetup"
Jan 02 15:24:25 yousef-pavilion sddm[528]: Display server started.
Jan 02 15:24:25 yousef-pavilion sddm[528]: Socket server starting...
Jan 02 15:24:25 yousef-pavilion sddm[528]: Socket server started.
Jan 02 15:24:25 yousef-pavilion sddm[528]: Loading theme configuration from "/usr/share/sddm/themes/breath2/theme.conf"
Jan 02 15:24:25 yousef-pavilion sddm[528]: Greeter starting...
Jan 02 15:24:26 yousef-pavilion sddm-helper[792]: [PAM] Starting...
Jan 02 15:24:26 yousef-pavilion sddm-helper[792]: [PAM] Authenticating...
Jan 02 15:24:26 yousef-pavilion sddm-helper[792]: [PAM] returning.
Jan 02 15:24:26 yousef-pavilion sddm-helper[792]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=967) by (uid=0)
Jan 02 15:24:27 yousef-pavilion sddm[528]: Greeter session started successfully
Jan 02 15:24:28 yousef-pavilion sddm[528]: Message received from greeter: Connect
Jan 02 15:31:04 yousef-pavilion sddm[528]: Message received from greeter: Login
Jan 02 15:31:04 yousef-pavilion sddm[528]: Reading from "/usr/share/xsessions/plasma.desktop"
Jan 02 15:31:04 yousef-pavilion sddm[528]: Reading from "/usr/share/xsessions/plasma.desktop"
Jan 02 15:31:04 yousef-pavilion sddm[528]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startplasma-x11"
Jan 02 15:31:04 yousef-pavilion sddm-helper[846]: [PAM] Starting...
Jan 02 15:31:04 yousef-pavilion sddm-helper[846]: [PAM] Authenticating...
Jan 02 15:31:04 yousef-pavilion sddm-helper[846]: [PAM] Preparing to converse...
Jan 02 15:31:04 yousef-pavilion sddm-helper[846]: [PAM] Conversation with 1 messages
Jan 02 15:31:04 yousef-pavilion sddm-helper[846]: pam_unix(sddm:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=yousef
Jan 02 15:31:04 yousef-pavilion sddm-helper[846]: pam_systemd_home(sddm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.servi>
Jan 02 15:31:06 yousef-pavilion sddm-helper[846]: [PAM] authenticate: Permission denied
Jan 02 15:31:06 yousef-pavilion sddm-helper[846]: [PAM] returning.
Jan 02 15:31:06 yousef-pavilion sddm[528]: Authentication error: "Permission denied"
Jan 02 15:31:06 yousef-pavilion sddm-helper[846]: [PAM] Ended.
Jan 02 15:31:06 yousef-pavilion sddm[528]: Auth: sddm-helper exited with 1
Jan 02 15:31:15 yousef-pavilion sddm[528]: Message received from greeter: Login
Jan 02 15:31:15 yousef-pavilion sddm[528]: Reading from "/usr/share/xsessions/plasma.desktop"
Jan 02 15:31:15 yousef-pavilion sddm[528]: Reading from "/usr/share/xsessions/plasma.desktop"
Jan 02 15:31:15 yousef-pavilion sddm[528]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startplasma-x11"
Jan 02 15:31:15 yousef-pavilion sddm-helper[848]: [PAM] Starting...
Jan 02 15:31:15 yousef-pavilion sddm-helper[848]: [PAM] Authenticating...
Jan 02 15:31:15 yousef-pavilion sddm-helper[848]: [PAM] Preparing to converse...
Jan 02 15:31:15 yousef-pavilion sddm-helper[848]: [PAM] Conversation with 1 messages
Jan 02 15:31:15 yousef-pavilion sddm-helper[848]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
Jan 02 15:31:15 yousef-pavilion sddm-helper[848]: [PAM] returning.
Jan 02 15:31:15 yousef-pavilion sddm-helper[848]: pam_systemd_home(sddm:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.se>
Jan 02 15:31:15 yousef-pavilion sddm[528]: Authenticated successfully
Jan 02 15:31:15 yousef-pavilion sddm-helper[848]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Jan 02 15:31:15 yousef-pavilion sddm-helper[848]: pam_unix(sddm:session): session opened for user yousef(uid=1000) by (uid=0)
Jan 02 15:31:15 yousef-pavilion sddm-helper[848]: pam_env(sddm:session): deprecated reading of user environment enabled
Jan 02 15:31:15 yousef-pavilion sddm-helper[848]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Jan 02 15:31:15 yousef-pavilion sddm[528]: Auth: sddm-helper exited successfully
Jan 02 15:31:15 yousef-pavilion sddm[528]: Greeter stopped.
Jan 02 15:31:15 yousef-pavilion sddm-helper[848]: Starting: "/usr/share/sddm/scripts/Xsession \"/usr/bin/startplasma-x11\""
Jan 02 15:31:16 yousef-pavilion sddm[528]: Session started
Jan 03 22:58:47 yousef-pavilion systemd[1]: Stopping Simple Desktop Display Manager...
Jan 03 22:58:47 yousef-pavilion sddm[528]: Authentication error: "Process crashed"
Jan 03 22:58:47 yousef-pavilion sddm[528]: Auth: sddm-helper crashed (exit code 15)
Jan 03 22:58:47 yousef-pavilion sddm[528]: Authentication error: "Process crashed"
Jan 03 22:58:47 yousef-pavilion sddm[528]: Auth: sddm-helper exited with 15
Jan 03 22:58:47 yousef-pavilion sddm[528]: Socket server stopping...
Jan 03 22:58:47 yousef-pavilion sddm[528]: Socket server stopped.
Jan 03 22:58:47 yousef-pavilion sddm[528]: Display server stopping...
Jan 03 22:58:52 yousef-pavilion sddm[528]: Removing display ":0" ...
Jan 03 22:58:54 yousef-pavilion sddm[528]: Adding new display on vt 1 ...
Jan 03 22:58:54 yousef-pavilion sddm[528]: Loading theme configuration from ""
Jan 03 22:58:54 yousef-pavilion sddm[528]: Display server starting...
Jan 03 22:58:54 yousef-pavilion sddm[528]: Adding cookie to "/var/run/sddm/{8ed984e9-0435-4c27-8338-cbc0e2c80f32}"
Jan 03 22:58:55 yousef-pavilion sddm[528]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{8ed984e9-0435-4c2>
Jan 03 22:59:08 yousef-pavilion sddm[528]: Setting default cursor
Jan 03 22:59:09 yousef-pavilion sddm[528]: Running display setup script "/usr/share/sddm/scripts/Xsetup"
Jan 03 22:59:09 yousef-pavilion sddm[528]: Display server started.
Jan 03 22:59:09 yousef-pavilion sddm[528]: Socket server starting...
Jan 03 22:59:09 yousef-pavilion sddm[528]: Socket server started.
Jan 03 22:59:09 yousef-pavilion sddm[528]: Loading theme configuration from "/usr/share/sddm/themes/breath2/theme.conf"
Jan 03 22:59:09 yousef-pavilion sddm[528]: Greeter starting...
Jan 03 22:59:09 yousef-pavilion sddm[528]: Display server stopping...
Jan 03 22:59:09 yousef-pavilion sddm[528]: Display server stopped.
Jan 03 22:59:09 yousef-pavilion sddm[528]: Running display stop script "/usr/share/sddm/scripts/Xstop"
Jan 03 22:59:09 yousef-pavilion sddm[528]: Signal received: SIGTERM
Jan 03 22:59:09 yousef-pavilion sddm[528]: Socket server stopping...
Jan 03 22:59:09 yousef-pavilion sddm[528]: Socket server stopped.
Jan 03 22:59:09 yousef-pavilion sddm[528]: Display server stopping...
Jan 03 22:59:09 yousef-pavilion sddm-helper[37111]: [PAM] Starting...
Jan 03 22:59:09 yousef-pavilion sddm-helper[37111]: [PAM] Authenticating...
Jan 03 22:59:09 yousef-pavilion sddm-helper[37111]: [PAM] returning.
Jan 03 22:59:10 yousef-pavilion sddm[528]: Display server stopped.
Jan 03 22:59:10 yousef-pavilion sddm[528]: Running display stop script "/usr/share/sddm/scripts/Xstop"
Jan 03 22:59:10 yousef-pavilion sddm[528]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Jan 03 22:59:10 yousef-pavilion systemd[1]: sddm.service: Succeeded.
Jan 03 22:59:10 yousef-pavilion systemd[1]: Stopped Simple Desktop Display Manager.
~
Well this is from Jan 03… xD
Try this:
journalctl --since=today --no-pager
This one is really long. Please use pastebin or something else for this.
usef
15 May 2021 16:31
11
Figured so lol, well here is the output in pastebin.
Seems to be pretty normal at the logs. sddm started and you reached the graphical target.
May 15 17:26:02 yousef-pavilion sddm[575]: Display server starting...
May 15 17:26:02 yousef-pavilion sddm[575]: Adding cookie to "/var/run/sddm/{ef33ef3c-9bf6-4b8a-a5d6-70720134728d}"
May 15 17:26:02 yousef-pavilion dbus-daemon[520]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.7' (uid=0 pid=521 comm="/usr/bin/NetworkManager --no-daemon ")
May 15 17:26:02 yousef-pavilion systemd[1]: Starting WPA supplicant...
May 15 17:26:02 yousef-pavilion kernel: audit: type=1130 audit(1621092362.212:39): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=ModemManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 15 17:26:02 yousef-pavilion audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=ModemManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 15 17:26:02 yousef-pavilion NetworkManager[521]: <info> [1621092362.1818] ovsdb: Could not connect: No such file or directory
May 15 17:26:02 yousef-pavilion NetworkManager[521]: <info> [1621092362.1819] ovsdb: disconnected from ovsdb
May 15 17:26:02 yousef-pavilion sddm[575]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{ef33ef3c-9bf6-4b8a-a5d6-70720134728d} -noreset -displayfd 17
May 15 17:26:02 yousef-pavilion systemd[1]: Started Modem Manager.
May 15 17:26:02 yousef-pavilion NetworkManager[521]: <info> [1621092362.2185] modem-manager: ModemManager not available
May 15 17:26:02 yousef-pavilion systemd[1]: Reached target Multi-User System.
May 15 17:26:02 yousef-pavilion systemd[1]: Reached target Graphical Interface.
May 15 17:26:02 yousef-pavilion systemd[1]: Starting TLP system startup/shutdown...
What is at the Xorg logs?
for x in /var/log/Xorg* ; do echo -e "--- $x ---\n $(cat $x)\n"; done
Here is the error:
[ 43562.914] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[ 43562.914] (EE) NVIDIA: system's kernel log for additional error messages and
[ 43562.914] (EE) NVIDIA: consult the NVIDIA README for details.
[ 43562.914] (EE) [drm] Failed to open DRM device for (null): -2
There seems to be a conflict:
[ 43561.992] (II) LoadModule: "nvidia"
[ 43561.992] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 43562.093] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 43562.093] compiled for 1.6.99.901, module version = 1.0.0
[ 43562.093] Module class: X.Org Video Driver
and
[ 43562.094] (II) LoadModule: "nouveau"
[ 43562.094] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 43562.104] (II) Module nouveau: vendor="X.Org Foundation"
[ 43562.104] compiled for 1.20.10, module version = 1.0.17
[ 43562.105] Module class: X.Org Video Driver
[ 43562.105] ABI class: X.Org Video Driver, version 24.1
These 2 cannot be loaded at the same time. You have to blacklist nouveau in favor for nvidia or remove the nvidia driver.
Please check these files:
cat /etc/modules-load.d/mhwd-gpu.conf
It should look like this:
##
## Generated by mhwd - Manjaro Hardware Detection
##
nvidia
nvidia-drm
and
cat /etc/modprobe.d/mhwd-gpu.conf
It should look like this:
##
## Generated by mhwd - Manjaro Hardware Detection
##
blacklist nouveau
blacklist ttm
blacklist drm_kms_helper
blacklist drm
usef
15 May 2021 17:47
15
Yes, that’s exactly what I got except I got this line in the last file
options nvidia "NVreg_DynamicPowerManagement=0x02"
usef
15 May 2021 17:50
17
> 0000:01:00.0 (0300:10de:1c8d) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-hybrid-intel-nvidia-prime 2020.11.30 false PCI
video-hybrid-intel-nvidia-390xx-bumblebee 2020.11.30 false PCI
video-nvidia 2020.11.30 false PCI
video-nvidia-390xx 2020.11.30 false PCI
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI
> 0000:05:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
network-r8168 2016.04.20 true PCI
> 0000:00:02.0 (0300:8086:591b) Display controller Intel Corporation:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-hybrid-intel-nvidia-prime 2020.11.30 false PCI
video-hybrid-intel-nvidia-390xx-bumblebee 2020.11.30 false PCI
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
Warning: No installed USB configs!
How did you install the nvidia driver? Seems not with mhwd. To fix that at least, you need to remove nvidia completely for this moment.
Remove all packages which are listed with this command:
pamac search nvidia --installed --quiet | grep -v mhwd
Also remove
sudo rm /etc/modprobe.d/mhwd-gpu.conf /etc/modules-load.d/mhwd-gpu.conf
and
sudo mhwd -r video-modesetting
and check also the xorg confs, if there is a mhwd file:
ls /etc/X11/xorg.conf.d/
And let nouveau start next time. Intel is anyway the main GPU.
If everything works, then you can reinstall the nividia driver again.
usef
15 May 2021 20:19
19
Have done all of that, but still stuck at the same stage.
usef
15 May 2021 22:48
20
Haven’t found any working solution, so just made a new fresh install. Thanks anyways