Gigablue UHD Trio 4k stuck on boot

[Willo3092]

You still maybe able to telnet into the box, just depends how far it has reached in the process..... especially with these sf8008/trio4k boxes ... they are kind of different during the boot up.
Both hdf and teamblue use the same image build process, so I would expect it to boot and then crash during the initial steps - thats why I expect you to be able to telönet

You're right, I can telnet in. How do I get to the terminal log?

 

[twol]

Type enigma2

 

[twol]

You can send the log to a file e.g enigma2 > /tmp/log.txt and then filezilla to your pc (but need passwd set first)

 

[Willo3092]

Does this mean anything to you?



Welcome to OpenViX for gbtrio4k
openvix 5.4 gbtrio4k

gbtrio4k login: root
Password:
Last login: Sun Nov 8 19:19:52 GMT 2020 on pts/0
root@gbtrio4k:~# enigma2 > /tmp/log.txt
< 1170.7218> 19:37:56.8434 [Avahi] avahi_timeout_new
< 1170.7222> 19:37:56.8438 [Avahi] avahi_watch_new(3 0x1)
< 1170.7223> 19:37:56.8439 [Avahi] avahi_timeout_update
< 1170.7225> 19:37:56.8441 [Avahi] avahi_timeout_new
< 1170.7227> 19:37:56.8443 [Avahi] avahi_timeout_free
< 1170.7229> 19:37:56.8445 [Avahi] avahi_timeout_new
< 1170.7232> 19:37:56.8448 [Avahi] avahi_timeout_free
< 1170.7232> 19:37:56.8448 [Avahi] avahi_timeout_new
< 1170.7234> 19:37:56.8450 [Avahi] avahi_timeout_free
< 1170.7235> 19:37:56.8451 [Avahi] avahi_timeout_new
< 1170.7238> 19:37:56.8454 [Avahi] avahi_timeout_free
< 1170.7239> 19:37:56.8455 [Avahi] avahi_timeout_new
< 1170.7242> 19:37:56.8458 [Avahi] avahi_timeout_free
< 1170.7243> 19:37:56.8459 [Avahi] avahi_timeout_new
< 1170.7246> 19:37:56.8462 [Avahi] avahi_timeout_free
< 1170.7247> 19:37:56.8463 [Avahi] client state: 2
< 1170.7249> 19:37:56.8465 [Avahi] avahi_timeout_new
< 1170.7253> 19:37:56.8469 [Avahi] avahi_timeout_free
< 1170.7253> 19:37:56.8469 [eInit] + (1) Background File Eraser
< 1170.7254> 19:37:56.8470 [eInit] + (5) Tuxtxt
< 1170.7254> 19:37:56.8470 [eInit] + (8) graphics acceleration manager
< 1170.7255> 19:37:56.8471 [bcm] /dev/fb0 No such file or directory
< 1170.7256> 19:37:56.8472 [eInit] + (9) GFBDC
< 1170.7256> 19:37:56.8472 [fb] /dev/fb0 No such file or directory
< 1170.7257> 19:37:56.8473 [fb] framebuffer /dev/fb0 not available
< 1170.7257> 19:37:56.8473 [gFBDC] no framebuffer available
Segmentation fault
root@gbtrio4k:~#

 

[Willo3092]

Found it

View attachment Enigma2_crash.log

 

[twol]

Does this mean anything to you?



Welcome to OpenViX for gbtrio4k
openvix 5.4 gbtrio4k

