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.