Karsten Keil schrieb:
Nein, Neuinstallation macht keinen Sinn. Wie sehen denn /etc/sysconfig/isdn/cfg-contr0 und /etc/sysconfig/isdn/capi* aus ?
Soweit ich das beurteilen kann, ist alles im grünen Bereich.
Was steht in /var/log/messages beim booten ? Was ergibt 'lsmod |grep fcusb' ?
# grep messages fcusb Dec 14 07:40:18 boss kernel: fcusb2: unsupported module, tainting kernel. Dec 14 07:40:18 boss kernel: fcusb2: module license 'Proprietary' taints kernel. Dec 14 07:40:18 boss kernel: fcusb2: AVM FRITZ!Card USB v2 driver, revision 0.5.0 Dec 14 07:40:18 boss kernel: fcusb2: (fcusb2 built on Oct 6 2004 at 12:24:19) Dec 14 07:40:18 boss kernel: fcusb2: Loading... Dec 14 07:40:18 boss kernel: fcusb2: Driver 'fcusb2' attached to stack. (152) Dec 14 07:40:18 boss kernel: kcapi: Controller 1: fcusb2-0003 attached Dec 14 07:40:18 boss kernel: usbcore: registered new driver fcusb2 Dec 14 07:40:18 boss kernel: fcusb2: Loaded. #lsmod | grep fcusb fcusb2 608536 0 kernelcapi 45856 3 fcusb2,capidrv,capi usbcore 106724 6 usbserial,fcusb2,ehci_hcd,uhci_hcd #capi.conf.usb.contr0 #temp capi.conf generated by load-avmusb # card file proto io irq mem cardnr options fcusb2 fus3base.frm - - - - - #cfg-contr0 AREACODE="+49 6332" DIALPREFIX="" DRIVER="fcusb2" ISDNLOG_START="yes" NAME="AVM FRITZ!Card USB v2.1" PARA_SUBTYPE="3" PARA_TYPE="8003" PROTOCOL="euro" STARTMODE="onboot" UNIQUE="hSuP.mVMDu_CEMyC" #cfg-net0 CALLBACK="off" CBDELAY="2" CHARGEHUP="on" DEFAULTROUTE="yes" DYNAMICIP="yes" FIREWALL="no" IPADDR="" IPPPD_OPTIONS="" MSN="xxxxxx" MULTILINK="no" PROTOCOL="syncppp" PROVIDER="tonline" PTPADDR="" REMOTE_IN="" SECURE="on" STARTMODE="onboot" USERCONTROL="yes"