Bugzilla – Bug 304119
YaST2 network device configuration not saved
Last modified: 2007-08-30 13:27:28 UTC
Created attachment 159596 [details] YaST2 logs YaST2 module "Network Card" does not write network address configuration. After filling in info in "address" panel (either static or DHCP) and clicking on "next" button, the "overview" panel still says "Not configured" (and no configuration file written into /etc/sysconfig/network, only empty 'routes'). Happens both during install and when invoked from installed system. Installation into VMware Server 1.0.3, one network interface, bridged mode. Traditional network setup without NetworkManager, SuSEfirewall2 switched off. YaST2 logs attached. In 10.3 Beta 1, configuration worked correctly.
same bug here with a rt2500 card. the configuration in will not save in 10.2 Beta 2. Without changing below I am running 32 bit KDE install.
what is device file: hwinfo --netcard|grep "Device File:" ?
Device File: eth0 (card is emulated Intel Pro/1000 (82545EM), module e1000)
attach yast logs (/var/log/YaST2/*), please
Created attachment 159781 [details] YaST2 logs, second version Here they are. This version is not much different from the first one, only y2log is a bit longer (one or two more attempts to set up network interface).
*** Bug 304595 has been marked as a duplicate of this bug. ***
Created attachment 159822 [details] y2logs for rt2500pci failure setup
from opensuse 10.3 Beta 2 hwinfo --netcard:grep "rt2500pci" Driver Modules: "rt2500pci" Driver Status: rt2500pci is active Driver Activation Cmd: "modprobe rt2500pci" Now I have this working on opensuse 10.2. If I ifup rt2500 opensuse 10.3 states that the device is not active. i have yalogs tar balled
Same bug with 3945 wifi card. Can't set to "external zone" so connection doesn't work. How can I edit it manually ? Lan card is well config at start, so it works (but I can't change settings).
*** Bug 304637 has been marked as a duplicate of this bug. ***
Perret - your problem is completly different (see bugs #288450 and #303847 - problem is with device name). It's fixed in yast2-network-2.15.67 and yast2-2.15.48 (use Factory)
Michal - I'm not able to reproduce your problem, but I tried it with VirtualBox, not VMware From second attached log I can see that for configuration name is used empty string (it should be device_name from hwinfo) Can you please set up temporary network (with dhcpcd or ip commands) and copy last yast2-network nad yast packages? I will attach them. Perret - try that packages too
Created attachment 159902 [details] yast2-network-2.15.67 yast2-network-2.15.67
Created attachment 159903 [details] yast2-2.15.48 yast2-2.15.48
Still have bug with the new package. Yast network crash when activating new settings and doesn't save them. Error message is : (gtk:4443): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with 0 and height -42 This bug is also for others yast modules. It's possibly link to another bug (297971).
Perret, please open new bugreport for that and put yast logs there
I didn't try newer yast2 and yast2-network yet but I tried to install few more times (all 64-bit) and made an important observation: problem appears only if LILO is used as bootloader (had to manually add 'image=' lines - se bug #294432), when GRUB was used, yast2 module works fine.
Michal : OK, it's done : bug 304822
Newer yast2 and yast2-network save configuration correctly (from installed system). Later today I'm going to try using them during installation.
>> problem appears only if LILO is used as bootloader I didn't tried it with LILO, but sounds funny ;-)
Yes, it does. There might be a connection to bug #294432, bootloader module writes incomplete lilo.conf and maybe there is a problem with generated initrd as well. I'll try to compare content of initrd from LILO and GRUB installation.
Hannes, is mkinitrd somehow related with lilo?
No.
2007-08-23 23:09:22 <3> edu13(3976) [ag_udev_persistent] OPEN_FAILED opening /etc/udev/rules.d/70-persistent-net.rules failed: není souborem ani adresářem 2007-08-23 23:09:22 <5> edu13(3583) [YCP] LanItems.ycp:139 read udev : nil What's that? It means udev events wasn't triggered? That's really strange but not related to YaST at all. Michal, can you check difference between LILO / GRUB in udev rules?
Good news: yast2-2.15.47-12 and yast2-network-2.15.67-2 save configuration during second phase of install (with LILO) as well.
Great, closed as fixed
an rpm -U of the two attached updates works on the 32 bit version of opensuse 10.3 Beta 2 as well. Figured another confirmation would be nice to this bug. Cheers
udev rules between grub and lilo install differ only in existence of three files: GRUB installation has 70-persistent-cd.rules and 70-persistent-net.rules (both missing in LILO installation) and LILO installation has empty 79-yast2-drivers.rules (missing in GRUB installation).
Please fill a new bugreport for this (maybe it's caused by #294432 - I'm not expert here)
*** Bug 305596 has been marked as a duplicate of this bug. ***