TDM410 won't work anymore!

I have a new problem with my TDM410. Driver seems OK but asterisk won’t bind.

Jun  2 13:06:51 ns kernel: dahdi_vpmadt032_loader: module license 'Digium Commercial' taints kernel.
Jun  2 13:06:51 ns kernel: Disabling lock debugging due to kernel taint
Jun  2 13:06:56 ns kernel: wctdm24xxp 0000:08:00.0: Booting VPMADT032
Jun  2 13:06:56 ns kernel: wctdm24xxp 0000:08:00.0: VPM present and operational (Firmware version 125)
Jun  2 13:06:57 ns kernel: wctdm24xxp 0000:08:00.0: Port 1: Installed -- AUTO FXO (FCC mode)
Jun  2 13:06:57 ns kernel: wctdm24xxp 0000:08:00.0: Port 2: Not installed
Jun  2 13:06:57 ns kernel: wctdm24xxp 0000:08:00.0: Port 3: Installed -- AUTO FXS/DPO
Jun  2 13:06:57 ns kernel: wctdm24xxp 0000:08:00.0: Port 4: Not installed
Jun  2 13:06:57 ns kernel: wctdm24xxp 0000:08:00.0: Found a Wildcard TDM: Wildcard TDM410P (0 BRI spans, 2 analog channels)
Jun  2 13:06:57 ns 'dahdi_handle_device'[805]: add: /devices/pci0000:00/0000:00:1c.7/0000:07:00.0/0000:08:00.0/pci:0000:08:00.0
Jun  2 13:06:57 ns 'dahdi_handle_device'[808]: auto_assign_spans=1. Skip /devices/pci0000:00/0000:00:1c.7/0000:07:00.0/0000:08:00.0/pci:0000:08:00.0
Jun  2 13:06:57 ns 'dahdi_span_config'[816]: add: /devices/pci0000:00/0000:00:1c.7/0000:07:00.0/0000:08:00.0/pci:0000:08:00.0/span-1
Jun  2 13:06:57 ns 'dahdi_span_config'[818]: auto_assign_spans=1. Skip /devices/pci0000:00/0000:00:1c.7/0000:07:00.0/0000:08:00.0/pci:0000:08:00.0/span-1
Jun  2 13:06:57 ns 'dahdi_span_config'[826]: UNHANDLED: bind: /devices/pci0000:00/0000:00:1c.7/0000:07:00.0/0000:08:00.0/pci:0000:08:00.0/span-1

[root@ns sbin]# dahdi_span_assignments list
cut: '/sys/bus/dahdi_devices/devices/pci:0000:08:00.0/spantype': No such file or directory
[root@ns sbin]# cd /sys/bus/dahdi_devices/devices/pci:0000:08:00.0
[root@ns pci:0000:08:00.0]# dir
assign_span  dahdi_registration_time  hardware_id  manufacturer  span-1      subsystem  uevent
auto_assign  dahdi_spantype
[root@ns pci:0000:08:00.0]# cat dahdi_spantype
1:ANALOG_MIXED
[root@ns sbin]# cd /sys/bus/dahdi_devices/devices/pci:0000:08:00.0/span-1
[root@ns span-1]# dir
alarms    dahdi!chan!001!001  dahdi!chan!001!004  driver          lbo         local_spanno  spantype   uevent
basechan  dahdi!chan!001!002  ddev                is_digital      linecompat  name          subsystem
channels  dahdi!chan!001!003  desc                is_sync_master  lineconfig  power         syncsrc
[root@ns span-1]# cat spantype
ANALOG_MIXED
[root@ns sbin]# dahdi_scan
[1]
active=yes
alarms=OK
description=Wildcard TDM410P
name=WCTDM/0
manufacturer=Digium
devicetype=Wildcard TDM410P (VPMADT032)
location=PCI Bus 08 Slot 01
basechan=1
totchans=4
irq=0
type=analog
port=1,FXO
port=2,none
port=3,FXS
port=4,none