gbtrio4k login: root
Password:
Last login: Sun Nov 8 19:19:52 GMT 2020 on pts/0
root@gbtrio4k:~# enigma2 > /tmp/log.txt
< 1170.7218> 19:37:56.8434 [Avahi] avahi_timeout_new
< 1170.7222> 19:37:56.8438 [Avahi] avahi_watch_new(3 0x1)
< 1170.7223> 19:37:56.8439 [Avahi] avahi_timeout_update
< 1170.7225> 19:37:56.8441 [Avahi] avahi_timeout_new
< 1170.7227> 19:37:56.8443 [Avahi] avahi_timeout_free
< 1170.7229> 19:37:56.8445 [Avahi] avahi_timeout_new
< 1170.7232> 19:37:56.8448 [Avahi] avahi_timeout_free
< 1170.7232> 19:37:56.8448 [Avahi] avahi_timeout_new
< 1170.7234> 19:37:56.8450 [Avahi] avahi_timeout_free
< 1170.7235> 19:37:56.8451 [Avahi] avahi_timeout_new
< 1170.7238> 19:37:56.8454 [Avahi] avahi_timeout_free
< 1170.7239> 19:37:56.8455 [Avahi] avahi_timeout_new
< 1170.7242> 19:37:56.8458 [Avahi] avahi_timeout_free
< 1170.7243> 19:37:56.8459 [Avahi] avahi_timeout_new
< 1170.7246> 19:37:56.8462 [Avahi] avahi_timeout_free
< 1170.7247> 19:37:56.8463 [Avahi] client state: 2
< 1170.7249> 19:37:56.8465 [Avahi] avahi_timeout_new
< 1170.7253> 19:37:56.8469 [Avahi] avahi_timeout_free
< 1170.7253> 19:37:56.8469 [eInit] + (1) Background File Eraser
< 1170.7254> 19:37:56.8470 [eInit] + (5) Tuxtxt
< 1170.7254> 19:37:56.8470 [eInit] + (8) graphics acceleration manager
< 1170.7255> 19:37:56.8471 [bcm] /dev/fb0 No such file or directory
< 1170.7256> 19:37:56.8472 [eInit] + (9) GFBDC
< 1170.7256> 19:37:56.8472 [fb] /dev/fb0 No such file or directory
< 1170.7257> 19:37:56.8473 [fb] framebuffer /dev/fb0 not available
< 1170.7257> 19:37:56.8473 [gFBDC] no framebuffer available
Segmentation fault
root@gbtrio4k:~#

Thanks, never seen that before - if the trio4k is like the sf8008 the real reason for the crash is often hidden at this point(pain in the ****) is this from the terminal or log.txt??? The fact that avahi is active shows that it is a fair way into initialisation

 

[twol]

Found it

View attachment 60859

Need a pc to have a look - have to wait for strctly to finish

 

[Willo3092]

This is the crash log

OpenViX Enigma2 Crashlog

Crashdate = Sun Nov 8 19:39:07 2020

Creator = OpenViX
Version = 5.4
Build = 002
Dev = 013
Type = release
Machine = gbtrio4k
URL = http://www.world-of-satellite.com
Compiled = Nov 4 2020
Skin = Default Skin
Component = enigma2

Kernel CMDline = console=ttyAMA0,115200 root=/dev/mmcblk0p16 rootsubdir=linuxrootfs2 rootfstype=ext4 kernel=/dev/mmcblk0p13 userdataroot=/dev/mmcblk0p16 userdatasubdir=userdata2 blkdevparts=mmcblk0:1M(boot),1M(bootargs),1M(bootoptions),3M(baseparam),4M(pqparam),4M(logo),4M(deviceinfo),4M(softwareinfo),4M(loaderdb),32M(loader),8M(trustedcore),16M(linuxkernel1),16M(linuxkernel2),16M(linuxkernel3),16M(linuxkernel4),-(userdata) coherent_pool=2M mem=1G mmz=ddr,0,0,72M vmalloc=500M MACHINEBUILD=gbtrio4k OEM=gigablue MODEL=gbtrio4k
Nim Sockets =


