Hallo! Ich habe jetzt nochmal was anderes versucht: ich habe nochmals den AVM-Treiber installiert (fcpci.ko) und dafür dann noch ein paar kleine Änderungen vorgenommen (Ausgangszustand: laufendes Capi-System mit Hilfe von capi-thepenguin.de-Edition): - /etc/modprobe.conf: alias /dev/capi20 fcpci alias char-major-68-0 fcpci alias char-major-43 fcpci alias char-major-44 fcpci alias char-major-45 fcpci - /etc/init.d/i4l_hardware ######################################################### # AVM-B1 / AVM Capi Driver ######################################################### if test ! -z "$AVM_IDX" ; then CONTR=1 echo "Loading CAPI4Linux AVM-Driver ..." /usr/sbin/capiinit start echo "Loading bridge for ISDN4Linux ..." modprobe -v fcpci if test $? -ne 0; then echo "" echo "Loading of bridge for ISDN4Linux failed!" echo "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~" echo "Check /var/log/messages and /var/log/warn." echo "You will not be able to use applications using" echo "ISDN4Linux until loading is successful." echo "Also ISDNlog won't be started." echo "" ISDNLOG_START="no" LOAD_OK="yes" else LOAD_OK="yes" fi # To recover the original file "i4l_hardware", please # take a look into "i4l_hardware.old"! fi [...] if test "$LOAD_OK" = "yes"; then # start iprofd not longer recommended # test "$I4L_IPROFD" = "yes" && ($SBIN/iprofd /etc/isdn/modemsettings &) # start isdnlog if test "$ISDNLOG_START" = "yes"; then for optionfile in /etc/isdn/isdnlog.*.options; do if test -f $optionfile; then device=${optionfile#*.} device=${device%.*} echo "Starting isdnlog with $optionfile for $device..." $SBIN/isdnlog -f $optionfile /dev/$device else echo "Starting isdnlog with defaults for /dev/isdnctrl0..." $SBIN/isdnlog -D -l1015 -x4087 -M -n -W80 /dev/isdnctrl0 & fi done fi weiterhin ergibt "mount": root@debian:/etc > mount /dev/hda6 on / type ext2 (rw) proc on /proc type proc (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/hda1 on /boot type ext2 (rw) /dev/hde5 on /home type ext2 (rw) capifs on /dev/capi type capifs (rw,mode=0666) root@debian:/etc > wobei ich nicht genau weiss, woher der letzte Eintrag kommt. wenn ich dann "rci4l_hardware start" mache, kommt: root@debian:/etc > rci4l_hardware start Loading ISDN drivers ... Loading CAPI4Linux AVM-Driver ... Loading bridge for ISDN4Linux ... FATAL: Module fcpci already in kernel. Loading of bridge for ISDN4Linux failed! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check /var/log/messages and /var/log/warn. You will not be able to use applications using ISDN4Linux until loading is successful. Also ISDNlog won't be started. root@debian:/etc > lsmod Module Size Used by fcpci 504020 2 reiserfs 309056 2 pppoe 11456 2 pppox 3464 1 pppoe ipv6 236736 12 ppp_generic 26700 6 pppoe,pppox slhc 6912 1 ppp_generic sis900 17092 0 8139too 22272 0 capi 15744 6 capifs 4424 2 capi kernelcapi 45152 2 fcpci,capi ip_nat_ftp 5440 0 ip_conntrack_ftp 71712 1 ip_nat_ftp rtc 11616 0 root@debian:/etc/init.d > capiinfo Number of Controllers : 1 Controller 1: Manufacturer: AVM GmbH CAPI Version: 2.0 Manufacturer Version: 3.101-02 (49.18) Serial Number: 1000001 BChannels: 2 Global Options: 0x00000039 internal controller supported DTMF supported Supplementary Services supported channel allocation supported (leased lines) B1 protocols support: 0x4000011f 64 kbit/s with HDLC framing 64 kbit/s bit-transparent operation V.110 asynconous operation with start/stop byte framing V.110 synconous operation with HDLC framing T.30 modem for fax group 3 Modem asyncronous operation with start/stop byte framing B2 protocols support: 0x00000b1b ISO 7776 (X.75 SLP) Transparent LAPD with Q.921 for D channel X.25 (SAPI 16) T.30 for fax group 3 ISO 7776 (X.75 SLP) with V.42bis compression V.120 asyncronous mode V.120 bit-transparent mode B3 protocols support: 0x800000bf Transparent T.90NL, T.70NL, T.90 ISO 8208 (X.25 DTE-DTE) X.25 DCE T.30 for fax group 3 T.30 for fax group 3 with extensions Modem 0100 0200 39000000 1f010040 1b0b0000 bf000080 00000000 00000000 00000000 00000000 00000000 00000000 01000001 00020000 00000000 00000000 00000000 Supplementary services support: 0x000003ff Hold / Retrieve Terminal Portability ECT 3PTY Call Forwarding Call Deflection MCID CCBS root@debian:/etc/init.d > Zudem verabschiedet sich sofort das isdnlog wieder, wenn ich die i4l_hardware so veränder, dass er in jedem Falle die ISDNLOG_STARt auf "yes" setzt, andernfalls wird´s anscheinend gar nicht erst gestartet: May 31 11:39:47 debian kernel: fcpci: module license 'Proprietary' taints kernel. May 31 11:39:47 debian kernel: fcpci: AVM FRITZ!Card PCI driver, revision 0.6.1 May 31 11:39:47 debian kernel: fcpci: (fcpci built on May 30 2004 at 17:40:09) May 31 11:39:47 debian kernel: PCI: Found IRQ 12 for device 0000:00:0b.0 May 31 11:39:47 debian kernel: PCI: Sharing IRQ 12 with 0000:00:02.1 May 31 11:39:47 debian kernel: fcpci: AVM FRITZ!Card PCI found: port 0xc400, irq 12 May 31 11:39:47 debian kernel: fcpci: Loading... May 31 11:39:47 debian kernel: fcpci: Driver 'fcpci' attached to stack. (152) May 31 11:39:47 debian kernel: fcpci: Stack version 3.11-02 May 31 11:39:47 debian kernel: kcapi: Controller 1: fcpci-c400-12 attached May 31 11:39:47 debian kernel: kcapi: card 1 "fcpci-c400-12" ready. May 31 11:39:47 debian kernel: fcpci: Loaded. May 31 11:39:47 debian isdnlog: isdnlog: Can't open /dev/isdnctrl0 (No such device or address) May 31 11:39:47 debian isdnlog: isdnlog Version 4.29 exiting May 31 11:39:47 debian isdnlog: exit now 2 Im Grunde scheint es für mich so, dass er 1) einen woher-auch-immer-stammenden Eintrag hat, der für ein mount capifs /dev/capi type capifs sorgt (und mir damit die Möglichkeit nimmt, ein sauberes rci4l_hardware start laufen zu lassen 2) ich dem isdnlog irgendwie mitteilen muss, dass es es jetzt nicht mehr mit dem Device isdnctrll1, sondern mit dem /dev/capi* zu tun hat (eventl. z.B. auch mittels Symlink) kann man das regeln? Wie? Danke! cu, Stefan