<font size="2">BAD News! the card doesn't seem to work at all. even when it's detected by kernel it doesn't send/recv any interrupts in system. /proc/interrupts shows this.<br>i also send p to sysrq but nothing special was shown:
<br><br>Zapata Telephony Interface Registered on major 196<br>Zaptel Version: SVN-branch-1.2-r1686M Echo Canceller: KB1<br>ACPI: PCI interrupt 0000:03:01.0[A] -> GSI 48 (level, low) -> IRQ 82<br>PCI Config reg is 02900117
<br>WCTDM2400P: New Reg: fe590000!<br>Detected REG0: 00000100<br>Detected REG1: 00007849<br>Detected REG2: 0000001d<br>(pre) Reg fc is 50000027<br>(post) Reg fc is 50000024<br>Detected REG2: 0000ffff<br>wctdm2400p: reg is a04c0004
<br>Resetting the modules...</font><br><br><div><span class="gmail_quote">On 2/18/07, <b class="gmail_sendername">Tzafrir Cohen</b> <<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.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;">On Sat, Feb 17, 2007 at 11:52:32PM +0330, Paradise Dove wrote:<br>> On 2/17/07, Tzafrir Cohen <
<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a>> wrote:<br>> ><br>> >On Sat, Feb 17, 2007 at 07:52:25PM +0330, Paradise Dove wrote:<br>> >> Hi,<br>> >><br>> >> I'm running FC3 with kernel
2.6.11.<br>> >> All the binary files and zaptel kernel modules is not available to system at<br>> >> boot time.<br>> >> They are extracted in a ram disk at system startup and then zaptel modules
<br>> >> are loaded manually and so on.<br>> >> I have no problem with this boot routine and i've been tested all digium<br>> >> cards (expect tdm24) and they work fine till now.<br>> >>
<br>> >> The problem appeared when i purchased the new TDM2400 card. after installing<br>> >> this new card system stopped on modprobe wctdm24xxp ot boot time! (randomly<br>> >> sleeping on "Resetting the modules.." / "During Resetting the modules..."
<br>> >> and sometimes "After resetting the modules...) but no step further.<br>> >> Nothing happened till i killed modprobe manually so no modules detected on<br>> >> tdm24. (Port 1: Not Installed, ....)
<br><br>Strange. You can kill the modprobe process? In't probing done in kernel<br>with the process in state D?<br><br>To see what the kernel is doing: alt-sysrq-p (or: echo p >/proc/sysrq-trigger )<br><br>> >> My motherboard is a brand new Intel 3010 chipset from supermicro with
<br>> >> 3.3Vpci slots. i also changed the motherboard to Intel 7230 chipset<br>> >> with 5V slot<br>> >> but nothing changed. I also switched back to zaptel-1.2.13 and removed the<br>> >> modules from the board and re-inserted them as digium support recommended,
<br>> >> but nothing changed. I also changed to 2.6.12 kernel but still the same<br>> >> problem.<br>> >><br>> >> Finally i changed the system startup routine and copied all extracted zaptel
<br>> >> files to hard-disk into the standard location in kernel dirs and found that<br>> >> now system starts-up with no problem and detects TDM24 at boot time!!!<br>> ><br>> >Hmmm...<br>> >
<br>> >How exactly do you load the modules? With insmod or modprobe?<br>><br>><br>> when i put zaptel modules in kernel dirs. it detects all the needed modules.<br>> and from the dmesg it seems (as it should be) to load zaptel first and then
<br>> wctdm24xxp. so i don't need to do a insmod or modprobe at all. the problem<br>> comes when i rmmod these modules and modprobe or insmod them again.<br><br>This is run somewhere in rc.sysinit . Specifically, where it loads
<br>modules of "other" devices.<br><br>><br>> ><br>> >> it seemed that the problem is that the wctdm24xxp needs to be detected<br>> >at<br>> >> boot time by the kernel.<br>> >> But now the problem is that when i rmmod the wctdm24xxp module and
<br>> >modprobe<br>> >> it again still system doesn't detect it and sleeps on modprobe utill i<br>> >kill<br>> >> it.<br>> >><br>> >> i dont have such a problem with all other cards from digium.
<br>> >> i think this is a weird problem with wctdm24xxp driver.<br>> ><br>> >Another theory: only the first modprobe after a boot is successful, and<br>> >the modules are loaded automatically at boot.
<br>><br>><br>> no it's not true that the first modprobe is the successful one. it seems<br>> the card works when kernel detects it and loads the modules itself.<br>> something that happens before init scripts.
<br>><br>> Test: remove the modules copletely, reboot, re-add the modules and<br>> >modprobe again.<br>><br>><br>> you mean remove the physical modules? if yes i've done it once. made no<br>> sense
<br><br>Yes. A long-shot, but easy to accomploish (if you can afford a reboot).<br><br><br>--<br> Tzafrir Cohen<br>icq#16849755 <a href="mailto:jabber:tzafrir@jabber.org">jabber:tzafrir@jabber.org
</a><br>+972-50-7952406 mailto:<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a><br><a href="http://www.xorcom.com">http://www.xorcom.com</a> <a href="http://iax:guest@local.xorcom.com/tzafrir">
iax:guest@local.xorcom.com/tzafrir</a><br>_______________________________________________<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:
<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></blockquote></div><br>