I am totally lost here could someone help me?
Thanks.

The card vendor. should provide the help here.

Go to same source you compliled from hopefully you still have it on disk. Recompile and install again

No they won’t TDM410 is obsolete so they are doing what they can to stop that card of working.

I did that more than once.

Did you upgrade the kernel on your machine ? Try to use old one. If you did not apt remove it . It is still there

Yes, it’s a new hard drive and a fresh fedora installation.
Something is missing but what?

The only warning during the compilation of dahdi is :

  CC [M]  /usr/src/phones/dahdi-linux/drivers/dahdi/dahdi-sysfs-chan.o
/usr/src/phones/dahdi-linux/drivers/dahdi/dahdi-sysfs-chan.c: In function  « fixed_devfiles_remove » :
/usr/src/phones/dahdi-linux/drivers/dahdi/dahdi-sysfs-chan.c:384:17: warning: this  « if »  clause does not guard... [8;;https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wmisleading-indentation-Wmisleading-indentation8;;]
  384 |                 if (d && !IS_ERR(d))
      |                 ^~
/usr/src/phones/dahdi-linux/drivers/dahdi/dahdi-sysfs-chan.c:40:9: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the  Ç if Ç
   40 |         device_destroy(dahdi_class, MKDEV(DAHDI_MAJOR, num))
      |         ^~~~~~~~~~~~~~
/usr/src/phones/dahdi-linux/drivers/dahdi/dahdi-sysfs-chan.c:387:25: note: in expansion of macro  « DEL_DAHDI_DEV »
  387 |                         DEL_DAHDI_DEV(fixed_minors[i].minor);
      |                         ^~~~~~~~~~~~~

#define DEL_DAHDI_DEV(num) \
        device_destroy(dahdi_class, MKDEV(DAHDI_MAJOR, num))

static void fixed_devfiles_remove(void)
{
        int i;

        if (!dahdi_class)
                return;
        for (i = 0; i < ARRAY_SIZE(fixed_minors); i++) {
                void *d = fixed_minors[i].dev;
                if (d && !IS_ERR(d))
                        dahdi_dbg(DEVICES, "Removing fixed device file %s\n",
                                fixed_minors[i].name);
                        DEL_DAHDI_DEV(fixed_minors[i].minor);
        }
}

I have only 2 channels equiped and both LEDs are on.
I am still lost.

Did you try to recompile asterisk with dahdi driver ?

Yes, I did it more than once.

The only warning is inside the skype module that I don’t use :

   [CC] chan_skinny.c -> chan_skinny.o
In function  « handle_enbloc_call_message » ,
    inlined from  « handle_message »  at chan_skinny.c:7331:9,
    inlined from  « skinny_session »  at chan_skinny.c:7638:9:
chan_skinny.c:6968:17: warning:  « dialandactivatesub »  accessing 80 bytes in a region of size 24 [8;;https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wstringop-overflow=-Wstringop-overflow=8;;]
 6968 |                 dialandactivatesub(sub, req->data.enbloccallmessage.calledParty);
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
chan_skinny.c: In function  « skinny_session » :
chan_skinny.c:6968:17: note: referencing argument 2 of type  « char * »
chan_skinny.c:6071:13: note: in a call to function  « dialandactivatesub »
 6071 | static void dialandactivatesub(struct skinny_subchannel *sub, char exten[AST_MAX_EXTENSION])
      |             ^~~~~~~~~~~~~~~~~~

I understand why a seller wishes to stop providing support for something.
But here they are trying their best to impede their product to continue working.
In my opinion it’s unethical

Yes many times and :

ns*CLI> module load chan_dahdi
Unable to load module chan_dahdi
Command 'module load chan_dahdi' failed.
[2021-06-03 13:25:46] WARNING[284466]: loader.c:1771 load_resource: Module 'chan_dahdi' already loaded and running.

The only thing strange is :

