Bug 115845 - hwcfg-eth0 not needed
Summary: hwcfg-eth0 not needed
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: RC 1
Hardware: PowerPC All
: P5 - None : Normal
Target Milestone: ---
Assignee: Steffen Winterfeldt
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-08 12:27 UTC by Patrick Kirsch
Modified: 2006-09-28 13:25 UTC (History)
1 user (show)

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


Attachments
yast2 logfile, ifcfg-files, udev rules file (142.18 KB, application/x-gtar)
2005-09-08 12:29 UTC, Patrick Kirsch
Details
getsysinfo output (92.20 KB, application/x-gzip)
2005-09-12 08:56 UTC, Patrick Kirsch
Details
hwinfo --netcard output (1.56 KB, text/plain)
2005-09-12 08:57 UTC, Patrick Kirsch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Kirsch 2005-09-08 12:27:58 UTC
Problem: NIS install on G4 failed, because no network is loaded. 
Although in network configuration dialog both eth-cards are set to dhcp.
In the NIS dialog check the option retrieve via dhcp. 
And the error rises ypbind could not start.
There are 2 network cards, eth0 is unplugged and eth1 is plugged.

IMHO, the file /etc/sysconfig/network/ifcfg-eth0  conflicts with the udev rule
in /etc/udev/rules.d/30-net_persistent_names.rules.
Comment 1 Patrick Kirsch 2005-09-08 12:29:06 UTC
Created attachment 49193 [details]
yast2 logfile, ifcfg-files, udev rules file
Comment 2 Martin Vidner 2005-09-08 14:10:06 UTC
Hwinfo tells yast neither the MAC nor the bus position of the BMAC NIC. So 
yast uses just eth as the configuration identifier. The bmac module was loaded 
so I rule out the case that a missing module causes missing information. 
 
y2log:2236: 2005-09-08 13:42:23 <1> linux(5435) [YCP] Lan.ycp:1208 
Hardware=[$["active":true, "bus":"pci", "busid":"0000:01:04.0", "drivers":
[$["active":true, "modprobe":true, "modules":[["tulip", ""]]]], "link":nil, 
"mac":"00:a0:cc:54:08:a0", "module":"tulip", "name":"Netgear FA310TX", 
"num":0, "options":"", "requires":[], "type":"eth", 
"unique":"vQLu.27Dwad8y0MC", "wl_auth_modes":nil, "wl_bitrates":nil, 
"wl_channels":nil, "wl_enc_modes":nil], $["active":true, "bus":"none", 
"busid":"", "drivers":[$["active":true, "modprobe":true, "modules":[["bmac", 
""]]]], "link":nil, 
"mac":"", "module":"bmac", "name":"Apple BMAC+ Ethernet Controller", "num":1, 
"options":"", "requires":[], "type":"eth", "unique":"AGj9.fV1ejj+LieA", 
"wl_auth_modes":nil, "wl_bitrates":nil, "wl_channels":nil, 
"wl_enc_modes":nil]] 
 
Patrick what does hwinfo --netcard say? 
If it doesn't provide the data either, Steffen should fix it. 
Comment 3 Steffen Winterfeldt 2005-09-08 14:20:12 UTC
I need the result of 'getsysinfo' in that case. 
Comment 4 Patrick Kirsch 2005-09-12 08:56:29 UTC
Created attachment 49571 [details]
getsysinfo output
Comment 5 Patrick Kirsch 2005-09-12 08:57:09 UTC
Created attachment 49573 [details]
hwinfo --netcard output
Comment 6 Olaf Hering 2005-09-19 11:30:42 UTC
this happend also with rc4.
Comment 7 Martin Vidner 2005-09-19 11:49:09 UTC
Steffen, hwinfo does not provide the MAC. 
 
Comment 8 Steffen Winterfeldt 2006-03-27 16:01:40 UTC
fixed in 10.1 rc1