Bug 141942 - dsl with capi doesn't work without isdn configuration
Summary: dsl with capi doesn't work without isdn configuration
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: unspecified
Hardware: i586 SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Martin Vidner
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-07 11:46 UTC by Rolf Schreiber
Modified: 2006-01-11 21:56 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
log-file from yast2 configuring dsl (44.95 KB, text/plain)
2006-01-10 08:47 UTC, Rolf Schreiber
Details
output of hwinfo --network (1.31 KB, application/octet-stream)
2006-01-10 20:09 UTC, Rolf Schreiber
Details
empty, just wanted to insert the comment (5 bytes, application/octet-stream)
2006-01-11 20:17 UTC, Rolf Schreiber
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rolf Schreiber 2006-01-07 11:46:02 UTC
I've got a Fritzcard DSL, and registered everything 
under Yast->DSL

Trying to use it I got only the /var/log/localmessages:

capiplugin: CAPI_REGISTER failed - CAPI not installed (0x1009) [No such file or directory (2)]

which didn't help at all locating the problem. The problem was: I had to configure ISDN too to select/start/whatever the capi-driver. 
Then finally DSL works.

Yast2 should detect that automatically IMHO
Comment 1 Michael Gross 2006-01-09 15:59:02 UTC
AFAIK CAPI has nothing to do with DSL, as this is a complete different subsystem. So this is somehow confusing. Nontheless, please attach the yast2 logfiles here. Also attach the output of `hwinfo --dsl'. What exactly did you configure here?
Comment 2 Rolf Schreiber 2006-01-10 08:47:43 UTC
Created attachment 62538 [details]
log-file from yast2 configuring dsl

hwinfo --dsl > file
creates an empty file
running in a shell I can see some output which disappears  immediately (Backspaces in the output???)

dsl runs in mode capi-adsl, which obviously has something todo with capi
Comment 3 Michael Gross 2006-01-10 09:15:27 UTC
Let's try `hwinfo --network' as well as `lspci'. The YaST logfiles are still needed. Thanks.
Comment 4 Rolf Schreiber 2006-01-10 20:09:19 UTC
Created attachment 62731 [details]
output of hwinfo --network

The Yast-Log is in the last Attachement;

Output of lspci is: 

00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:06.0 Multimedia controller: Philips Semiconductors TriMedia TM-1300 (rev 83)
00:07.0 SCSI storage controller: Tekram Technology Co.,Ltd. TRM-S1040 (rev 01)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01)
Comment 5 Michael Gross 2006-01-11 11:20:23 UTC
Martin: I'm not quite sure if this is a problem caused by YaST, so I take Karsten into CC, maby he can provide a clue here.
Comment 6 Karsten Keil 2006-01-11 11:35:35 UTC
Here is no other solution for this combo card, since it need some configuration for the ISDN part (even if not used) before the driver can be loaded. Since it is not possible to do this after the driver was loaded, here is no way to obmit the ISDN configuration. The ISDN part is the "master" part
for our setup.
Comment 7 Rolf Schreiber 2006-01-11 20:17:12 UTC
Created attachment 62997 [details]
empty, just wanted to insert the comment

You can't resolve the dependency, but Yast could help the user! A small warning, when capi-dsl is configured before isdn-capi is, or atleast something in the help-text at the left would have saved me 3 hours of searching, why dsl doesn't work.
Comment 8 Karsten Keil 2006-01-11 21:56:08 UTC
If this would be so easy as it sounds, I would already have done this.
Here are some problems:
Currently the CYaST DSL module doesn't know anything about different HW types.
This ISDN step is only needed for AVM Fritz!card DSL PCI/USB not for the other
DSL only cards. So a unconditional text would be confuse other users, we already have too much help text, it do not fit in one page, so users must scroll.