Bugzilla – Bug 148615
YaST2 change after first reboot the device
Last modified: 2006-02-14 14:39:17 UTC
When a SLP installation is given with CD's and the Computer have 2 networkcards (one connectid one have no connect) YaST2 change after first reboot to the second Card, which is not connectid ? The Logs from YaST2 can be found, Bug #141181 SLES10 Beta3 is also Concerned.
Please give more information about the hardware: `hwinfo --network' What did you configure during the installation and what was wrong exactly afterwards? Please be more verbosive about this point.
OK 'hwinfo --network" is coming as attachment. An entire "hwinfo" is in the case of Bug #141181 I du a NORMAL installation from 10.1 Beta3 with SLP from CD's only the boot Parameter apic is added.I had always after first reboot a not functioning network. With older versions there are no problems (SL9.3, SL10, SLES9) I found the error by coincidence. With me there are problems with the network with the SL10.1 Beta1-2.I must mostly draw, then again attach the network plug after booting the System. I confounded the network cards, a ping to my "server" ran and i had at one time a network connection. I changed it again no network connection. I hope that was detailed enough.
Sorry but this does not really help. What did you configure: this means: Which of the both cards was configured as eth0, which one as eth1, and so on What goes wrong: Are the devices swapped (eth0 should be eth1), do they not work at all, wrong IP adress, whatsoever. Please attach the output if `ifconfig' here.
It is a normal installation with DHCP and SLP fdrom my server. With the first Reboot the wrong Network-Card is handed over. YaST2 don't remember the correct device? The Device are not swapped, it is no IP Address in in the ifconfig output.I hope my remember is correct ? I have no original ifconfig output waived.
Created attachment 66863 [details] The original Logs from YaST2
Created attachment 66864 [details] The hwinfo --network log
a wild guess: does rcnetwork restart help?
No, afterwards the ifconfig output shows mostly only the lo device or nothing ? I mean in the ifconfig output, at the fist time after reboot the deviices have only IPv6 addresses ?
> It is a normal installation with DHCP and SLP fdrom my server. With the first > Reboot the wrong Network-Card is handed over. > No, afterwards the ifconfig output shows mostly only the lo device or nothing ? I still don't know the excat problem and these two comments are inconsistent. Are you using NetworkManager?
I can't use Networkmanager ? I tell bevor: . I use a installation with the SUSE-10.1-CD-OSS-i386-Beta3-mini.iso, over DHCP and SLP. On my "Server" I have installad "YaST2 Installations Server" (works fine with "SLES9 7 CD's" and "SL10 DVD9" "SL9.3 5 CD's" ec.).The "SL10.1 5 CD's" works not. I make a normal Install, after the 1. CD instalation, YaST2.make the FIST REBOOT, OK ? Afterwards YaST2 continue with the installation with the 2. CD (on this Place the first Bug is shown Bug #141181) I correct the Path frpm /data1/SL10.2 to /data/SL10.1 and say OK. The next are the Network-Problem! YaST2 change after the reboot the Device. You say: these two comments are inconsisten ?? Question: Comment #7 Answer: No, afterwards the ifconfig output shows mostly only the "lo" device or nothing ? the answer: I mean in the ifconfig output, at the fist time after reboot the deviices have only IPv6 addresses ? was a comment. Additional: in the ifconfig output are no IP v4 from the DHCP Server
Please attach the /etc/sysconfig/network directory which contains your network configuration.
Created attachment 67020 [details] Status after first reboot This is the Status AFTER the first reboot
Created attachment 67024 [details] Status: YaST2 Log after the first reboot This are the YaST2 Logs after a clean new install after the first reboot.
Created attachment 67026 [details] This is the running config This is after config with YaST2 on a runnin installation from SL10.1
We'll check this. Setting to NEED in the meantime.
What is now? NEED you INFO ??
Additional Info: YaST2 always uses after reboot the not attached DEVICE ?
This is a duplicate. *** This bug has been marked as a duplicate of 116537 ***