MHWD (Hardware Configuration) fails to install DKMS-modules

Hi guys,

I have a problem with MHWD after reinstalling my GPU-driver which results in it failing to install the DKMS-modules it needs. I think it's similar to the problem in this thread:

I can also fix the driver problem itself by manually installing the necessary modules with

sudo dkms install --no-depmod -m nvidia -v 470.74 -k 5.14.11-zen1-1-zen

however I would prefer to fix MHWD itself so that I dont have to reinstall all DKMS-modules myself each time I change something.
By looking in the error log I think something is wrong with the PATH in MHWD because it cant find basic programs like cc and make (which I can use both normally if I use the command myself both in bash and fish).

I hope somebody can help me, unfortunately I dont have a snapshot from before the driver installation as I'm new to Garuda and configured the tool badly (max 10 snapshots and no timed snapshots) and tried reinstalling the driver many times, resulting in me only having snapshots after the first driver installation.

MHWD-Output:

:: Running post-transaction hooks...

( 1/14) Reloading system manager configuration...

( 2/14) Arming ConditionNeedsUpdate...

( 3/14) Install DKMS modules

==> dkms install --no-depmod -m bbswitch -v 0.8 -k 5.10.72-1-lts

Error! Bad return status for module build on kernel: 5.10.72-1-lts (x86_64)

Consult /var/lib/dkms/bbswitch/0.8/build/make.log for more information.

==> Warning, `dkms install --no-depmod -m bbswitch -v 0.8 -k 5.10.72-1-lts' returned 10

==> dkms install --no-depmod -m acpi_call -v 1.2.1 -k 5.10.72-1-lts

Error! Bad return status for module build on kernel: 5.10.72-1-lts (x86_64)

Consult /var/lib/dkms/acpi_call/1.2.1/build/make.log for more information.

==> Warning, `dkms install --no-depmod -m acpi_call -v 1.2.1 -k 5.10.72-1-lts' returned 10

==> dkms install --no-depmod -m acpi_call -v 1.2.1 -k 5.14.11-zen1-1-zen

Error! Bad return status for module build on kernel: 5.14.11-zen1-1-zen (x86_64)

Consult /var/lib/dkms/acpi_call/1.2.1/build/make.log for more information.

==> Warning, `dkms install --no-depmod -m acpi_call -v 1.2.1 -k 5.14.11-zen1-1-zen' returned 10

==> dkms install --no-depmod -m bbswitch -v 0.8 -k 5.14.11-zen1-1-zen

Error! Bad return status for module build on kernel: 5.14.11-zen1-1-zen (x86_64)

Consult /var/lib/dkms/bbswitch/0.8/build/make.log for more information.

==> Warning, `dkms install --no-depmod -m bbswitch -v 0.8 -k 5.14.11-zen1-1-zen' returned 10

==> dkms install --no-depmod -m nvidia -v 470.74 -k 5.10.72-1-lts

Error! Bad return status for module build on kernel: 5.10.72-1-lts (x86_64)

Consult /var/lib/dkms/nvidia/470.74/build/make.log for more information.

==> Warning, `dkms install --no-depmod -m nvidia -v 470.74 -k 5.10.72-1-lts' returned 10

==> dkms install --no-depmod -m nvidia -v 470.74 -k 5.14.11-zen1-1-zen

Error! Bad return status for module build on kernel: 5.14.11-zen1-1-zen (x86_64)

Consult /var/lib/dkms/nvidia/470.74/build/make.log for more information.

==> Warning, `dkms install --no-depmod -m nvidia -v 470.74 -k 5.14.11-zen1-1-zen' returned 10

==> depmod 5.10.72-1-lts

==> depmod 5.14.11-zen1-1-zen

Log from /var/lib/dkms/nvidia/470.74/build/make.log:

DKMS make.log for nvidia-470.74 for kernel 5.14.11-zen1-1-zen (x86_64)
Thu Oct 14 00:01:57 CEST 2021
make[1]: Entering directory '/usr/lib/modules/5.14.11-zen1-1-zen/build'
make[1]: cc: No such file or directory
make[1]: make: No such file or directory
make[1]: *** [Makefile:1855: /var/lib/dkms/nvidia/470.74/build] Error 127
make[1]: Leaving directory '/usr/lib/modules/5.14.11-zen1-1-zen/build'
make: *** [Makefile:80: modules] Error 2
2 Likes

Hmm. This comes up from time-to-time and I don't think there was a solid answer...

As it is, once you've installed nvidia-dkms then it will recompile whenever the kernel is updated (which is the whole point of DKMS), so if this isn't happening it might indicate why MHWD is having an issue.

1 Like

It's not only the Nvidia-module of DKMS, acpi_call and bbswitch (which are both needed by video-optimus-manager) also needed manual installation with the same problem. As I wrote it works normally and as intened when I execute the commands MHWD tries to execute myself.
I also just tested to install a new kernel and got the same errors when it tried to install the DKMS-modules, so I guess its a problem with Garuda Settings Manager (and therefore Manjaro Settings Manager) in general. Does anyone know of any config files for the Garuda Settings Manager I could look into?

The problem is not breaking my system or anything, I can always run the commands myself when I change a kernel or driver, I just hate the thought of having a "broken" system which cant do something its supposed to do.

1 Like