Doesn't boot after turning off power

[hh2]

I also had this problem with 5.3.006

When I flash the box it runs fine, I setup my stuff (I only install 1 tuner, 1 single LNB at 1 single satellite at this moment), install a softcam, change the behaviour of 2 buttons on the remote, set recording pre/after times and that's about it.
So then it worked fine all day, but the box was still open, so I put it in deep standby, turned off the power, re-inserted the screws, tried to startup again and it just won't start.
In the display the OpenVIX PLEASE WAIT keeps displaying, Enigma is not running, however I can get to the box with ftp/ssh.

In my log directory the boot file is empty
dmesg doesn't show anything of interest
lastlog is empty

last piece of messages:

O
Oct 14 10:21:56 gbue4k daemon.notice ntpdate[2016]: adjust time server 131.211.8.244 offset 0.000330 sec
Oct 14 10:22:03 gbue4k daemon.notice ntpdate[2095]: adjust time server 131.211.8.244 offset 0.000537 sec
Oct 14 10:22:11 gbue4k daemon.notice ntpdate[2152]: adjust time server 131.211.8.244 offset -0.000792 sec
Oct 14 10:22:19 gbue4k daemon.notice ntpdate[2222]: adjust time server 131.211.8.244 offset 0.000519 sec
Oct 14 10:22:29 gbue4k cron.info crond[1914]: (readme.txt) ORPHAN (no passwd entry)
Oct 14 10:22:30 gbue4k daemon.notice ntpdate[2290]: adjust time server 87.233.197.123 offset -0.000363 sec
Oct 14 10:22:43 gbue4k daemon.notice ntpdate[2386]: adjust time server 87.233.197.123 offset 0.000920 sec
Oct 14 10:22:44 gbue4k daemon.info init: Id "gui" respawning too fast: disabled for 5 minutes
Oct 14 10:22:44 gbue4k daemon.info init: no more processes left in this runlevel
Oct 14 10:22:56 gbue4k daemon.notice ntpdate[2459]: adjust time server 87.233.197.123 offset -0.000020 sec
Oct 14 10:23:01 gbue4k cron.info crond[1914]: (readme.txt) ORPHAN (no passwd entry)
Oct 14 10:23:09 gbue4k daemon.notice ntpdate[2493]: adjust time server 87.233.197.123 offset -0.000125 sec
Oct 14 10:23:20 gbue4k daemon.notice ntpdate[2530]: adjust time server 87.233.197.123 offset 0.000077 sec
Oct 14 10:23:34 gbue4k daemon.notice ntpdate[2564]: adjust time server 87.233.197.123 offset 0.000623 sec
Oct 14 10:24:01 gbue4k cron.info crond[1914]: (readme.txt) ORPHAN (no passwd entry)
Oct 14 10:25:01 gbue4k cron.info crond[1914]: (readme.txt) ORPHAN (no passwd entry)
Oct 14 10:26:01 gbue4k cron.info crond[1914]: (readme.txt) ORPHAN (no passwd entry)
Oct 14 10:27:01 gbue4k cron.info crond[1914]: (readme.txt) ORPHAN (no passwd entry)
Oct 14 10:27:57 gbue4k daemon.notice ntpdate[3250]: adjust time server 91.148.192.49 offset 0.006669 sec
Oct 14 10:28:01 gbue4k cron.info crond[1914]: (readme.txt) ORPHAN (no passwd entry)
Oct 14 10:28:08 gbue4k daemon.notice ntpdate[3341]: adjust time server 91.148.192.49 offset 0.001038 sec
Oct 14 10:28:15 gbue4k daemon.notice ntpdate[3393]: adjust time server 91.148.192.49 offset -0.000043 sec
Oct 14 10:28:24 gbue4k daemon.notice ntpdate[3468]: adjust time server 91.148.192.49 offset 0.000772 sec
Oct 14 10:28:33 gbue4k daemon.notice ntpdate[3531]: adjust time server 91.148.192.49 offset -0.000436 sec
Oct 14 10:28:41 gbue4k daemon.notice ntpdate[3586]: adjust time server 91.148.192.49 offset -0.000047 sec
Oct 14 10:28:48 gbue4k daemon.info init: Id "gui" respawning too fast: disabled for 5 minutes
Oct 14 10:28:49 gbue4k daemon.notice ntpdate[3658]: adjust time server 91.148.192.49 offset 0.000540 sec
Oct 14 10:28:58 gbue4k daemon.notice ntpdate[3703]: adjust time server 91.148.192.49 offset -0.000600 sec
Oct 14 10:29:01 gbue4k cron.info crond[1914]: (readme.txt) ORPHAN (no passwd entry)
Oct 14 10:29:11 gbue4k daemon.notice ntpdate[3740]: adjust time server 91.148.192.49 offset 0.000883 sec
Oct 14 10:29:37 gbue4k daemon.notice ntpdate[3805]: adjust time server 213.136.0.252 offset -0.000035 sec

