Problem testing E1 link

historical

I think I still have a problem with mISDN cause I checked the RJ45 cable
connections and it's ok.
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).
In my menuconfig I put an * for :
<*> Modular ISDN driver ---> <*>Digital Audio Processing of transparent data
                                          <*>ISDN over IP tunnel
                                          <*>Support for HFC PCI cards
                                          <*>Support for HFC multiport cards
(HFC-4S/8S/E1)

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.

I can't even do "modprobe mISDN_core" for exemple. mISDN_core is not found.
So I checked the /lib/modules/2.6.27.4/ directories.
I didn't find any mISDN directory in /lib/modules/
2.6.27.4/kernel/drivers/isdn
but I found it in /lib/modules/2.6.27.4/build/drivers/isdn with about 60
files inside (.o, .c, .h and .ko)
and I found it also in /lib/modules/2.6.27.4/source/drivers/isdn (exactly
the same content in mISDN directory)

Is this normal?

Thanks
Eric Cathelinaud

2009/5/26, Harald Welte <laforge at gnumonks.org>:
>
> On Mon, May 25, 2009 at 03:08:10PM +0200, Eric Cathelinaud wrote:
>
> > I didn't doanwload:
> > -the SAFETY LOAD software
> > -the BTS software
> > Is it necessary since I can reach Phase 3 and since I can see the
> Firmware
> > Code Number?
>
> no, it is not. the firmware is completely installed on your system,
> otherwise the TRX0 would never get into 'Load"
>
> > Mon May 25 16:07:39 2009 <1000> input/misdn.c:125 alen =6, dev(0)
> channel(0)
> > sapi(63) tei(127)
> > Mon May 25 16:07:39 2009 <1000> input/misdn.c:128 <= len = 12, prim(0x8)
> > id(0x7f3f): DL_INFORMATION_IND
> > Mon May 25 16:07:39 2009 <1000> input/misdn.c:135 DL_INFORMATION_IND: use
> > channel(0) sapi(63) tei(127) for now
> > mISDN message for unknown sign_link
>
> this basically means that the TEI manager was instantiated on the E1 link,
> but no TEIs were established, most likely a layer 1 problem...
>
> Regards,
> --
> - Harald Welte <laforge at gnumonks.org>
> http://laforge.gnumonks.org/
>
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
>                                                  (ETSI EN 300 175-7 Ch. A6)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20090527/3c05eceb/attachment.htm>