[ET10x00] No VIX country view picture when rebooting

[ccs]

Just couched flashed from 4.2.016 to 4.2.019, and the VIX country view picture doesn't show when booting.

It was missing when the flash rebooted for the first time, so no settings restore at that point.

Just a black screen. Everything else seems ok.

 

[ccs]

root@et10000:~# ls -l /usr/share
drwxr-xr-x    8 root     root           784 Nov 29 10:17 alsa
drwxr-xr-x    2 root     root           312 Oct  9 17:04 avahi
-rw-r--r--    1 root     root        742478 Nov 29 10:08 backdrop.mvi
-rw-r--r--    1 root     root        742478 Nov 29 10:08 bootlogo.mvi
drwxr-xr-x    3 root     root           224 Oct  8 18:03 ca-certificates
lrwxrwxrwx    1 root     root            22 Nov 23 20:11 cables.xml -> /etc/tuxbox/cables.xml
drwxr-xr-x    6 root     root           592 Oct  9 17:00 dbus-1
drwxr-xr-x    2 root     root           160 Oct  9 16:32 dict
drwxr-xr-x    9 root     root          2192 Nov 29 10:17 enigma2
drwxr-xr-x    2 root     root          1464 Nov 29 10:17 fonts
drwxr-xr-x    3 root     root           224 Oct  9 08:37 glib-2.0
drwxr-xr-x    3 root     root           224 Nov 13 13:12 gst-plugins-base
drwxr-xr-x    2 root     root           160 Oct  9 16:32 info
drwxr-xr-x    2 root     root           864 Nov 29 10:12 keymaps
drwxr-xr-x    2 root     root           232 Oct  8 18:04 locale
drwxr-xr-x    2 root     root           160 Oct  9 16:32 man
drwxr-xr-x    2 root     root           160 Oct  9 16:32 misc
drwxr-xr-x    2 root     root           760 Oct  9 16:59 nmap
drwxr-xr-x    3 root     root           232 Oct  9 16:58 opkg
drwxr-xr-x    2 root     root          1168 Oct  9 08:26 readline
lrwxrwxrwx    1 root     root            26 Nov 23 20:11 satellites.xml -> /etc/tuxbox/satellites.xml
lrwxrwxrwx    1 root     root            27 Nov 23 20:11 terrestrial.xml -> /etc/tuxbox/terrestrial.xml
drwxr-xr-x    2 root     root           376 Nov 23 20:11 tuxbox
drwxr-xr-x    2 root     root           232 Oct  9 17:08 udhcpc
drwxr-xr-x   15 root     root          2888 Nov 29 10:17 zoneinfo
root@et10000:~#

 

[abu baniaz]

Is it the same if you flash bu USB instead of flashing by Image Manager?

The debug log may show more information.

 

[No.Trace]

Hi there ...

i had the same thing after the online update from 018 to 019, but anything else works well.
I did not try another reboot since tomorrow. Perhaps at a 2nd boot the Bootlogo will work again ?!
There is something written in the "Changelog" [openvix-bootlogo] bump pr
But i do not know what it means.

CU No.Trace

P.S.: Here is my UpdateLog - View attachment ipkgupgrade.log

 

[spanner123]

Just rebooted my solo2 to check and no bootlogo/splash screen!

 

[ccs]

Debug log....

 

[iwg]

