|
Bugzilla – Full Text Bug Listing |
| Summary: | network configuration problems during installation | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | peter czanik <peter> |
| Component: | Installation | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | holgi, kkaempf |
| Version: | Alpha 6 | ||
| Target Milestone: | --- | ||
| Hardware: | PowerPC | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
screenshot of broken network summary
yast2 logs of installation and network setup |
||
Please attach y2logs. If you are in doubt follow: http://en.opensuse.org/Bugs/YaST/ Thanks! Seems to be fixed in beta1. Installing today's factory (21st August), the bug reappeared in a slightly different form: both interfaces were identified as Via-rhine on screen. One of them was configured for DHCP, which turned out to be the Marvell one. Using 'delete' revealed the interface's real name. Created attachment 158722 [details]
yast2 logs of installation and network setup
Michal, afaik you fixed the udev rule creation in the first stage of installation. It seems not to work properly. Please have a look. Peter, give me please y2-n version number (rpm -q yast2-network) ppc0821:~ # rpm -q yast2-network yast2-network-2.15.64-2 Already downloaded beta2 (I'm a mirror admin :-) ), will report experiences later today. great, thanks (set NEEDINFO back) Tested in beta2, problem seems to be solved. Closed with WORKSFORME. Sorry, but it is not working in Beta 2 - see Bug #302544 Then that is a separate problem, as it works perfectly over here, even with 3 networking cards. yes, bug Holger pointed in comment #10 is related to upgrade *** Bug 304275 has been marked as a duplicate of this bug. *** |
Created attachment 152695 [details] screenshot of broken network summary Network configuration has some 'interesting' problems during installation. My machine has two network interfaces on-board: a via 10/100 and a marvell gigabit. For the first stage of installation 10/100 was used. After the reboot the gigabit interface was used. The setup screen showed, that both are inactive ant there is an "ethernet network card" which uses DHCP. Went to network setup, which did not list it, and showed as expected, that 10/100 is not configured, gigabit is using dhcp. Tried to change the 10/100 to DHCP, but after "finish" the summary screen still showed that it is not configured. Tried it again, with the same result. Exited the network configuration screen, which resulted in the attached screen. Looks a bit chaotic...