On 05/26/2010 08:00 PM, cov...@ccs.covici.com wrote:
From another thread, I blacklisted netjet and now things are working.
But I wonder what is going on here and where did netjet come from -- it
doesn't look like an dahdi module to me.
It comes from mISDN. It is a very badly misbehaving
Tzafrir Cohen tzafrir.co...@xorcom.com wrote:
On Sun, May 23, 2010 at 04:54:38AM -0400, cov...@ccs.covici.com wrote:
Hi. I am having problems with dahdi using kernel 2.6.32. I am using
2.6.30 kernel and it works fine -- here is the output of dahdi_cfg -vv
++ dahdi_cfg -vv
DAHDI Tools
Hi. I am having problems with dahdi using kernel 2.6.32. I am using
2.6.30 kernel and it works fine -- here is the output of dahdi_cfg -vv
++ dahdi_cfg -vv
DAHDI Tools Version - SVN-trunk-r8670
DAHDI Version: SVN-trunk-r7445M
Echo Canceller(s):
Configuration
==
Channel
On Sun, May 23, 2010 at 04:54:38AM -0400, cov...@ccs.covici.com wrote:
Hi. I am having problems with dahdi using kernel 2.6.32. I am using
2.6.30 kernel and it works fine -- here is the output of dahdi_cfg -vv
++ dahdi_cfg -vv
DAHDI Tools Version - SVN-trunk-r8670
DAHDI Version:
Tzafrir Cohen tzafrir.co...@xorcom.com wrote:
On Sun, May 23, 2010 at 04:54:38AM -0400, cov...@ccs.covici.com wrote:
Hi. I am having problems with dahdi using kernel 2.6.32. I am using
2.6.30 kernel and it works fine -- here is the output of dahdi_cfg -vv
++ dahdi_cfg -vv
DAHDI Tools
On Sun, May 23, 2010 at 09:40:25AM -0400, cov...@ccs.covici.com wrote:
How would the device be created, I certainly did not do it myself -- I
thought modprobing the modules would do such a thing. I will certainly
try lsdahdi when I can reboot into the new kernel.
The device is created is the
