LinuxMCE Forums

General => Installation issues => Topic started by: nite_man on July 25, 2007, 04:23:57 pm

Title: Core lost IP during installation
Post by: nite_man on July 25, 2007, 04:23:57 pm
Hi,

I decided to install LinuxMCE on my home PC. I successfully installed Kubuntu, didn't apply any updates and tried to install LinuxMCE. But during installation my core/hybrid lost IP and as result installation failed because no packages can be downloaded from the internet.

Can somebody tell me how to fix that?

Thanks in advance.
Title: Re: Core lost IP during installation
Post by: tkmedia on July 25, 2007, 05:37:05 pm
I have experienced this in my many attempts to install LinuxMCE, just go to a terminal and sudo ifdown eth0 and sudo ifup eth0 this should reconnect to internet. If install fails just start it again and it should recover after recopying the CD. It will see the packages that were already downloaded skip them, download what it needs and eventually finish the install.



good luck


Tim
Title: Re: Core lost IP during installation
Post by: nite_man on July 26, 2007, 09:15:18 am
Thanks for your replay, Tim. It's good that LinuxMCE will continue installation if it run again. But this might be a bug. And the main problem is the installation takes a lot of time and it's impossible to sit near PC to catch that case and bring up network interface.

P. S. I'm a Fedora guy. So, I prefer /etc/init.d/network restart :) I really miss service in Debian/Kubuntu
Title: Re: Core lost IP during installation
Post by: gazlang on July 26, 2007, 12:42:40 pm
I had the same issue, and it is because LMCE uninstalls knetworkmanager in place of arping midway through the installation. To solve this just re-boot and re-start the LMCE installer when it loses connection, then it'll go all the way through.
Or you can sudo apt-get install arping before starting the LMCE installer, reboot first and make sure you are still connected to the net.
Title: Re: Core lost IP during installation
Post by: nite_man on July 28, 2007, 03:06:46 pm
In the latest RC1 that problem is fixed. I installed it yesterday without problems.