Satellite my Zgemma H7S has never booted from deep standby

[mw3744]

Hi all,


(my 7th day with H7S, newbie)


with crossepg, autobouqets & autotimers


Day 2 pressed the red button, to check if autotimers had worked, and got 'boot' on display, but no boot and no recordings.
Cycled the power and it booted (it still hasn't failed to boot on power up).

I've tried recovery flashing: openvix 6.5 & 6.4 and OpenAtv 7.3 which I'm using now with crossepg, autobouqets & autotimers


Below are crash log and debug log from a good boot.


I've run out of ideas and any help will be much appreciated.


--------------------------------------
openATV Enigma2 crash log

crashdate=Tue Apr 30 21:09:51 2024
compiledate=Apr 18 2024
skin=Default Skin
sourcedate=2024-04-18
branch=7.3
rev=33360+5e429f8
component=enigma2

model=h7
machinebuild=zgemmah7
imageversion=7.3
imagebuild=20240421

kernelcmdline=root=/dev/mmcblk0p3 rootsubdir=linuxrootfs1 kernel=/dev/mmcblk0p2 rw rootwait h7_4.boxmode=1 brcm_cma=440M@328M brcm_cma=192M@768M console=ttyS0,115200

nimsockets:


21:09:50.9804 [Enigma] Python path is '/usr/lib/enigma2/python'.
21:09:50.9808 [Enigma] DVB API version 5, DVB API version minor 11.
21:09:50.9808 [Enigma] Enigma debug level 4.
21:09:50.9808 [Enigma] sourcedate 2024-04-18 / 7.3 33360+5e429f8.
21:09:51.0557 [Avahi] avahi_watch_new(3 0x1)
21:09:51.0577 [Avahi] client state: 2
21:09:51.0584 [eInit] + (1) Background File Eraser
21:09:51.0585 [eInit] + (5) Tuxtxt
21:09:51.0585 [eInit] + (8) graphics acceleration manager
21:09:51.0587 [bcm] /dev/fb0 Function not implemented < :-(
21:09:51.0587 [eInit] + (9) Font Render Class
21:09:51.0587 [Font] Initializing lib.
21:09:51.0589 [Font] Loading fonts.
21:09:51.0590 [Font] Intializing font cache, using max. 4MB.
21:09:51.0590 [eInit] + (9) gLCD
21:09:51.0591 [eLCD] m_oled_brightness_proc = 0
21:09:51.0591 [eDboxLCD] No oled0 or lcd0 device found!
21:09:51.0592 [eLCD] (132x64x8) buffer 0x41cb28 8448 bytes, stride 132
21:09:51.0592 [gLCDDC] resolution: 132x64x8 stride=132
21:09:51.0592 [eInit] + (9) GFBDC
21:09:51.0592 [fb] /dev/fb0 Function not implemented
21:09:51.0593 [fb] framebuffer not available
21:09:51.0593 [gFBDC] no framebuffer available


dmesg

--------------------------------------
Successful boot on power up

06:15:31.8035 [Enigma] Python path is '/usr/lib/enigma2/python'.
06:15:31.8038 [Enigma] DVB API version 5, DVB API version minor 11.
06:15:31.8038 [Enigma] Enigma debug level 4.
06:15:31.8038 [Enigma] sourcedate 2024-04-18 / 7.3 33360+5e429f8.
06:15:31.9622 [Avahi] avahi_watch_new(3 0x1)
06:15:31.9644 [Avahi] client state: 2
06:15:31.9680 [eInit] + (1) Background File Eraser
06:15:31.9682 [eInit] + (5) Tuxtxt
06:15:31.9682 [eInit] + (8) graphics acceleration manager
06:15:31.9683 [eInit] + (9) Font Render Class < :-)
06:15:31.9684 [Font] Initializing lib.
06:15:31.9761 [Font] Loading fonts.
06:15:31.9762 [Font] Intializing font cache, using max. 4MB.
06:15:31.9763 [eInit] + (9) gLCD
06:15:31.9796 [eLCD] m_oled_brightness_proc = 1
06:15:31.9797 [eLCD] found OLED display!
06:15:31.9798 [eDboxLCD] xres=132, yres=64, bpp=8 lcd_type=1
06:15:31.9798 [eLCD] (132x64x8) buffer 0x41cb28 8448 bytes, stride 132
06:15:31.9799 [gLCDDC] resolution: 132x64x8 stride=132
06:15:31.9799 [eInit] + (9) GFBDC
06:15:31.9799 [fb] /dev/fb0: 24300k video mem
06:15:31.9800 [fb] 24300k video mem
06:15:31.9835 [fb] double buffering available!
06:15:31.9836 [fb] 2 page(s) available!
06:15:32.0002 [gFBDC] resolution: 1280 x 720 x 32 (stride: 5120) pages: 2
06:15:32.0004 [gFBDC] 17100kB available for acceleration surfaces.
06:15:32.0004 [eInit] + (10) gRC

 

[bmitie]

Is the box new, did you set it up from scratch, what image did you use, has it the SSD sticking out the rear? is it working now , waht made you think pressing the red button would etc.

we can help but is box working now or is it stuck>

 

[mw3744]

The box is new and setup from scratch. 1st image was openvix-6.5.003.release-zgemmah7_recovery_emmc

I meant the red button on the remote (didn't want to mention power) - to wake it up.

It's working well (brill compared to humax foxsat) except for not waking from deep standby.

 

[bmitie]

why are you putting it in deep standby? and I would not have used emmc. have you created partitons? and are u on openatv 7.3 now?

 

[mw3744]

why are you putting it in deep standby? and I would not have used emmc. have you created partitons? and are u on openatv 7.3 now?

To save power. I used emmc because most of the advice for boot problems suggests it.
On openatv 7.3 now.
I just online flashed partition 2 with 7.3 and booted it - no change.
SSD is sticking out

 

[moshibeth]

To save power. I used emmc because most of the advice for boot problems suggests it.
On openatv 7.3 now.
I just online flashed partition 2 with 7.3 and booted it - no change.
SSD is sticking out

Flash it with willobuild on partition 3 it will give you a good idea how a finished box looks when setup correctly.