Bug 132387 - eth0 not available after first reboot on fresh NFS install
Summary: eth0 not available after first reboot on fresh NFS install
Status: RESOLVED DUPLICATE of bug 116537
: 128611 (view as bug list)
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: Final
Hardware: PC All
: P5 - None : Normal
Target Milestone: ---
Assignee: Martin Vidner
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-04 19:58 UTC by Hans-Peter Jansen
Modified: 2006-07-13 18:38 UTC (History)
1 user (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
y2start.log (7.95 KB, text/x-log)
2005-11-13 10:36 UTC, Hans-Peter Jansen
Details
y2log-1 (1.00 MB, text/plain)
2005-11-13 10:37 UTC, Hans-Peter Jansen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hans-Peter Jansen 2005-11-04 19:58:30 UTC
On a system with two ethernet interfaces, I had to manually "ifup-dhcp eth0", 
"rcportmap start", and "ifdown eth1". The last was necessary to get the 
routing right, and yast going..
Comment 1 Martin Vidner 2005-11-11 15:46:48 UTC
Please attach the y2logs:
http://www.opensuse.org/Bug_Reporting_FAQ#YaST
Comment 2 Hans-Peter Jansen 2005-11-13 10:36:40 UTC
Created attachment 57183 [details]
y2start.log

Sorry for the long delay!
Here's the requested data. I greped the yast logs for
eth{0,1} and attached the matched files here. 

In case of call backs, please bear with me, since I'M out of office until 17th nov..
Comment 3 Hans-Peter Jansen 2005-11-13 10:37:28 UTC
Created attachment 57184 [details]
y2log-1
Comment 4 Hans-Peter Jansen 2005-11-13 10:44:21 UTC
Looks like this issue is another fallout of NIC devices magically changing their name.. 

This problem has potential to take over leadership in my personal most annoying bug list of SUSE Linux.
Comment 5 Hans-Peter Jansen 2005-11-20 22:04:49 UTC
*** Bug 128611 has been marked as a duplicate of this bug. ***
Comment 6 Martin Vidner 2006-03-15 17:20:59 UTC

*** This bug has been marked as a duplicate of 116537 ***
Comment 7 Vance Baarda 2006-07-13 18:38:31 UTC
Deleting invalid NTS Priority value. (Value needs to be an integer between 1 and
1000, inclusive.)