You are not logged in.
Hey everyone,
I started having an issue with GDM after recently updating my system. When I boot up, I'm greeted with a black screen instead of the gdm login screen with some very minor graphics corruption at the top of the screen.
If I Ctrl-Alt-F2 into a terminal, then go back and Ctrl-Alt-F1, GDM loads normally, I can login without issue.
I've tried deleting my ~/.config directory which fixes the problem for the first boot. But this behavior repeats itself after the next reboot without me making any changes to my environment.
Is anyone else experiencing this issue?
My Hardware Specs are:
Ryzen 1700
Vega 64
64 GB DDR4 @ 2933MHz
Offline
I have the exact same issue on both my Arch machines - One is a laptop with a Ryzen 4500u processor with built-in graphics, the other a desktop with an i5 and Nvidia GTX970 graphics. One wayland, one Xorg.
At first I thought I'd been hit by the "insufficient entropy" problem mentioned in the GDM wiki page but it's definitely a separate thing.
Offline
Usually an issue with KMS not being ready before the graphics server tries to start, enable early KMS for your kernel driver, i.e. amdgpu for the amd systems, and nvidia and nvidia_drm for the prop nvidia driver.
Offline
Yeah I already tried early KMS, and it seems to not have solved the issue sadly.
Offline
If you did not forget to rerun mkinitcpio after making the relevant adjustment, post a complete
sudo journalctl -b
on reproduction of the issue.
Offline
forget to rerun mkinitcpio
Bingo, thanks. Been a while since I've had to do any real maintenance with arch!
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
Do I have to run mkinitcpio every time there is a nvidia driver update? Adding nvidia & nvidia_drm in modules also solved the issue for me. Is this an issue with gdm?
Last edited by Computer Email (2021-04-06 03:03:19)
Offline
You can make pacman do that for you, https://wiki.archlinux.org/index.php/NVIDIA#Pacman_hook
Afawu it's a race condition and likely introduced by a systemd update.
Offline
That's what the pacman hook on the nvidia page is for: https://wiki.archlinux.org/index.php/NVIDIA#Pacman_hook and you only need to do that if there's an nvidia update without an accompanying kernel update which will be seldom. This is as far as I know an issue with systemd and the kernel, as there appears to be no proper interface (... or it's not used at least) with which the kernel can communicate to systemd when it's safe to continue starting the graphical target unit.
Offline
Thank you very much to both of you.
Last edited by Computer Email (2021-04-05 17:15:38)
Offline