< 1240.9766> 19:39:07.0982 [Avahi] avahi_timeout_new
< 1240.9768> 19:39:07.0984 [Avahi] avahi_watch_new(3 0x1)
< 1240.9769> 19:39:07.0985 [Avahi] avahi_timeout_update
< 1240.9770> 19:39:07.0986 [Avahi] avahi_timeout_new
< 1240.9773> 19:39:07.0989 [Avahi] avahi_timeout_free
< 1240.9774> 19:39:07.0990 [Avahi] avahi_timeout_new
< 1240.9776> 19:39:07.0992 [Avahi] avahi_timeout_free
< 1240.9777> 19:39:07.0993 [Avahi] avahi_timeout_new
< 1240.9778> 19:39:07.0994 [Avahi] avahi_timeout_free
< 1240.9779> 19:39:07.0995 [Avahi] avahi_timeout_new
< 1240.9782> 19:39:07.0998 [Avahi] avahi_timeout_free
< 1240.9782> 19:39:07.0998 [Avahi] avahi_timeout_new
< 1240.9785> 19:39:07.1001 [Avahi] avahi_timeout_free
< 1240.9786> 19:39:07.1002 [Avahi] avahi_timeout_new
< 1240.9788> 19:39:07.1004 [Avahi] avahi_timeout_free
< 1240.9788> 19:39:07.1004 [Avahi] client state: 2
< 1240.9791> 19:39:07.1007 [Avahi] avahi_timeout_new
< 1240.9794> 19:39:07.1010 [Avahi] avahi_timeout_free
< 1240.9795> 19:39:07.1011 [eInit] + (1) Background File Eraser
< 1240.9795> 19:39:07.1011 [eInit] + (5) Tuxtxt
< 1240.9795> 19:39:07.1011 [eInit] + (8) graphics acceleration manager
< 1240.9796> 19:39:07.1012 [bcm] /dev/fb0 No such file or directory
< 1240.9796> 19:39:07.1012 [eInit] + (9) GFBDC
< 1240.9796> 19:39:07.1013 [fb] /dev/fb0 No such file or directory
< 1240.9797> 19:39:07.1013 [fb] framebuffer /dev/fb0 not available
< 1240.9797> 19:39:07.1013 [gFBDC] no framebuffer available


dmesg

 

[twol]

ANy chance you can download 5.3.019 (from the archives) and try to flash with hdf??? Or with the recovery system



Actually 038 would be better

 

[Willo3092]

Both TeamBlue and HDF only give you the option to flash online and only their own images are listed.

Trying Automatic FullBackup plugin.

Success, 5.3.038 flashed.

 

[twol]

Teamblue use flashonline which should find any zip file on your hdd and add it to the list of images so copy the vix zip with filezilla

 

[Willo3092]

This is the debug log from a full reboot.

View attachment Enigma2_debug_2020-11-08_21-26-41.log

 

[Willo3092]

Teamblue use flashonline which should find any zip file on your hdd and add it to the list of images so copy the vix zip with filezilla

I managed to flash using AutomaticFullBackup - Is it the debug log you need?

 

[twol]

I managed to flash using AutomaticFullBackup - Is it the debug log you need?

So you manaed to flash which image. And did it load or?

 

[twol]

This is the debug log from a full reboot.

View attachment 60860

So thats 5.3 ver038 it seems to be running?
Appreciate all the help

 

[squig007]

Did you load image unzipped or zipped onto usb bud ?

 

[Willo3092]

Did you load image unzipped or zipped onto usb bud ?

Which image, the 5.3.038 one?
If so I just copied the zipped file to imagebackups and unzipped and flashed with automatic fullbackup. It doesn't give you the option to choose a partition though, just flashes the active one.

If you mean flashing from the usb recovery manager, it wouldn't flash 5.4.002 either zipped or unzipped. It said it couldn't see an image file.

 

[ronand]

When using the recovery menu you need to use the correct zip file [openvix-5.4.002.release-gbtrio4k_recovery_emmc.zip]

 

[Willo3092]

When using the recovery menu you need to use the correct zip file [openvix-5.4.002.release-gbtrio4k_recovery_emmc.zip]

That's probably where I went wrong then. I thought that the recovery_emmc was only for the 'flash recovery image' section of the recovery menu. I tried to use the mmc version in the 'usb image flashing' bit.

 

[ronand]

Sorry I might have got mixed up. the sf8008 has a similar system but I havent used it in a while and memory isnt what it was. Although it might be no harm to flash the recovery from usb to make sure you have the latest installed if you haven't anything important in the other slots.