Author Topic: 1004: The time has come.  (Read 29706 times)

jamo

  • Guru
  • ****
  • Posts: 459
    • View Profile
    • LMCE user Page
Re: 1004: The time has come.
« Reply #75 on: May 17, 2012, 08:55:12 am »
Diskless Setup is failing for everyone. I do not know why. I will investigate.
Good to know I'm not alone there. Not sure if it helps but I then ran the old manual Diskless_CreateTBZ on the core which took the usual x+1 hours and was able to bring up a media director relatively successfully this morning. There was a message that some of the devices did not start correctly but I don't know what that refers to and if it is related.

l3mce

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1081
    • View Profile
Re: 1004: The time has come.
« Reply #76 on: May 17, 2012, 08:12:07 pm »
Ok... so I have fixed diskless for the next batch... but... I don't know if ssh will work between core/moon.

This code is so sticky. Everything interacts with everything, and you touch one piece and get stuck to 14 other pieces.

MD update doesn't seem to be occurring on my end, but I am on a really old unstable image... so... please watch what is going on when you hook your MDs up. SEE if nvidia install is failing, not just a failure to setup x once it tries to load without the driver installed. See if it is updating... when you get a splash screen, hit escape and watch it.

Thanks.
I never quit... I just ping out.

jamo

  • Guru
  • ****
  • Posts: 459
    • View Profile
    • LMCE user Page
Re: 1004: The time has come.
« Reply #77 on: May 18, 2012, 08:40:09 am »
Ta. Incidentally, ssh appears to be working fine in prev (25970) image so hopefully that carries through. So far so good on that image after I ran DisklessCreate. Still haven't tracked down or looked further as far as the "some devices not starting" on the MD.

DragonK

  • Guru
  • ****
  • Posts: 429
    • View Profile
Re: 1004: The time has come.
« Reply #78 on: May 18, 2012, 09:08:21 am »
Still haven't tracked down or looked further as far as the "some devices not starting" on the MD.

Mine was the Picture viewer, but after leaving it on overnight and a reload/reboot, it sorted itself out.

Karel

jamo

  • Guru
  • ****
  • Posts: 459
    • View Profile
    • LMCE user Page
Re: 1004: The time has come.
« Reply #79 on: May 18, 2012, 10:33:27 am »
Mine was the Picture viewer, but after leaving it on overnight and a reload/reboot, it sorted itself out.
Most likely the same for me. Didn't check this morning when I started the MD if it was still reporting that. Incidentally, how did you know it was the picture viewer... because you tried it or because you know where to look to see what didn't sart?

DragonK

  • Guru
  • ****
  • Posts: 429
    • View Profile
Re: 1004: The time has come.
« Reply #80 on: May 18, 2012, 10:43:54 am »
By assumption. When I got the "Some Devices failed to start" message, my screen saver wasnt working. Picture Viewer was allways the last one in the queue just before the orbiter loads. Next morning no error message and a couple of minutes the screensaver started.

Karel

l3mce

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1081
    • View Profile
Re: 1004: The time has come.
« Reply #81 on: May 18, 2012, 09:21:15 pm »
It is always either pluto-photo-screen-saver or lmce-picture-viewer.

I don't know why. They are explicitly installed before the dvd is created.

Running diskless create will definitely fix the md stuff... but part of the point of this is to avoid that. I am trying to get as close to perfect a full install with diskless and everything run and ready. I know 270 was botched. Could use feedback on the latest.

Thanks :)
« Last Edit: May 18, 2012, 10:19:10 pm by l3mce »
I never quit... I just ping out.

pedplar

  • Veteran
  • ***
  • Posts: 89
    • View Profile
Re: 1004: The time has come.
« Reply #82 on: May 18, 2012, 11:15:43 pm »
I have the latest 5972 downloaded. Getting ready to eat dinner then will try it out for ya.

pedplar

  • Veteran
  • ***
  • Posts: 89
    • View Profile
Re: 1004: The time has come.
« Reply #83 on: May 19, 2012, 01:11:00 am »
Diskless setup works again.  It rebooted after it finished setting up

Then installed the Pluto nvidia drivers.
Then tried to install nvidia and failed
I manually rebooted and still failed to install.  If I login to a terminal on the core and SSH to the MD, and just do an apt-get update. Go back to the MD and reboot it the drivers installed. One more reboot after the drivers are installed, AVWizard comes up.  So is there anyway you can force an apt-get update before the script tries to install the nvidia drivers?

here is the picture of my screen
http://i47.tinypic.com/2eg5ywy.jpg

I already got the drivers installing before I looked at the log, so the log doesnt show anything wrong.

I messed up my working install, my backup didnt work right, so on my next md setup i will get the log .
« Last Edit: May 19, 2012, 01:49:01 am by pedplar »

pedplar

  • Veteran
  • ***
  • Posts: 89
    • View Profile
Re: 1004: The time has come.
« Reply #84 on: May 19, 2012, 01:46:08 am »
Ok... so I have fixed diskless for the next batch... but... I don't know if ssh will work between core/moon.

Yes Diskless setup does work.  If you mean  by logging in to the core then ssh to a md that also works. so does using putty by sshing to the core then sudo ssh moon47 that also works.

l3mce

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1081
    • View Profile
Re: 1004: The time has come.
« Reply #85 on: May 19, 2012, 02:04:21 am »
Hot dog


Can you try using desktop on hybrid?
I never quit... I just ping out.

pedplar

  • Veteran
  • ***
  • Posts: 89
    • View Profile
Re: 1004: The time has come.
« Reply #86 on: May 19, 2012, 08:36:47 am »
I will give the desktop a try in the morning.  Just to see if it works?

This is the nvidia-install.log


== Begin NVidia driver installation (Fri May 18 23:31:51 EDT 2012) ==
Card Detected: 03:00.0 VGA compatible controller [0300]: nVidia Corporation ION LE VGA [10de:087e] (rev b1)
PCI_ID Detected: 087e
LMCE prefers driver nvidia-glx-260
installing NEW driver nvidia-glx-260!
Unable to install driver:
E: Broken packages
== End NVidia driver installation (Fri May 18 23:35:24 EDT 2012) ==



pedplar

  • Veteran
  • ***
  • Posts: 89
    • View Profile
Re: 1004: The time has come.
« Reply #87 on: May 19, 2012, 10:29:37 am »
Anyone else experiencing A very long MD setup, starting with the AVWizard.  Took me about 10 minutes to go through the AVWizard, and then at least 45 minutes for sarah to appear, and then another 40 or so minutes to finish to the orbiter.  well over 2 hours to setup each md.

Edit:  Fixed my problem. Bad network card.
« Last Edit: May 19, 2012, 09:56:28 pm by pedplar »

posde

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 3009
  • Wastes Life On LinuxMCE Since 2007
    • View Profile
    • My Home
Re: 1004: The time has come.
« Reply #88 on: May 19, 2012, 11:21:15 am »
The setup can take quite a while, especially if the network itself has some problems. For example, if the switch and the MD don't think they both should use gigabit, some NICs are better than others, i.e. sometimes you only get rates of 1-2MB/s, instead of 20-30MB/s or more.

pedplar

  • Veteran
  • ***
  • Posts: 89
    • View Profile
Re: 1004: The time has come.
« Reply #89 on: May 19, 2012, 11:32:47 am »
I have never had it take this long before.  Normally maybe 20 minutes after I get through the avwizard. I can copy files at over 30MB/s to and from anywhere on the network, except on wifi.
« Last Edit: May 19, 2012, 11:34:50 am by pedplar »