<div>I think I still have a problem with mISDN cause I checked the RJ45 cable connections and it's ok.</div>
<div>If I try a lsmod I can't see any mISDN_*** modules. But the line in /boot/grub/menu.lst "hfcmulti.dslot=1" is recognized at the boot (no more ignored).</div>
<div>In my menuconfig I put an * for :</div>
<div><*> Modular ISDN driver ---> <*>Digital Audio Processing of transparent data</div>
<div> <*>ISDN over IP tunnel</div>
<div> <*>Support for HFC PCI cards</div>
<div> <*>Support for HFC multiport cards (HFC-4S/8S/E1)</div>
<div> </div>
<div>Is there something more to do for mISDN? I saw on mISDN.org that mISDNv2 is already in the kernel >= 2.6.27 so I were thinking it should work directly.</div>
<div> </div>
<div>I can't even do "modprobe mISDN_core" for exemple. mISDN_core is not found.</div>
<div>So I checked the /lib/modules/<a href="http://2.6.27.4/">2.6.27.4/</a> directories.</div>
<div>I didn't find any mISDN directory in /lib/modules/<a href="http://2.6.27.4/kernel/drivers/isdn">2.6.27.4/kernel/drivers/isdn</a></div>
<div>but I found it in /lib/modules/<a href="http://2.6.27.4/build/drivers/isdn">2.6.27.4/build/drivers/isdn</a> with about 60 files inside (.o, .c, .h and .ko)</div>
<div>and I found it also in /lib/modules/<a href="http://2.6.27.4/source/drivers/isdn">2.6.27.4/source/drivers/isdn</a> (exactly the same content in mISDN directory)<br> </div>
<div>Is this normal?</div>
<div> </div>
<div>Thanks</div>
<div>Eric Cathelinaud</div>
<div><br> </div>
<div><span class="gmail_quote">2009/5/26, Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Mon, May 25, 2009 at 03:08:10PM +0200, Eric Cathelinaud wrote:<br><br>> I didn't doanwload:<br>> -the SAFETY LOAD software<br>
> -the BTS software<br>> Is it necessary since I can reach Phase 3 and since I can see the Firmware<br>> Code Number?<br><br>no, it is not. the firmware is completely installed on your system, otherwise the TRX0 would never get into 'Load"<br>
<br>> Mon May 25 16:07:39 2009 <1000> input/misdn.c:125 alen =6, dev(0) channel(0)<br>> sapi(63) tei(127)<br>> Mon May 25 16:07:39 2009 <1000> input/misdn.c:128 <= len = 12, prim(0x8)<br>> id(0x7f3f): DL_INFORMATION_IND<br>
> Mon May 25 16:07:39 2009 <1000> input/misdn.c:135 DL_INFORMATION_IND: use<br>> channel(0) sapi(63) tei(127) for now<br>> mISDN message for unknown sign_link<br><br>this basically means that the TEI manager was instantiated on the E1 link,<br>
but no TEIs were established, most likely a layer 1 problem...<br><br>Regards,<br>--<br>- Harald Welte <<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>> <a href="http://laforge.gnumonks.org/">http://laforge.gnumonks.org/</a><br>
============================================================================<br>"Privacy in residential applications is a desirable marketing option."<br> (ETSI EN 300 175-7 Ch. A6)<br>
</blockquote></div><br>