Arch Linux

Gor Madatyan

Member

Registered: 2025-12-07

Posts: 3

error on reboot: nvidia-modeset

So, while configuring my nvidia drivers, I have done everything up to the most little details according to the official wiki, but I get this weird spam message at reboot/shutdown:
nvidia-modeset: ERROR: GPU:0: Idling display engine timed out

and a ton of it, it spams like for minute or two, then system normally reboots.
For context, both gpus work and are very performant, the problem is in shutdown,
Maybe my shutdown/reboot process is wrong?

here are my context:
Wayland (niri)
nvidia propraitary
Nvidia RTX 2060 mobile (I am on laptop)
Intel core i7 9th gen
latest standard packages from offical repos
Ly as my display manager

I reboot in a terminal emulator in my wayland compositor (just type reboot in alacritty)
Apparently it appears because I have D3Cold mode enabled (I am on Turing generation (RTX 2060), so I  had to pass some kernel parameters and set udev rules, also early load nvidia kernel modules)
If I change udev rules, or dont early load this nvidia modules, D3 mode is disabled, but all other things work

Here are the twaks I made to my setup:

in modprobe.d/nvidia-pm.conf
options nvidia NVreg_EnableGpuFirmware=0 NVreg_DynamicPowerManagement=0x02

in /etc/mkinitcpio.conf
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
FILES=(/etc/modprobe.d/nvidia-pm.conf)

in /etc/udev/rules.d/80-nvidia-pm.rules
# Enable runtime PM for NVIDIA VGA/3D controller devices on driver bind
ACTION=="bind", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x030000", TEST=="power/control", ATTR{power/control}="auto"
ACTION=="bind", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x030200", TEST=="power/control", ATTR{power/control}="auto"

# Disable runtime PM for NVIDIA VGA/3D controller devices on driver unbind
ACTION=="unbind", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x030000", TEST=="power/control", ATTR{power/control}="on"
ACTION=="unbind", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x030200", TEST=="power/control", ATTR{power/control}="on"

# Some Users Reported
# Enable runtime PM for NVIDIA VGA/3D controller devices on adding device
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x030000", TEST=="power/control", ATTR{power/control}="auto"
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x030200", TEST=="power/control", ATTR{power/control}="auto"

here are my logs that I got from journalctl -b -1:
http://0x0.st/KwoX.txt

Is it a bug form upstram, or am I doing something wrong?

These logs look this way https://imgur.com/a/t8kgPEb

Thanks in advance

Last edited by Gor Madatyan (2025-12-07 12:26:55)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,951

Re: error on reboot: nvidia-modeset

Please put program output in multiple [ code ] / [ /code ] blocks, see https://bbs.archlinux.org/help.php#bbcode .

pastebin.com is not popular here, see https://wiki.archlinux.org/title/List_o … n_services for alternatives .

Does nvidia-open have the same issue ?

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Gor Madatyan

Member

Registered: 2025-12-07

Posts: 3

Re: error on reboot: nvidia-modeset

Thanks for reply, I updated it, and sadly, no. Nvidia Open don’t have support for D3Cold mode on Turing series,

Last edited by Gor Madatyan (2025-12-07 12:13:10)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,081

Re: error on reboot: nvidia-modeset

If I change udev rules, or dont early load this nvidia modules, D3 mode is disabled, but all other things work

Have you confirmed D3 is actually entered?
Does it help to disable the https://wiki.archlinux.org/title/NVIDIA … P_firmware ?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Gor Madatyan

Member

Registered: 2025-12-07

Posts: 3

Re: error on reboot: nvidia-modeset

If I change udev rules, or dont early load this nvidia modules, D3 mode is disabled, but all other things work

Have you confirmed D3 is actually entered?
Does it help to disable the https://wiki.archlinux.org/title/NVIDIA … P_firmware ?

Yes, it helps indeed, anyway it’s soooo buggy, I am intended to change udev rules to disable and enable it by hand

In some cases it is stuck at D0 and don’t move to D3, reboot helps, but still, IG it happens because I send to many requests to gpu, and there is some sort of race condition, but I am not an expert, so don’t take my words too serious

Last edited by Gor Madatyan (2025-12-07 16:13:49)