DAHDI installing problem

Hey guy’s.

You are awsome, i was stuck with this problém until i found this Topic.

after installing Dahdi i wasen’t able to start it i was getting this error.

Failed to start dahdi.service: Unit dahdi.service failed to load: No such file or directory.

I checked the /etc/init.d/ folder if the service file exist as Fmk_ca said and it dind’t.

So i changed the version of Dahdi to a previous one dahdi-linux-complete-2.10.2-rc1+2.10.2-rc1.tar.gz as Sruffell said that the last one “make config” is broken then it worked.

Thanks.

root@$HOSTNAME:/usr/src/dahdi-linux-complete-2.8.0+2.8.0# make all
make -C linux all
make[1]: Entering directory ‘/usr/src/dahdi-linux-complete-2.8.0+2.8.0/linux’
make -C drivers/dahdi/firmware firmware-loaders
make[2]: Entering directory ‘/usr/src/dahdi-linux-complete-2.8.0+2.8.0/linux/drivers/dahdi/firmware’
make[2]: Leaving directory ‘/usr/src/dahdi-linux-complete-2.8.0+2.8.0/linux/drivers/dahdi/firmware’
You do not appear to have the sources for the 3.16.0-4-amd64 kernel installed.

I have seemingly the same problem david already solved - or knows how to solve.
How do I find and compile a compatible DAHDI version for:

root@$HOSTNAME:/usr/src/dahdi-linux-complete-2.8.0+2.8.0# uname -a
Linux $HOSTNAME 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux

???
I would not like to use an older kernel, just for DAHDI - because updates are always important.
I already tried different DAHDI-Versions, all result in this error…

I’m about to install Asterisk with FreePBX following this doc http://wiki.freepbx.org/display/FOP/Installing+FreePBX+13+on+Debian+8.1#InstallingFreePBX13onDebian8.1-CompileandinstallDAHDI.
We definitely need physical PSTN support…

Install the -devel package for the kernel version it mentions, or boot the kernel for which you do have the devel package.

I’m a complete noob for that.

apt-get install kernel-3.16.0-4-amd64-devel

?
How do I find the appropriate package name to install for this specific kernel? Is this a package normally installed by default - like “build-essentials” - which is from the debian ISO images?
Using google brings up this Debian -- Error - but that doesn’t look like devel (developer?) packages
so - “apt-get install linux-image-3.16.0-4-amd64” ?

Append -devel to the kernel package name that is booted.

It is not a normal pakckage, and people often have several kernels installed but don’t boot from the most recent, so you may need an older version.

Note this is a Linux FAQ. See for example: http://unix.stackexchange.com/questions/110682/yum-installs-kernel-devel-different-from-my-kernel-version

Now trying to find something like your Howto for Debian, not Feodora. Internet said it’s rather helpful not to install yum on debian.

ran after apt-get update:

root@$HOSTNAME:/usr/src# apt-cache search kernel-devel-3.16.0-4-amd64
root@$HOSTNAME:/usr/src#

so - kernel-devel packages for the currently running kernel (therefore booted) version - found with uname -a seems not to exist.

In the debian forums theres a similar post from a user trying to install software which requires devel-packages - Install kernel-devel - Debian User Forums
there it’s advised to install “module-assistant” and run “m-a prepare”. That’s a kernel developer toolkit as far as I see.
That’s seems to be in no way associated with the sources make wants to have when trying to compile dahdi.

After executing m-a prepare

this seems to be a partially successfull build. I’ll try to install and look if it works in our testing.
Thanks for the useful help.

This appears to still be a problem. Are there any plans to fix this?

Hello, (dahdi 2.11.1 working fine now)

i’ve same problem with dhadi 2.11.1 and kernel-3.10.0-693.el7.x86_64

when i installed kernel-devel module that was 3.10.0-693.5.2.el7.x86_64 (version with 5.2.el7.x86_64)

i’ve tried to update the machine kernel but the very easy way i’ve found to update the kernel-devel module rather than kernel of machine…etc… etc…

the simple command found is :

$ sudo yum install “kernel-devel-uname-r == $(uname -r)”

for details page link is: https://unix.stackexchange.com/questions/110682/yum-installs-kernel-devel-different-from-my-kernel-version

if you are still interested to update the kernel any ways…
then the link : https://git.centos.org/summary/rpms!kernel

