DKMS error - returned 10 - after installing new kernel

luigir-it · 20 December 2020 14:54

Hello

System:
  Kernel: 5.8.18-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 
  root=UUID=73af93b2-0824-465a-9ed3-a4f540eb9da9 rw quiet apparmor=1 
  security=apparmor udev.log_priority=3 
  Desktop: KDE Plasma 5.20.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 
  dm: SDDM Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX B350-F GAMING v: Rev X.0x 
  serial: <filter> UEFI: American Megatrends v: 5603 date: 07/28/2020 
CPU:
  Info: 6-Core model: AMD Ryzen 5 1600 bits: 64 type: MT MCP arch: Zen 
  family: 17 (23) model-id: 1 stepping: 1 microcode: 8001138 
  L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 86437 
  Speed: 3007 MHz min/max: 1550/3600 MHz boost: disabled Core speeds (MHz): 
  1: 3007 2: 1719 3: 1616 4: 1465 5: 1772 6: 2470 7: 1674 8: 1456 9: 2748 
  10: 1506 11: 2219 12: 2917 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: 
  disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: ZOTAC driver: nvidia 
  v: 455.45.01 alternate: nouveau,nvidia_drm bus ID: 08:00.0 
  chip ID: 10de:1b81 
  Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: nvidia 
  display ID: :0 screens: 1 
  Screen-1: 0 s-res: 1920x1080 s-dpi: 92 s-size: 528x297mm (20.8x11.7") 
  s-diag: 606mm (23.9") 
  Monitor-1: DP-1 res: 1920x1080 hz: 60 dpi: 93 size: 525x297mm (20.7x11.7") 
  diag: 603mm (23.7") 
  OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 455.45.01 
  direct render: Yes 
Audio:
  Device-1: NVIDIA GP104 High Definition Audio vendor: ZOTAC 
  driver: snd_hda_intel v: kernel bus ID: 08:00.1 chip ID: 10de:10f0 
  Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 0a:00.3 chip ID: 1022:1457 
  Device-3: Logitech Webcam C170 type: USB driver: snd-usb-audio,uvcvideo 
  bus ID: 1-6:4 chip ID: 046d:082b 
  Sound Server: ALSA v: k5.8.18-1-MANJARO 
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: 5.6.0-k 
  port: e000 bus ID: 03:00.0 chip ID: 8086:1539 
  IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 1.14 TiB used: 647.02 GiB (55.6%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda vendor: Seagate model: ST1000LM014-1EJ164 size: 931.51 GiB 
  block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  rotation: 5400 rpm serial: <filter> rev: SM14 scheme: MBR 
  ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
  block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
  rev: 2B6Q scheme: GPT 
Partition:
  ID-1: / raw size: 70.53 GiB size: 69.17 GiB (98.07%) used: 43.48 GiB (62.9%) 
  fs: ext4 dev: /dev/sdb7 
  ID-2: /home raw size: 50.70 GiB size: 49.78 GiB (98.19%) 
  used: 34.94 GiB (70.2%) fs: ext4 dev: /dev/sdb5 
Swap:
  Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
  ID-1: swap-1 type: file size: 8.00 GiB used: 337.2 MiB (4.1%) priority: -2 
  file: /swapfile 
Sensors:
  System Temperatures: cpu: 46.2 C mobo: N/A gpu: nvidia temp: 42 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 30% 
Info:
  Processes: 362 Uptime: 9d 8h 45m Memory: 15.64 GiB used: 10.09 GiB (64.6%) 
  Init: systemd v: 246 Compilers: gcc: 10.2.0 alt: 5/9 clang: 11.0.0 Packages: 
  pacman: 1662 lib: 419 flatpak: 0 Shell: Bash v: 5.0.18 running in: konsole 
  inxi: 3.1.08

Few days ago, someone in this forum make me notice that the kernel 5.8 is EOL, so I decided to switch to 5.9.
While upgrading, i found different errors during dkms modules installation, as you can see below

The following packages will be installed:
linux59
linux59-virtualbox-host-modules
linux59-nvidia-455xx
linux59-headers

Starting
resolving dependencies...
looking for conflicting packages...
Packages (4) linux59-5.9.11-3  linux59-headers-5.9.11-3  linux59-nvidia-455xx-455.45.01-4  linux59-virtualbox-host-modules-6.1.16-9
Total Download Size:   118.06 MiB
Total Installed Size:  220.35 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
downloading linux59-5.9.11-3-x86_64.pkg.tar.zst...
downloading linux59-headers-5.9.11-3-x86_64.pkg.tar.zst...
downloading linux59-virtualbox-host-modules-6.1.16-9-x86_64.pkg.tar.zst...
downloading linux59-nvidia-455xx-455.45.01-4-x86_64.pkg.tar.zst...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing linux59...
Optional dependencies for linux59
    crda: to set the correct wireless channels of your country [installed]
    installing linux59-virtualbox-host-modules...
    ===> You must load vboxdrv module before starting VirtualBox:
    ===> # modprobe vboxdrv
    installing linux59-nvidia-455xx...
    In order to use nvidia module, reboot the system.
    installing linux59-headers...
    :: Running post-transaction hooks...
    (1/6) Arming ConditionNeedsUpdate...
    (2/6) Updating module dependencies...
    (3/6) Install DKMS modules





    ==> dkms install --no-depmod -m v4l2loopback-dc -v 1.6 -k 5.9.11-3-MANJARO
    Error! Bad return status for module build on kernel: 5.9.11-3-MANJARO (x86_64)
    Consult /var/lib/dkms/v4l2loopback-dc/1.6/build/make.log for more information.
    ==> Warning, `dkms install --no-depmod -m v4l2loopback-dc -v 1.6 -k 5.9.11-3-MANJARO' returned 10

    ==> dkms install --no-depmod -m vboxhost -v 6.1.16_OSE -k 5.9.11-3-MANJARO
    Error! Bad return status for module build on kernel: 5.9.11-3-MANJARO (x86_64)
    Consult /var/lib/dkms/vboxhost/6.1.16_OSE/build/make.log for more information.
    ==> Warning, `dkms install --no-depmod -m vboxhost -v 6.1.16_OSE -k 5.9.11-3-MANJARO' returned 10

    ==> dkms install --no-depmod -m zenpower -v 0.1.12 -k 5.9.11-3-MANJARO
    Error! Bad return status for module build on kernel: 5.9.11-3-MANJARO (x86_64)
    Consult /var/lib/dkms/zenpower/0.1.12/build/make.log for more information.
    ==> Warning, `dkms install --no-depmod -m zenpower -v 0.1.12 -k 5.9.11-3-MANJARO' returned 10

    ==> dkms install --no-depmod -m rtl8723bu -v 245 -k 5.9.11-3-MANJARO
    Error! Bad return status for module build on kernel: 5.9.11-3-MANJARO (x86_64)
    Consult /var/lib/dkms/rtl8723bu/245/build/make.log for more information.
    ==> Warning, `dkms install --no-depmod -m rtl8723bu -v 245 -k 5.9.11-3-MANJARO' returned 10

    ==> dkms install --no-depmod -m i2c-piix4-aura -v 5.6.11 -k 5.9.11-3-MANJARO
    Error! Bad return status for module build on kernel: 5.9.11-3-MANJARO (x86_64)
    Consult /var/lib/dkms/i2c-piix4-aura/5.6.11/build/make.log for more information.
    ==> Warning, `dkms install --no-depmod -m i2c-piix4-aura -v 5.6.11 -k 5.9.11-3-MANJARO' returned 10

    ==> dkms install --no-depmod -m i2c-ch341 -v 20190628 -k 5.9.11-3-MANJARO
    Error! Bad return status for module build on kernel: 5.9.11-3-MANJARO (x86_64)
    Consult /var/lib/dkms/i2c-ch341/20190628/build/make.log for more information.
    ==> Warning, `dkms install --no-depmod -m i2c-ch341 -v 20190628 -k 5.9.11-3-MANJARO' returned 10
    




    ==> depmod 5.9.11-3-MANJARO
    (4/6) Updating linux initcpios...
    ==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: 'default'
    -> -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64.img
    ==> Starting build: 5.9.11-3-MANJARO
    -> Running build hook: [base]
    -> Running build hook: [udev]
    -> Running build hook: [autodetect]
    -> Running build hook: [modconf]
    -> Running build hook: [block]
    -> Running build hook: [keyboard]
    -> Running build hook: [keymap]
    -> Running build hook: [filesystems]
    ==> Generating module dependencies
    ==> Creating gzip-compressed initcpio image: /boot/initramfs-5.9-x86_64.img
    ==> Image generation successful
    ==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: 'fallback'
    -> -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64-fallback.img -S autodetect
    ==> Starting build: 5.9.11-3-MANJARO
    -> Running build hook: [base]
    -> Running build hook: [udev]
    -> Running build hook: [modconf]
    -> Running build hook: [block]
    -> Running build hook: [keyboard]
    -> Running build hook: [keymap]
    -> Running build hook: [filesystems]
    ==> Generating module dependencies
    ==> Creating gzip-compressed initcpio image: /boot/initramfs-5.9-x86_64-fallback.img
    ==> Image generation successful
    (5/6) Updating Kernel initcpios for Nvidia-DRM...
    ==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
    -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
    ==> Starting build: 5.4.80-2-MANJARO
    -> Running build hook: [base]
    -> Running build hook: [udev]
    -> Running build hook: [autodetect]
    -> Running build hook: [modconf]
    -> Running build hook: [block]
    -> Running build hook: [keyboard]
    -> Running build hook: [keymap]
    -> Running build hook: [filesystems]
    ==> Generating module dependencies
    ==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64.img
    ==> Image generation successful
    ==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'fallback'
    -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect
    ==> Starting build: 5.4.80-2-MANJARO
    -> Running build hook: [base]
    -> Running build hook: [udev]
    -> Running build hook: [modconf]
    -> Running build hook: [block]
    -> Running build hook: [keyboard]
    -> Running build hook: [keymap]
    -> Running build hook: [filesystems]
    ==> Generating module dependencies
    ==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64-fallback.img
    ==> Image generation successful
    ==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'default'
      -> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64.img
      ==> Starting build: 5.8.18-1-MANJARO
      -> Running build hook: [base]
      -> Running build hook: [udev]
      -> Running build hook: [autodetect]
      -> Running build hook: [modconf]
      -> Running build hook: [block]
      -> Running build hook: [keyboard]
      -> Running build hook: [keymap]
      -> Running build hook: [filesystems]
      ==> Generating module dependencies
      ==> Creating gzip-compressed initcpio image: /boot/initramfs-5.8-x86_64.img
      ==> Image generation successful
      ==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'fallback'
      -> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64-fallback.img -S autodetect
      ==> Starting build: 5.8.18-1-MANJARO
      -> Running build hook: [base]
      -> Running build hook: [udev]
      -> Running build hook: [modconf]
      -> Running build hook: [block]
      -> Running build hook: [keyboard]
      -> Running build hook: [keymap]
      -> Running build hook: [filesystems]
      ==> Generating module dependencies
      ==> Creating gzip-compressed initcpio image: /boot/initramfs-5.8-x86_64-fallback.img
      ==> Image generation successful
      ==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: 'default'
      -> -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64.img
      ==> Starting build: 5.9.11-3-MANJARO
      -> Running build hook: [base]
      -> Running build hook: [udev]
      -> Running build hook: [autodetect]
      -> Running build hook: [modconf]
      -> Running build hook: [block]
      -> Running build hook: [keyboard]
      -> Running build hook: [keymap]
      -> Running build hook: [filesystems]
      ==> Generating module dependencies
      ==> Creating gzip-compressed initcpio image: /boot/initramfs-5.9-x86_64.img
      ==> Image generation successful
      ==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: 'fallback'
      -> -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64-fallback.img -S autodetect
      ==> Starting build: 5.9.11-3-MANJARO
      -> Running build hook: [base]
      -> Running build hook: [udev]
      -> Running build hook: [modconf]
      -> Running build hook: [block]
      -> Running build hook: [keyboard]
      -> Running build hook: [keymap]
      -> Running build hook: [filesystems]
      ==> Generating module dependencies
      ==> Creating gzip-compressed initcpio image: /boot/initramfs-5.9-x86_64-fallback.img
      ==> Image generation successful
      (6/6) Updating Grub-Bootmenu
      Generating grub configuration file ...
      Found theme: /usr/share/grub/themes/manjaro/theme.txt
      Found linux image: /boot/vmlinuz-5.9-x86_64
      Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.9-x86_64.img
      Found initrd fallback image: /boot/initramfs-5.9-x86_64-fallback.img
      Found linux image: /boot/vmlinuz-5.8-x86_64
      Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.8-x86_64.img
      Found initrd fallback image: /boot/initramfs-5.8-x86_64-fallback.img
      Found linux image: /boot/vmlinuz-5.4-x86_64
      Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.4-x86_64.img
      Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
      Found Windows Boot Manager on /dev/sdb2@/efi/Microsoft/Boot/bootmgfw.efi
      Adding boot menu entry for UEFI Firmware Settings ...
      Found memtest86+ image: /boot/memtest86+/memtest.bin
      done


      Done

Booting the system up, I noticed that sensors and other stuff didn’t work.
Searching through the wiki and randomly online, I wasn’t able to understand where’s the problem at.
So i tried to reinstall the kernel, but with the same results.
I tried to install the 5.10 experimental kernel also, and the log showed the same errors during dkms installation.
I also tried this command: dkms autoinstall (specifing the 5.9 kernel)

Error! Could not locate dkms.conf file.

File: /var/lib/dkms/rtl8723bu/240/source/dkms.conf does not exist.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...(bad exit status: 2)
make -j12 KERNELRELEASE=5.9.11-3-MANJARO -C /usr/lib/modules/5.9.11-3-MANJARO/build SUBDIRS=/var/lib/dkms/i2c-ch341/20190628/build modules...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.9.11-3-MANJARO (x86_64)
Consult /var/lib/dkms/i2c-ch341/20190628/build/make.log for more information.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j12 KERNELRELEASE=5.9.11-3-MANJARO...
cleaning build area...
Kernel cleanup unnecessary for this kernel.  Skipping...

DKMS: build completed.

i2c-piix4.ko.xz:
Running module version sanity check.
 - Original module
   - Found /usr/lib/modules/5.9.11-3-MANJARO/kernel/drivers/i2c/busses/i2c-piix4.ko.xz
   - Storing in /var/lib/dkms/i2c-piix4-aura/original_module/5.9.11-3-MANJARO/x86_64/
   - Archiving for uninstallation purposes
 - Installation
   - Installing to /usr/lib/modules/5.9.11-3-MANJARO/kernel/drivers/i2c/busses/

depmod.....

DKMS: install completed

But same errors…
So I’m asking you guys, pls pardon my English and where’s the problem at?
Thank you!

TriMoon · 20 December 2020 15:20

I think your output already points you to the answer, see the lines that say:

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

luigir-it · 20 December 2020 15:32

Yes, I read it but I wasn’t able to understand the problem and forgot to add it here:

[luigi@Luigi-pc ~]$ cat /var/lib/dkms/v4l2loopback-dc/1.6/build/make.log
DKMS make.log for v4l2loopback-dc-1.6 for kernel 5.10.0-1-MANJARO (x86_64)
Sun Dec 20 15:14:19 CET 2020
make: pwd: No such file or directory
make -C /lib/modules/5.10.0-1-MANJARO/build M= modules
make: make: No such file or directory
make: *** [Makefile:8: all] Error 127
[luigi@Luigi-pc ~]$ cat /var/lib/dkms/vboxhost/6.1.16_OSE/build/make.log
DKMS make.log for vboxhost-6.1.16_OSE for kernel 5.10.0-1-MANJARO (x86_64)
Sun Dec 20 15:14:18 CET 2020
make: Entering directory '/usr/lib/modules/5.10.0-1-MANJARO/build'
make: uname: No such file or directory
make: gcc: No such file or directory

  ERROR: Kernel configuration is invalid.
         include/generated/autoconf.h or include/config/auto.conf are missing.
         Run 'make oldconfig && make prepare' on kernel src to fix it.

make: *** [Makefile:720: include/config/auto.conf] Error 1
make: Leaving directory '/usr/lib/modules/5.10.0-1-MANJARO/build'
[luigi@Luigi-pc ~]$ cat /var/lib/dkms/zenpower/0.1.12/build/make.log
DKMS make.log for zenpower-0.1.12 for kernel 5.10.0-1-MANJARO (x86_64)
Sun Dec 20 15:14:20 CET 2020
make: uname: No such file or directory
make: make: No such file or directory
make: *** [Makefile:27: modules] Error 127
[luigi@Luigi-pc ~]$ cat /var/lib/dkms/rtl8723bu/245/build/make.log
DKMS make.log for rtl8723bu-245 for kernel 5.10.0-1-MANJARO (x86_64)
Sun Dec 20 15:14:19 CET 2020
make: Entering directory '/usr/lib/modules/5.10.0-1-MANJARO/build'
make: uname: No such file or directory
make: gcc: No such file or directory

  ERROR: Kernel configuration is invalid.
         include/generated/autoconf.h or include/config/auto.conf are missing.
         Run 'make oldconfig && make prepare' on kernel src to fix it.

make: *** [Makefile:720: include/config/auto.conf] Error 1
make: Leaving directory '/usr/lib/modules/5.10.0-1-MANJARO/build'
[luigi@Luigi-pc ~]$ /var/lib/dkms/i2c-piix4-aura/5.6.11/build/make.log
bash: /var/lib/dkms/i2c-piix4-aura/5.6.11/build/make.log: Permission denied
[luigi@Luigi-pc ~]$ cat /var/lib/dkms/i2c-piix4-aura/5.6.11/build/make.log
DKMS make.log for i2c-piix4-aura-5.6.11 for kernel 5.10.0-1-MANJARO (x86_64)
Sun Dec 20 15:14:20 CET 2020
make: pwd: No such file or directory
make -C /usr/lib/modules/5.10.0-1-MANJARO/build M= modules
make: make: No such file or directory
make: *** [Makefile:15: default] Error 127
[luigi@Luigi-pc ~]$ cat /var/lib/dkms/i2c-ch341/20190628/build/make.log
DKMS make.log for i2c-ch341-20190628 for kernel 5.10.0-1-MANJARO (x86_64)
Sun Dec 20 15:14:17 CET 2020
make: Entering directory '/usr/lib/modules/5.10.0-1-MANJARO/build'
make: uname: No such file or directory
make: gcc: No such file or directory
  SYNC    include/config/auto.conf.cmd
make[1]: uname: No such file or directory
make[1]: make: No such file or directory
make[1]: *** [Makefile:537: scripts_basic] Error 127
make: *** [Makefile:712: include/config/auto.conf.cmd] Error 2
make: *** [include/config/auto.conf.cmd] Deleting file 'include/generated/autoconf.h'
make: Leaving directory '/usr/lib/modules/5.10.0-1-MANJARO/build'

The recurrent error seems to be “no such file or directory”

luigir-it · 20 December 2020 20:06

Reinstalling the dkms modules solved the problem. I don’t know if this is the proper way to do it but it does work.
I noticed that also some services didn’t work anymore, like a service for increase nvidia tdp at startup. I solved with systemctl reenable “units”.

AkhIL · 20 September 2021 03:32

I have same the issue with Manjaro Settings Manager and xpadneo module. It seems the PATH environment variable not well configured during the module rebuild.

/var/lib/dkms/hid-xpadneo/0.9.r85.g67585b3/build/make.log

DKMS make.log for hid-xpadneo-0.9.r85.g67585b3 for kernel 5.14.2-1-MANJARO (x86_64)
Mon Sep 20 10:18:07 +07 2021
make: Entering directory '/usr/lib/modules/5.14.2-1-MANJARO/build'
make: uname: No such file or directory
make: gcc: No such file or directory
make: make: No such file or directory
make: *** [Makefile:1851: /var/lib/dkms/hid-xpadneo/0.9.r85.g67585b3/build/src] Error 127
make: Leaving directory '/usr/lib/modules/5.14.2-1-MANJARO/build'

AkhIL · 20 September 2021 04:52

I’m trying to install kernel form the Manjaro settings manager.
During installation, this error occurs:

/var/log/pacman.log

[2021-09-20T10:18:07+0700] [ALPM] running '70-dkms-install.hook'...                                                                                                                                                  
[2021-09-20T10:18:07+0700] [ALPM-SCRIPTLET] ==> dkms install --no-depmod -m hid-xpadneo -v 0.9.r85.g67585b3 -k 5.14.2-1-MANJARO
[2021-09-20T10:18:07+0700] [ALPM-SCRIPTLET] Error! Bad return status for module build on kernel: 5.14.2-1-MANJARO (x86_64)
[2021-09-20T10:18:07+0700] [ALPM-SCRIPTLET] Consult /var/lib/dkms/hid-xpadneo/0.9.r85.g67585b3/build/make.log for more information.
[2021-09-20T10:18:07+0700] [ALPM-SCRIPTLET] ==> Warning, `dkms install --no-depmod -m hid-xpadneo -v 0.9.r85.g67585b3 -k 5.14.2-1-MANJARO' returned 10

/var/lib/dkms/hid-xpadneo/0.9.r85.g67585b3/build/make.log

DKMS make.log for hid-xpadneo-0.9.r85.g67585b3 for kernel 5.14.2-1-MANJARO (x86_64)
Mon Sep 20 10:18:07 +07 2021
make: Entering directory '/usr/lib/modules/5.14.2-1-MANJARO/build'
make: uname: No such file or directory
make: gcc: No such file or directory
make: make: No such file or directory
make: *** [Makefile:1851: /var/lib/dkms/hid-xpadneo/0.9.r85.g67585b3/build/src] Error 127
make: Leaving directory '/usr/lib/modules/5.14.2-1-MANJARO/build'

Seems like the PATH is not well configured during dkms install.
Similar issue was reported earlier DKMS error - returned 10 - after installing new kernel - #3 by luigir-it.

Console command yay -S linux514 linux514-headers works as expected, dkms successfully builds and installs the module.

Fabby · 21 September 2021 21:35

As you seem to have found a solution using yay, could you cut and paste that in a new answer so @luigir-it can test that out and we can make your workaround into a Solution ???

AkhIL · 22 September 2021 03:25

This workaround does not solve a bug somewhere around the Manjaro settings manajer. My point is to let know about a problem in Manjaro settings manager.

AkhIL · 22 September 2021 03:49

There is bug report.