Bug 113101

Summary: network not activated after backing out and configuring again (was: DSL configuration does not work)
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Carsten Hoeger <choeger>
Component: InstallationAssignee: Martin Vidner <mvidner>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Major    
Priority: P5 - None CC: yast2-maintainers
Version: Beta 3   
Target Milestone: ---   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: YaST logs

Description Carsten Hoeger 2005-08-25 18:06:17 UTC 
I've a regular DSL modem attached to my second network card.
Comment 1 Carsten Hoeger 2005-08-25 18:07:07 UTC 
Created attachment 47649 [details]
YaST logs
Comment 2 Carsten Hoeger 2005-08-25 20:08:46 UTC 
After I rebooted the system, it suddenly works.
Comment 3 Martin Vidner 2005-08-26 10:14:59 UTC 
What did not work? Please tell me what you did, what were the expected results
and the actual results. And why you consider it a blocker.
Comment 4 Carsten Hoeger 2005-08-26 10:23:23 UTC 
1. I as usual changed the proposal (dhcp for onboard network card) to static
address for pci network card and disabled the internal one
2. Then I configured my DSL provider and assigned it to the pci network card

DSL parameters: Startup mode: On-boot

- The internet connection test failed
- kinternet did not start automatically upon first startup of KDE
- even when I started it, it did not work

I had no time to check whether the network interface had been up or down at that
time. Later I had to reboot the testinstallation and all of a sudden, everything
seems to be up and running. Network card, DSL and SUSEfirewall.

Could be, that the network card did not come up the first time.
Comment 5 Carsten Hoeger 2005-08-26 10:25:07 UTC 
I consider it a blocker, because I think DSL is a very important technologie to
support. I have a standard DSL modem which worked with all versions so far. It's
not a bleeding edge technology.
Comment 6 Martin Vidner 2005-08-26 11:05:16 UTC 
The NIC indeed did not come up. After entering the NIC configuration and backing
out of it, as you did, yast incorrectly sets a helper variable (OriginalModules,
OriginalDevices) which results in missing hwup for the newly configured NIC.

Downgrading a bit since it does not occur in the default case.
Comment 7 Martin Vidner 2005-09-01 15:18:25 UTC 
Fixed in yast2-network-2.12.14.