|
Bugzilla – Full Text Bug Listing |
| Summary: | Install creates faulty MAC address in /etc/udev/rules.d/30-net_persistent_names.rules | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | David Rankin <drankinatty> |
| Component: | Installation | Assignee: | Christian Zoz <zoz> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | mvidner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
yast does not touch udev rules. This is a very special problem. Seems the device is somehow broken. So the driver cannt get the proper MAC address in all cases. Additionally the driver has then the silly idea to provide a fake MAC address. This is to much effort to catch such rare use cases. It would not help to add an exception in rename_netiface, since YaST did also use the faked MAC address. Please correct the udev rules file and ifcfg-* manually and be done. For reference see: http://lists.suse.com/archive/suse-linux-e/2006-Jan/3540.html |
See the list topic "[SLE] eth0 now eth1 WTF? Network woes....The saga....[Long]" Posted 1/23/2006 and responses. System: Abit kt7; AMD T-bird 800; 512M Ram; Linksys network anywhere NIC (tulip); ATI Expert video; USR sportster 33.4 modem at irq 3. When I first installed SuSE 10, the network would come up and it used eth0: Simply /etc/sysconfig/network/ifcfg-eth-id-00:4c:69:6e:75:79 would bring up the Linksys card as eth0. This is how it worked. Then on a subsequent reboot the network doesn't come up. I mean loopback is fine, but the NIC fails to load and the error is "unable to load mandatory services.." doneWaiting for mandatory devices: eth-id-00:4c:69:6e:75:79 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 0 eth-id-00:4c:69:6e:75:79 No interface found failedSetting up service network . . . . . . . . . . . . . . . .failed dmesg says it is now trying to load eth1? Ok, cp ifcfg-eth-id-00:4c:69:6e:75:79 ifcfg-eth1 rcnetwork restart -- presto! /var/log/boot.msg says it is looking for the NIC at: 00:04:5a:87:c8:43. WTF? How can there be 2 MAC address when I only have 1 NIC? OK, easy enough: cp eth-id-00:4c:69:6e:75:79 eth-id-00:04:5a:87:c8:43; rm eth-id-00:4c:69:6e:75:79. rcnetwok restart -- it works! The [BUG]: The problem seems to be in /etc/udev/rules.d/30-net_persistent_names.rules. The question [bug] is how duplicate entries got created in the first place. Something in SuSE setup must have created the first entry. Of course, the hardware address is wrong, but for some reason it is there. As noted, this must be a popular MAC address given the 372 references to it on Google. Also, it must have worked following installation since Yast and online update were able to connect during set up. /etc/udev/rules.d/30-net_persistent_names.rules contained: SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:4c:69:6e:75:79", IMPORT="/sbin/rename_netiface %k eth0" SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:04:5a:87:c8:43", IMPORT="/sbin/rename_netiface %k eth1" Explanation: on subsequent reboot, the network failed because there is no NIC that corresponds to eth-id-00:4c:69:6e:75:79. Also, due to the multiple entries in /etc/udev/rules.d/30-net_persistent_names.rules above, eth0 would fail and the NIC with the real MAC address of 00:04:5a:87:c8:43 would load as eth1.