Nvidia can't change power state from D3cold to D0 (config space inaccessible)

Support Graphics & Display
1

Hi everyone,

When I reboot Manjaro sometimes (not always) I get this message: nvidia can’t change power state from D3cold to D0 (config space inaccessible)

I have to power off and on a couple of times before I’m able to start the system.

I have a Dell XPS15 9560 with Nvidia GTX 1050 and Intel 630 HD Graphics and I have “video-hybrid-intel-nvidia-450xx-prime” driver.

What should I do?
Thanks for taking the time!

1 Like
2

Hello,

This seems to have been discussed on Nvidia forum


But i still can’t make much of it.
Also seem to be mentioned here, since 2019
https://patchwork.kernel.org/project/dri-devel/patch/20191017121901.13699-1-kherbst@redhat.com/

I wonder if with the upcoming to stable of the 455xx driver this issue will not happen…

3

Thanks Bogdan! I saw that too but couldn’t figure out if there’s a solution or not… it seems it’s not…

4

Sadly i can’t confirm either way or another, but hopefully someone else using a hybrid intel-nvidia GPUs laptop will pass by with some ideas.
Did all this came out while fixing the overheating, or it still does that too?

5

No, that was separate from the power thing… it happened right after the installation but I ignored it because I couldn’t find a solution and the power off and start again worked…

Since I’m at the troubleshooting day :slight_smile: do you have any idea what should I do so my mouse connected to an USB port be visible at the login screen? Now I have to unplug and plug the mouse USB port to be visible to the system.

Many thanks for taking the time!

6

That sounds like a TLP thing. Install tlpui package and disable the power management on that port, or the power saving.

7

I tried that… I changed USB_AUTOSUSPEND from ON to OFF but still can’t see the mouse at startup…

8

Is it a USB3 port? Change to a USB2 one.

9

Hello @theodore,

Yesterday night I installed kernel 5.10 and when checking for errors with sudo journalctl -p 3 -xb ,
I have these two errors

snd_hda_intel 0000:01:00.1: can't change power state from D3cold to D0 (config space inaccessible)
snd_hda_intel 0000:01:00.1: can't change power state from D3hot to D0 (config space inaccessible)

so I googled and stumbled upon this thread.

Do you experience anything out of the ordinary with the error ?
Did you resolve your error and if so, how ??

Thanks…

10

I’m also having this error when trying to use primusrun to require a program to use my NVIDIA GPU. I’ve been using optimus-manager but I’ve disabled it for now before enabling bumblebeed. Anyone have any other ideas? I’m at a loss here.

The key issue seems to be the cannot change power state portion. But what’s strange is that optimus-manager seems to have no problem switching the card on and off. Maybe the issue is switching the GPU while in an X session? Is there something I need to change in my xinit to allow the GPU to be switched on without logging out first?

From dmesg:

bbswitch: version 0.8
bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
bbswitch: detected an Optimus _DSM function
bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
nvidia-nvlink: Unregistered the Nvlink Core, major device number 511
bbswitch: disabling discrete graphics
bbswitch: enabling discrete graphics
pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible)
nvidia-nvlink: Nvlink Core is being initialized, major device number 511
nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=none
NVRM: loading NVIDIA UNIX x86_64 Kernel Module  460.39  Thu Jan 21 21:54:06 UTC 2021
NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

From journalctl -u bumblebeed

Mar 15 08:41:43 kratos bumblebeed[2910]: /usr/bin/bumblebeed 3.2.1-2017-02-27-Format:%h$ started
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (EE) NVIDIA(GPU-0):     check your system's kernel log for additional error
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (EE) NVIDIA(GPU-0):     messages and refer to Chapter 8: Common Problems in the
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (EE) NVIDIA(GPU-0):     README for additional information.
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device!
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (EE) NVIDIA(0): Failing initialization of X screen
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (EE) Screen(s) found, but none have a usable configuration.
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (EE)
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (EE) no screens found(EE)
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (EE)
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional information.
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (EE)
Mar 15 08:42:05 kratos bumblebeed[2910]: [XORG] (EE) Server terminated with error (1). Closing log file.
Mar 15 08:42:05 kratos bumblebeed[2910]: X did not start properly