Bugzilla – Bug 402578
Installation can not complete when installing over the network, leaves system broken.
Last modified: 2009-04-21 21:39:40 UTC
I used this installer that I got from download.opensuse.org, I chose to do a network install: http://download.opensuse.org/distribution/11.0/iso/cd/openSUSE-11.0-NET-x86_64.iso Everything goes fine (partitioning, installing software) until the time comes to configure the system. At that point, it complains that "curl" can not be downloaded, the cause is that it can not resolve download.opensuse.org. On a first install, I figured this probably was not a major problem, so I just clicked "Abort" or "Skip", the installation completes, but it is not possible to login on the GUI or the console. On the console I get an error about "Module not found" or something like that. * How I fixed it: in case someone else runs into this problem and wants a quick fix: I did a new installation from scratch, and I ran into the same problem again. This time I switched to the console (Control-Alt-F2 I believe), then noticed that the ethernet devices were not configured, only the loopback device was configured (I used netstat -nr, and only the route to 127.0.0.1 showed up) I did: $ ifup eth0 It said that the interface was already running, but after this, I got an IP address on eth0 and I got the route listed on netstat -nr. But no default route existed, so I manually typed: $ route add default gw IPOFMYGATEWAY (in my case that was 192.168.1.1) Once that was there, I was able to verify that things worked, I did: $ nslookup download.opensuse.org And it produced an IP address. I went back to the GUI, clicked "Retry", this time it downloaded whatever it needed to download and the installation completed successfully. But of course this is not a solution for someone that wants to try Linux or someone that is not familiar with networking.
Hello, could you provide yast2 logs from installation ? If you are unsure follow: http://en.opensuse.org/Bugs/YaST Thanks
ping
I have had this error at least 3 times installing different systems, it would take you less to reproduce this issue with a local machine than wait for me to provide this information. I finally got back home, here are the logs. But then again, it would take you 10 minutes to get to the failure point as described in the original report.
*** This bug has been marked as a duplicate of bug 399645 ***
*** This bug has been marked as a duplicate of bug 471731 ***