Bug 113263 - DSL interface available within KInternet after system reboot only
Summary: DSL interface available within KInternet after system reboot only
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: ISDN (show other bugs)
Version: Beta 3
Hardware: i586 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-26 10:47 UTC by Sven Schmidt
Modified: 2007-06-18 15:56 UTC (History)
1 user (show)

See Also:
Found By: Third Party Developer/Partner
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
YaST2 Logs Machine 1 (242.88 KB, application/x-gzip)
2005-08-30 08:16 UTC, Sven Schmidt 		Details
YaST2 Logs Machine 2 (228.94 KB, application/x-gzip)
2005-08-30 08:17 UTC, Sven Schmidt 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Schmidt 2005-08-26 10:47:11 UTC 
Clean SUSE 10 Beta 3 installation: at the end of the AVM DSL/ISDN controller
configuration KInternet does only show the ISDN provider and interface as
connection possibility. The DSL part is completely missing, although YaST shows
both entries.

DSL interface and provider are available via KInternet after a system reboot.
Comment 1 Karsten Keil 2005-08-30 07:37:48 UTC 
Seems smpppd is not reloaded after DSL configuration in this case. 
Please attach the /var/log/YaST2 files as .tar.gz
Comment 2 Sven Schmidt 2005-08-30 08:16:37 UTC 
Created attachment 48099 [details]
YaST2 Logs Machine 1
Comment 3 Sven Schmidt 2005-08-30 08:17:03 UTC 
Created attachment 48100 [details]
YaST2 Logs Machine 2
Comment 4 Martin Vidner 2005-09-02 13:41:30 UTC 
Comment 3:   
  
No DSL hardware was detected at installation time. Where is the problem?  
  
Comment 2:   
 
No, SMPPPD is started only after yast finishes. And it was enabled in 
init.d/*.   
 
Probably unrelated: the ethernet interface failed to start when   
writing the network configuration. UTC clock is used so bug 112909 should not  
be involved.  
The log says (y2log-1:1555)  
[YCP] Service.ycp:277 Running service initscript network start  
[bash] ShellCommand.cc(shellcommand):78 [1Awaiting[1A..failed..failed  
The second line is the stderr.
Comment 5 Martin Vidner 2006-08-28 11:52:23 UTC 
Reassigning to the new maintainer of yast2-network.
Comment 6 Michal Zugec 2007-05-31 15:11:22 UTC 
What is status of this now(10.2/10.3Alpha4+)?
Comment 7 Michal Zugec 2007-06-18 15:56:28 UTC 
Sven, when you'll be able to reproduce, just reopen bug.
Otherwise I think it works now