[SOLVED] ArcoLinux no longer boots into lightdm/Gnome, display stays black, system does not respond

[mseidel]

Hello,

I have started using ArcoLinux only one year ago and have a Thinkpad E595 (Ryzen7, 3700U with a Radeon RX Vega10 APU, 512GB 970 PRO NVMe SSD) on it is an encrypted ArcoLinux B (Gnome) installation. The Thinkpad no longer boots correctly.

The boot manager grub is still displayed, the kernel is loaded and the SSD block check clean... also still. After that the display stays black and the system stops responding.

My guess is that due to an update in ~ 12/2020 there is an error in the installation. I have removed the word "quit" (In the line of the Linux image) in the edit mode of grub and replaced it with a "nomodeset". This allowed me to see the normal boot process and do a pacman -Syu via tty (command line access). The system was updated. However, the error is still present.

In the Xorg.log I saw in the entry "cannot start framebuffer mode". lightdm failed to start and prints via systemctl status an exit-code status 1 failure.

The package arcolinux-lightdm-gtk-greeter currently seems to have an invalid PGP signature, I have uninstalled it. I reinstalled lightdm, but the problem is still present.

I would be very grateful for any hints and help to fix the problem.


Best regards
mseidel

[erikdubois]

Nothing comes to mind.

Lets first gather information.

After checking there is no such issue posted on the forum you create a new post in the correct forum. Give us the following elements at least.
- what iso are you using - type' iso' in the terminal and copy paste that in the post between tags in the forum post
- type 'inxi -b' in a terminal and copy/paste the code between tags in the forum post
- type 'probe' in a terminal and provide us the link
- what graphical drivers have you installed
- on what desktop does the error occur
- is that system up to date - go to TTY (CTRL + ALT + F2 or in VIrtualbox RIght CTRL + F2) and type 'update' and reboot first
- why do you think you have an issue - previous actions can explain the current issue

[mseidel]

Hello,

unfortunately I do not know the tool "iso".

The output of Inxi:
----
System: Host: zagara Kernel: 5.10.7-arch1-1 x86_64 bits: 64 Console: N/A Distro: ArcoLinux
Machine: Type: Laptop System: LENOVO product: 20NFCTO1WW v: ThinkPad E595 serial: PF1YJ8KC
Mobo: LENOVO model: 20NFCTO1WW serial: L1HF9AD0008 UEFI [Legacy]: LENOVO v: R11ET30W (1.10 ) date: 10/11/2019
Battery: ID-1: BAT0 charge: 40.5 Wh condition: 42.6/45.7 Wh (93%)
CPU: Info: Quad Core AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx [MT MCP] speed: 1224 MHz min/max: 1400/2300 MHz
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: N/A
Display: server: X.org 1.20.10 driver: ati,radeon,vesa unloaded: fbdev,modesetting tty: 240x67
Message: Advanced graphics data unavailable in console for root.
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
Device-2: Intel Wireless-AC 9260 driver: iwlwifi
Device-3: Intel Wireless-AC 9260 Bluetooth Adapter type: USB driver: btusb
Drives: Local Storage: total: 492.06 GiB used: 72.99 GiB (14.8%)
Info: Processes: 193 Uptime: 2m Memory: 13.51 GiB used: 499.7 MiB (3.6%) Init: systemd Shell: Bash inxi: 3.2.01
----

Probe URL: https://linux-hardware.org/?probe=fc5afc1dc2

- The system is up to date. Update was performed and the ThinkPad rebooted. Unfortunately, the problem is still present.
- I have not installed any specific graphics card driver that I know of. The APU is the integr. Radeon RX Vega 10 chip.
- The image I originally installed contains the desktop environment GNOME (with lightdm as display manager).

- I have not been using the Thinkpad regularly lately. The last time I used it ~ early December, I did an update, used the device, and then shut it down without rebooting it again. Bad handling, I know!

I have the following additional info:

The output of: systemctl status lightdm.service
----
● lightdm.service - Light Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2021-01-18 18:07:26 CET; 3min 9s ago
Docs: man:lightdm(1)
Process: 1652 ExecStart=/usr/bin/lightdm (code=exited, status=1/FAILURE)
Main PID: 1652 (code=exited, status=1/FAILURE)

Jan 18 18:07:26 zagara systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Jan 18 18:07:26 zagara systemd[1]: Stopped Light Display Manager.
Jan 18 18:07:26 zagara systemd[1]: lightdm.service: Start request repeated too quickly.
Jan 18 18:07:26 zagara systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jan 18 18:07:26 zagara systemd[1]: Failed to start Light Display Manager.
----