1 Like

Make sure “secure boot” is disabled on the boot options, i tested too many things in this post, but only when i disable secure boot it worked out, hope it helps you.

[root@localhost ~]# cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)
Asterisk 13.18.2
dahdi-linux-complete-2.11.1+2.11.1

kernel-tools-libs-3.10.0-693.5.2.el7.x86_64
kernel-tools-3.10.0-693.5.2.el7.x86_64
kernel-headers-3.10.0-693.5.2.el7.x86_64
kernel-3.10.0-693.5.2.el7.x86_64
kernel-3.10.0-693.el7.x86_64
kernel-devel-3.10.0-693.el7.x86_64
kernel-devel-3.10.0-693.5.2.el7.x86_64

1 Like

hi Iam very new to asterisk,
by using digium manual procedure install asterisk, dahdi, and libpri. but when iam trying to start dahdi service below is the observations

service dahdi start

Starting dahdi (via systemctl): Job for dahdi.service failed because the control process exited with error code. See “systemctl status dahdi.service” and “journalctl -xe” for details.
[FAILED]

ystemctl status dahdi.service

● dahdi.service - LSB: DAHDI kernel modules
Loaded: loaded (/etc/rc.d/init.d/dahdi; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2020-02-04 13:13:52 IST; 4min 56s ago
Docs: man:systemd-sysv-generator(8)
Process: 8789 ExecStart=/etc/rc.d/init.d/dahdi start (code=exited, status=1/FAILURE)

Feb 04 13:13:52 localhost.localdomain dahdi[8789]: auto-assign /sys/bus/dahdi_devices/devices/pci:0000:5f:00.0
Feb 04 13:13:52 localhost.localdomain dahdi[8789]: /sbin/dahdi_span_assignments: Missing ‘/etc/dahdi/assigned-spans.conf’
Feb 04 13:13:52 localhost.localdomain dahdi[8789]: Running dahdi_cfg: Notice: Configuration file is /etc/dahdi/system.conf
Feb 04 13:13:52 localhost.localdomain dahdi[8789]: line 0: Unable to open configuration file ‘/etc/dahdi/system.conf’
Feb 04 13:13:52 localhost.localdomain dahdi[8789]: 1 error(s) detected
Feb 04 13:13:52 localhost.localdomain dahdi[8789]: [FAILED]
Feb 04 13:13:52 localhost.localdomain systemd[1]: dahdi.service: control process exited, code=exited status=1
Feb 04 13:13:52 localhost.localdomain systemd[1]: Failed to start LSB: DAHDI kernel modules.
Feb 04 13:13:52 localhost.localdomain systemd[1]: Unit dahdi.service entered failed state.
Feb 04 13:13:52 localhost.localdomain systemd[1]: dahdi.service failed.
[root@localhost dahdi-linux-complete-3.1.0+3.1.0]#

journalctl -xe
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: wcte13xp: [ OK ]
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: /usr/share/dahdi/waitfor_xpds: line 106: astribank_is_starting: command not found
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: D: auto ‘/sys/bus/dahdi_devices/devices/pci:0000:af:00.0’
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: auto-assign /sys/bus/dahdi_devices/devices/pci:0000:af:00.0
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: D: auto ‘/sys/bus/dahdi_devices/devices/pci:0000:d8:00.0’
Feb 04 13:43:45 localhost.localdomain kernel: dahdi_devices pci:0000:af:00.0: local span 1 is already assigned span 1
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: auto-assign /sys/bus/dahdi_devices/devices/pci:0000:d8:00.0
Feb 04 13:43:45 localhost.localdomain kernel: dahdi_devices pci:0000:d8:00.0: local span 1 is already assigned span 2
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: D: auto ‘/sys/bus/dahdi_devices/devices/pci:0000:3b:00.0’
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: auto-assign /sys/bus/dahdi_devices/devices/pci:0000:3b:00.0
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: D: auto ‘/sys/bus/dahdi_devices/devices/pci:0000:5e:00.0’
Feb 04 13:43:45 localhost.localdomain kernel: dahdi_devices pci:0000:3b:00.0: local span 1 is already assigned span 3
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: auto-assign /sys/bus/dahdi_devices/devices/pci:0000:5e:00.0
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: D: auto ‘/sys/bus/dahdi_devices/devices/pci:0000:5f:00.0’
Feb 04 13:43:45 localhost.localdomain kernel: dahdi_devices pci:0000:5e:00.0: local span 1 is already assigned span 4
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: auto-assign /sys/bus/dahdi_devices/devices/pci:0000:5f:00.0
Feb 04 13:43:45 localhost.localdomain kernel: dahdi_devices pci:0000:5f:00.0: local span 1 is already assigned span 5
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: /sbin/dahdi_span_assignments: Missing ‘/etc/dahdi/assigned-spans.conf’
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: Running dahdi_cfg: Notice: Configuration file is /etc/dahdi/system.conf
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: line 0: Unable to open configuration file ‘/etc/dahdi/system.conf’
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: 1 error(s) detected
Feb 04 13:43:45 localhost.localdomain dahdi[10021]: [FAILED]
Feb 04 13:43:45 localhost.localdomain systemd[1]: dahdi.service: control process exited, code=exited status=1
Feb 04 13:43:45 localhost.localdomain systemd[1]: Failed to start LSB: DAHDI kernel modules.
– Subject: Unit dahdi.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit dahdi.service has failed.

– The result is failed.
Feb 04 13:43:45 localhost.localdomain systemd[1]: Unit dahdi.service entered failed state.
Feb 04 13:43:45 localhost.localdomain systemd[1]: dahdi.service failed.
Feb 04 13:43:45 localhost.localdomain polkitd[2169]: Unregistered Authentication Agent for unix-process:10015:257342 (system bus name :1.132, object
lines 2544-2577/2577 (END)

please help to resolve

Looks like the problem is in the output from your systemctl command.

do you have a valid /etc/dahdi/system.conf ?

Ihave the same problem,
Unable to open configuration file ‘/etc/dahdi/system.conf’

Ihave file as /etc/dahdi/system.conf.sample

i find the following list of files in /etc/dahdi directory
total eight files are there,which are listed below…

assigned-spans.conf.sample
genconf_parameters
init.conf
modules
modules.bak
modules.sample
span-types.conf.sample
system.conf.sample

Right, you don’t have a /etc/dahdi/system.conf file and that is your problem.

Configure Dahdi and then try and start it.

I configured Dahdi many times as below, but same issue repeated, (is it means Configure Dahdi and then try and start it ??)
cd dahdi-linux-complete-3.1.0+3.1.0
** make**
** make install**
** make install-config** (when i run #make config results:make: Nothing to be done for `config’. so i proceeded with make install-config )

Iam thinking to uninstall 'dahdi-linux-complete" totally and reinstall again , (can I proceed, is there any complications in thet?)
If I can do, Please suggest the effective Procedure to Uninstall Dahdi completely, Iam very much thankful to you

Iam uninstalled dahdi and reinstalled , but same problem facing.,

Did you run dahdi_genconf and dahdi_config?

Hello,

Maybe you already solved the issue, but I have installed today dahdi-linux-complete-3.1.0+3.1.0 on CentOS 8 Linux and Asterisk 16.10 sucessfully after many times showing the same issue:
make -C linux all
make[1]: Entering directory ‘/usr/src/dahdi-linux-complete-3.1.0+3.1.0/linux’
make -C drivers/dahdi/firmware firmware-loaders
make[2]: Entering directory ‘/usr/src/dahdi-linux-complete-3.1.0+3.1.0/linux/drivers/dahdi/firmware’
make[2]: Leaving directory ‘/usr/src/dahdi-linux-complete-3.1.0+3.1.0/linux/drivers/dahdi/firmware’
You do not appear to have the sources for the 4.18.0-147.el8.x86_64 kernel installed.
make[1]: *** [Makefile:72: modules] Error 1
make[1]: Leaving directory ‘/usr/src/dahdi-linux-complete-3.1.0+3.1.0/linux’
make: *** [Makefile:9: all] Error 2

I was trying to install the proper kernel version and finally gave the command:

yum distro-sync

reboot

after this it worked for me and allowed me install DAHDI.

1 Like

Using Ubuntu 14.04.6 with kernel 4.4.0-148-generic.
Unable to run past the very first dahdi make all

end up getting this.
checking that generated files are newer than configure… done
configure: creating ./config.status
config.status: creating makeopts
config.status: creating version.c
config.status: error: cannot find input file: `Makefile.in’
make: *** [all] Error 1