dsdreamer wrote: 
> Well, actually, I re-imaged my micro-SDHC card about a dozen times
> trying to see what would trigger this apparent "freeze" in Jivelite with
> different permutations of USB devices plugged in. The first boot always
> resulted in a freeze, no matter what USB devices I had connected at the
> time. The only time I had a normal startup experience was one time I was
> using a class 4 micro SDHC card, which I normally avoid due to the slow
> write speeds. All my other tests were done with a class 10 SDHC card. 
> 
> I was, unfortunately, fooling myself by changing too many variables when
> I reported earlier that I got a clean initial boot when removing my USB
> hub and its associated DAC and USB keyboard adapters since I also
> changed from a class 10 to class 4 SDHC card at the same time.
> 
> I notice that when Jivelite gets stuck in the first boot scenario, it
> leaves behind only the following two files: SetupWelcome.lua, and
> DesktopJive.lua with date stamps close to the Unix Time epoch, i.e., the
> jivelite user autologin is happening before the ntp time server gets a
> chance to step the time. 
> Jivelite is starting 15 seconds after boot:
> > 
Code:
--------------------
  >   > 01:00:15 wandboard systemd-logind[198]: New session c1 of user jivelite.
--------------------
> > 
> This is before DHCP moves from the preinit state to the bound state
> and the network services start up and finally the ntp service gets to
> update the date/time at 19.5 seconds after boot.
> > 
Code:
--------------------
  >   > Jul 14 03:36:03 wandboard ntpdate[353]: step time server 134.121.64.62 
offset 1373769343.488106 sec
--------------------
> > 
> 
> My working theory is that there is some kind of race condition when
> starting up for the first time. I think that Jivelite is starting a
> bit to early for its own good. Perhaps the faster SDHC class 10 card
> is making this worse?  
> 
> The standard installation is not set up to capture any logs from
> jivelite. I was wondering if I should change the /etc/passwd file to
> use jivelite-cs > /var/log/jivelite.log 2>&1 or something like it?

Is this on a quad or dual lite?  Does it make any difference?


------------------------------------------------------------------------
Triode's Profile: http://forums.slimdevices.com/member.php?userid=17
View this thread: http://forums.slimdevices.com/showthread.php?t=98544

_______________________________________________
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix

Reply via email to