L
2005-Dec-09 02:59 UTC
[Asterisk-Users] /dev/zap/ctl or /dev/zapctl cause ztdummy in init.d failed
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Hi list,<br> <br> I m wondering is there a bug regarding the zaptel/ztdummy? or it is just my misconfiguration?<br> As the log shown zaptel is refering to the /dev/zap/ctl when it suppose to refer to /dev/zapctl as i m concering.<br> <br> I m using<br> 1) zaptel-1.2.1<br> 2) kernel 2.6.12-1.1381_FC3<br> 3) no zap's PCI hardware<br> <br> On the second try I started the modprobe manually and the system shown the statement ("line 0: Unable to open master device '/dev/zap/ctl'").<br> But when i crosscheck using lsmod, ztdummy is actually loaded into the kernel.<br> And this line somehow cause init.d/zaptel failed to load the later half of the script.<br> <br> <hr size="2" width="100%"><b>[root@super ~]#</b> modprobe zaptel<br> <b>[root@super ~]#</b> lsmod | grep z<br> Module Size Used by<br> zaptel 208132 0<br> crc_ccitt 2113 1 zaptel<br> dm_zero 2113 0<br> dm_mod 57333 6 dm_snapshot,dm_zero,dm_mirror<br> <b>[root@super ~]#</b> modprobe ztdummy<br> Notice: Configuration file is /etc/zaptel.conf<br> line 0: Unable to open master device '/dev/zap/ctl'<br> <br> 1 error(s) detected<br> <br> FATAL: Error running install command for ztdummy<br> <b>[root@super ~]#</b> lsmod | grep z<br> Module Size Used by<br> ztdummy 3924 0<br> zaptel 208132 1 ztdummy<br> crc_ccitt 2113 1 zaptel<br> dm_zero 2113 0<br> dm_mod 57333 6 dm_snapshot,dm_zero,dm_mirror<br> <hr size="2" width="100%"> <br> Any idea?<br> <br> -L- </body> <br />-- <br />This message has been scanned for viruses and <br />dangerous content by <a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is <br />believed to be clean. </html>
Tony Mountifield
2005-Dec-09 04:03 UTC
[Asterisk-Users] Re: /dev/zap/ctl or /dev/zapctl cause ztdummy in init.d failed
In article <4399559E.5030706@darkcolt.com>, L <asterisk@darkcolt.com> wrote:> -=-=-=-=-=- > Hi list, > > I m wondering is there a bug regarding the zaptel/ztdummy? or it is just my misconfiguration? > As the log shown zaptel is refering to the /dev/zap/ctl when it suppose to refer to > /dev/zapctl as i m concering. > > I m using > 1) zaptel-1.2.1 > 2) kernel 2.6.12-1.1381_FC3 > 3) no zap's PCI hardware > > On the second try I started the modprobe manually and the system shown the statement ("line > 0: Unable to open master device '/dev/zap/ctl'").Have you followed the instructions in zaptel/README.udev? Cheers Tony -- Tony Mountifield Work: tony@softins.co.uk - http://www.softins.co.uk Play: tony@mountifield.org - http://tony.mountifield.org
Steve Ringwald
2005-Dec-09 04:37 UTC
[Asterisk-Users] /dev/zap/ctl or /dev/zapctl cause ztdummy in init.d failed
Are you running udev? If so, you need to follow the directions in README.udev... http://www.voip-info.org/wiki-Asterisk+Fedora+Core+3 Help!: line 146: Unable to open master device '/dev/zap/ctl' You are probably running udev and don't know it.. were you paying attention during the make? If you were, you would have seen this fly by: **** Dynamic filesystem detected -- not creating device nodes **** If you are running udev, read README.udev If you didn't, try doing a: [root@localhost zaptel]# make devices In your zaptel directory and see if it comes up.. If it does, view the suggested README.udev. *Run "udevstart" to re-read the new configuration and to create the zap nodes.* *Note:* My Fedora Core 3 install which came with a 2.6.9 kernel did just this. If you follow the directions in README.udev, you will fix this. L wrote:> Hi list, > > I m wondering is there a bug regarding the zaptel/ztdummy? or it is > just my misconfiguration? > As the log shown zaptel is refering to the /dev/zap/ctl when it > suppose to refer to /dev/zapctl as i m concering. > > I m using > 1) zaptel-1.2.1 > 2) kernel 2.6.12-1.1381_FC3 > 3) no zap's PCI hardware > > On the second try I started the modprobe manually and the system shown > the statement ("line 0: Unable to open master device '/dev/zap/ctl'"). > But when i crosscheck using lsmod, ztdummy is actually loaded into the > kernel. > And this line somehow cause init.d/zaptel failed to load the later > half of the script. > > ------------------------------------------------------------------------ > *[root@super ~]#* modprobe zaptel > *[root@super ~]#* lsmod | grep z > Module Size Used by > zaptel 208132 0 > crc_ccitt 2113 1 zaptel > dm_zero 2113 0 > dm_mod 57333 6 dm_snapshot,dm_zero,dm_mirror > *[root@super ~]#* modprobe ztdummy > Notice: Configuration file is /etc/zaptel.conf > line 0: Unable to open master device '/dev/zap/ctl' > > 1 error(s) detected > > FATAL: Error running install command for ztdummy > *[root@super ~]#* lsmod | grep z > Module Size Used by > ztdummy 3924 0 > zaptel 208132 1 ztdummy > crc_ccitt 2113 1 zaptel > dm_zero 2113 0 > dm_mod 57333 6 dm_snapshot,dm_zero,dm_mirror > ------------------------------------------------------------------------ > > Any idea? > > -L- > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is > believed to be clean. > ------------------------------------------------------------------------ > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >