After kernel update 5.13 -> 5.15 system wont boot

Support Kernel
1

INFO:
Computer: Lenovo IdeaPad L340
RAM: 16GB
GPU: NVIDIA GeForce GTX 1650
Software: encrypted Manjaro with xfce and i3

BEGINING:
I started with trying to update the kernel from the xfce gui which did nothing, so I did it through the terminal.

sudo pacman -S linux515
reboot

After reboot I entered encryption passphrase but after that there was only black screen.

WHAT I TRIED:

  1. I chrooted with my live manjaro USB boot and reinstalled video drivers.
    result: No longer black screen but everything stops on this screen:
    image
    /dev/mapper/luks-de5c95eb-8a2b-41eb-b56e-fc7cf3ea891d: recovering journal
    /dev/mapper/luks-de5c95eb-8a2b-41eb-b56e-fc7cf3ea891d: clean, 607988/62513152 fi
    les, 25871938/250048948 block
    _
  2. Updated everything with
    sudo pacman -Suy
    result: no change
  3. Reinstalling the 5.15 Kernel and booting with only the old one 5.13
    result: no change
  4. uninstalling the old kernel 5.13 and booting with only the new one
    result: no change

mhwd-kernel -li
Outputs:
Currently running: 5.13.19-2-MANJARO (linux513)
The following kernels are installed in your system:
* linux515

PROBABLE CAUSE FOUND:

Solution:
¯\(ツ)/¯
Dont have time, need laptop for school - reinstalling system.

2

Use MHWD to install 5.15 and remove the existing kernel:

sudo mhwd-kernel -i linux515 rmc

See Manjaro Kernels - Manjaro

1 Like
3

done, no change while booting and mhwd-kernel -li says that Its still running 5.13

4

Do note that while chrooting, mhwd-kernel will read the (old) ISO kernel as the one being running.

You may want to look for logs: [HowTo] Find error logs

5

You can also install 5.15…

sudo mhwd-kernel -i linux515

…reboot…

…then remove 5.13.

sudo mhwd-kernel -r linux513
6

after looking at some logs it looks like there is some problem with starting lightdm.service
journalctl --boot=-1 --priority=3 --catalog

Feb 27 03:37:24 mrk-81ll kernel: x86/cpu: SGX disabled by BIOS.
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS07._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS08._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS08._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS09._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS10._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS11._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS12._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS13._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS14._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS14._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.XHC.RHUB.USR1], AE_NOT_FOUND (20210730/dswload2-162)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.XHC.RHUB.USR2], AE_NOT_FOUND (20210730/dswload2-162)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS01._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS02._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS02._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS03._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS03._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS04._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS04._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS05._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS06._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS07._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS08._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS09._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS10._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.I2C2.TPD0], AE_NOT_FOUND (20210730/dswload2-162)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:24 mrk-81ll kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.I2C3.TPL1], AE_NOT_FOUND (20210730/dswload2-162)
Feb 27 03:37:24 mrk-81ll kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220)
Feb 27 03:37:29 mrk-81ll systemd[1]: Failed to start Light Display Manager.
-- Subject: A start job for unit lightdm.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit lightdm.service has finished with a failure.
-- 
-- The job identifier is 1141 and the job result is failed.

