[Bug 244709] New: YaST2 does not install dual onboard NICs
https://bugzilla.novell.com/show_bug.cgi?id=244709 Summary: YaST2 does not install dual onboard NICs Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rcromi@neo.rr.com QAContact: jsrain@novell.com 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=244709 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |rcromi@neo.rr.com ------- Comment #1 from chrubis@novell.com 2007-02-13 10:23 MST ------- Please attach y2logs. If you are in doubt follow: http://en.opensuse.org/Bugs/YaST Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=244709 ------- Comment #2 from rcromi@neo.rr.com 2007-02-13 11:47 MST ------- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=244709 rcromi@neo.rr.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|rcromi@neo.rr.com | ------- Comment #3 from rcromi@neo.rr.com 2007-02-14 14:52 MST ------- Created an attachment (id=119270) --> (https://bugzilla.novell.com/attachment.cgi?id=119270&action=view) log files -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=244709 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |mzugec@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=244709 mzugec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |rcromi@neo.rr.com ------- Comment #4 from mzugec@novell.com 2007-02-16 05:50 MST ------- It seems as duplicate of #180821 Does the network works when you change forcedeth module to skge? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=244709 rcromi@neo.rr.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|rcromi@neo.rr.com | ------- Comment #5 from rcromi@neo.rr.com 2007-02-16 14:31 MST ------- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=244709 ------- Comment #6 from rcromi@neo.rr.com 2007-02-18 09:37 MST ------- Created an attachment (id=119835) --> (https://bugzilla.novell.com/attachment.cgi?id=119835&action=view) 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=244709 mzugec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Comment #7 from mzugec@novell.com 2007-02-19 02:32 MST ------- 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 *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=244709 ------- Comment #8 from mzugec@novell.com 2007-02-19 02:45 MST -------
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 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com