Bug 388587

Summary:	yast configures eth1 instead of eth0
Product:	[openSUSE] openSUSE 11.0	Reporter:	Olaf Hering <ohering>
Component:	Installation	Assignee:	Michal Zugec <mzugec>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	mt, mvidner, snwint
Version:	Beta 2
Target Milestone:	---
Hardware:	PowerPC
OS:	Linux
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	bug388587.tar.bz2

Description Olaf Hering 2008-05-09 07:31:55 UTC

11.0 beta2 on  a g5 with two onboard network interfaces


During setup in second stage, yast configures eth1 instead of eth0.
It was not clear that eth1 was meant, because the _first_ entry in the network card list in the main window was (automatically) configured for dhcp.

Comment 1 Olaf Hering 2008-05-09 07:34:37 UTC

Created attachment 213799 [details]
bug388587.tar.bz2

Comment 2 Michal Zugec 2008-05-09 12:28:44 UTC

Summary is invalid, because yast configures eth1 when you select eth1.
The order of devices is same like output from "hwinfo --netcard" (eth1, eth0)

Comment 3 Olaf Hering 2008-05-09 12:35:36 UTC

I did not configure eth1, I just left the defaults.

Better set all interfaces into UP state, use ethtool to check for link up, and use only the one that has a cable connected.

Comment 4 Michal Zugec 2008-05-09 12:48:19 UTC

> Better set all interfaces into UP state
What is UP state?


> use ethtool to check for link up
Why? YaST uses "link" from hwinfo and from your log both devices has link:true


In your initial description there's nothing about link status. So where's the problem?

Comment 5 Olaf Hering 2008-05-09 12:56:21 UTC

ip link set up dev ethN

I'm sure that only one cable is connected at home, but I have to double check this weekend.
The link status was just a suggestion to not configure interfaces per default that can not work due to lack of cable.

Comment 6 Michal Zugec 2008-05-09 13:02:47 UTC

>> ip link set up dev ethN
No, this is work for sysconfig. YaST just writes configurations


>> I'm sure that only one cable is connected at home
Check it and try "hwinfo --netcard" ("Link detected" option). Also check "/sys/class/net/*/carrier" values

Comment 7 Olaf Hering 2008-05-09 13:25:17 UTC

hwinfo --netcard is in the attachments. And eth1 has no link.

Comment 8 Michal Zugec 2008-05-09 13:28:34 UTC

Hm, but from YaST log I can see link true:


          "hwinfo":$[
                      "active":true,
                      "bus":"pci",
                      "busid":"0001:05:04.1",
                      "dev_name":"eth1",
                      "drivers":[
                                  $[
                                     "active":true,
                                     "modprobe":true,
                                     "modules":[
                                                 [
                                                   "tg3",
                                                   ""
                                                 ]
                                     ]
                                  ]
                      ],
                      "link":true,
                      "mac":"00:14:51:68:b7:01",
                      "modalias":"pci:v000014E4d0000166Asv0000106Bsd00000085bc02sc00i00",
                      "module":"tg3",
                      "name":"NetXtreme BCM5780 Gigabit Ethernet",
                      "num":0,
                      "options":"",
                      "requires":[

                      ],
                      "sysfs_id":"/devices/pci0001:00/0001:00:02.0/0001:05:04.1",
                      "type":"eth",
                      "udi":"/org/freedesktop/Hal/devices/pci_14e4_166a_0",
                      "wl_auth_modes":nil,
                      "wl_bitrates":nil,
                      "wl_channels":nil,
                      "wl_enc_modes":nil
          ],

Comment 9 Michal Zugec 2008-05-09 13:31:28 UTC

Can you compare "hwinfo --netcard" and :

echo '`Read(.probe.netcard)'|/usr/lib/YaST2/bin/y2base stdio scr


on running system and during installation (to be sure)

Comment 10 Michal Zugec 2008-05-11 13:41:43 UTC

Marked as duplicate (YaST really didn't check "link" status), but according comment #8 and comment #9 test your system and create new bugreport if needed

*** This bug has been marked as a duplicate of bug 389131 ***