http://bugzilla.novell.com/show_bug.cgi?id=500383 User vendion@charter.net added comment http://bugzilla.novell.com/show_bug.cgi?id=500383#c2 Adam Jimerson <vendion@charter.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vendion@charter.net --- Comment #2 from Adam Jimerson <vendion@charter.net> 2009-05-14 08:14:49 MDT --- I have a similar problem but using the ifup method of configuring my network. Upon booting it configures the loopback correctly then goes into a 25 second wait for eth0 which at the end of the 25 second countdown it gives a "No such interface eth0" error and continues to boot. When I log in I check the network with ifconfig and it only shows the lo device, in order to get it to see my ethernet device I have to run "yast lan" and let it load and it will see my ethernet card but show it as not connected after closing (abort is fine sense no changes have been made) ifconfig sees the eth0 device but has no ip for it. When I try to run ifup I get the following errors for my card RTNITLINK answers: Device or resource busy Cannot enable interface eth0 If I try and run ifdown I get the same errors, instead I have to run rcnetwork restart before the card shows up with an ip and is connected. If it helps the card in question for me is a 21x4x DEC-Tulip compatible 10/100 card using the dmfe kernel module. Reproducible: Always Just start up your system and use ifconfig to reproduce, I haven't been able to tell if this effects just some cards or not, this is the only machine that I installed on. Going to throw up a VM with milestone 1 to test if it is also effected, will post details and my findings on that when I have them. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.