PDA

View Full Version : Gigablue UHD Trio 4k stuck on boot



squig007
08-11-20, 12:03
I have followed this https://www.world-of-satellite.com/showthread.php?62746-How-to-USB-flash-New-Multi-boot-recovery-menu-and-Image-to-Gigablue-UHD-Trio-4K-New-procedure-21-04-2020 to the letter loaded first five files fine . Then loaded new image followed instructions perfectly . Now box is stuck on boot screen showing openatv any ideas ?

Also says upgrading directory linixrootfs1 this may take several minutes . Can’t see that bit in your instructions ?

twol
08-11-20, 12:36
So I am assuming that the Trio is like the sf8008, so what happens if you depress & hold the power on/off button on the receiver, switch on whilst still holding thebutton - do you get recovery menu displayed (takes a few moments - like about 30 seconds) - if so use this to flash an image

squig007
08-11-20, 12:45
I hold in recovery button back of box then updt shows . I let go then it brings me to the recovery screen showing multiboot selector usb mutilboot image upgrade etc . Usb is recognised as it shows in top right free space etc . When I scroll down to usb murilboot image upgrade it says no image found on usb I’ve loaded it Unzipped as per instructions any ideas ?

twol
08-11-20, 14:04
I haven‘t done this in a long while but 1) make sure you have the multiboot image not the recovery image and 2) try copying the zip to the usb .......... or try the option to download from the WEB ............ once you have flashed you can forget about this **** and flash online

squig007
08-11-20, 14:25
Was able to get it to update online . It downloaded the new image and once rebooted it’s still stuck on boot screen I’m at a loss as to how to fix this. ? Do world of satellite reflash boxes for a fee?

abu baniaz
08-11-20, 14:55
Check your router for connected devices, then find IP address of receiver. Start Enigma2 in console mode, it should reveal the problem. Links to guide to commands/putty in my signature if you need it.

squig007
08-11-20, 15:36
Sorry way over my head . Do you know of WOS offer a reflash service for a fee ?

abu baniaz
08-11-20, 15:43
I don't know. Ask them on support ticket.

I am sure people can help you remotely with TeamViewer

twol
08-11-20, 16:06
Was able to get it to update online . It downloaded the new image and once rebooted it’s still stuck on boot screen I’m at a loss as to how to fix this. ? Do world of satellite reflash boxes for a fee?

Which Image did you download??

squig007
08-11-20, 17:17
Tried with latest vix and openatv

Willo3092
08-11-20, 17:24
Has anyone successfully flashed a Trio with ViX using this guide? My Trio was also stuck on boot.
The recovery emmc flashes fine but then won't boot.
The usb recovery will not see the zipped mmc file even though I just used it to flash the emmc. I tried extracting it but no different.
Network recovery downloads ViX and flashes it but still won't boot.
I have just managed to get it to start up by flashing TeamBlue image via network but will wait to see if anyone else has had any success before flashing ViX back.

squig007
08-11-20, 17:41
That the exact same issue as me to the letter. It won’t recognise the new image at all even though it recognises the Emmc . Although I haven’t tried any other image except open atv and vix

abu baniaz
08-11-20, 17:49
I have moved the posts away from guide thread and created a separate thread. If someone with the receiver can get serial/boot logs, that will be greatly appreciated.

ronand
08-11-20, 17:49
When you are in the recovery menu is there an option to update it? If it is like the sf8008 recovery menu then scroll through the list of images available for download and you might see it.

squig007
08-11-20, 17:51
Just tried team blue online download and it worked first time defiantly something wrong with vix and openatv that’s what I’m saying the updates are tills stuck on boot screen except team blue image

Willo3092
08-11-20, 19:52
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
08-11-20, 19:59
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
08-11-20, 20:06
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
08-11-20, 20:11
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
08-11-20, 20:12
Same here all other work ok except vix and openatv

Willo3092
08-11-20, 20:21
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
08-11-20, 20:22
Type enigma2

twol
08-11-20, 20:25
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
08-11-20, 20:35
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
08-11-20, 20:41
Found it

60859

twol
08-11-20, 20:44
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
08-11-20, 20:49
Found it

60859


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

Willo3092
08-11-20, 20:50
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
08-11-20, 21:07
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
08-11-20, 22:11
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
08-11-20, 22:23
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
08-11-20, 22:28
This is the debug log from a full reboot.

60860

Willo3092
08-11-20, 22:30
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
08-11-20, 22:37
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
08-11-20, 22:45
This is the debug log from a full reboot.

60860


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

squig007
08-11-20, 22:54
Did you load image unzipped or zipped onto usb bud ?

Willo3092
08-11-20, 23:11
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
08-11-20, 23:19
When using the recovery menu you need to use the correct zip file [openvix-5.4.002.release-gbtrio4k_recovery_emmc.zip]

Willo3092
08-11-20, 23:24
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
08-11-20, 23:27
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.

squig007
09-11-20, 20:26
There’s still and issue with vix and openatv they won’t download the rest work fine except vix and openatv

twol
09-11-20, 20:44
There’s still and issue with vix and openatv they won’t download the rest work fine except vix and openatv

Its being worked on - the following version works fine https://www.openvix.co.uk/openvix-builds/gbtrio4k/openvix-5.4.001.release-gbtrio4k_mmc.zip, only the latest fails in tests. Hopefully there will be a resolution shortly

squig007
09-11-20, 23:33
Is openatv being worked on as well bud do you know ?

twol
10-11-20, 12:25
Is openatv being worked on as well bud do you know ?

No idea - if its common issue then Yes, otherwise you need to raise it with them

Sicilian
10-11-20, 18:09
Is openatv being worked on as well bud do you know ?

3rd November build of OpenATV boots fine.

OpenViX 5.4.001 also boots fine.

We may have found the issue, I'm running a dev build this evening to check.

squig007
10-11-20, 20:47
Briliant mate can you let me know if it works ok so I can try it on my box ?

Sicilian
11-11-20, 09:23
Fixed in build 5.4.003, release build running now. All going well will be completed in 1-2 days.

Delagroov
16-11-20, 18:02
Hi Sicilian,

Long time ago

I just bought me a trio also, and luckily i knew not to update.
Seems to be a problem with a new kernel update as far as i heard.

Cheers

Sicilian
16-11-20, 18:03
Hi Silician,
Long time ago

I just bought me a trio also, and luckely i knew not to update.
Seems to be a problem with a new kernel update as far as i heard.

Cheers

See post above, its fixed.

Delagroov
16-11-20, 18:24
Oh I thought that build from 5-11 was havin issues and you were still building a new image

Because i also have atv on multiboot and that was still not booting

Delagroov
16-11-20, 19:40
Ag forget last post, I have eyesight problem and did not see the correct date