lightdm --test-mode -d

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.30.0, UID=0 PID=15
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /var/lib/snapd/desktop/lightdm/lightdm.conf.d
[+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 /var/lib/flatpak/exports/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /home/manjaro/.local/share/flatpak/exports/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: Using Xephyr for X servers
[+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] WARNING: Failed to get system bus: Could not connect: No such file or directory
[+0.00s] DEBUG: Adding default seat
[+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.00s] DEBUG: Seat seat0: Starting
[+0.00s] DEBUG: Seat seat0: Creating greeter session
[+0.00s] DEBUG: Seat seat0: Creating display server of type x
[+0.00s] DEBUG: Could not run plymouth --ping: Failed to execute child process ?plymouth? (No such file or directory)
[+0.00s] DEBUG: Using VT 7
[+0.00s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.00s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.00s] DEBUG: XServer 0: Can't launch X server Xephyr, not found in path
[+0.00s] DEBUG: XServer 0: X server stopped
[+0.00s] DEBUG: Releasing VT 7
[+0.00s] DEBUG: Seat seat0: Display server stopped
[+0.00s] DEBUG: Seat seat0: Can't create display server for greeter
[+0.00s] DEBUG: Seat seat0: Session stopped
[+0.00s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.00s] DEBUG: Seat seat0: Stopping
[+0.00s] DEBUG: Seat seat0: Stopped

Althou I dont really know what to do with this…

7

Just to confirm it has to do with LightDM:

journaltcl --boot=-1 --unit=lightdm
8

journalctl --boot=-1 --unit=lightdm

Feb 27 03:37:26 mrk-81ll systemd[1]: Starting Light Display Manager...
Feb 27 03:37:26 mrk-81ll systemd[1]: Started Light Display Manager.
Feb 27 03:37:28 mrk-81ll systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 27 03:37:28 mrk-81ll systemd[1]: lightdm.service: Failed with result 'exit-code'.
Feb 27 03:37:28 mrk-81ll systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
Feb 27 03:37:28 mrk-81ll systemd[1]: Stopped Light Display Manager.
Feb 27 03:37:28 mrk-81ll systemd[1]: Starting Light Display Manager...
Feb 27 03:37:28 mrk-81ll systemd[1]: Started Light Display Manager.
Feb 27 03:37:28 mrk-81ll systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 27 03:37:28 mrk-81ll systemd[1]: lightdm.service: Failed with result 'exit-code'.
Feb 27 03:37:28 mrk-81ll systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 2.
Feb 27 03:37:28 mrk-81ll systemd[1]: Stopped Light Display Manager.
Feb 27 03:37:28 mrk-81ll systemd[1]: Starting Light Display Manager...
Feb 27 03:37:28 mrk-81ll systemd[1]: Started Light Display Manager.
Feb 27 03:37:28 mrk-81ll systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 27 03:37:28 mrk-81ll systemd[1]: lightdm.service: Failed with result 'exit-code'.
Feb 27 03:37:28 mrk-81ll systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 3.
Feb 27 03:37:28 mrk-81ll systemd[1]: Stopped Light Display Manager.
Feb 27 03:37:28 mrk-81ll systemd[1]: Starting Light Display Manager...
Feb 27 03:37:28 mrk-81ll systemd[1]: Started Light Display Manager.
Feb 27 03:37:28 mrk-81ll systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 27 03:37:28 mrk-81ll systemd[1]: lightdm.service: Failed with result 'exit-code'.
Feb 27 03:37:29 mrk-81ll systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 4.
Feb 27 03:37:29 mrk-81ll systemd[1]: Stopped Light Display Manager.
Feb 27 03:37:29 mrk-81ll systemd[1]: Starting Light Display Manager...
Feb 27 03:37:29 mrk-81ll systemd[1]: Started Light Display Manager.
Feb 27 03:37:29 mrk-81ll systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 27 03:37:29 mrk-81ll systemd[1]: lightdm.service: Failed with result 'exit-code'.
Feb 27 03:37:29 mrk-81ll systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Feb 27 03:37:29 mrk-81ll systemd[1]: Stopped Light Display Manager.
Feb 27 03:37:29 mrk-81ll systemd[1]: lightdm.service: Start request repeated too quickly.
Feb 27 03:37:29 mrk-81ll systemd[1]: lightdm.service: Failed with result 'exit-code'.
Feb 27 03:37:29 mrk-81ll systemd[1]: Failed to start Light Display Manager.

cat /var/log/Xorg.0.log

[    10.075] 
X.Org X Server 1.21.1.3
X Protocol Version 11, Revision 0
[    10.075] Current Operating System: Linux mrk-81ll 5.15.21-1-MANJARO #1 SMP PREEMPT Sun Feb 6 12:21:42 UTC 2022 x86_64
[    10.075] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64 root=UUID=b838d76d-25ab-42cd-ad75-f175c6fd38c3 rw quiet cryptdevice=UUID=de5c95eb-8a2b-41eb-b56e-fc7cf3ea891d:luks-de5c95eb-8a2b-41eb-b56e-fc7cf3ea891d root=/dev/mapper/luks-de5c95eb-8a2b-41eb-b56e-fc7cf3ea891d apparmor=1 security=apparmor udev.log_priority=3
[    10.075]  
[    10.075] Current version of pixman: 0.40.0
[    10.075] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    10.075] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    10.075] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Feb 27 15:30:01 2022
[    10.075] (==) Using config file: "/etc/X11/xorg.conf"
[    10.075] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    10.075] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    10.076] (==) ServerLayout "Layout0"
[    10.076] (**) |-->Screen "Screen0" (0)
[    10.076] (**) |   |-->Monitor "Monitor0"
[    10.076] (**) |   |-->Device "Device0"
[    10.076] (**) |-->Input Device "Keyboard0"
[    10.076] (**) |-->Input Device "Mouse0"
[    10.076] (==) Automatically adding devices
[    10.076] (==) Automatically enabling devices
[    10.076] (==) Automatically adding GPU devices
[    10.076] (==) Automatically binding GPU devices
[    10.076] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    10.076] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[    10.076] 	Entry deleted from font path.
[    10.076] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    10.076] 	Entry deleted from font path.
[    10.076] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[    10.076] 	Entry deleted from font path.
[    10.076] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[    10.076] 	Entry deleted from font path.
[    10.076] (==) FontPath set to:
	/usr/share/fonts/misc,
	/usr/share/fonts/TTF
