You are not logged in.
Hi, I have a Tuxedo Pulse 15 Gen2. My root is encrypted and I use systemd-boot with dracut and Secure Boot with a TPM2 key to automatically unlock it when booting. When I tried updating linux and linux-headers from 5.19.7arch1-1 to 5.19.8arch1-1, the boot looked normal until gdm is supposed to start. The encrypted container unlocks and I don't see any errors. However instead of my login screen, I only see a black screen with a blinking white cursor. I downgraded and today I tried with 5.19.9.arch1-1 but I got the same result. Does anyone know what changed between those versions and how I can get gdm to start again?
Thank you very much!
Cheers pentamassiv
Last edited by pentamassiv (2022-09-21 13:46:18)
Offline
This can often be just a race with gdm trying to start before the graphics device is ready, can you switch VT with Ctrl+Alt+F2 and the like?
If you can try setting up early KMS https://wiki.archlinux.org/title/Kernel … _KMS_start
Offline
Okay, thank you for your help
In the meantime there was an update for mutter and gnome-shell and I installed those without any problems. Everything but linux and linux-headers is currently updated.
I followed the dracut guide and enabled the amdgpu module in early KMS. Now when I update linux and linux-headers, I can see the login screen but when I enter my password, it just asks me again for my password. I checked that my keyboard layout is correct and my password is correct. If I enter a wrong password, it still tells me it is wrong so I am sure the password is correct. I tried CTRL+ALT+F3 and then login but its the same issue. I enter my username and type my password. It then asks me for my password again without displaying any errors.
I also noticed that there are some red "FAILED" notifications when I boot the new kernel. They all seem to be related to the network. I think it said for example that reflector failed.
Offline
That's a different situation, after having had such a breaking log in, are you able to switch to a VT and post
sudo journalctl -b
Offline
Okay, I figured it out when I looked at the logs.
Turns out I forgot to set up the dracut hook to run after kernel updates. I installed dracut-hook-uefi from the AUR and now that should not happen in the future.
Thank you very much for your help V1del
Offline