Arch Linux

wurtles

Member

From: USA

Registered: 2023-02-02

Posts: 3

Boot hangs at Starting systemd-udevd version 252.5-1-arch, Nvidia card

So I've gone through a fresh install on my desktop with an Nvidia graphics card, but upon booting in, the boot sequence seems to get stuck at "Starting systemd-udevd version 252.5-1-arch" instead of reaching a GUI login screen.

At first I thought the system might have been defaulting to the integrated Intel graphics card, chrooted in and installed that but it didn't make a difference.
I've also checked that the Nvidia drivers are there (they are) and ran 'pacman -Syu', no difference.

This post seemed relevant, but it seems like they had a concrete error.

The last event for me was a warning:

Feb 01 22:08:27 arch-pc kernel: ACPI Warning: \_SB.WMID._WED: Return type mismatch - found Package, expected Integer/String/Buffer (20220331/nspredef-254)
Feb 01 22:08:27 arch-pc kernel: hp_wmi: Unknown response received 4

Which according to this forum post is harmless.

Here's the journal
I let it sit for 5 minutes or so, you could jump to where I hit the power button by ctrl-f "Feb 01 22:14:59 arch-pc systemd-logind[434]: Power key pressed short."

Anything I could do to clarify or give more info, let me know!

Last edited by wurtles (2023-02-02 14:37:04)

---

Foi tudo ilusão passageira
Que a brisa primeira levou

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,088

Re: Boot hangs at Starting systemd-udevd version 252.5-1-arch, Nvidia card

There's no mention of any GPU driver whatsoever in that log. How are you booting so you get to the journal? live disk/nomodeset or so? Can you boot to a terminal with the systemd.unit=multi-user.target cmdline maybe in combination with nomodeset? Can you get a journal from there and the output of

lspci -k
pacman -Qs nvidia

wurtles

Member

From: USA

Registered: 2023-02-02

Posts: 3

Re: Boot hangs at Starting systemd-udevd version 252.5-1-arch, Nvidia card

I'm booting through a live usb, then mounting and chrooting into the installation.

There's no mention of any GPU driver in that log

Do you mean there's no mention of a driver error? I figured that this meant a GPU driver's being loaded:

Feb 01 22:08:15 arch-pc kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  525.85.05  Sat Jan 14 00:40:03 UTC 2023
Feb 01 22:08:15 arch-pc kernel: [drm] [nvidia-drm] [GPU ID 0x00000200] Loading driver
Feb 01 22:08:15 arch-pc kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:02:00.0 on minor 1

Passing nomodeset to the installation let me boot to a terminal, but first I had to reboot to the live usb, mount and chroot in to install dhcpcd on the installation, then boot into the installation and run dhcpcd on the system as I couldn't connect to anything.
Here's the output:
For lspci
For pacman
For journal

I'm not sure what you mean by systemd.unit=multi-user.target cmdline, should I boot in differently or is this info good?

For anyone that might wonder how to pass nomodeset to the kernel:
At the GRUB menu, hover over the installation and press e, then add "nomodeset" to the string titled linux before "quiet" (it should look like "linux [...] nomodeset quiet"), then boot in (F10). Note that this will not save between boots

---

Foi tudo ilusão passageira
Que a brisa primeira levou

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,088

Re: Boot hangs at Starting systemd-udevd version 252.5-1-arch, Nvidia card

Then it might've been a weird network bug on my side? There was nothing when I looked when I made my post. Driver is fine but you have a i915 GPU loading while not attached to anything at all. Best would be to disable that in the UEFI/BIOS or blacklisting it via the /bin/true method to be sure, create a file on your root partition /etc/modprobe.d/disableiGPU.conf

install i915 /usr/bin/true

what we also see is

