Re: [asterisk-users] Zaptel / TDM400P card stopped working
On Monday 15 December 2008 00:57:08 Langdon Stevenson wrote: Hi Paul Thanks for the reply. I have removed and re-installed all of the Fedora Zaptel packages with Yum. I have the following installed: asterisk-zaptel 1.4.12.1-1.fc8 zaptel.i386 1.4.12.1-1.fc8 zaptel-devel.i386 1.4.12.1-1.fc8 zaptel-lib.i386 1.4.12.1-1.fc8 zaptel-utils.i386 1.4.12.1-1.fc8 The command: modprobe wctdm produces: FATAL: Module wctdm not found. This probably means that the modules were compiled for a kernel other than the one you have installed. You probably have multiple directories within /lib/modules, and the zaptel modules are in a directory other than what is listed with 'uname -r'. In this case, compiling from source is probably your best bet. -- Tilghman ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Zaptel / TDM400P card stopped working
Tilghman Lesher wrote: On Monday 15 December 2008 00:57:08 Langdon Stevenson wrote: Hi Paul Thanks for the reply. I have removed and re-installed all of the Fedora Zaptel packages with Yum. I have the following installed: asterisk-zaptel 1.4.12.1-1.fc8 zaptel.i386 1.4.12.1-1.fc8 zaptel-devel.i386 1.4.12.1-1.fc8 zaptel-lib.i386 1.4.12.1-1.fc8 zaptel-utils.i386 1.4.12.1-1.fc8 The command: modprobe wctdm produces: FATAL: Module wctdm not found. This probably means that the modules were compiled for a kernel other than the one you have installed. You probably have multiple directories within /lib/modules, and the zaptel modules are in a directory other than what is listed with 'uname -r'. In this case, compiling from source is probably your best bet. This may be an obvious thing, but you didn't mention checking whether or not the card was still seated in the slot properly after the move. I know from experience that when you move offices, even if you take all the precautions possible, a card can get bumped just enough to jostle the connections loose. Even if the card appears to be seated correctly I'd take it out and re-seat it. Unfortunately it looks like you may have compounded the problem by removing and reinstalling the zaptel packages. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Zaptel / TDM400P card stopped working
This may be an obvious thing, but you didn't mention checking whether or not the card was still seated in the slot properly after the move. I know from experience that when you move offices, even if you take all the precautions possible, a card can get bumped just enough to jostle the connections loose. Even if the card appears to be seated correctly I'd take it out and re-seat it. Unfortunately it looks like you may have compounded the problem by removing and reinstalling the zaptel packages. It looked like the card was still there - from memory the lspci command said it was. PaulH ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Zaptel / TDM400P card stopped working
Paul Hales wrote: This may be an obvious thing, but you didn't mention checking whether or not the card was still seated in the slot properly after the move. I know from experience that when you move offices, even if you take all the precautions possible, a card can get bumped just enough to jostle the connections loose. Even if the card appears to be seated correctly I'd take it out and re-seat it. Unfortunately it looks like you may have compounded the problem by removing and reinstalling the zaptel packages. It looked like the card was still there - from memory the lspci command said it was. PaulH That is correct, lspci shows the card is there. I have also tried moving the card to a different slot to be sure. Langdon ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Zaptel / TDM400P card stopped working
Langdon Stevenson wrote: Paul Hales wrote: It looked like the card was still there - from memory the lspci command said it was. PaulH That is correct, lspci shows the card is there. I have also tried moving the card to a different slot to be sure. Langdon So - the current state of play is: card = yes drivers = no As a stop gap, have you tried building the drivers from source? PaulH ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Zaptel / TDM400P card stopped working
On Mon, Dec 15, 2008 at 05:57:08PM +1100, Langdon Stevenson wrote: Hi Paul Thanks for the reply. I have removed and re-installed all of the Fedora Zaptel packages with Yum. I have the following installed: asterisk-zaptel 1.4.12.1-1.fc8 zaptel.i386 1.4.12.1-1.fc8 zaptel-devel.i386 1.4.12.1-1.fc8 zaptel-lib.i386 1.4.12.1-1.fc8 zaptel-utils.i386 1.4.12.1-1.fc8 None of those packages contains kernel modules. A simple test: find /lib/modules/`uname -r` -name zaptel.ko Should not find anything. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Zaptel / TDM400P card stopped working
Paul Hales wrote: Langdon Stevenson wrote: Paul Hales wrote: It looked like the card was still there - from memory the lspci command said it was. PaulH That is correct, lspci shows the card is there. I have also tried moving the card to a different slot to be sure. Langdon So - the current state of play is: card = yes drivers = no As a stop gap, have you tried building the drivers from source? PaulH Yes, that is the current state of play and yes, it looks like I will have to build from source. I haven't done this before and am pretty busy at the moment, so it will take me a while. I will post back when I have done so. Thanks for the input (to all who have contributed), it is much appreciated. Regards, Langdon ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Zaptel / TDM400P card stopped working
Langdon Stevenson wrote: Yes, that is the current state of play and yes, it looks like I will have to build from source. I haven't done this before and am pretty busy at the moment, so it will take me a while. I will post back when I have done so. Thanks for the input (to all who have contributed), it is much appreciated. Regards, Langdon Building the drivers from source will only take you 10 minutes - not a huge hassle. PaulH ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Zaptel / TDM400P card stopped working
Hi Paul This is the thing that is confusing. When I set up Asterisk first time round I just used the Fedora packages, I didn't build from source. Is the asterisk-zaptel or the zaptel rpm supposed to provide the drivers? Does rpm -qf filename show the correct kernel version? My understanding is that yes, the Fedora packages provide everything. It may be relevant to mention that: uname -a returns: Linux switch 2.6.26.3-14.fc8 #1 SMP Wed Sep 3 03:40:05 EDT 2008 i686 i686 i386 GNU/Linux I then checked for the wctdm module: locate wtctdm returns: /lib/modules/2.6.23.15-80.fc7/misc/wctdm.ko /lib/modules/2.6.23.15-80.fc7/misc/wctdm24xxp /lib/modules/2.6.23.15-80.fc7/misc/wctdm24xxp/wctdm24xxp.ko /lib/modules/2.6.24.3-34.fc8/misc/wctdm.ko /lib/modules/2.6.24.3-34.fc8/misc/wctdm24xxp /lib/modules/2.6.24.3-34.fc8/misc/wctdm24xxp/wctdm24xxp.ko snip So it looks like the Zaptel packages (at least for wctdm) don't have a version to support the kernel that I have installed, which would explain things. Langdon Paul Hales wrote: h...I haven't used the RPM's before, so I can only guess that the RPM's are doing something not quite right. Is the asterisk-zaptel or the zaptel rpm supposed to provide the drivers? Does rpm -qf filename show the correct kernel version? If that fails, you could download the source files from the Asterisk site and build them yourself. PaulH Langdon Stevenson wrote: Hi Paul Thanks for the reply. I have removed and re-installed all of the Fedora Zaptel packages with Yum. I have the following installed: asterisk-zaptel 1.4.12.1-1.fc8 zaptel.i386 1.4.12.1-1.fc8 zaptel-devel.i386 1.4.12.1-1.fc8 zaptel-lib.i386 1.4.12.1-1.fc8 zaptel-utils.i386 1.4.12.1-1.fc8 The command: modprobe wctdm produces: FATAL: Module wctdm not found. The command: modprobe zaptel produces: FATAL: Module zaptel not found. Is there anything else that I should be doing? Regards, Langdon Paul Hales wrote: Have you tried loading the zaptel driver for your card manually? PaulH Langdon Stevenson wrote: Hi I have a Dell PE2300 with a Digium TDM400P line card in it (with one module to handle an inbound phone line). This is running on a Fedora 8 system with Asterisk 1.4.21.2-1.fc8 This system has been working nicely for about 12 months. After a recent move of office and relocation of the server Asterisk is back on line, but the TDM line card has stopped working. I have spent half a day working through Google search results, but no luck so far. The command: lspci -v produces: snip 02:0a.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface Subsystem: Unknown device b1d9:0001 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at e400 [size=256] Memory at f9ffd000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel modules: hisax The IRQ is not in use by any other device, so there is no conflict (this seems to be a common problem). The card has always been detected as a Tiger3XX. What stands out here to me is: Kernal modules: hisax I don't believe that this was the case when I first installed the card (but it was over a year ago, so I may be wrong). The hisax driver is blacklisted in /etc/modprobe.d/blacklist. The command: lsmod produces: Module Size Used by xt_dscp 6465 0 rfcomm 32721 0 l2cap 21953 9 rfcomm bluetooth 47013 6 rfcomm,l2cap autofs420933 2 fuse 47837 1 tun12613 0 sunrpc154785 3 nf_conntrack_netbios_ns 6593 0 iptable_nat 8777 0 nf_nat 18393 1 iptable_nat iptable_mangle 6849 0 nf_conntrack_ipv4 11849 5 iptable_nat,nf_nat xt_state6209 2 nf_conntrack 51221 5 nf_conntrack_netbios_ns,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state ipt_REJECT 6977 2 ipt_LOG 9285 4 iptable_filter 6849 1 ip_tables 14033 3 iptable_nat,iptable_mangle,iptable_filter xt_tcpudp 6977 33 ip6t_REJECT 7617 2 ip6table_filter 6593 1 ip6_tables 15057 1 ip6table_filter x_tables 15557 9 xt_dscp,iptable_nat,xt_state,ipt_REJECT,ipt_LOG,ip_tables,xt_tcpudp,ip6t_REJECT,ip6_tables ipv6 238277 25 ip6t_REJECT dm_multipath 18505 0 parport_pc 26725 0 parport32173 1 parport_pc floppy 52229 0 i2c_piix4 11473 0 i2c_core 20949 1 i2c_piix4 pcspkr 6593 0 e100 33997 0 mii 8385 1 e100 dcdbas
Re: [asterisk-users] Zaptel / TDM400P card stopped working
Tilghman Lesher wrote: On Monday 15 December 2008 00:57:08 Langdon Stevenson wrote: Hi Paul Thanks for the reply. I have removed and re-installed all of the Fedora Zaptel packages with Yum. I have the following installed: asterisk-zaptel 1.4.12.1-1.fc8 zaptel.i386 1.4.12.1-1.fc8 zaptel-devel.i386 1.4.12.1-1.fc8 zaptel-lib.i386 1.4.12.1-1.fc8 zaptel-utils.i386 1.4.12.1-1.fc8 The command: modprobe wctdm produces: FATAL: Module wctdm not found. This probably means that the modules were compiled for a kernel other than the one you have installed. You probably have multiple directories within /lib/modules, and the zaptel modules are in a directory other than what is listed with 'uname -r'. In this case, compiling from source is probably your best bet. Hi Tilghman, I think that you are spot on. Sounds like I should try building from source. Regards, Langdon ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Zaptel / TDM400P card stopped working
Hi I have a Dell PE2300 with a Digium TDM400P line card in it (with one module to handle an inbound phone line). This is running on a Fedora 8 system with Asterisk 1.4.21.2-1.fc8 This system has been working nicely for about 12 months. After a recent move of office and relocation of the server Asterisk is back on line, but the TDM line card has stopped working. I have spent half a day working through Google search results, but no luck so far. The command: lspci -v produces: snip 02:0a.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface Subsystem: Unknown device b1d9:0001 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at e400 [size=256] Memory at f9ffd000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel modules: hisax The IRQ is not in use by any other device, so there is no conflict (this seems to be a common problem). The card has always been detected as a Tiger3XX. What stands out here to me is: Kernal modules: hisax I don't believe that this was the case when I first installed the card (but it was over a year ago, so I may be wrong). The hisax driver is blacklisted in /etc/modprobe.d/blacklist. The command: lsmod produces: Module Size Used by xt_dscp 6465 0 rfcomm 32721 0 l2cap 21953 9 rfcomm bluetooth 47013 6 rfcomm,l2cap autofs420933 2 fuse 47837 1 tun12613 0 sunrpc154785 3 nf_conntrack_netbios_ns 6593 0 iptable_nat 8777 0 nf_nat 18393 1 iptable_nat iptable_mangle 6849 0 nf_conntrack_ipv4 11849 5 iptable_nat,nf_nat xt_state6209 2 nf_conntrack 51221 5 nf_conntrack_netbios_ns,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state ipt_REJECT 6977 2 ipt_LOG 9285 4 iptable_filter 6849 1 ip_tables 14033 3 iptable_nat,iptable_mangle,iptable_filter xt_tcpudp 6977 33 ip6t_REJECT 7617 2 ip6table_filter 6593 1 ip6_tables 15057 1 ip6table_filter x_tables 15557 9 xt_dscp,iptable_nat,xt_state,ipt_REJECT,ipt_LOG,ip_tables,xt_tcpudp,ip6t_REJECT,ip6_tables ipv6 238277 25 ip6t_REJECT dm_multipath 18505 0 parport_pc 26725 0 parport32173 1 parport_pc floppy 52229 0 i2c_piix4 11473 0 i2c_core 20949 1 i2c_piix4 pcspkr 6593 0 e100 33997 0 mii 8385 1 e100 dcdbas 10465 0 sr_mod 17541 0 cdrom 33249 1 sr_mod sg 31605 0 ata_piix 19397 0 libata131937 1 ata_piix raid1 22593 2 dm_snapshot18661 0 dm_zero 5825 0 dm_mirror 19521 0 dm_log 12229 1 dm_mirror dm_mod 48265 8 dm_multipath,dm_snapshot,dm_zero,dm_mirror,dm_log aic7xxx 101753 15 scsi_transport_spi 23233 1 aic7xxx sd_mod 26329 20 scsi_mod 123917 6 sr_mod,sg,libata,aic7xxx,scsi_transport_spi,sd_mod raid456 121681 1 async_xor 7361 1 raid456 async_memcpy6209 1 raid456 async_tx9869 3 raid456,async_xor,async_memcpy xor18633 2 raid456,async_xor ext3 110281 2 jbd41045 1 ext3 mbcache10309 1 ext3 uhci_hcd 22993 0 ohci_hcd 22853 0 ehci_hcd 32845 0 The command: ztcfg -v produces: Notice: Configuration file is /etc/zaptel.conf line 0: Unable to open master device '/dev/zap/ctl' 1 error(s) detected The command: ls -al /dev/ | grep zap produces nothing So, I am left wondering what has changed and why the Zaptel drivers are no longer loading. Can anyone suggest to me how I might go about troubleshooting this issue? Langdon ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Zaptel / TDM400P card stopped working
Have you tried loading the zaptel driver for your card manually? PaulH Langdon Stevenson wrote: Hi I have a Dell PE2300 with a Digium TDM400P line card in it (with one module to handle an inbound phone line). This is running on a Fedora 8 system with Asterisk 1.4.21.2-1.fc8 This system has been working nicely for about 12 months. After a recent move of office and relocation of the server Asterisk is back on line, but the TDM line card has stopped working. I have spent half a day working through Google search results, but no luck so far. The command: lspci -v produces: snip 02:0a.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface Subsystem: Unknown device b1d9:0001 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at e400 [size=256] Memory at f9ffd000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel modules: hisax The IRQ is not in use by any other device, so there is no conflict (this seems to be a common problem). The card has always been detected as a Tiger3XX. What stands out here to me is: Kernal modules: hisax I don't believe that this was the case when I first installed the card (but it was over a year ago, so I may be wrong). The hisax driver is blacklisted in /etc/modprobe.d/blacklist. The command: lsmod produces: Module Size Used by xt_dscp 6465 0 rfcomm 32721 0 l2cap 21953 9 rfcomm bluetooth 47013 6 rfcomm,l2cap autofs420933 2 fuse 47837 1 tun12613 0 sunrpc154785 3 nf_conntrack_netbios_ns 6593 0 iptable_nat 8777 0 nf_nat 18393 1 iptable_nat iptable_mangle 6849 0 nf_conntrack_ipv4 11849 5 iptable_nat,nf_nat xt_state6209 2 nf_conntrack 51221 5 nf_conntrack_netbios_ns,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state ipt_REJECT 6977 2 ipt_LOG 9285 4 iptable_filter 6849 1 ip_tables 14033 3 iptable_nat,iptable_mangle,iptable_filter xt_tcpudp 6977 33 ip6t_REJECT 7617 2 ip6table_filter 6593 1 ip6_tables 15057 1 ip6table_filter x_tables 15557 9 xt_dscp,iptable_nat,xt_state,ipt_REJECT,ipt_LOG,ip_tables,xt_tcpudp,ip6t_REJECT,ip6_tables ipv6 238277 25 ip6t_REJECT dm_multipath 18505 0 parport_pc 26725 0 parport32173 1 parport_pc floppy 52229 0 i2c_piix4 11473 0 i2c_core 20949 1 i2c_piix4 pcspkr 6593 0 e100 33997 0 mii 8385 1 e100 dcdbas 10465 0 sr_mod 17541 0 cdrom 33249 1 sr_mod sg 31605 0 ata_piix 19397 0 libata131937 1 ata_piix raid1 22593 2 dm_snapshot18661 0 dm_zero 5825 0 dm_mirror 19521 0 dm_log 12229 1 dm_mirror dm_mod 48265 8 dm_multipath,dm_snapshot,dm_zero,dm_mirror,dm_log aic7xxx 101753 15 scsi_transport_spi 23233 1 aic7xxx sd_mod 26329 20 scsi_mod 123917 6 sr_mod,sg,libata,aic7xxx,scsi_transport_spi,sd_mod raid456 121681 1 async_xor 7361 1 raid456 async_memcpy6209 1 raid456 async_tx9869 3 raid456,async_xor,async_memcpy xor18633 2 raid456,async_xor ext3 110281 2 jbd41045 1 ext3 mbcache10309 1 ext3 uhci_hcd 22993 0 ohci_hcd 22853 0 ehci_hcd 32845 0 The command: ztcfg -v produces: Notice: Configuration file is /etc/zaptel.conf line 0: Unable to open master device '/dev/zap/ctl' 1 error(s) detected The command: ls -al /dev/ | grep zap produces nothing So, I am left wondering what has changed and why the Zaptel drivers are no longer loading. Can anyone suggest to me how I might go about troubleshooting this issue? Langdon ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Zaptel / TDM400P card stopped working
Hi Paul Thanks for the reply. I have removed and re-installed all of the Fedora Zaptel packages with Yum. I have the following installed: asterisk-zaptel 1.4.12.1-1.fc8 zaptel.i386 1.4.12.1-1.fc8 zaptel-devel.i386 1.4.12.1-1.fc8 zaptel-lib.i386 1.4.12.1-1.fc8 zaptel-utils.i386 1.4.12.1-1.fc8 The command: modprobe wctdm produces: FATAL: Module wctdm not found. The command: modprobe zaptel produces: FATAL: Module zaptel not found. Is there anything else that I should be doing? Regards, Langdon Paul Hales wrote: Have you tried loading the zaptel driver for your card manually? PaulH Langdon Stevenson wrote: Hi I have a Dell PE2300 with a Digium TDM400P line card in it (with one module to handle an inbound phone line). This is running on a Fedora 8 system with Asterisk 1.4.21.2-1.fc8 This system has been working nicely for about 12 months. After a recent move of office and relocation of the server Asterisk is back on line, but the TDM line card has stopped working. I have spent half a day working through Google search results, but no luck so far. The command: lspci -v produces: snip 02:0a.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface Subsystem: Unknown device b1d9:0001 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at e400 [size=256] Memory at f9ffd000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel modules: hisax The IRQ is not in use by any other device, so there is no conflict (this seems to be a common problem). The card has always been detected as a Tiger3XX. What stands out here to me is: Kernal modules: hisax I don't believe that this was the case when I first installed the card (but it was over a year ago, so I may be wrong). The hisax driver is blacklisted in /etc/modprobe.d/blacklist. The command: lsmod produces: Module Size Used by xt_dscp 6465 0 rfcomm 32721 0 l2cap 21953 9 rfcomm bluetooth 47013 6 rfcomm,l2cap autofs420933 2 fuse 47837 1 tun12613 0 sunrpc154785 3 nf_conntrack_netbios_ns 6593 0 iptable_nat 8777 0 nf_nat 18393 1 iptable_nat iptable_mangle 6849 0 nf_conntrack_ipv4 11849 5 iptable_nat,nf_nat xt_state6209 2 nf_conntrack 51221 5 nf_conntrack_netbios_ns,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state ipt_REJECT 6977 2 ipt_LOG 9285 4 iptable_filter 6849 1 ip_tables 14033 3 iptable_nat,iptable_mangle,iptable_filter xt_tcpudp 6977 33 ip6t_REJECT 7617 2 ip6table_filter 6593 1 ip6_tables 15057 1 ip6table_filter x_tables 15557 9 xt_dscp,iptable_nat,xt_state,ipt_REJECT,ipt_LOG,ip_tables,xt_tcpudp,ip6t_REJECT,ip6_tables ipv6 238277 25 ip6t_REJECT dm_multipath 18505 0 parport_pc 26725 0 parport32173 1 parport_pc floppy 52229 0 i2c_piix4 11473 0 i2c_core 20949 1 i2c_piix4 pcspkr 6593 0 e100 33997 0 mii 8385 1 e100 dcdbas 10465 0 sr_mod 17541 0 cdrom 33249 1 sr_mod sg 31605 0 ata_piix 19397 0 libata131937 1 ata_piix raid1 22593 2 dm_snapshot18661 0 dm_zero 5825 0 dm_mirror 19521 0 dm_log 12229 1 dm_mirror dm_mod 48265 8 dm_multipath,dm_snapshot,dm_zero,dm_mirror,dm_log aic7xxx 101753 15 scsi_transport_spi 23233 1 aic7xxx sd_mod 26329 20 scsi_mod 123917 6 sr_mod,sg,libata,aic7xxx,scsi_transport_spi,sd_mod raid456 121681 1 async_xor 7361 1 raid456 async_memcpy6209 1 raid456 async_tx9869 3 raid456,async_xor,async_memcpy xor18633 2 raid456,async_xor ext3 110281 2 jbd41045 1 ext3 mbcache10309 1 ext3 uhci_hcd 22993 0 ohci_hcd 22853 0 ehci_hcd 32845 0 The command: ztcfg -v produces: Notice: Configuration file is /etc/zaptel.conf line 0: Unable to open master device '/dev/zap/ctl' 1 error(s) detected The command: ls -al /dev/ | grep zap produces nothing So, I am left wondering what has changed and why the Zaptel drivers are no longer loading. Can anyone suggest to me how I might
Re: [asterisk-users] Zaptel / TDM400P card stopped working
h...I haven't used the RPM's before, so I can only guess that the RPM's are doing something not quite right. Is the asterisk-zaptel or the zaptel rpm supposed to provide the drivers? Does rpm -qf filename show the correct kernel version? If that fails, you could download the source files from the Asterisk site and build them yourself. PaulH Langdon Stevenson wrote: Hi Paul Thanks for the reply. I have removed and re-installed all of the Fedora Zaptel packages with Yum. I have the following installed: asterisk-zaptel 1.4.12.1-1.fc8 zaptel.i386 1.4.12.1-1.fc8 zaptel-devel.i386 1.4.12.1-1.fc8 zaptel-lib.i386 1.4.12.1-1.fc8 zaptel-utils.i386 1.4.12.1-1.fc8 The command: modprobe wctdm produces: FATAL: Module wctdm not found. The command: modprobe zaptel produces: FATAL: Module zaptel not found. Is there anything else that I should be doing? Regards, Langdon Paul Hales wrote: Have you tried loading the zaptel driver for your card manually? PaulH Langdon Stevenson wrote: Hi I have a Dell PE2300 with a Digium TDM400P line card in it (with one module to handle an inbound phone line). This is running on a Fedora 8 system with Asterisk 1.4.21.2-1.fc8 This system has been working nicely for about 12 months. After a recent move of office and relocation of the server Asterisk is back on line, but the TDM line card has stopped working. I have spent half a day working through Google search results, but no luck so far. The command: lspci -v produces: snip 02:0a.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface Subsystem: Unknown device b1d9:0001 Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at e400 [size=256] Memory at f9ffd000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel modules: hisax The IRQ is not in use by any other device, so there is no conflict (this seems to be a common problem). The card has always been detected as a Tiger3XX. What stands out here to me is: Kernal modules: hisax I don't believe that this was the case when I first installed the card (but it was over a year ago, so I may be wrong). The hisax driver is blacklisted in /etc/modprobe.d/blacklist. The command: lsmod produces: Module Size Used by xt_dscp 6465 0 rfcomm 32721 0 l2cap 21953 9 rfcomm bluetooth 47013 6 rfcomm,l2cap autofs420933 2 fuse 47837 1 tun12613 0 sunrpc154785 3 nf_conntrack_netbios_ns 6593 0 iptable_nat 8777 0 nf_nat 18393 1 iptable_nat iptable_mangle 6849 0 nf_conntrack_ipv4 11849 5 iptable_nat,nf_nat xt_state6209 2 nf_conntrack 51221 5 nf_conntrack_netbios_ns,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state ipt_REJECT 6977 2 ipt_LOG 9285 4 iptable_filter 6849 1 ip_tables 14033 3 iptable_nat,iptable_mangle,iptable_filter xt_tcpudp 6977 33 ip6t_REJECT 7617 2 ip6table_filter 6593 1 ip6_tables 15057 1 ip6table_filter x_tables 15557 9 xt_dscp,iptable_nat,xt_state,ipt_REJECT,ipt_LOG,ip_tables,xt_tcpudp,ip6t_REJECT,ip6_tables ipv6 238277 25 ip6t_REJECT dm_multipath 18505 0 parport_pc 26725 0 parport32173 1 parport_pc floppy 52229 0 i2c_piix4 11473 0 i2c_core 20949 1 i2c_piix4 pcspkr 6593 0 e100 33997 0 mii 8385 1 e100 dcdbas 10465 0 sr_mod 17541 0 cdrom 33249 1 sr_mod sg 31605 0 ata_piix 19397 0 libata131937 1 ata_piix raid1 22593 2 dm_snapshot18661 0 dm_zero 5825 0 dm_mirror 19521 0 dm_log 12229 1 dm_mirror dm_mod 48265 8 dm_multipath,dm_snapshot,dm_zero,dm_mirror,dm_log aic7xxx 101753 15 scsi_transport_spi 23233 1 aic7xxx sd_mod 26329 20 scsi_mod 123917 6 sr_mod,sg,libata,aic7xxx,scsi_transport_spi,sd_mod raid456 121681 1 async_xor 7361 1 raid456 async_memcpy6209 1 raid456 async_tx9869 3 raid456,async_xor,async_memcpy xor18633 2 raid456,async_xor ext3 110281 2 jbd41045 1 ext3 mbcache10309 1 ext3 uhci_hcd 22993 0 ohci_hcd 22853 0 ehci_hcd 32845 0
