Page 1 of 1
Nvidia GPU: Unable to change power state from D3cold to D0, device inaccessible
Posted: 2025-02-16 18:25
by saydash
Hi! I have an Acer laptop with an integrated Intel GPU and a dedicated Nvidia GeForce MX150 GPU. I use debian 12 with gnome and wayland. As per instructions on debian wiki, I installed the proprietary driver and signed it, but it does not load. And before you ask, no, the issue is not related to secure boot, as the same error messages occur when secure boot is turned off.
nvidia-smi:
Code: Select all
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
dmesg | grep nvidia:
Code: Select all
[ 4.664791] nvidia: loading out-of-tree module taints kernel.
[ 4.664806] nvidia: module license 'NVIDIA' taints kernel.
[ 4.884506] nvidia-nvlink: Nvlink Core is being initialized, major device number 236
[ 4.890854] nvidia 0000:02:00.0: Unable to change power state from D3cold to D0, device inaccessible
[ 4.891031] nvidia: probe of 0000:02:00.0 failed with error -1
[ 4.896117] nvidia-nvlink: Unregistered Nvlink Core, major device number 236
[ 4.986948] audit: type=1400 audit(1739727808.075:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=563 comm="apparmor_parser"
[ 4.986954] audit: type=1400 audit(1739727808.075:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=563 comm="apparmor_parser"
[ 5.564608] nvidia-nvlink: Nvlink Core is being initialized, major device number 236
[ 5.565488] nvidia: probe of 0000:02:00.0 failed with error -1
[ 5.565684] nvidia-nvlink: Unregistered Nvlink Core, major device number 236
[ 6.128540] nvidia-nvlink: Nvlink Core is being initialized, major device number 236
[ 6.129412] nvidia: probe of 0000:02:00.0 failed with error -1
[ 6.129594] nvidia-nvlink: Unregistered Nvlink Core, major device number 236
The issue seems to be related to power management, but I might be wrong. I tried everything, but could not solve it. Any help is appreciated.
Re: Nvidia driver problem
Posted: 2025-02-16 18:38
by Aki
Hello,
Are you dual booting with Windows or other operating systems ?
Re: Nvidia driver problem
Posted: 2025-02-16 19:01
by saydash
Yes, I am dual booting with Windows, but they are installed on two separate physical drives each having their own bootloaders. So, they are completely separate.
Re: Nvidia driver problem
Posted: 2025-02-16 19:07
by Aki
saydash wrote: 2025-02-16 19:01
Yes, I am dual booting with Windows, but they are installed on two separate physical drives each having their own bootloaders. So, they are completely separate.
Yes, but:
- you cannot hibernate windows and boot Debian
- you need to configure Windows disabling the “fast startup” at boot because with fast startup enabled, the machine does not completely shut down
Re: Nvidia driver problem
Posted: 2025-02-16 19:16
by kalle123
saydash wrote: 2025-02-16 19:01
Yes, I am dual booting with Windows, but they are installed on
two separate physical drives each having their own bootloaders. So, they are completely separate.
Very good! and when you power up the Acer laptop, it starts with the grub screen and this lets you decide, if you want to start Linux or WIN!?
Re: Nvidia driver problem
Posted: 2025-02-16 20:30
by saydash
I never use hibernation in Windows. I have configured the laptop so that it always boots into Windows by default. When I want to use debian, I reboot while I am in Windows, which actually closes everything, and then I choose debian via boot options.
Aki wrote: 2025-02-16 19:07
saydash wrote: 2025-02-16 19:01
Yes, I am dual booting with Windows, but they are installed on two separate physical drives each having their own bootloaders. So, they are completely separate.
Yes, but:
- you cannot hibernate windows and boot Debian
- you need to configure Windows disabling the “fast startup” at boot because with fast startup enabled, the machine does not completely shut down
Re: Nvidia driver problem
Posted: 2025-02-16 20:32
by saydash
No, as I mentioned above, I have configured the laptop so that it always boots into Windows by default. When I want to use debian, I reboot while I am in Windows, which actually closes everything, and then I choose debian via F12 boot options. Windows does not even appear in the grub menu. If I do not want to start Windows, when I power up the laptop, I again choose debian via F12. So, I do not see how Windows might affect debian in this case.
kalle123 wrote: 2025-02-16 19:16
saydash wrote: 2025-02-16 19:01
Yes, I am dual booting with Windows, but they are installed on
two separate physical drives each having their own bootloaders. So, they are completely separate.
Very good! and when you power up the Acer laptop, it starts with the grub screen and this lets you decide, if you want to start Linux or WIN!?
Re: Nvidia driver problem
Posted: 2025-02-16 20:41
by Aki
Hello,
Have you configured Windows to disable the “fast startup” ?
Please change the subject of the first post from "Nvidia driver problem" to "Nvidia GPU: Unable to change power state from D3cold to D0, device inaccessible" to make it more informative for other forum readers.
Re: Nvidia GPU: Unable to change power state from D3cold to D0, device inaccessible
Posted: 2025-02-16 21:12
by saydash
Yes, I just disabled fast startup and the problem still persists.
Aki wrote: 2025-02-16 20:41
Hello,
Have you configured Windows to disable the “fast startup” ?
Please change the subject of the first post from "Nvidia driver problem" to "Nvidia GPU: Unable to change power state from D3cold to D0, device inaccessible" to make it more informative for other forum readers.
Re: Nvidia GPU: Unable to change power state from D3cold to D0, device inaccessible
Posted: 2025-02-17 13:32
by saydash
Anyone?
Re: Nvidia GPU: Unable to change power state from D3cold to D0, device inaccessible
Posted: 2025-02-17 17:45
by Aki
Hello,
saydash wrote: 2025-02-16 21:12
Yes, I just disabled fast startup and the problem still persists.
Aki wrote: 2025-02-16 20:41
Hello,
Have you configured Windows to disable the “fast startup” ?
Please change the subject of the first post from "Nvidia driver problem" to "Nvidia GPU: Unable to change power state from D3cold to D0, device inaccessible" to make it more informative for other forum readers.
It may be a firmware issue; you might try the solution posted in this previous discussion:
Hope this helps.
Re: Nvidia GPU: Unable to change power state from D3cold to D0, device inaccessible
Posted: 2025-02-19 22:59
by saydash
Hi,
Not only your suggestion did not fix the problem, it also disabled the touchpad. At this point, I don't think this issue has any solution... Doesn't anyone else have any other ideas?
Aki wrote: 2025-02-17 17:45
Hello,
saydash wrote: 2025-02-16 21:12
Yes, I just disabled fast startup and the problem still persists.
Aki wrote: 2025-02-16 20:41
Hello,
Have you configured Windows to disable the “fast startup” ?
Please change the subject of the first post from "Nvidia driver problem" to "Nvidia GPU: Unable to change power state from D3cold to D0, device inaccessible" to make it more informative for other forum readers.
It may be a firmware issue; you might try the solution posted in this previous discussion:
Hope this helps.
Re: Nvidia GPU: Unable to change power state from D3cold to D0, device inaccessible
Posted: 2025-02-21 05:10
by Aki
Is your computer designed to remove the battery to force a cold-reboot ?
Re: Nvidia GPU: Unable to change power state from D3cold to D0, device inaccessible
Posted: 2025-02-21 08:45
by saydash
I am not sure what you mean by that. There is a battery reset pinhole at the back. Is that what you mean?
Re: Nvidia GPU: Unable to change power state from D3cold to D0, device inaccessible
Posted: 2025-02-21 17:25
by Aki
Hello,
saydash wrote: 2025-02-21 08:45
I am not sure what you mean by that. There is a battery reset pinhole at the back. Is that what you mean?
My guess is that your internal Nvidia card is in a low-power state from which the kernel is unable to wake it up.
The first thing to understand is why it is in this state:
- The most common explanation is that it was put into this state after Windows was partially shut down or suspended to ram or hibernated to disk. However, you have reported that this is not the case, although it is suspected that an interaction with Windows could indeed be the case.
- The other explanation is that the computer's BIOS has put it in this state for some reason. In this case, you should be able to configure the BIOS to check that it is not disabled at BIOS level.
In case 1), you could double check that you have forced a hardware shutdown after the software shutdown. The hardware shutdown (which should reset the computer's peripherals to their reset state) can be done by disconnecting the computer from the main power supply and, for notebooks, disconnecting the battery for a sufficient period of time after disconnecting the computer from the main power supply .
Modern notebooks are not always designed to allow normal users to disconnect the battery, so I asked you.
According to the Acer website [1], Acer seems to have taken this situation into account with this "battery pinhole reset" (I was not aware of such a solution):
This procedure will temporarily disconnect and then reconnect the internal battery.
In any case, it's an invasive measure and I don't know about side effects (i.e. on Windows).
So the decision and risk assessment is up to you.
Hope this helps.
--
[1]
Acer Internal Battery Reset