wtmp contains a lot of garbage and a lot of gui 4.1.20-1.9 entries

Full logs attached.logs.zip

That's what I could find out.
I already reflashed through recovery mode (http) and through USB. Every time it seems to run just fine whole day until I turn the thing off.

[dntaylor]

I have GigaBlue UHD QUAD 4K, when it has been powered off and switched back on it will not boot up unless the TV is switched on. TheVix sign on the lcd display just stays on . It is like it needs a compliance handshake from the TV'series HDMI before it fully boots up. It works fine swiching it to and from standby without the TV being switched on but this has never bothered me that much as we don't tend to have many powere failures if any. But thinking about it, it would be a pain if you were on holiday and had a few programes to record on timer and there was a power failure! Using OpenViX 5.3.001

[hh2]

I have GigaBlue UHD QUAD 4K, when it has been powered off and switched back on it will not boot up unless the TV is switched on. TheVix sign on the lcd display just stays on . It is like it needs a compliance handshake from the TV'series HDMI before it fully boots up. It works fine swiching it to and from standby without the TV being switched on but this has never bothered me that much as we don't tend to have many powere failures if any. But thinking about it, it would be a pain if you were on holiday and had a few programes to record on timer and there was a power failure! Using OpenViX 5.3.001

I have to try this, because I don't use a tv, but a receiver and a projector, which are both indeed turned off.
I have all HDMI CEC-stuff turned off, but if we can turn off this "feature" it would be great.

[hh2]

So with just turning on the receiver (not the projector) and powering it on it starts right away and is up and running in seconds!
I think this might also have been the problem on 5.3 then.
I hope this is a "feature" that can be turned off in a future update
Thanks for the help, I didn't want to reflash again (and also didn't want to switch to another image, as I have OpenVix on my vu+ as well and I like it).

[Andy_Hazza]

Doubt its a feature, you just need to lear to turn on beforehand!


Sent from my iPhone using Tapatalk

[hh2]

Doubt its a feature, you just need to lear to turn on beforehand!

No, it's a bug, but I wanted to put it nicely.
For now this works, but like said by dntaylor: if power goes out while you're not there it won't boot up again after.
It's not always possible to also turn on a tv or receiver.

[ccs]

Maybe a powered hdmi switch between the GBlue and the projector could be used to kid the box?

Not sure how, but there might be a way.

[hh2]

Maybe a powered hdmi switch between the GBlue and the projector could be used to kid the box?

Not sure how, but there might be a way.

I guess this is a software issue, not a hardware issue. I have a collegue with a Gigablue, he uses another image, so I let him try the same. If the box boots there then this is an issue in OpenVIX, if his box also doesn't boot maybe it's an issue in Enigma?

[ccs]

I guess this is a software issue, not a hardware issue. I have a collegue with a Gigablue, he uses another image, so I let him try the same. If the box boots there then this is an issue in OpenVIX, if his box also doesn't boot maybe it's an issue in Enigma?

…. or more likely a problem with the Gigablue drivers.

[twol]

I don‘t have this issue .... but I have a ViX mod for Giga during booting... and my boxes boot regardless of the receiver or TV powered on ... but I will remove the change just to test ... if it is the issue will issue a Pull.

Update: ...... doesn't make a difference my boxes boot regardless.

[twol]

So found the problem will issue a Pull ......... so probably in next ViX release

[hh2]

That would be great! I only run 1 image, no multiboot (I don't need that).