Gigablue UHD Trio 4k stuck on boot

[Willo3092]

I've just flashed partition 2 with ViX 5.4.002 and stuck on boot again so clearly a problem with the image for this box.
I've learned that you don't need to insert a usb to get it working though.
Just power on and press the recovery button and you can revert back to partition 1 in the recovery menu or flash another image via the network menu.

[twol]

I've just flashed partition 2 with ViX 5.4.002 and stuck on boot again so clearly a problem with the image for this box.
I've learned that you don't need to insert a usb to get it working though.
Just power on and press the recovery button and you can revert back to partition 1 in the recovery menu or flash another image via the network menu.

Can you boot the partition with Vix and then telnet into the box and logon (root) - at this point there will be no password set but just in case we need to go further enter passwd and type in a password (2 x) then enter enigma2 and see whats in the terminal log. Post here if possible.
Teamblue is an OE-A image so something strange is happening if ATV/VIX don’t load

[Willo3092]

It won't boot into ViX at all, just sticks on boot.
I've just flashed HD Freaks to partition 3 and that boots okay.

[twol]

It won't boot into ViX at all, just sticks on boot.
I've just flashed HD Freaks to partition 3 and that boots okay.

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

[squig007]

Same here all other work ok except vix and openatv

[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

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

Enigma2_crash.log

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(booto ptions),3M(baseparam),4M(pqparam),4M(logo),4M(devi ceinfo),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.