Lionel Elie Mamane schrieb:
> On Wed, Sep 05, 2007 at 11:00:39PM +0200, David Ayers wrote:
> 
>>Hardware: AVM ISDN-Controller B1 PCI v4.0
> 
> Did you also install / load the (non-free, binary-only) firmware?

No I didn't!  Did not realize I needed proprietary software for an
active CAPI 2.0 card!  [PS: I'd be very interested if there are PCI
Cards that will work 'out-of-the-box' with Etch or at least with free
software],

> Package isdnactivecards and download
> ftp://ftp.in-berlin.de/pub/capi4linux/firmware/b1/3-11-03/b1*.t4 into
> /usr/share/isdn/ and put a line like:
>  b1pci           b1.t4           DSS1    -       -       -       -
> into /etc/isdn/capi.conf and ( reboot or run
> "/etc/init.d/isdnactivecards start" ).

Thanks, I'm currently searching for the documentation I missed here...

I've now:
a) downloaded the 2 files into that directory
b) edited /etc/isdn/capi.conf to uncomment the entry you specified (it
was already there with a preceding #)
c) and then wanted to restart /etc/init.d/isdnactivecards yet that file
doesn't seem to part of the isdnactivecards (which was previously
automatically installed).

> You can test if everything is all right with "capiinfo" (as a user
> that has the right to read /dev/capi20).

Of course this still fails since the issue above hasn't been resolved yet.

> The error above shows that is not a permission issue. If it were a
> permission issue, the error would be EPERM. ENXIO means that the
> device is not present, not recognised, the driver not loaded,
> something like that. Probably here the firmware not loaded.

ACK. Thanks!

>>INTARS65:/tmp# ls -l /dev/capi*
>>crw-rw-rw- 1 root dialout 68, 0 2007-09-05 21:11 /dev/capi20
> 
> 
> You shouldn't need to make it world-readable nor
> world-writable. c2faxrcvd and hylafax run as a user member of
> dialout, so it should "just work" with mode 0660.

ACK, I've added the group "dialout" to the "uucp" user and reverted the
permissions.

>>I'd be grateful for a pointer (and some information whether this service 
>>should
>>provide the /dev/faxCAPI device that hylafax seems to expect.)
> 
> No, hylafax doesn't expect /dev/faxCAPI, but
> /var/spool/hylafax/dev/FIFO.faxCAPI , which is used as a pipe to
> communicate between hylafax and capi4hylafax (c2faxrcvd). Also don't
> forget to put
>  USE_FAXGETTY=no
> in /etc/default/hylafax .

ACK.  (Yet I hope I will still be able to receive faxes.)

> If this information solves your problem, please close the bug by
> sending mail to [EMAIL PROTECTED] .

Will do once I figure this out.
Thanks a lot for your help!

Cheers,
David


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to