LinuxMCE Forums

General => Users => Topic started by: Websteria on April 20, 2007, 03:33:06 pm

Title: Remote P3 iPaq Legacy desktop diskless rebooting when oribiter starts
Post by: Websteria on April 20, 2007, 03:33:06 pm
Hi there.

I got my core all configured, but when I Try to boot my diskless P3 Media Director it gets through the network config and then boom reboots. what can I do to diagnose this? I'm guessing it's something to do with the build of linux it's getting as when I tried to install ESX server on a P3 machine I got a similar issue as it requires a P4. Is there something specific I need to do to tell it "This machine is a P3", I tried changing the architecture to "386" although I think a P3 is a 686.... anyways, anyone?
Title: Re: Remote P3 iPaq Legacy desktop diskless rebooting when oribiter starts
Post by: sharlee_angelo on April 20, 2007, 04:11:32 pm
can you tell us some messages before it reboots?
Title: Re: Remote P3 iPaq Legacy desktop diskless rebooting when oribiter starts
Post by: Websteria on April 20, 2007, 06:36:09 pm
Basically if I don't set up an orbiter it boots and says "We've announced ourselves to the router" I see all the DHCP messages, my IP, etc..
but once the "orbiter" starts up on it then it reboots...
Title: Re: Remote P3 iPaq Legacy desktop diskless rebooting when oribiter starts
Post by: rictec on April 21, 2007, 01:51:20 am
please go to pluto admin and to media director and force the diskless boot image  to be created and wait

maybe there was some error on them first time


Rictec
Title: Re: Remote P3 iPaq Legacy desktop diskless rebooting when oribiter starts
Post by: Websteria on April 23, 2007, 09:17:36 pm
I've done that before but I'll give it a try again. Could it have anything to do with a video card problem (These are intel i815 integrated) or sound problem?

Thanks.
Title: Re: Remote P3 iPaq Legacy desktop diskless rebooting when oribiter starts
Post by: rictec on April 24, 2007, 02:13:36 am
please remember that the diskless boot creation takes some time to finish.
and dont forget to reload the router of course after.

you can check all diskless boot log on the core just go to the corresponding number and check inside /var/logs for any errors..

Rictec