Bugzilla – Bug 307162
NIC incorrectly configured at install time
Last modified: 2007-09-21 09:01:20 UTC
At first install when trying to configure the Ethernet cards (3 fitted; one builtin, 2 pci) yast displays the Ethernet nics in the following order: Eth0 – 3com Eth1 - realtek Eth2 – reported as HP onboard device (Intel) The onboard device (eth2) is selected and configured as static IP since this is the connected device. However this fails the connectivity test (curl) – I should mention that this is via a proxy, but the failure is to find a DNS server (which was correctly specified) and once the ethernet device begins working none of the proxy networking parameters require further change. Continuing with the install is otherwise successful. Attached are dmesg.txt, log.tar.gz which contains /var/log and ifconfig.txt which contains the ifconfig output. Following the first successful user login then the nics are listed in the following order whilst shutting down: Eth0 – 3com Eth1 – HP onboard device Eth2 – realtek Following a full reboot the nics are now ordered in yast2: Eth0 – 3com Eth1 – HP onboard device Eth2 – realtek Delete middle ethernet device (which was reported as HP) and it then reappeared as Realtek. HP device has moved down the list. Use yast to configure correctly – static IP, mask, default gateway[remembered this], DNS[had lost this]. Still no ethernet access. Shutdown & restart. Networking works ok this time. Captured dmesg_working.txt and ifconfig_working.txt files.
Created attachment 161490 [details] dmesg.txt dmesg at failure point.
Created attachment 161491 [details] ifconfig failing report
Created attachment 161494 [details] /var/log files at failing point
Created attachment 161495 [details] lspci output
Created attachment 161496 [details] dmesg of working boot
Created attachment 161497 [details] ifconfig working report
duplicate report, already fixed for Beta3 2007-09-03 12:08:17 <3> linux(3542) [bash] ShellCommand.cc(shellcommand):78 /bin/cp: cannot stat `/var/lib/dhcpcd/dhcpcd-*.cache': No such file or directory 2007-09-03 12:08:17 <3> linux(3542) [bash] ShellCommand.cc(shellcommand):78 /bin/cp: cannot stat `/etc/udev/rules.d/70-net_persistent_names.rules': No such file or directory it should be /etc/udev/rules.d/70-persistent-net.rules file copied into installed system *** This bug has been marked as a duplicate of bug 292375 ***
Retested with 10.3 beta3 and same issue remains - ie this is not necessarily a duplicate of 292375. I'm attaching another tar.gz which includes all the relevant info just after install/reboot, following reconfiguration with yast2 (at which point it doesn't work) and then following a further reboot at which point the interface works correctly. Includes yast2 snapshots showing misnamed interfaces.
Created attachment 162229 [details] tar.gz containing /var/log, dmesg and ifconfig at various points.
Retested with 10.3 beta3 and same issue remains - ie this is not necessarily a duplicate of 292375 (not sure whether that is resolved or not). I'm attaching another tar.gz which includes all the relevant info just after install/reboot, following reconfiguration with yast2 (at which point it doesn't work) and then following a further reboot at which point the interface works correctly. Includes yast2 snapshots showing misnamed interfaces.
Oh no: 2007-09-06 08:59:09 <3> linux(3537) [bash] ShellCommand.cc(shellcommand):78 /bin/cp: missing destination file operand after `/etc/udev/rules.d/70-persistent-net.rules/mnt/etc/udev/rules.d' missing space between source and destination ;-( The only problem is that udev is not copy between reboot. That's why network devices names are changed. We have NAME option in ifcfg-eth* files to show interface name. yast2-network-2.15.74
*** Bug 308966 has been marked as a duplicate of this bug. ***
Verified as working correctly in RC1. Thanks!