Arch Linux

greembow

Member

Registered: 2022-02-23

Posts: 35

[SOLVED] Nvidia GPU randomly gets disabled

Hi there, I have a Microsoft Surface Book 2 15" with a GTX 1060. I'm using the nvidia driver with bumblebee and primus to handle the gpu.

Sometimes, when the laptop goes to sleep, the gpu will be disabled, and it will no longer show up in nvidia-smi. I also can no longer use optirun or primusrun to use the gpu. I'm not really sure where to go from here, so some help would be much appreciated.

EDIT: nvidia-smi error

Unable to determine the device handle for GPU0000:02:00.0: Unknown Error

Last edited by greembow (2023-02-17 18:43:54)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,707

Re: [SOLVED] Nvidia GPU randomly gets disabled

Do you also have a Microsoft Windows on that Microsoft Surfacebook?
=> 3rd link below.

---

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

greembow

Member

Registered: 2022-02-23

Posts: 35

Re: [SOLVED] Nvidia GPU randomly gets disabled

I do not. I only have Arch on the laptop. Fastboot in bios is disabled.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,707

Re: [SOLVED] Nvidia GPU randomly gets disabled

BIOS fastboot is irrelevant in this context.

Please post your complete system journal for a boot where this happened:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

for the current one.

---

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

greembow

Member

Registered: 2022-02-23

Posts: 35

Re: [SOLVED] Nvidia GPU randomly gets disabled

http://0x0.st/Hr7D.txt

Okay, so I wrote a script to notify me if nvidia-smi errored. Turns out, it happens as soon as I detach the keyboard. This makes sense because the GPU is actually in the keyboard, but it's not coming back online when I reattach the keyboard.

greembow

Member

Registered: 2022-02-23

Posts: 35

Re: [SOLVED] Nvidia GPU randomly gets disabled

Did more research and this appears to be a common behavior, not a problem. I don't really mind as I usually don't detach the screen. Marking as solved.