# Zaptel-\>dahdi migration: Not finding card **URL:** \ **Category:** Asterisk Support\ **Created:** [June 24, 2011, 10:15pm UTC](https://community.asterisk.org/t/zaptel-dahdi-migration-not-finding-card/35738 "2011-06-24T22:15:09Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mpounsett](https://avatars.discourse-cdn.com/v4/letter/m/f14d63/32.png) [@mpounsett](https://community.asterisk.org/u/mpounsett)\ **Post date:** [June 24, 2011, 10:15pm UTC](https://community.asterisk.org/t/zaptel-dahdi-migration-not-finding-card/35738/1 "2011-06-24T22:15:09Z")
I just did an OS update on my PBX machine, including an OS reinstall (FreeBSD 8.2).. this meant grabbing newer versions of everything, so I’m moving from zaptel to dahdi. My current install includes the ports: asterisk18-1.8.4.2 dahdi-2.4.0rc5\_5 dahdi-kmod-2.4.0rc5 I basically copied my old zapata.conf file verbatim to the dahdi system.conf: fxsks=4 fxoks=1-2 loadzone = us defaultzone=us However, dahdi doesn’t seem to be recognizing my Digium card. I get nothing (an empty list) from dahdi\_tool, and dadhi\_cfg gives me the content pasted below. I’ve done a reboot just to be sure everything’s loading. The only thing dahdi-related in dmesg is: dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.4.0-rc5 It looks like everything from the upgrade is working except this one piece. Any thoughts on what I might be missing? > sudo dahdi\_cfg -vv > DAHDI Tools Version - 2.4.0-rc1 # DAHDI Version: 2.4.0-rc5 Echo Canceller(s): Configuration Channel map: Channel 01: FXO Kewlstart (Default) (Echo Canceler: none) (Slaves: 01) Channel 02: FXO Kewlstart (Default) (Echo Canceler: none) (Slaves: 02) Channel 04: FXS Kewlstart (Default) (Echo Canceler: none) (Slaves: 04) 3 channels to configure. DAHDI\_CHANCONFIG failed on channel 1: Device not configured (6) ---
**Author:** ![navaismo](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/navaismo/32/2481_2.png) [@navaismo](https://community.asterisk.org/u/navaismo)\ **Post date:** [June 25, 2011, 4:15pm UTC](https://community.asterisk.org/t/zaptel-dahdi-migration-not-finding-card/35738/2 "2011-06-25T16:15:52Z")
try with dahdi\_hardware to know if dahdi see your card. if yes, use dahdi\_genconf to configure the card. What model is the card? ---
**Author:** ![mpounsett](https://avatars.discourse-cdn.com/v4/letter/m/f14d63/32.png) [@mpounsett](https://community.asterisk.org/u/mpounsett)\ **Post date:** [June 26, 2011, 3:50am UTC](https://community.asterisk.org/t/zaptel-dahdi-migration-not-finding-card/35738/3 "2011-06-26T03:50:19Z")
Sure. Any idea where I can find either of those? The dahdi port on FreeBSD doesn’t include either one. I tried compiling the dahdi-tools package from the Asterisk site, but it claims to require the Dahdi Linux kernel modules… and since I’m not running Linux… As for the model card, I couldn’t quote you the model number. It’s been three or four years since I bought the card. It’s a four port PCI card that takes daughter boards to turn them into fxs or fxo ports. I’ve got three boards on mine for two fxo ports and one fxs. ---
**Author:** ![system](https://global.discourse-cdn.com/asterisk/original/2X/4/475d0c889911cfb84ac4881ad6df8b523e3f9105.png) [@system](https://community.asterisk.org/u/system)\ **Post date:** [July 1, 2011, 8:07pm UTC](https://community.asterisk.org/t/zaptel-dahdi-migration-not-finding-card/35738/4 "2011-07-01T20:07:33Z")
Hey Matt, I just went through the same thing. Sounds like you and I have the same PCI card. I solved it by adding this to /etc/rc.conf ``` dahdi_modules="wctdm" ``` Then the wctdm kernel module gets loaded correctly. Before adding that line I was not seeing this in /var/log/messages: Jul 1 12:43:02 pbx kernel: wctdm0: vendor=e159 device=1 subvendor=b119 Jul 1 12:43:02 pbx kernel: wctdm0: port 0xd800-0xd8ff mem 0xff101000-0xff101fff irq 10 at device 13.0 on pci0 DW