 Relationships |
|
| Anonymous | Login | Signup for a new account | 2010-02-27 10:41 CET |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000104 | [CapiSuite] core | major | always | 2004-12-03 11:07 | 2004-12-04 08:26 | ||||
| Reporter | Frank Bandle | View Status | public | ||||||
| Assigned To | gernot | ||||||||
| Priority | normal | Resolution | not an issue | ||||||
| Status | closed | Product Version | |||||||
| Summary | 0000104: capisuite not starting, after last Online update kernel Suse 9.2 | ||||||||
| Description |
All was perfect running - sinnce months. Now after the online update with the Suse 9.2 - kernel update form 30. Nov capisuite will not work anymore. here is capisuite.error log Wed Nov 3 16:15:28 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Thu Nov 11 21:43:58 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Wed Nov 17 11:31:36 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Wed Nov 17 11:34:44 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Wed Nov 17 12:07:00 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Wed Nov 17 12:37:43 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Wed Nov 17 13:17:18 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Wed Nov 17 14:50:42 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Wed Nov 17 15:07:52 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Wed Nov 17 15:29:02 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Thu Nov 25 12:40:50 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Fri Nov 26 23:08:06 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Sun Nov 28 15:07:44 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Tue Nov 30 16:33:03 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Tue Nov 30 16:33:03 2004 CapiSuite 0xbffffc80: Can't start Capi abstraction. The given error message was: CapiError: Error in CAPI20_ISINSTALLED: CAPI not installed. occured in Capi::getCapiInfo() Fri Dec 3 10:21:28 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.4 started. Fri Dec 3 10:21:28 2004 CapiSuite 0xbfffef50: Can't start Capi abstraction. The given error message was: CapiError: Error in CAPI20_ISINSTALLED: CAPI not installed. occured in Capi::getCapiInfo() Fri Dec 3 10:21:42 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.4 started. Fri Dec 3 10:21:42 2004 CapiSuite 0xbfffef50: Can't start Capi abstraction. The given error message was: CapiError: Error in CAPI20_ISINSTALLED: CAPI not installed. occured in Capi::getCapiInfo() Fri Dec 3 10:21:44 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.4 started. Fri Dec 3 10:21:44 2004 CapiSuite 0xbfffef50: Can't start Capi abstraction. The given error message was: CapiError: Error in CAPI20_ISINSTALLED: CAPI not installed. occured in Capi::getCapiInfo() Fri Dec 3 10:21:55 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.4 started. Fri Dec 3 10:21:55 2004 CapiSuite 0xbfffef50: Can't start Capi abstraction. The given error message was: CapiError: Error in CAPI20_ISINSTALLED: CAPI not installed. occured in Capi::getCapiInfo() Fri Dec 3 10:22:17 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.4 started. Fri Dec 3 10:22:17 2004 CapiSuite 0xbfffef50: Can't start Capi abstraction. The given error message was: CapiError: Error in CAPI20_ISINSTALLED: CAPI not installed. occured in Capi::getCapiInfo() Fri Dec 3 10:23:14 2004 CapiSuite 0xbffff070: CapiSuite 0.4.4 started. Fri Dec 3 10:23:14 2004 CapiSuite 0xbffff070: Can't start Capi abstraction. The given error message was: CapiError: Error in CAPI20_ISINSTALLED: CAPI not installed. occured in Capi::getCapiInfo() Fri Dec 3 10:36:06 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.5 started. Fri Dec 3 10:36:06 2004 CapiSuite 0xbfffef50: Can't start Capi abstraction. The given error message was: CapiError: Error in CAPI20_ISINSTALLED: CAPI not installed. occured in Capi::getCapiInfo() Fri Dec 3 10:36:10 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.5 started. Fri Dec 3 10:36:10 2004 CapiSuite 0xbfffef50: Can't start Capi abstraction. The given error message was: CapiError: Error in CAPI20_ISINSTALLED: CAPI not installed. occured in Capi::getCapiInfo() Any idea what happened ? Regards Frank |
||||||||
| Additional Information |
Tue Nov 30 16:19:30 2004 Connection 0x8229c50: call from 0951000000 to 96064 for frank connecting with voice Tue Nov 30 16:19:55 2004 Connection 0x8229c50: accepting with service 0 Tue Nov 30 16:19:55 2004 Connection 0x8229c50: connection lost with cause 0x349a,0x0 Tue Nov 30 16:19:55 2004 Connection 0x8229c50: Connection object deleted Tue Nov 30 16:33:03 2004 CapiSuite 0xbffffc80: CapiSuite 0.4.4 started. Fri Dec 3 10:21:28 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.4 started. Fri Dec 3 10:21:42 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.4 started. Fri Dec 3 10:21:44 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.4 started. Fri Dec 3 10:21:55 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.4 started. Fri Dec 3 10:22:17 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.4 started. Fri Dec 3 10:23:14 2004 CapiSuite 0xbffff070: CapiSuite 0.4.4 started. Fri Dec 3 10:36:06 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.5 started. Fri Dec 3 10:36:10 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.5 started. |
||||||||
| Attached Files | |||||||||
|
|
|||||||||
|
Relationships |
|
|
Notes |
|
|
(0000210) Frank Bandle 2004-12-03 14:07 |
isdn-driver is started successfuĺly - thats not the reason i guess, why capisuite start fails. femax:~ # rcisdn restart Unloading ISDN driver capi fcpci done Setting up ISDN card contr0 AVM FRITZ!Card PCI v2.0 done Loading Driver contr0 1 kcapi capi capidrv done Initializing capi for contr0 (1) done femax:~ # rccapisuite restart Shutting down CapiSuite done Starting CapiSuite failed femax:~ # tail /var/log/capisuite.error Fri Dec 3 14:04:28 2004 CapiSuite 0xbfffef50: CapiSuite 0.4.5 started. Fri Dec 3 14:04:28 2004 CapiSuite 0xbfffef50: Can't start Capi abstraction. The given error message was: CapiError: Error in CAPI20_ISINSTALLED: CAPI not installed. occured in Capi::getCapiInfo() |
|
(0000215) gernot 2004-12-04 08:26 |
Well, this is definitely no CapiSuite bug. It means that your ISDN driver isn't working anymore. Please ask these kind of questions on the CapiSuite mailing list - or even better on the SUSE ISDN mailing list (see http://www.suse.de/de/private/support/online_help/mailinglists/ [^]). |
|
(0000216) gernot 2004-12-04 08:26 |
BTW: You can see if your CAPI driver is working by calling "capiinfo" as described in the CapiSuite documentation. |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2004-12-03 11:07 | Frank Bandle | New Issue | |
| 2004-12-03 14:04 | Frank Bandle | Issue Monitored: Frank Bandle | |
| 2004-12-03 14:07 | Frank Bandle | Note Added: 0000210 | |
| 2004-12-04 08:26 | gernot | Status | new => resolved |
| 2004-12-04 08:26 | gernot | Resolution | open => not an issue |
| 2004-12-04 08:26 | gernot | Assigned To | => gernot |
| 2004-12-04 08:26 | gernot | Note Added: 0000215 | |
| 2004-12-04 08:26 | gernot | Status | resolved => closed |
| 2004-12-04 08:26 | gernot | Note Added: 0000216 | |