The output of: journalctl -xe | grep lightdm | tail
----
Jan 18 18:07:26 zagara audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
░░ Subject: A start job for unit lightdm.service has begun execution
░░ A start job for unit lightdm.service has begun execution.
░░ Subject: A start job for unit lightdm.service has finished successfully
░░ A start job for unit lightdm.service has finished successfully.
Jan 18 18:07:26 zagara audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 18 18:07:26 zagara systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit lightdm.service has exited.
Jan 18 18:07:26 zagara systemd[1]: lightdm.service: Failed with result 'exit-code'.
░░ The unit lightdm.service has entered the 'failed' state with result 'exit-code'.
Jan 18 18:07:26 zagara audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jan 18 18:07:26 zagara kernel: audit: type=1131 audit(1610989646.596:48): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jan 18 18:07:26 zagara systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
░░ Automatic restarting of the unit lightdm.service has been scheduled, as the result for
Jan 18 18:07:26 zagara audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 18 18:07:26 zagara audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
░░ Subject: A stop job for unit lightdm.service has finished
░░ A stop job for unit lightdm.service has finished.
Jan 18 18:07:26 zagara systemd[1]: lightdm.service: Start request repeated too quickly.
Jan 18 18:07:26 zagara systemd[1]: lightdm.service: Failed with result 'exit-code'.
░░ The unit lightdm.service has entered the 'failed' state with result 'exit-code'.
░░ Subject: A start job for unit lightdm.service has failed
░░ A start job for unit lightdm.service has finished with a failure.
Jan 18 18:07:26 zagara kernel: audit: type=1130 audit(1610989646.949:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 18 18:07:26 zagara kernel: audit: type=1131 audit(1610989646.949:50): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
----
---

The output of /var/log/lightdm.log:
----
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.01s] DEBUG: Seat seat0: Creating display server of type x
[+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: Starting local X display on VT 7
[+0.01s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.01s] DEBUG: XServer 0: Launching X Server
[+0.01s] DEBUG: Launching process 1658: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.13s] DEBUG: Process 1658 exited with return value 1
[+0.13s] DEBUG: XServer 0: X server stopped
[+0.13s] DEBUG: Releasing VT 7
[+0.13s] DEBUG: XServer 0: Removing X server authority /run/lightdm/root/:0
[+0.13s] DEBUG: Seat seat0: Display server stopped
[+0.13s] DEBUG: Seat seat0: Stopping session
[+0.13s] DEBUG: Seat seat0: Session stopped
[+0.13s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.13s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+0.13s] DEBUG: Seat seat0: Stopping
[+0.13s] DEBUG: Seat seat0: Stopped
[+0.13s] DEBUG: Required seat has stopped
[+0.13s] DEBUG: Stopping display manager
[+0.13s] DEBUG: Display manager stopped
[+0.13s] DEBUG: Stopping daemon
[+0.13s] DEBUG: Exiting with return value 1
----

The output of /var/log/Xorg.0.log:
----
[ 20.553] (II) LoadModule: "fbdevhw"
[ 20.553] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 20.553] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 20.553] compiled for 1.20.10, module version = 0.0.2
[ 20.553] ABI class: X.Org Video Driver, version 24.1
[ 20.553] (EE) Unable to find a valid framebuffer device
[ 20.553] (WW) Falling back to old probe method for fbdev
[ 20.553] (II) Loading sub module "fbdevhw"
[ 20.553] (II) LoadModule: "fbdevhw"
[ 20.553] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 20.553] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 20.553] compiled for 1.20.10, module version = 0.0.2
[ 20.553] ABI class: X.Org Video Driver, version 24.1
[ 20.553] (II) FBDEV(2): using default device
[ 20.553] (EE) Screen 0 deleted because of no matching config section.
[ 20.553] (II) UnloadModule: "modesetting"
[ 20.553] (EE) Screen 0 deleted because of no matching config section.
[ 20.553] (II) UnloadModule: "fbdev"
[ 20.553] (II) UnloadSubModule: "fbdevhw"
[ 20.553] (EE)
Fatal server error:
[ 20.553] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
[ 20.553] (EE)
[ 20.553] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 20.554] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 20.554] (EE)
[ 20.651] (EE) Server terminated with error (1). Closing log file.
----

Thank you for the support. I am still quite at a loss.

Best regards
mseidel

[erikdubois]

Check this post while I continue searching.

https://bbs.archlinux.org/viewtopic.php?id=251636

[erikdubois]

They talk about removing or adding amd drivers.

That is one option to go.

Removing I have done myself already and all my pcs are fine but I do not have AMD but Intel.
You are welcome to use my script.

https://github.com/erikdubois/arcolinux ... drivers.sh

then you reboot and see...

Afterwards you can always try adding the amdgpu or ati driver. One by one and reboot.

Mesa is our next stop.

[mseidel]

Hello,

i have removed all xf86-video drivers and reinstalled the xf86-video-amdgpu package. Since then my ArcoLinux system boots again. However, lightdm fails to load gkr-pam on a systemctl status call.

sudo pacman -Rs xf86-video-amdgpu
sudo pacman -Rs xf86-video-ati
sudo pacman -Rs xf86-video-fbdev
sudo pacman -Rs xf86-video-intel
sudo pacman -Rs xf86-video-nouveau
sudo pacman -Rs xf86-video-openchrome
sudo pacman -Rs xf86-video-vesa
sudo pacman -Rs xf86-video-vmware

sudo pacman -S xf86-video-amdgpu

Many, many thanks for the support so far!


Best regards
mseidel

[erikdubois]

Typed gkr-pam in pamac - no hits.
Was there a question in there or just a fact you stated.

[mseidel]

Hello,

So far, only one fact that I have observed.


Best regards
mseidel