cut: '/sys/bus/dahdi_devices/devices/pci:0000:08:00.0/spantype': No such file or directory

When I run dahdi_genconf. But the configuration files seem OK.

OK, everything is working fine now.
I tried to restart dahdi and received :

ns*CLI> dahdi restart
 Destroying channels and reloading DAHDI configuration.
       > Initial softhangup of all DAHDI channels complete.
       > Final softhangup of all DAHDI channels complete.
    -- Unregistered channel -2
[2021-06-03 16:54:00] WARNING[41704]: chan_dahdi.c:4118 dahdi_open: Unable to specify channel 1: No such device or address

I tried to restart dahdi and messages said :

Jun  3 17:29:29 ns dahdi[48962]:  wctdm24xxp:  [  OK  ]
Jun  3 17:29:30 ns kernel: NOTICE-dahdi: chan-1: dahdi_ioctl_chanconfig: bad sigtype. sigcap: 16785, sigtype: 1020.
Jun  3 17:29:30 ns kernel: dahdi: Registered tone zone 0 (United States / North America)
Jun  3 17:29:30 ns kernel: dahdi: Unregistering tone zone 0 (United States / North America)
Jun  3 17:29:30 ns kernel: dahdi: Registered tone zone 0 (United States / North America)
Jun  3 17:29:30 ns kernel: NOTICE-dahdi: chan-3: dahdi_ioctl_chanconfig: bad sigtype. sigcap: 157f8, sigtype: 2004.
Jun  3 17:29:30 ns dahdi[48995]: /usr/share/dahdi/waitfor_xpds: line 106: astribank_is_starting: command not found
Jun  3 17:29:30 ns dahdi[49003]: using '/etc/dahdi/assigned-spans.conf'
Jun  3 17:29:30 ns dahdi[49018]: cut: '/sys/bus/dahdi_devices/devices/pci:0000:08:00.0/spantype': No such file or directory
Jun  3 17:29:30 ns dahdi[48962]: Running dahdi_cfg:  [  OK  ]
Jun  3 17:29:30 ns kernel: dahdi: Registered tone zone 17 (Belgium)
Jun  3 17:29:30 ns systemd[1]: Started LSB: DAHDI kernel modules.

Out of patience I edited by hand /etc/dahdi/assigned-spans.conf to add /span-1 :

# Device: [] @PCI_Bus_08_Slot_01 /sys/devices/pci0000:00/0000:00:1c.7/0000:07:00.0/0000:08:00.0/pci:0000:08:00.0/span-1

Restarted dahdi and :

