Arch Linux

ja1a

Member

Registered: 2021-01-07

Posts: 6

[Solved] System hangs on boot after "Initialized nvidia-drm"

My system hangs on boot after this:

Oct 13 11:06:43 archlinux kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 0

It started after a recent system upgrade. I think nvidia was updated at that time.

dmesg is full of:

[ 2067.341757] pcieport 0000:00:1c.6:   device [8086:a296] error status/mask=00000001/00002000
[ 2067.341982] pcieport 0000:00:1c.6: AER: Correctable error message received from 0000:00:1c.6
[ 2067.341985] pcieport 0000:00:1c.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)

Not sure if that is relevant.

I tried loading nvidia modules using early KMS as suggested here but then it still hung after "Initialized nvidia-drm", it just seemed to happen earlier.

I reinstalled the system, and then it worked for a day or so but now I have the same error again. Not clear what changed or if it is intermittent.

My current command line is

loglevel=7 splash pcie_aspm=off nvidia-drm.modeset=1

I added pcie_aspm=off to see if that fixed the errors in dmesg but it did not seem to do any difference. I added nvidia-drm.modeset=1 to try to fix the hanging but it did not seem to change anything either.

If I remove pcie_aspm=off and nvidia-drm.modeset=1 it still hangs.

I have an NVIDIA GeForce GTX 1070 Ti GPU.

Sometimes when I'm chrooted using an USB I get a core dump seemingly at random:

[   556.865838] systemd-coredump[1319]: Process 540 (systemd-journal) of user 0 dumped core

I didn't save the full stacktrace but I can probably get another one if it is relevant.

journalctl.log
dmesg
Xorg.log
Xorg.log.old
pacman.log
paru -Q output

Does anyone recognize this / know what to do about it?

Last edited by ja1a (2024-10-13 11:52:56)

ja1a

Member

Registered: 2021-01-07

Posts: 6

Re: [Solved] System hangs on boot after "Initialized nvidia-drm"

It seems this was a lightdm/greeter related issue. I wasn't using lightdm or any greeter before reinstalling when I had the same issue but at least it works now.

This is what I did to fix it:

# ssh into the computer
pacman -Rsn ly
pacman -S lightdm-gtk-greeter
systemctl enable lightdm.service
systemctl start lightdm.service

This started the greeter and I could log in (without ssh)