Bugzilla – Bug 113101
network not activated after backing out and configuring again (was: DSL configuration does not work)
Last modified: 2005-09-01 15:18:25 UTC
I've a regular DSL modem attached to my second network card.
Created attachment 47649 [details] YaST logs
After I rebooted the system, it suddenly works.
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.
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.
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.
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.
Fixed in yast2-network-2.12.14.