Kevin P. Fleming wrote:
I've just located an E400P from our graveyard of old cards... if it
works, I'll be able to solve this problem in the morning.
This has been fixed in revision 3863 of the 1.4 branch; it's a one line
fix that you should be able to easily apply to existing Zaptel source
Thank you very much!!!
What was the one line fix?
Also, what file was the problem in? Also, if you know the line number or
function it was in, that would be nice too. I'd do a diff, but I assume
there has been other changes since 1.4.9 was released.
Thanks again!
-- Nick
On Thu, 21 Feb
On Thu, Feb 21, 2008 at 02:17:20PM -0500, Nick Seraphin wrote:
Thank you very much!!!
What was the one line fix?
Also, what file was the problem in? Also, if you know the line number or
function it was in, that would be nice too. I'd do a diff, but I assume
there has been other
I have a Pentium 4 2.4ghz CPU with a T400P on CentOS 5.1 and I can't get
Zaptel 1.4.9 to run. When I compile and then start zaptel start I get a
kernel panic as well.
Zaptel 1.4.7 compiles and runs just fine. Under 1.4.9 tor2 loads and
wastes the system. I too have no resources to capture the
On Wed, Feb 20, 2008 at 06:30:13PM -0500, RE Kushner List Account wrote:
I have a Pentium 4 2.4ghz CPU with a T400P on CentOS 5.1 and I can't get
Zaptel 1.4.9 to run. When I compile and then start zaptel start I get a
kernel panic as well.
Zaptel 1.4.7 compiles and runs just fine. Under
RE Kushner List Account wrote:
Zaptel 1.4.7 compiles and runs just fine. Under 1.4.9 tor2 loads and
wastes the system. I too have no resources to capture the panic output.
I've just located an E400P from our graveyard of old cards... if it
works, I'll be able to solve this problem in the
The system won't boot at all if the tor2.ko file exists. Period. It
doesn't matter what is in the startup scripts. Even if I DELETE the
startup scripts, it still crashes until I go in with a rescue CD and
delete tor2.ko from the modules directory for the kernel.
It's a full kernel panic...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would try make clean/make/make install.
also add tor2 to the black list and remove it from any zaptel init stuff.
Finally once your systems up (note asterisk wont be) try loading the
module with insmod.
If it panics this may give you a better
Hi all... I did some Google searches and didn't find any info on this so
I'm posting it here... if this was recently discussed, I apologize for the
duplication -- please point me to the appropriate thread.
System Description:
Supermicro SuperServer 5015M-MF w/ PDSMi Motherboard
