Re: c2faxrecv-mISDNcapid

merk <[email protected]> Mon, 19 Feb 2018 08:57:11 +0100
Newsgroups gmane.linux.isdn.i4l.user
Message-ID <[email protected]>
Hello,


after several tries  and searching and reading in the net i am not
able despite your aid to get this running.

Cause of great lack of basic knowledge on my side I give it up

and thank you all for your time and answers.

Have a nice time

Jürgen

P.S. My  hope is that the belug fcpci dkms module will run again in
newer kernels.


Am 05.02.2018 um 08:32 schrieb jugge:
>
> Am 05.02.2018 um 07:06 schrieb jm:
>> Hello
>>
>> Am 03.02.2018 um 14:25 schrieb Christoph Schulz:
>>> Hello!
>>>
>>> jm <[email protected]> schrieb am Fr 02 Feb 2018 04:48:04 CET:
>>>
>>>
>>>
>>>> Feb 01 17:25:07 arch c2faxrecv[3038]:             capi20.c:
>>>> 164              CapiDebug():[capi20_isinstalled]: other loop - module:
>>>> misdn
>>>> Feb 01 17:25:07 arch c2faxrecv[3038]:             capi20.c:
>>>> 164              CapiDebug():[capi20_isinstalled]: capi_fd: -1
>>> That's bad, because IsInstalled() returned an invalid file handle (-1).
>>> That happens if mISDNcapid is not running, or more exactly, if the
>>> corresponding UNIX socket cannot be opened (whose upstream path is
>>> /var/run/mISDNcapid/sock). And mISDNcapid is perhaps not running because
>>> /etc/capi20.conf did not contain the correct mISDN line, which must be
>>>
>>> mISDN 0 1 1
>>>
>>> or (shorter)
>>>
>>> mISDN 0
>>>
>> I ask me how can I open the above sock?
>>
>> After having my original /etc/capi20.conf on the right place the output
>> if I do "systemctl status mISDNcapid" is:
>>
>> """mISDNcapid.service - mISDN CAPI daemon
>>     Loaded: loaded (/usr/lib/systemd/system/mISDNcapid.service; enabled;
>> vendor p
>>     Active: active (running) since Mon 2018-02-05 06:39:13 CET; 11min ago
>>    Process: 281 ExecStart=/usr/bin/mISDNcapid (code=exited, status=0/SUCCESS)
>>   Main PID: 298 (mISDNcapid)
>>      Tasks: 1 (limit: 4915)
>>     CGroup: /system.slice/mISDNcapid.service
>>             └─298 /usr/bin/mISDNcapid
>>
>> Feb 05 06:39:13 arch systemd[1]: Starting mISDN CAPI daemon...
>> Feb 05 06:39:13 arch mISDNcapid[281]: Controller 2 not detected - ignored
>> Feb 05 06:39:13 arch mISDNcapid[281]: debug=0x13 do_daemon=1
>> config=/etc/capi20.
>> Feb 05 06:39:13 arch systemd[1]: Started mISDN CAPI daemon. """
>>
>>
>>
>> Reading from misdn site the "howto for debian"there are, after compiling
>> and installing misdn and misdnuser two modules mISDN_core and
>> mISDN_l1loop, both of them i am missing on my arch.
> Sorry i am wrong, mISDN_core is there(see below), i am
> missing l1loop_mISDN
>
> Jürgen
>>
>> Could it be that I have modules loaded that should be blacklisted?
>> After lsmod | egrep  'capi|avm|isdn|hisax' I get:
>>
>>
>> mISDN_core            118784  6 mISDNipac,avmfritz
>> c
>>
>>
>> _______________________________________________
>> isdn4linux mailing list
>> [email protected]
>> https://www.isdn4linux.de/mailman/listinfo/isdn4linux
> _______________________________________________
> isdn4linux mailing list
> [email protected]
> https://www.isdn4linux.de/mailman/listinfo/isdn4linux

_______________________________________________
isdn4linux mailing list
[email protected]
https://www.isdn4linux.de/mailman/listinfo/isdn4linux