The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →In the EndeavourOS/NVIDIA case described by developer hopsayer, DKMS marked nvidia/565.57.01 as broken because its module-source directory or its source link was missing. The confusing part was that a separate find: warning named a missing kernel directory, /usr/lib/modules/6.12.3-arch1-1/. DKMS’s source check concerned /var/lib/dkms/nvidia/565.57.01/source—a different path. Hopsayer reports that a change to print the checked source path was merged upstream, making the error more actionable.
What “Manual intervention is required!” means in DKMS
DKMS documents a module/version as broken when its source directory is missing or when the symbolic link named source that should point to that directory is absent. DKMS takes no further action on that module/version combination while it is in this state.
As an Amazon Associate I earn from qualifying purchases.
That message does not, by itself, identify why the source went missing or prescribe one repair that works for every cause. It tells you the DKMS entry cannot find the source it needs; you still need to identify which path is absent and whether the module version is still needed.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Why the kernel-directory warning can be misleading
In hopsayer’s example, after a kernel update on EndeavourOS, the status included nvidia/565.57.01: broken. A nearby find: warning named /usr/lib/modules/6.12.3-arch1-1/, which is a kernel-module directory. The missing location relevant to DKMS’s broken-source check was instead /var/lib/dkms/nvidia/565.57.01/source.
#1 Best Overall
These paths refer to different things. A warning about a missing kernel directory does not establish that it is the cause of the missing DKMS source entry. In particular, removing or recreating the kernel directory is not a demonstrated repair for a missing source directory or link under /var/lib/dkms.
How to decide what to do
- Identify the exact broken entry. Read the module name and version shown by DKMS status—for example,
nvidia/565.57.01—rather than treating every DKMS entry as affected. - Check the source path for that entry. The relevant location follows the module and version under
/var/lib/dkms; in the example, it was/var/lib/dkms/nvidia/565.57.01/source. Distinguish an absent source directory from an absentsourcesymlink. - If only the source link is missing, consider DKMS’s documented
addaction. The manual describes this as a possible remedy for that specific condition. It does not establishaddas a universal fix for every broken status. - If the version is still needed, restore its source. Hopsayer’s proposed diagnostic hint recommends reinstalling the package that provides the source. Confirm which package supplies it for your distribution and module before acting.
- If the version is no longer needed, treat it as stale only after confirming that. The proposed hint also distinguishes an unneeded version, whose stale directory can be removed, from one whose source is still required. Do not delete all of
/var/lib/dkmsor remove every broken entry as a blanket cleanup step.
What the reported upstream change improved
Hopsayer reports that issue #606 described the vague error and pull request #607 changed DKMS diagnostics to print the specific source path being checked at four call sites: module_is_broken_and_die, do_status, run_match and autoinstall. The reported patch also updated ten test blocks and added EndeavourOS to the test script’s distribution case. Its central usability improvement was to show the path behind the error instead of leaving users to infer it.
Rank #2
The account says the path change and a separate two-line repair hint were kept in separate commits, so maintainers could omit the hint without losing the diagnostic improvement. Hopsayer reports that PR #607 was merged into main. That merge status and the exact merged diff are reported by the author; they are not independently established here. No DKMS release number is established, so do not assume a particular installed release includes the change.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What the reported tests do—and do not—show
Hopsayer says the test script finished with *** All tests successful :) on EndeavourOS using kernel 7.2.7-zen1-1-zen. The account notes that this required addressing distribution recognition, expectations around /lib/modules versus /usr/lib/modules, the test installation using the system DKMS binary, and existing state under /var/lib/dkms.
Rank #3
The author also reports a Fedora 44 CI-container failure: an unrelated pahole version-mismatch warning caused an exact-output comparison in an earlier test to fail. These are the author’s reported results, not independent test findings. They describe testing of the change; they do not show that every broken DKMS entry has the same cause or repair.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