[    10.076] (==) ModulePath set to "/usr/lib/xorg/modules"
[    10.076] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[    10.076] (WW) Disabling Keyboard0
[    10.076] (WW) Disabling Mouse0
[    10.076] (II) Module ABI versions:
[    10.076] 	X.Org ANSI C Emulation: 0.4
[    10.076] 	X.Org Video Driver: 25.2
[    10.076] 	X.Org XInput driver : 24.4
[    10.076] 	X.Org Server Extension : 10.0
[    10.078] (++) using VT number 7

[    10.078] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    10.078] (II) xfree86: Adding drm device (/dev/dri/card0)
[    10.079] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
[    10.083] (--) PCI:*(1@0:0:0) 10de:1f91:17aa:3a41 rev 161, Mem @ 0xb2000000/16777216, 0xa0000000/268435456, 0xb0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/131072
[    10.083] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    10.083] (II) LoadModule: "glx"
[    10.084] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    10.086] (II) Module glx: vendor="X.Org Foundation"
[    10.086] 	compiled for 1.21.1.3, module version = 1.0.0
[    10.086] 	ABI class: X.Org Server Extension, version 10.0
[    10.086] (II) LoadModule: "nvidia"
[    10.086] (WW) Warning, couldn't open module nvidia
[    10.086] (EE) Failed to load module "nvidia" (module does not exist, 0)
[    10.086] (EE) No drivers available.
[    10.086] (EE) 
Fatal server error:
[    10.086] (EE) no screens found(EE) 
[    10.086] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    10.086] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    10.086] (EE) 
[    10.086] (EE) Server terminated with error (1). Closing log file.
9

When you messed up your system by keeping an unsupported (for months) kernel, you probably also broke your Nvidia drivers, that’s my guess. So once again, make sure to be up to date with pacman -Syyu, then use Manjaro tools to install latest LTS kernel 5.15, reboot, remove kernel 5.13, and remove/reinstall Nvidia drivers (check the WIKI for all that if you don’t know how to use Manjaro tools for that).

//EDIT: you edited your message above and added relevant log, that is what I guessed:

[    10.086] (EE) Failed to load module "nvidia" (module does not exist, 0)
10

yes, but I already tried all you suggested

11

You’re doing it wrong then.

You said you installed kernel 5.15 and removed 5.13, but you still use kernel 5.13, from your own messages, so what do we do with that?

12

I have followed these steps

13

Well I used this command which to my knowlege should remove the kernel I am using right now which would be the 5.13

but as I said
mhwd-kernel -li
Outputs:
Currently running: 5.13.19-2-MANJARO (linux513)
The following kernels are installed in your system:

  • linux515

thats just that

14

Go to TTY from your computer with CTRL+ALT+F3, login in this terminal, and do the steps explained here After kernel update 5.13 -> 5.15 system wont boot - #5 by Yochanan

sudo pacman -Syyu
sudo mhwd-kernel -i linux515

…reboot… then remove 5.13.

sudo mhwd-kernel -r linux513

Then when you are sure you have booted on kernel 5.15 and removed 5.13, reinstall Nvidia

sudo mhwd -r pci video-nvidia
sudo mhwd -i pci video-nvidia

Make sure to read your screen for any error in all the steps, if you have errors then obviously something will not go well so make sure everything is going properly. In case of error at any step don’t continue, report here the error. so we can figure it out.

15

Does it have to be through the TTY? The problem is that I cant get into it. That is why I always chrooted.
I have tried all the key combinations I could find online.

16

OK then if you can’t access TTY at all, then chroot your system but make sure you’re doing it right and no error message pops up. Also when chrooted you don’t need to use sudo for the commands as you will be in a root terminal.

17

Could mount -o bind /run/ /mnt/run/ cause any problems during the package updates?
I couldnt update before. I think its because /etc/resolv.conf is empty and I cant edit it, so I found this solution, but I am not sure if its alright to use it.

also mhwd-kernel -i linux515 gives me:

error: no targets specified (use -h for help)

and I am not sure I can do anything with that

18

To chroot you only need to do manjaro-chroot -a in terminal from the live environment, and select the system. Then you can use the commands when you are in the root terminal with system chrooted. I don’t know what you have done, I would reboot on clean live environment and start over.

19

I followed this
its basically the same but I have to mount the encrypted partition before chrooting

20

Follow what I wrote.