Feb 01 21:47:01 arch-pc systemd[1]: Started User Login Management.
Feb 01 21:47:01 arch-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 01 21:47:01 arch-pc systemd[1]: Reached target Multi-User System.
Feb 01 21:47:01 arch-pc systemd[1]: Reached target Graphical Interface.
Feb 01 21:47:01 arch-pc systemd[1]: Startup finished in 9.695s (firmware) + 1.915s (loader) + 2.556s (kernel) + 2.780s (userspace) = 16.948s.
Feb 01 21:47:01 arch-pc kernel: audit: type=1130 audit(1675306021.422:33): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 01 21:47:01 arch-pc kernel: audit: type=1130 audit(1675306021.422:34): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 01 21:47:01 arch-pc kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  525.85.05  Sat Jan 14 00:40:03 UTC 2023
Feb 01 21:47:01 arch-pc kernel: [drm] [nvidia-drm] [GPU ID 0x00000200] Loading driver
Feb 01 21:47:01 arch-pc kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:02:00.0 on minor 1
Feb 01 21:47:49 arch-pc systemd-logind[434]: Power key pressed short.

so the nvidia-drm module loads only after the display target has reached which can be mitigated by applying both, the kernel parameter and the early loading in mkinitcpio.conf that is mentioned in: https://wiki.archlinux.org/title/NVIDIA … de_setting

Last edited by V1del (2023-02-02 16:09:01)

wurtles

Member

From: USA

Registered: 2023-02-02

Posts: 3

Re: Boot hangs at Starting systemd-udevd version 252.5-1-arch, Nvidia card

OK, I've gone and applied the kernel parameter and the early loading:
in /proc/cmdline, appended

nvidia_drm.modeset=1

and in /etc/mkinitcpio.conf

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

then ran

grub-mkconfig -o /boot/grub/grub.cfg

and setup a pacman hook, as in that wiki page.

Nonetheless, got stuck at the same place (but now with higher grub resolution!)
It seems like those steps are in place, as in the journal:

Feb 02 12:57:46 arch-pc kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  525.85.05  Sat Jan 14 00:40:03 UTC 2023
Feb 02 12:57:46 arch-pc kernel: [drm] [nvidia-drm] [GPU ID 0x00000200] Loading driver
Feb 02 12:57:47 arch-pc systemd-modules-load[249]: Inserted module 'nvidia_uvm'
Feb 02 12:57:47 arch-pc kernel: nvidia-uvm: Loaded the UVM driver, major device number 510.
Feb 02 12:57:47 arch-pc systemd[1]: Finished Load Kernel Modules.
[...]
Feb 02 12:57:47 arch-pc systemd[1]: Reached target Multi-User System.
Feb 02 12:57:47 arch-pc systemd[1]: Reached target Graphical Interface.
Feb 02 12:57:47 arch-pc systemd[1]: Startup finished in 11.397s (firmware) + 8.303s (loader) + 2.569s (kernel) + 3.990s (userspace) = 26.260s.
Feb 02 12:57:47 arch-pc kernel: audit: type=1130 audit(1675360667.635:32): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 02 12:57:47 arch-pc kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:02:00.0 on minor 1
Feb 02 12:58:15 arch-pc systemd-logind[439]: Power key pressed short.

I imagine the issue here is that nvidia-drm is initialized too late? How might I cause it to initialize earlier?

---

Foi tudo ilusão passageira
Que a brisa primeira levou

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,088

Re: Boot hangs at Starting systemd-udevd version 252.5-1-arch, Nvidia card

You did not run mkinitcpio -P to actually generate the image with the new config. There are also still references to an useless i915 which is something you should be blacklisting (... run mkinitcpio after creating the blacklist file if you opt for that, so it is also honored in the initramfs) or disabling in your BIOS/UEFI, if you do not do this, the intel card will grab the framebuffer and nvidia will have nothing to initialize on, this is technically a kernel regression but if you have no use for the intel card it will block output from the nvidia card for a terminal

If you did those things and it doesn't work, post a new journal and your mkinitcpio.conf verbatim

Last edited by V1del (2023-02-02 23:33:28)