gpu unlock troubleshooting: start from the error, not the guide

gpu unlock troubleshooting works the same way on every page below: it starts from the log line you actually saw, then the cause, then the fix. If you are not sure which one you have, read the first column here.

What your gpu unlock log says

  • Five shapes, five destinations. The code is on the right if you already know it.
  • No gpu_unlock line at all

    What it means
    The module never ran. Install-stage problem.
  • Failed to load firmware / error -2

    What it means
    ENOENT: the module is in the image, the payload is not.
  • probe ... failed with error -16

    What it means
    EBUSY: nvidia claimed the device first. Load timing.
  • GPU is lost / error -110

    What it means
    ETIMEDOUT: the card stopped answering. Usually a warm boot.
  • gpu_unlock: unlocked, benchmarks unchanged

    What it means
    The unlock worked and your workload does not use the unlocked lane.

[official README] for the error codes; the log shapes come from the reports linked on each page.

Every row above is a different gpu unlock troubleshooting case, and the last column is the page that settles it. Before you go down any of them, confirm the card is supported at all: the gpu unlock compatibility table answers that in a minute, and an unsupported card is skipped at boot with its own log entry.

Stage 1: the image never received gpu unlock

Nothing here is a hardware problem. Either the module is missing from the initramfs, or it is in there without its firmware.

Stage 2: gpu unlock ran but lost the race

The module is in the image and executed. What failed is who got the device first, or whether the card answered at all.

Stage 3: gpu unlock worked and nothing got faster

This one is not a failure to fix. It is a workload that does not use the lane that was unlocked, or a card already at its power limit.

When none of these gpu unlock cases match

The guides above cover the failures that have dedicated pages. Other codes seen in project reports, including -19 and -22, have no separate guide here and belong in the project’s issue tracker, where the maintainer can see your full log. This site has no support channel and does not take bug reports.

github.com/Zagitta/gpu-unlock/issues

Checked VERSION 2.0.0commit 1fc6d62