Mailinglist Archive: opensuse-isdn-de (330 mails)

["Lothar Reupsch" <lothar@xxxxxxxxxx>]

Hi, beim Booten bekomme ich folgende, teilweise abweichende Treiberinfos:

(Was ist eigentlich mit der sogenannten Firmware? Muß ich da noch was
machen?)

----- Original Message -----
From: "Sebastian Huber" <sebastian-huber@xxxxxx>
To: <suse-isdn@xxxxxxxx>
Sent: Sunday, August 25, 2002 2:06 AM
Subject: Re: [suse-isdn] SuSE 8.0 und AVM Card USB 2.0


> Hi,
> und beim Booten gibt es folgende Treiberinfos:

> usb-uhci.c: USB UHCI at I/O 0x1c20, IRQ 11
usb-uhci.c: USB UHCI at I/O 0x1000, IRQ 5

> usb-uhci.c: Detected 2 ports
usb-uhci.c: Detected 2 ports

> usb.c: new USB bus registered, assigned bus number 2
usb.c: new USB bus registered, assigned bus number 1

> hub.c: USB hub found
hub.c: USB hub found

> hub.c: 2 ports detected
hub.c: 2 ports detected

> usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver

> hub.c: USB new device connect on bus1/1, assigned device number 2
hub.c: USB new device connect on bus1/2, assigned device number 2

> usb.c: USB device 2 (vend/prod 0x57c/0x1000) is not claimed by any active
driver.
usb.c: USB device 2 (vend/prod 0x57c/0x1000) is not claimed by any active
driver

> CAPI-driver Rev 1.1.4.1: loaded
CAPI-driver Rev 1.1.4.1: loaded

> fcusb2: AVM FRITZ!Card USB v2 driver, revision 0.2
fcusb2: AVM FRITZ!Card USB v2 driver, revision 0.2

> fcusb2: (fcusb2 built on Aug 19 2002 at 16:02:15)
fcusb2: (fcusb2 built on Jun  1 2002 at 02:15:10)

> fcusb2: Loading...
fcusb2: Loading...

> kcapi: driver fcusb2 attached
kcapi: driver fcusb2 attached

> usb.c: registered new driver fcusb2
usb.c: registered new driver fcusb2

> fcusb2: Driver 'fcusb2' attached to stack
fcusb2: Driver 'fcusb2' attached to stack

> kcapi: Controller 1: fritz-usb attached
kcapi: Controller 1: fritz-usb attached

> fcusb2: Loaded.
fcusb2: Loaded

> capifs: Rev 1.1.4.1
> capi20: started up with major 68
> kcapi: capi20 attached
> capi20: Rev 1.1.4.2: started up with major 68 (middleware+capifs)
> CSLIP: code copyright 1989 Regents of the University of California
> ISDN subsystem Rev: 1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1 loaded
> kcapi: capidrv attached
> kcapi: appl 1 up
> capidrv: Rev 1.1.4.1: loaded
> fcusb2: Stack version 3.09-10
> kcapi: card 1 "fritz-usb" ready.
> kcapi: notify up contr 1
> capidrv: controller 1 up
> capidrv-1: now up (2 B channels)
> capidrv-1: D2 trace enabled
> capi: controller 1 up

habe  ich alles nicht!,
dafür das:

pppd[1100]: Plugin userpass.so loaded.
linux pppd[1100]: userpass: $Revision: 1.3 $
linux pppd[1100]: Plugin capiplugin.so loaded.
linux pppd[1100]: capiplugin: $Revision: 1.27 $
linux pppd[1100]: capiconn:  1.7
linux modprobe: modprobe: Can't locate module char-major-68
linux pppd[1100]: capiplugin: CAPI_REGISTER failed - CAPI not installed
(0x1009) [No such device (19)]
linux pppd[1100]: Exit.

> So wie ich das sehe, laedt der USB Treiber den fcusb2 Treiber. Dieser
loest
> mit seinem post-install das Ausfuehren des ISDN Hotplugskript aus. Das
> wiederum fuehrt das load-fcusb2 Skript aus, was CAPI und Karte
initialisiert.
> Eigentlich genial.
>
> --
> Um die Liste abzubestellen, schicken Sie eine Mail an:
>     suse-isdn-unsubscribe@xxxxxxxx
> Um eine Liste aller verfügbaren Kommandos zu bekommen, schicken
> Sie eine Mail an: suse-isdn-help@xxxxxxxx
>