<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Hi Tzafrir,<br><br>I am not sure what to look for, so I haveattached both the contents of /var/log/kern.log as well as the outputof dmesg. If you are looking for something specific, perhaps I can grepfor it and send you a smaller version. I have attached these as a tar ball to get below the 40K limit at which moderator approval is required. Thanks for the help.<br><br><br>> Date: Fri, 7 Sep 2007 10:26:11 +0300<br>> From: tzafrir.cohen@xorcom.com<br>> To: asterisk-users@lists.digium.com<br>> Subject: Re: [asterisk-users] New Installed X100p<br>> <br>> On Fri, Sep 07, 2007 at 12:02:29AM -0700, G B wrote:<br>> > <br>> > Hi,<br>> > <br>> > I just installed an X100p knockoff (OpenVox a100lp). I have seen my <br>> > errors in the mailing list but without resolution. It seems that the <br>> > . other problems had to do with IRQ sharing. <br>> <br>> Sharing IRQ lines should generally not prevent a driver from loading. It<br>> may be related to performance issues. It is also an easy target to blame<br>> performance issues for.<br>> <br>> > However, it doesn't seem <br>> > like the X100p is sharing an IRQ channel with anything. Any ideas?<br>> > <br>> > Also, I am running on Ubuntu Fiesty with Zaptel 1.4.5.1 and Asterisk <br>> > 1.4.11.1. Thanks in advance.<br>> > <br>> > My commands below are preceded with '#'<br>> > <br>> > # less /etc/zaptel.conf<br>> > <br>> > fxsks=1<br>> > loadzone=us<br>> > defaultzone=us<br>> > <br>> > # ztcfg -vv<br>> > <br>> > Zaptel Version: 1.4.5.1<br>> > Echo Canceller: MG2<br>> > Configuration<br>> > ======================<br>> > <br>> > <br>> > Channel map:<br>> > <br>> > Channel 01: FXS Kewlstart (Default) (Slaves: 01)<br>> > <br>> > 1 channels configured.<br>> > <br>> > ZT_CHANCONFIG failed on channel 1: No such device or address (6)<br>> <br>> Ignore that message for the moment. This is from the needless automatic<br>> run of ztcfg at module probe.<br>> <br>> > <br>> > # dmesg | grep wcfxo<br>> > <br>> > [ 39.337283] wcfxo: probe of 0000:00:0c.0 failed with error -5<br>> <br>> Now, please look at /var/log/kern.log, or in the output of dmesg and<br>> give a number of extra lines around that. Generally the driver has<br>> failed to start using that specific card.<br>> <br>> -- <br>> Tzafrir Cohen <br>> icq#16849755 jabber:tzafrir@jabber.org<br>> +972-50-7952406 mailto:tzafrir.cohen@xorcom.com <br>> http://www.xorcom.com iax:guest@local.xorcom.com/tzafrir<br>> <br>> _______________________________________________<br>> <br>> Sign up now for AstriCon 2007! September 25-28th. http://www.astricon.net/ <br>> <br>> --Bandwidth and Colocation Provided by http://www.api-digital.com--<br>> <br>> asterisk-users mailing list<br>> To UNSUBSCRIBE or update options visit:<br>> http://lists.digium.com/mailman/listinfo/asterisk-users<br><br /><hr />Make your little one a shining star! <a href='http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us' target='_new'>Shine on!</a></body>
</html>