Bugzilla – Bug 120332
network device configuration not read from Yast
Last modified: 2007-05-23 14:34:16 UTC
my dfi x86-64 motherboard has two built in network cards, an nvidia and a dfi. All installed software (suse 9.2 and suse 9.3) use the dfi device as eth0 which connects to a small dhcp hub fed from a cable modem. The Alpha 1 boot disk for suse 10.1 was able to set up eth0 for ftp installation from kernel.org. The net card configuration was "left" as shown in Yast, dfi as eth0 and nvidia "not configured". Upon reboot the boot screen showed nvidia as eth0, dfi as eth1. subsequent reboots without yast correction showed dfi as eth1, nvidia as eth2, eth3, eth4 etc. If a reboot was allowed to complete and yast was called to reset the net cards, the config in Yast showed dfi as eth0, nvidia as "not configured"!! Repeated deletions of the dfi config and resetting to eth0 in yast eventually allow dfi to operate as eth0 and net connection would be established. Alas, the setup lasts until the next reboot. I want to keep the dfi "card" as eth0. Where the config is written any more I have no idea, clearly though it is hidden from yast. Such a small problem can be a show stopper for a windoze nubie. i can send you various logs, however i need advice which ones you want. thanks, Dimitris
Could you please attach the complete /var/log/YaST2 directory (as tar) for a start? We'll then see if we need anything else :-) Please also specify the version of 10.0, if possible. If you can't figure it out, the version of the yast2-network rpm would be most helpful. Thanks!
Created attachment 51590 [details] compressed /var/log/Yast2 file Attached is the file you requested. The version the bug is from is 10.1, Alpha1. Would you also like to see /var/log/boot stuff?
Eth4 is weird. Where exactly did you see that? Yes, attach the boot logs too, please. I see that you have changed the configuration name to "eth0". Did you try leaving in the default, id-$MAC ? The configuration is in /etc/sysconfig/network/ifcfg-*
I see "incremental" eth numbers in the text boot screen. If i do not make any eth changes thru Yast, the numbers go one higher at the next boot. Not forcing eth0 in Yast always ends up assigning eth0 to the nvidia card, so just using the mac address does not work. Btw, the same problem exists at 10.0 -oss, i just installed it in my spare partition thinking it would be more stable than 10.1 Perhaps the problem is in the hardware detection software, but that is doubtful. 9.1, 9.2 and 9.3 also detect the nvidia as eth0, the difference is that once Yast assigns eth0 to one card, it stays assigned that way... Up to 9.3 i can set either card to eth0. once.
Here is some additional info. I changed the network connection to the nvidia card, the one that 10.0 and 10.1 (and even 9.2 and 9.3) seem to prefer. The 9.3 installation on the machine required only one call up of yast to reset the network device for eth0. NOTHING changed with 10.0. The boot log reports nonexistent device for eth0 when connection is attempted to eth0, but somehow the mac address is read from it!!!!Apparently the problem is in hardware detection or hardware configuration retention!!! In order to get a net connection I have to play with the yast net device configuration 4-5-6-8 times, now it seems more than before!!!! I would hesitate to call this a hardware bug because both 9.2 and 9.3 work with the same hardware just fine. Before installing 10.0/10.1 I had 9.2 in hda2 and 9.3 in hdd2. To make room for 10.1 I retired 9.2, moved 9.3 to hda2 and used hdd2 for 10.1 and then for 10.0.
Reassigning to the new maintainer of yast2-network.
sorry for late answer could you reproduce this bug with 10.2? Mechanism for assigning names for network devices are rules written in /etc/udev/rules.d/30-net_persistent_names.rules. Could you attach this file, please? Also I would like to see output from "hwinfo --netcard"
No answer for nearly three months, therefore resolving as INVALID. Please, reopen if you can reproduce and attach requested information.