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? 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" ). You can test if everything is all right with "capiinfo" (as a user that has the right to read /dev/capi20). > I copyed and edited capi4hylafax to start the program directly with strace and > I hope I can attach the file to this report. I _believe_ the interresting > output > is: > open("/dev/capi20", O_RDWR) = -1 ENXIO (No such device or address) > yet I've already changed the permissions to that device to: 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. > 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. > 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 . If this information solves your problem, please close the bug by sending mail to [EMAIL PROTECTED] . -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
