Unable to install dahdi-dkms

S

sebinho

New Member
Joined
Feb 17, 2022
Messages
17
Reaction score
3
Credits
107
Hi, I'm running Debian 10 and I'm unable to install dahdi-dkms on various kernels including Debian kernel packages with their corresponding headers. For example, booting into 5.10.0-0.bpo.9-amd64 with linux-headers-5.10.0-0.bpo.9-amd64 installed, I do the following:

Code: 
sudo apt remove --purge dahdi-dkms
sudo apt install dahdi-dkms

Errors result:

Code: 
......Building for 5.10.0-0.bpo.9-amd64 5.15.12s1avl2-lowlatency
Building initial module for 5.10.0-0.bpo.9-amd64
Error! Bad return status for module build on kernel: 5.10.0-0.bpo.9-amd64 (x86_64)
Consult /var/lib/dkms/dahdi/DEB_VERSION/build/make.log for more information.
dpkg: error processing package dahdi-dkms (--configure): installed dahdi-dkms package post-installation
script subprocess returned error exit status 10
Errors were encountered while processing:
dahdi-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

/var/lib/dkms/dahdi/DEB_VERSION/build/make.log has the following:

DKMS make.log for dahdi-DEB_VERSION for kernel 5.10.0-0.bpo.9-amd64 (x86_64) Thu 17 Feb 17:10:48 -03 2022 make -C /lib/modules/5.10.0-0.bpo.9-amd64/build SUBDIRS=/var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi DAHDI_INCLUDE=/var/lib/dkms/dahdi/DEB_VERSION/build/include DAHDI_MODULES_EXTRA="dahdi_dummy.o dahdi_echocan_oslec.o " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m make[1]: Entering directory '/usr/src/linux-headers-5.10.0-0.bpo.9-amd64' /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:225: =============== ERROR ============== /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:226: 'SUBDIRS' was removed in Linux 5.3 /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:227: Use 'M=' or 'KBUILD_EXTMOD=' instead /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:228: ==================================== /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:229: *** .. Stop. make[1]: *** [/usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:185: __sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-0.bpo.9-amd64' make: *** [Makefile:74: modules] Error 2 make -C /lib/modules/5.10.0-0.bpo.9-amd64/build SUBDIRS=/var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi DAHDI_INCLUDE=/var/lib/dkms/dahdi/DEB_VERSION/build/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m make[1]: Entering directory '/usr/src/linux-headers-5.10.0-0.bpo.9-amd64' /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:225: =============== ERROR ============== /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:226: 'SUBDIRS' was removed in Linux 5.3 /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:227: Use 'M=' or 'KBUILD_EXTMOD=' instead /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:228: ==================================== /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:229: *** .. Stop. make[1]: *** [/usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:185: __sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-0.bpo.9-amd64' make: *** [Makefile:74: modules] Error 2 make -C drivers/dahdi/firmware firmware-loaders make[1]: Entering directory '/var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi/firmware' Attempting to download dahdi-fwload-vpmadt032-1.25.0.tar.gz --2022-02-17 17:10:48-- [URL]http://downloads.digium.com/pub/telephony/firmware/releases/dahdi-fwload-vpmadt032-1.25.0.tar.gz[/URL] Resolving [URL='https://downloads.digium.com/']downloads.digium.com[/URL] ( [URL='https://downloads.digium.com/']downloads.digium.com[/URL])... [URL='https://170.249.154.172/']170.249.154.172[/URL] Connecting to [URL='https://downloads.digium.com/']downloads.digium.com[/URL] ( [URL='https://downloads.digium.com/']downloads.digium.com[/URL])|170.249.154.172|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 149360 (146K) [application/x-gzip] Saving to: ‘dahdi-fwload-vpmadt032-1.25.0.tar.gz’ 0K .......... .......... .......... .......... .......... 34% 156K 1s 50K .......... .......... .......... .......... .......... 68% 312K 0s 100K .......... .......... .......... .......... ..... 100% 9.98M=0.5s 2022-02-17 17:10:49 (300 KB/s) - ‘dahdi-fwload-vpmadt032-1.25.0.tar.gz’ saved [149360/149360] make[1]: Leaving directory '/var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi/firmware' make -C /lib/modules/5.10.0-0.bpo.9-amd64/build SUBDIRS=/var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi DAHDI_INCLUDE=/var/lib/dkms/dahdi/DEB_VERSION/build/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m make[1]: Entering directory '/usr/src/linux-headers-5.10.0-0.bpo.9-amd64' /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:225: =============== ERROR ============== /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:226: 'SUBDIRS' was removed in Linux 5.3 /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:227: Use 'M=' or 'KBUILD_EXTMOD=' instead /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:228: ==================================== /usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:229: *** .. Stop. make[1]: *** [/usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:185: __sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-0.bpo.9-amd64' make: *** [Makefile:74: modules] Error 2[/CODE] This is happening in all kernels that I boot into. Hope someone can help
 
Last edited:


The problem might have something to do with the first line avove:
Code: 
Building for 5.10.0-0.bpo.9-amd64 5.15.12s1avl2-lowlatency
Why would it be trying to build 5.15.12s1avl2-lowlatency as well as 5.10.0-0.bpo.9-amd64 when the machine was booted into 5.10.0-0.bpo.9-amd64 and with the 5.10.0-0.bpo.9-amd64 headers are installed?
 
The problem looks to me is this line
make -C /lib/modules/5.10.0-0.bpo.9-amd64/build SUBDIRS=/var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi
There are no SUBDIRS in the Kernel after version 5.3 - need to modify that to read
make -C /lib/modules/5.10.0-0.bpo.9-amd64/build M=/var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi
 
Thanks very much. I had tried that, but didn't update the right makefile. I had updated /usr/src/modules/dahdi/Makefile and not /usr/src/dahdi-DEB_VERSION/Makefile

Now new errors are logged in /var/lib/dkms/dahdi/DEB_VERSION/build/make.log

Code: 
make[1]: Entering directory '/usr/src/linux-headers-5.10.0-0.bpo.9-amd64'
scripts/Makefile.lib:12: 'hostprogs-y' is deprecated. Please use 'hostprogs' instead
  CC [M]  /var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi/oct612x/oct612x-user.o
In file included from /var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi/oct612x/oct612x-user.c:27:
/var/lib/dkms/dahdi/DEB_VERSION/build/include/dahdi/kernel.h:71:10: fatal error: linux/pci-aspm.h: No such file or directory
 #include <linux/pci-aspm.h>
          ^~~~~~~~~~~~~~~~~~
compilation terminated.
make[4]: *** [/usr/src/linux-headers-5.10.0-0.bpo.9-common/scripts/Makefile.build:285: /var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi/oct612x/oct612x-user.o] Error 1
make[3]: *** [/usr/src/linux-headers-5.10.0-0.bpo.9-common/scripts/Makefile.build:502: /var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi/oct612x] Error 2
make[2]: *** [/usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:1846: /var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi] Error 2
make[1]: *** [/usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:185: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-0.bpo.9-amd64'
make: *** [Makefile:74: modules] Error 2
make -C drivers/dahdi/firmware firmware-loaders
make[1]: Entering directory '/var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi/firmware'
Attempting to download dahdi-fwload-vpmadt032-1.25.0.tar.gz
--2022-02-19 14:30:03--  http://downloads.digium.com/pub/telephony/firmware/releases/dahdi-fwload-vpmadt032-1.25.0.tar.gz
Resolving downloads.digium.com (downloads.digium.com)... 170.249.154.172
Connecting to downloads.digium.com (downloads.digium.com)|170.249.154.172|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 149360 (146K) [application/x-gzip]
Saving to: ‘dahdi-fwload-vpmadt032-1.25.0.tar.gz’

     0K .......... .......... .......... .......... .......... 34%  146K 1s
    50K .......... .......... .......... .......... .......... 68%  289K 0s
   100K .......... .......... .......... .......... .....     100%  282K=0.7s

2022-02-19 14:30:04 (215 KB/s) - ‘dahdi-fwload-vpmadt032-1.25.0.tar.gz’ saved [149360/149360]

make[1]: Leaving directory '/var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi/firmware'
make -C /lib/modules/5.10.0-0.bpo.9-amd64/build M=/var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi DAHDI_INCLUDE=/var/lib/dkms/dahdi/DEB_VERSION/build/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m
make[1]: Entering directory '/usr/src/linux-headers-5.10.0-0.bpo.9-amd64'
scripts/Makefile.lib:12: 'hostprogs-y' is deprecated. Please use 'hostprogs' instead
  CC [M]  /var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi/oct612x/oct612x-user.o
In file included from /var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi/oct612x/oct612x-user.c:27:
/var/lib/dkms/dahdi/DEB_VERSION/build/include/dahdi/kernel.h:71:10: fatal error: linux/pci-aspm.h: No such file or directory
 #include <linux/pci-aspm.h>
          ^~~~~~~~~~~~~~~~~~
compilation terminated.
make[4]: *** [/usr/src/linux-headers-5.10.0-0.bpo.9-common/scripts/Makefile.build:285: /var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi/oct612x/oct612x-user.o] Error 1
make[3]: *** [/usr/src/linux-headers-5.10.0-0.bpo.9-common/scripts/Makefile.build:502: /var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi/oct612x] Error 2
make[2]: *** [/usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:1846: /var/lib/dkms/dahdi/DEB_VERSION/build/drivers/dahdi] Error 2
make[1]: *** [/usr/src/linux-headers-5.10.0-0.bpo.9-common/Makefile:185: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-0.bpo.9-amd64'
make: *** [Makefile:74: modules] Error 2

So far I haven't found a solution to this.
 
You have to file a bug report to the debian dahdi-dkms packager, assuming you are using the version from apt in debian 10, and installing it on the standard debian 10 kernel, otherwise it's not their problem since they are only packaging for the kernel in the debian 10 repo. Also of course assuming you are running debian 10, and not some derived distro like LMDE, at which point it's not the debian maintainer's problem, it's an LMDE problem.
 
Last edited:
Thanks h2-1. It's a Debian 10 variant AV Linux. I'm giving up. I'm going to install a new sytem on a new HD and gradually move my projects over.
 
This is a reason not to use derived distros unless they offer good solid support, you can't expect Debian maintainers to know what could have gone wrong on a derived distro, and usually the derived distro people don't know enough about the innards of the system to actually help. This is why I don't use derived distros, the support becomes almost impossible because there are too many levels. Unless the people who make the derived distro are quite good at what they do and know how to not ever interfere with the core package pool, which some are good at, some are not.

With debian, it's all just packages installed via apt anyway, install once, upgrade forever, avoid core dependencies on anything not from core debian package pool, if you need stable setups that you can rely on, use debian stable, and it will keep working at least until 1 year after next stable comes out.

People think dkms kernel modules are magic or something, they aren't, the module has to build on the kernel, and if it fails, ti fails, dkms doesn't do anything to help with that situation, it doesn't make it not fail, it still fails if the kernel and module don't match, and the module build fails. If you need a specific module and it works on debian stable, it will keep working on debian stable at least until next debian stable, and in most cases, unless the module authors fail to update the module for kernel changes, the module will then build on next stable, and you start the cycle again.

But you can never use anything but the debian packaged kernel and module in this situation, otherwise there are zero guarantees the module will build on the non debian kernel. This is a frequent issue for kernels like liquuorix, where people try to run it on stable frozen pool distros 'to get a newer kernel', not realizing that this will promptly break their dkms modules, and then they report the issue and it's always the same, they don't understand that dkms cannot make incompatible modules and kernels work together. There are also zero guarantees that a 3rd party module will keep building on newer kernels, the only time you can count on modules basically mostly working is when the modules are part of the main kernel tree, not addons.
 
Last edited:
In my case I had to upgrade to a particular 5.15 kernel in order to get some rather expensive audio hardware to work on Linux. I could find no patches to patch a standard Debian kernel, only the full kernel. Other older kernels from this particular repo did not offer full functionality on the device. Apparently the changes in the repo's 5.15 kernel have been up-streamed to the very latest Linux kernels but these are not available on Debian 10. And my last attempts to get my Debian machine to work were on a standard Debian kernel as I mentioned in my first post.
 
Last edited:
h2-1 said:
This is a reason not to use derived distros unless they offer good solid support,
Click to expand...

Yup. There's a reason I don't stray far from the major branch - as a general rule. I stick with Ubuntu (technically Lubuntu, which is Ubuntu) as a general rule. No, no I am not going to use a distro with a few folks doing it as a hobby and I can't imagine doing so on anything even remotely important.

I'll play with those distros in a VM. That's fun. They don't make it to bare metal, however.
 
Re Debian 10, add backports repo, but checking, they only have 5.10 kernel. Basically if you have expensive hardware with no standard driver/module support, once you get something that works, stop there, and don't change anything except for security updates, and when time comes for next debian, confirm via tests or research FIRST that it works with your hardware still, then upgrade. If the driver has been added to the main kernel tree, it should be fine as of next debian stable however. And whatever you do, do NOT update your kernel, or use dkms, or anything like that, keep those frozen completely.
 
sebinho said:
var/lib/dkms/dahdi/DEB_VERSION/build/include/dahdi/kernel.h:71:10: fatal error: linux/pci-aspm.h: No such file or directory #include <linux/pci-aspm.h>
Click to expand...
Also the above error ( pci-aspm.h ) has been removed from the kernel tree and no longer exists - that file was removed since kernel 5.4, but I believe 5.3 still had it, but not for sure on that
 
You must log in or register to reply here.

Members online

Total: 431 (members: 2, guests: 429)

Latest posts

Top