I just copied a different backdrop.mvi and bootlogo.mvi into /usr/share - from an old backup of soccer related ones I had used on Zeus I think. They displayed OK. So must be the files themselves, not the code omitting to call them. Just going to sit with the custom ones until I see another update - could try going back to -016 to compare files (can't extract them from backups). Any ideas anyone? Not a biggie obviously as its only background for a few seconds!

 

[iwg]

ignore last post - just compared /usr/share/b*.mvi from -016 and -020 same size and perms. Can't find sum command to checksum though. There is something in release notes about new bootlogos so will await update from the team.

 

[birdman]

I put my own into /etc/enigma2, so should have the standard one in /usr/share.

They show when I run showiframe on them, so there's nothing wrong with the images (which are actually the same).

root@mbtwin:/usr/share# md5sum *.mvi
665a60a75de62489f151a865dca6371b  backdrop.mvi
665a60a75de62489f151a865dca6371b  bootlogo.mvi

But that is on 4.2.018. 4.2.020 is now in place. I've just updated to that - all still OK with them (same md5sums).

The mod times of the files did change though. Those on 4.2.018 were Aug 11 19:08. ccs's on 4.2.019 are Nov 29 10:08 and mine on 4.2.020 are now Nov 29 12:32.

 

[ccs]

I went back to 4.2.0016, and nothing odd to report....

root@et10000:~# cd /usr/share
root@et10000:/usr/share# md5sum *.mvi
665a60a75de62489f151a865dca6371b  backdrop.mvi
665a60a75de62489f151a865dca6371b  bootlogo.mvi
root@et10000:/usr/share#

root@et10000:/usr/share# ls -l *.mvi
-rw-r--r--    1 root     root        742478 [B]Oct  9 16:37 backdrop.mvi[/B]
-rw-r--r--    1 root     root        742478 [B]Oct  9 16:37 bootlogo.mvi[/B]
root@et10000:/usr/share#

Mod times look odd though...

The mod times of the files did change though. Those on 4.2.018 were Aug 11 19:08. ccs's on 4.2.019 are Nov 29 10:08 and mine on 4.2.020 are now Nov 29 12:32.

 

[birdman]

There is something in release notes about new bootlogos so will await update from the team.

That may relate to the mbtwin (et. al.) boot saying "Openvix" rather then using the manufacturers mbtwin logo. This is what first show on power-on, before the "country view" appears.
But oddly that hasn't changed at all - although now I read it the comment only refers to the xpeedlx3.

 

[ccs]

... just edited my last post.

 

[iwg]

I put my own into /etc/enigma2, so should have the standard one in /usr/share.

They show when I run showiframe on them, so there's nothing wrong with the images (which are actually the same).

root@mbtwin:/usr/share# md5sum *.mvi
665a60a75de62489f151a865dca6371b  backdrop.mvi
665a60a75de62489f151a865dca6371b  bootlogo.mvi

But that is on 4.2.018. 4.2.020 is now in place. I've just updated to that - all still OK with them (same md5sums).

The mod times of the files did change though. Those on 4.2.018 were Aug 11 19:08. ccs's on 4.2.019 are Nov 29 10:08 and mine on 4.2.020 are now Nov 29 12:32.

Hi - how do I run showiframe on mine. Although they have the same checksum as your's anyway so not much point. Thanks for the md5sums command. New one to me. So we have a mixture of people seeing bootlogo and some not now even though files are the same and the -020 image can show old boot logos for those who are currently failing.

 

[birdman]

Debug log....

Shouldn't show anything useful.
The bootlog.mvi is loaded by the bootlogo init.d file, and the backdrop.mvi is loaded ny enigma2.sh before emigma2 starts (it's what showiframe does).
So nothing to do with enigma2, so nothing to show in its log.

 

[birdman]

Hi - how do I run showiframe on mine.

/usr/bin/showiframe mvi-filename
It will put the image onto the screen.
To remove it change the channel, or go into/out of standby.

PS: I've looked at the files on an et1x000 image for 4.2.019. I can't see anything wrong. /etc/init.d/bootlogo is there, plus the rcS.d symlink, /usr/share contains the correct *.mvi files.
And the showiframe runs OK on my mbtwin (both mips32 systems)
Odd.

 

[iwg]

/usr/bin/showiframe mvi-filename
It will put the image onto the screen.
To remove it change the channel, or go into/out of standby.

PS: I've looked at the files on an et1x000 image for 4.2.019. I can't see anything wrong. /etc/init.d/bootlogo is there, plus the rcS.d symlink, /usr/share contains the correct *.mvi files.
And the showiframe runs OK on my mbtwin (both mips32 systems)
Odd.

Hi Birdman, tried that init.d file from a BASH shell and got the below. Still just a black screen unless I overwrite the bootlogo.mvi with a really old one. Check sums all OK and all sym links in place. I assume /usr/share/*.mvi are issued ones and /etc/e*2 ones can overwrite. Never working since -20 - was OK on -16. Didn't check on -18 due to other problem but did not notice the issue when booting. Never had -019.

root@vusolo2:/etc/init.d# sh -x bootlogo
+ [ -f /sys/class/vtconsole/vtcon1/bind ]
+ [ -f /etc/videomode ]
+ BOOTLOGO=/usr/share/bootlogo.mvi
+ [ -f /etc/enigma2/bootlogo.mvi ]
+ BOOTLOGO=/etc/enigma2/bootlogo.mvi
+ /usr/bin/showiframe /etc/enigma2/bootlogo.mvi
/dev/dvb/adapter0/video0: Device or resource busy
+ [ -f /etc/init.d/bootlogo.py ]
+ /bin/true
root@vusolo2:/etc/init.d#

I assume video busy as I am up and runing whilst telnet-ed in but get same behaviour on a reboot

 

[birdman]

/dev/dvb/adapter0/video0: Device or resource busy

I've never seen that.

I assume video busy as I am up and runing whilst telnet-ed in but get same behaviour on a reboot

I telnet (well ssh) in and run the command. it just puts the image onto the screen.
Not sure how the device can be busy - but that will be the problem. A driver issue?

 

[ccs]

I'm seeing device busy on 4.2.016

root@et10000:/usr/bin/showiframe /usr/share/bootlogo.mvi
/dev/dvb/adapter0/video0: Device or resource busy

 

[birdman]

Just checked on an et8000. It has the problem too at 4.2.020.003 (a dev image).
It's OK at 4.2.018.

 

[birdman]

Not sure how the device can be busy - but that will be the problem. A driver issue?

No. That's not the issue.
My et8000 also gets that on 4.2.018, where the Country view shows up at start-up.

If there is a TV channel active it gets the busy error.
If it is put into standby (so the display isn't active) the command succeeds (well - it doesn't report an error).