Bug 244709

Summary:	YaST2 does not install dual onboard NICs
Product:	[openSUSE] openSUSE 10.2	Reporter:	Rick Cromi <rcromi>
Component:	YaST2	Assignee:	Michal Zugec <mzugec>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	log files hwinfo --netcard

Description Rick Cromi 2007-02-12 17:41:08 UTC

Installation of openSUSE 10.2 does not enable dual onboard ethernet ports.

Running YaST2 discovers devices, but does not enable them, regardless of settings.

ifconfig -a does not display eth0 or eth1 as devices.

eth0 is renamed to eth2 at boot up.

Comment 1 Cyril Hrubis 2007-02-13 17:23:48 UTC

Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST


Thanks!

Comment 2 Rick Cromi 2007-02-13 18:47:43 UTC

No means of attaching requested tar files.
No Internet due to reported bug while running openSUSE 10.2
Files not writing to DVD+RW drive while in openSUSE 10.2

Mainboard is DFI LanParty UT nf4 Ultra-D
Dual onboard NICs are Vitesse VSC8201 Gigabit Phy and Marvell 88E8001 Gigabit PCI

System is set up for dual booting with Windows XP Pro x64.

Comment 3 Rick Cromi 2007-02-14 21:52:34 UTC

Created attachment 119270 [details]
log files

Comment 4 Michal Zugec 2007-02-16 12:50:01 UTC

It seems as duplicate of #180821
Does the network works when you change forcedeth module to skge?

Comment 5 Rick Cromi 2007-02-16 21:31:28 UTC

No, it doesn't.

In YaST I was able to disable the NVidia NIC and edit the Marvell Yukon NIC changing the bus-pci-0000:01:0a.0 to bus-pci0000:00:0a.0 and get a connection.  However, after a reboot it no longer worked.

Comment 6 Rick Cromi 2007-02-18 16:37:29 UTC

Created attachment 119835 [details]
hwinfo --netcard

You had referenced another similar bug, which I read through.  

I tried the hwinfo --netcard command and noticed that Marvell Yukon NIC had two driver commands listed, one for the sk98lin driver which was not active (?) and one for the skge, which was active.  I have attached output from this command.

Tested manually with modprobe and ifup commands and got NIC to enable as eth1.  In YaST, on the hardware configuration page, I changed the module/driver from sk98lin to skge.

After rebooting, the NIC is enabled and working as eth1, which is what I thought it should be.  Occasionally, I notice in the startup messages that eth1 is renamed to eth4.

It appears to be working with the skge driver.  There must be something wrong with the sk98lin driver in this type of configuration.

Comment 7 Michal Zugec 2007-02-19 09:32:57 UTC

All what you did is answer on my question from comment #4:

>> There must be something wrong
>> with the sk98lin driver in this type of configuration.

Yes, it is.
That's why this module is blacklisted (cat /etc/modprobe.d/blacklist |grep sk98)
but it's somewhere hardcoded in linuxrc and yast it uses, because was already proposed.
Mark as duplicate


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

Comment 8 Michal Zugec 2007-02-19 09:45:42 UTC

>> After rebooting, the NIC is enabled and working as eth1, which is what I
>> thought it should be.  Occasionally, I notice in the startup messages that eth1
>> is renamed to eth4.

Look at /etc/udev/rules.d/30-net_persistent_names.rules