Module zaptel not found -- trixbox 2.8

bert.rapp
Posts: 12
Member Since:
2009-02-24

I believe trixbox 2.8 uses dahdi instead of zaptel, but I'm not certain what all has been renamed.

I've just finished a fresh install of trixbox 2.8.0.2. I'm trying to configure an OpenVox A400P card.

zaptel_hardware shows me the card:
zaptel_hardware
pci:0000:05:04.0 wctdm- e159:0001 Wildcard TDM400P REV E/F

But it looks like the modules are missing:
modprobe zaptel and modprobe dahdi both fail, with "Module not found"

uname -a shows me
Linux trixbox1.localdomain 2.6.18-92.1.18.el5 #1 SMP Wed Nov 12 09:30:27 EST 2008 i686 i686 i386 GNU/Linux

And a quick locate shows me the zaptel drivers are in /lib/modules/2.6.18-128.1.10.el5
[trixbox1.localdomain ~]# locate zap | grep modules
/lib/modules/2.6.18-128.1.10.el5/extra/zaptel

Is there a reason the modules for 2.6.18-92.1.18.el5 are not installed? Am I making a mistake? Also, I cannot find any dahdi files on the system at all. I thought trixbox 2.8 used dahdi.



SkykingOH
Posts: 9541
Member Since:
2007-12-17
Why don't you just run the

Why don't you just run the setup-pstn script instead of trying to show us how smart you are?

If you want to see the dahdi tools type 'dahdi' from the shell and press the tab key twice.

--

Scott

aka "Skyking"



bert.rapp
Posts: 12
Member Since:
2009-02-24
dahdi[tab][tab] gives

dahdi[tab][tab] gives nothing. There are no files that begin with dahdi.

"locate dahdi" only reveals two files:
[trixbox1.localdomain zaptel]# locate dahdi
/etc/asterisk/chan_dahdi.conf.template
/usr/src/tbm-pbxconfig-5.5.1/amp_conf/astetc/chan_dahdi.conf.template

The results from setup-pstn are as folows (notice the last line: Module zaptel not found)
[trixbox1.localdomain zaptel]# setup-pstn

--------------------------------------------------------------
Detecting PSTN cards
--------------------------------------------------------------

Notice: Configuration file is /etc/zaptel.conf
line 0: Unable to open master device '/dev/zap/ctl'

1 error(s) detected

STOPPING ASTERISK
Asterisk Stopped

STOPPING FOP SERVER
FOP Server Stopped
Notice: Configuration file is /etc/zaptel.conf
line 0: Unable to open master device '/dev/zap/ctl'

1 error(s) detected

STOPPING ASTERISK

STOPPING FOP SERVER
wanpipe: unrecognized service
Unloading zaptel hardware drivers:.
Loading zaptel framework: FATAL: Module zaptel not found.



SkykingOH
Posts: 9541
Member Since:
2007-12-17
I find that very hard to

I find that very hard to believe. Did your install complete?

I think dahdi is not starting, however I would be shocked that it is not installed.

'yum list dahdi*'

--

Scott

aka "Skyking"



bert.rapp
Posts: 12
Member Since:
2009-02-24
[trixbox1.localdomain

[trixbox1.localdomain extra]# yum list dahdi*
Loading "fastestmirror" plugin
[... truncated...]
Error: No matching Packages to list

[trixbox1.localdomain extra]# yum list zaptel*
Loading "fastestmirror" plugin
[...truncated...]
Finished
Installed Packages
zaptel.i686 1.4.12.9-1_trixbox installed

It looks like the zaptel package is installed, but again, when I modprobe:
[trixbox1.localdomain extra]# modprobe zaptel
FATAL: Module zaptel not found.

This was a fresh install of 2.8.0.2. I did check the md5sum of the ISO before I burnt the CD. The install seemed to finish properly.



bert.rapp
Posts: 12
Member Since:
2009-02-24
yum update

After running yum update, the kernel was updated to 2.6.18-128.1.10.el5 and now the zaptel module loads. Is this the way trixbox 2.8.0.2 works, or was my installation incomplete?



SkykingOH
Posts: 9541
Member Since:
2007-12-17
Zaptel on 2.8 is impossible.

Zaptel on 2.8 is impossible. 2.8 is Asterisk 1.6 and only supports DAHDI.

--

Scott

aka "Skyking"



bert.rapp
Posts: 12
Member Since:
2009-02-24
Stupid mistake

Ugh, stupid mistake, I labeled the CDs wrong. I'm running 2.6. I downloaded both 2.6 and 2.8. Regardless of that mistake I wonder why the kernel and module versions didn't line up.



jfinstrom
Posts: 2008
Member Since:
2007-03-07
Welcome....

Welcome....

--



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.