Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

Install slot

There is a script to set the clock before enigma starts.
 
In the absence of a working network connection the script delay is 10-15 seconds at most IIRC. My old GBQuad Plus takes almost two minutes to boot, even with a working ethernet connection. My HiSilicon HD61 will boot in 35 seconds even on flaky WiFi.
 
It would be helpful to have a debug log... but if it is before enigma boots that is a problem.
 
In the absence of a working network connection the script delay is 10-15 seconds at most IIRC. My old GBQuad Plus takes almost two minutes to boot, even with a working ethernet connection. My HiSilicon HD61 will boot in 35 seconds even on flaky WiFi.
I have indeed the same experience with the old GB Quad Plus. It always had an ethernet connection and was extremely slow booting after getting power. Same slow booting as this brand new box.

Would that script work when having no power for days?
 
I have indeed the same experience with the old GB Quad Plus. It always had an ethernet connection and was extremely slow booting after getting power. Same slow booting as this brand new box.

Would that script work when having no power for days?
The script to set the time is part of the start-up sequence of linux init jobs before enigma loads. This will execute on every boot, irrespective of deep standby or cold boot from a no-power state. The first init job restores the RTC from the stored fake-hwclock settings unless the RTC already has a greater linux epoch time than the stored value. A subsequent job tries to get NTP from an online server, but this can be delayed 10-15 seconds if there is not a working wifi or ethernet network connection. Every box I have had until now would not maintain the RTC status during deep standby (my Quad+, mut@nt HD51, AX61HD). My current daily use machine is a Vu+ Uno 4kSE which does keep the RTC status during deep standby, but will lose the clock time if I unplug the power while in deep.
 
So it's always there?
If so, there is no explain for the extreme long boottime if the GB's, is there? My othere boxes don't show this phenomenon.
My gigablue boxes have always had a slow boot up…compared to the hisilicon boxes…however, mesured recently and my Pro is faster than my Vu+ duo4kse
 
My gigablue boxes have always had a slow boot up…compared to the hisilicon boxes…however, mesured recently and my Pro is faster than my Vu+ duo4kse
Yes but yours have a network connection, right?
 
Two things cross my mind, from a lot of posts read and my own experience:

1) at 36/37% during botting-up from scratch E2 is checking out the network (I just moved house and my new modem's address is different now). In my current circumstance a full reboot lasts for ages! E2 restart is fast. No checking the network then... I suppose that when I finally get the time to install E2 from scratch it will not be doing the "37% slow and forever dance"... All my recs are doing it now and probably the only explanation I can think of is that...

2) On the other hand, OpenPLi has been shown to fcuk up multiboot in some instances, when mixed with OE-A images (you haven't said if you had that installed in your GB)... Zgemma H7, H9 Twin/Combo, Edision+ didn't like that combination...
 
Like I said above, can we have some debug logs please, otherwise we might as well close the thread as unsolvable.
 

OpenViX Feeds Status

Back
Top