|
Bugzilla – Full Text Bug Listing |
| Summary: | dsl with capi doesn't work without isdn configuration | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Rolf Schreiber <rolf.schreiber> |
| Component: | YaST2 | Assignee: | Martin Vidner <mvidner> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
log-file from yast2 configuring dsl
output of hwinfo --network empty, just wanted to insert the comment |
||
|
Description
Rolf Schreiber
2006-01-07 11:46: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? 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
Let's try `hwinfo --network' as well as `lspci'. The YaST logfiles are still needed. Thanks. 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)
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. 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. 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.
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. |