Turns out this appears to be related to hald -- the hardware abstraction layer daemon running on Centos. I had the almost identical situation occur with a completely separate system which I loaded Trixbox up on, with a single Digium TDM400P card in it. Struggled for several hours over the weekend trying to figure it out.
<br><br>I ended up shutting off all the services I didn't specifically need, and turned them back on one at a time (turned out, hald was the first I tried -- I was most suspicious with it). As soon as I started it up, it locked the system up.
<br><br>Turned all the other services back on, leaving hald off, and the system is running fine.<br><br>Did the same with the original problem system, and now have no problems with the Rhino cards either!<br><br><div><span class="gmail_quote">
On 1/23/07, <b class="gmail_sendername">Barry D. Hassler</b> <<a href="mailto:barry.hassler@gmail.com">barry.hassler@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Folks,<br><br>Struggling with a new * installation with 2 <span id="st" name="st" class="st">Rhino</span> R2T1 cards. For some reason, the system is locking up tight when you run ztcfg to configure the card(s). Configuration is asterisk
1.2.14, zaptel 1.2.12, and <span id="st" name="st" class="st">rhino</span>'s
1.05 rxt1 drivers. The cards seem to load fine with a "modprobe rxt1", but once you run "ztcfg -vvv", the system will lock up within a few seconds, no errors reported in logs or console.<br><br>I'm stumped,
<span id="st" name="st" class="st">Rhino</span> is stumped, and I haven't seen any other threads of this nature.
<br clear="all"><br>-- <br><span class="sg">Barry D. Hassler
</span></blockquote></div><br><br clear="all"><br>-- <br>Barry D. Hassler