Jun  3 17:52:19 ns systemd[1]: Starting LSB: DAHDI kernel modules...
Jun  3 17:52:19 ns kernel: dahdi: Version: 3.1.0-12-g5c840cf4M
Jun  3 17:52:19 ns kernel: dahdi: Telephony Interface Registered on major 196
Jun  3 17:52:19 ns dahdi[53565]: Loading DAHDI hardware modules:
Jun  3 17:52:19 ns dahdi[53565]:  dahdi:  [  OK  ]
Jun  3 17:52:19 ns dahdi[53565]:  dahdi_dummy:  [  OK  ]
Jun  3 17:52:19 ns dahdi[53565]:  dahdi_transcode:  [  OK  ]
Jun  3 17:52:19 ns kernel: dahdi_transcode: Loaded.
Jun  3 17:52:24 ns kernel: wctdm24xxp 0000:08:00.0: Booting VPMADT032
Jun  3 17:52:24 ns kernel: wctdm24xxp 0000:08:00.0: VPM present and operational (Firmware version 125)
Jun  3 17:52:25 ns kernel: wctdm24xxp 0000:08:00.0: Port 1: Installed -- AUTO FXO (FCC mode)
Jun  3 17:52:25 ns kernel: wctdm24xxp 0000:08:00.0: Port 2: Not installed
Jun  3 17:52:25 ns kernel: wctdm24xxp 0000:08:00.0: Port 3: Installed -- AUTO FXS/DPO
Jun  3 17:52:25 ns kernel: wctdm24xxp 0000:08:00.0: Port 4: Not installed
Jun  3 17:52:25 ns kernel: wctdm24xxp 0000:08:00.0: Found a Wildcard TDM: Wildcard TDM410P (0 BRI spans, 2 analog channels)
Jun  3 17:52:25 ns dahdi[53565]:  wctdm24xxp:  [  OK  ]
Jun  3 17:52:25 ns 'dahdi_handle_device'[53605]: add: /devices/pci0000:00/0000:00:1c.7/0000:07:00.0/0000:08:00.0/pci:0000:08:00.0
Jun  3 17:52:25 ns 'dahdi_handle_device'[53608]: auto_assign_spans=1. Skip /devices/pci0000:00/0000:00:1c.7/0000:07:00.0/0000:08:00.0/pci:0000:08:00.0
Jun  3 17:52:25 ns 'dahdi_span_config'[53616]: add: /devices/pci0000:00/0000:00:1c.7/0000:07:00.0/0000:08:00.0/pci:0000:08:00.0/span-1
Jun  3 17:52:25 ns 'dahdi_span_config'[53618]: auto_assign_spans=1. Skip /devices/pci0000:00/0000:00:1c.7/0000:07:00.0/0000:08:00.0/pci:0000:08:00.0/span-1
Jun  3 17:52:25 ns 'dahdi_span_config'[53626]: UNHANDLED: bind: /devices/pci0000:00/0000:00:1c.7/0000:07:00.0/0000:08:00.0/pci:0000:08:00.0/span-1
Jun  3 17:52:25 ns dahdi[53640]: /usr/share/dahdi/waitfor_xpds: line 106: astribank_is_starting: command not found
Jun  3 17:52:25 ns dahdi[53648]: using '/etc/dahdi/assigned-spans.conf'
Jun  3 17:52:25 ns dahdi[53663]: cut: '/sys/bus/dahdi_devices/devices/pci:0000:08:00.0/spantype': No such file or directory
Jun  3 17:52:25 ns dahdi[53565]: Running dahdi_cfg:  [  OK  ]
Jun  3 17:52:25 ns systemd[1]: Started LSB: DAHDI kernel modules.
Jun  3 17:52:25 ns audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dahdi comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Still that error with the path but thinks are going better.

ns*CLI> dahdi restart
 Destroying channels and reloading DAHDI configuration.
       > Initial softhangup of all DAHDI channels complete.
       > Final softhangup of all DAHDI channels complete.
    -- Unregistered channel -2
    -- Unregistered channel 1
    -- Unregistered channel 3
[2021-06-03 17:58:27] WARNING[54931]: chan_dahdi.c:7376 handle_alarms: Detected alarm on channel 1: Red Alarm
    -- Reconfigured channel 1, FXS Kewlstart signalling
    -- Reconfigured channel 3, FXO Kewlstart signalling
[2021-06-03 17:58:27] WARNING[54931]: chan_dahdi.c:19251 process_dahdi: Ignoring any changes to 'userbase' (on reload) at line 23.
[2021-06-03 17:58:27] WARNING[54931]: chan_dahdi.c:19251 process_dahdi: Ignoring any changes to 'vmsecret' (on reload) at line 31.
[2021-06-03 17:58:27] WARNING[54931]: chan_dahdi.c:19251 process_dahdi: Ignoring any changes to 'hassip' (on reload) at line 35.
[2021-06-03 17:58:27] WARNING[54931]: chan_dahdi.c:19251 process_dahdi: Ignoring any changes to 'hasiax' (on reload) at line 39.
[2021-06-03 17:58:27] WARNING[54931]: chan_dahdi.c:19251 process_dahdi: Ignoring any changes to 'hasmanager' (on reload) at line 47.

And now it’s working!