Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[VU+ Ultimo4K] No video output, green band on display

lincsat

ViX Beta Tester
Joined
May 3, 2011
Messages
871
Reaction score
19
Points
18
This is an occasional bug that I noticed once on 5.4.013, so I did a flash with settings restore to 5.4.016 and it has just happened again Today.

The screen goes blank with no output signal and on the front LED I just get a thick Green horizontal band. Box still responds to networking and init 4/ init 3 or killall -9 enigma2 doesn't recover, it needs a hard reboot.

No crash log is created, the last few entries from the debug log are below. I have a FTV card inserted but no CI module, the last entries suggest it's detected a CI module, could that be the problem?


Code:
14:04:21.1956 [SoftcamManager] oscam-11703 already running
14:04:21.1978 [SoftcamManager] Checking if oscam-11703 is frozen
14:04:21.1980 [Console] command: wget -T 1 http://127.0.0.1:10001/status.html -O /tmp/status.html &> /tmp/frozen
14:04:21.1981 [eConsoleAppContainer] Starting /bin/sh
14:04:21.1989 [Console] pid = 8448
14:04:21.3947 [Console] finished: wget -T 1 http://127.0.0.1:10001/status.html -O /tmp/status.html &> /tmp/frozen
14:04:23.3970 [SoftcamManager] oscam-11703 is responding like it should
14:04:23.3991 [Task] job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None
14:08:59.3801 [NetworkTime] Updating
14:08:59.3803 [Console] command: /usr/bin/ntpdate-sync
14:08:59.3804 [eConsoleAppContainer] Starting /bin/sh
14:09:07.2202 [Console] finished: /usr/bin/ntpdate-sync
14:09:07.2204 [NetworkTime] setting E2 time: 1636553347.22
14:11:16.8817 [gRC] main thread is non-idle! display spinner!
14:11:32.2797 [gRC] main thread is non-idle! display spinner!
14:11:40.9473 [Avahi] watch activated: 0x1
14:11:40.9792 [Avahi] avahi_timeout_update
14:11:43.5191 [Avahi] timeout elapsed
14:11:43.5277 [Avahi] avahi_timeout_update
14:12:05.0340 [CI] Slot 0: reset requested
14:12:05.0343 [CI] flush
14:12:05.0344 [CI] ci inserted in slot 0
14:12:05.0355 [CI] Slot 1: reset requested
14:12:05.0355 [CI] flush
14:12:05.0356 [CI] ci inserted in slot 1
========== Enigma2 log ends ==========
 
This is an occasional bug that I noticed once on 5.4.013, so I did a flash with settings restore to 5.4.016 and it has just happened again Today.

The screen goes blank with no output signal and on the front LED I just get a thick Green horizontal band. Box still responds to networking and init 4/ init 3 or killall -9 enigma2 doesn't recover, it needs a hard reboot.

No crash log is created, the last few entries from the debug log are below. I have a FTV card inserted but no CI module, the last entries suggest it's detected a CI module, could that be the problem?


Code:
14:04:21.1956 [SoftcamManager] oscam-11703 already running
14:04:21.1978 [SoftcamManager] Checking if oscam-11703 is frozen
14:04:21.1980 [Console] command: wget -T 1 http://127.0.0.1:10001/status.html -O /tmp/status.html &> /tmp/frozen
14:04:21.1981 [eConsoleAppContainer] Starting /bin/sh
14:04:21.1989 [Console] pid = 8448
14:04:21.3947 [Console] finished: wget -T 1 http://127.0.0.1:10001/status.html -O /tmp/status.html &> /tmp/frozen
14:04:23.3970 [SoftcamManager] oscam-11703 is responding like it should
14:04:23.3991 [Task] job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None
14:08:59.3801 [NetworkTime] Updating
14:08:59.3803 [Console] command: /usr/bin/ntpdate-sync
14:08:59.3804 [eConsoleAppContainer] Starting /bin/sh
14:09:07.2202 [Console] finished: /usr/bin/ntpdate-sync
14:09:07.2204 [NetworkTime] setting E2 time: 1636553347.22
14:11:16.8817 [gRC] main thread is non-idle! display spinner!
14:11:32.2797 [gRC] main thread is non-idle! display spinner!
14:11:40.9473 [Avahi] watch activated: 0x1
14:11:40.9792 [Avahi] avahi_timeout_update
14:11:43.5191 [Avahi] timeout elapsed
14:11:43.5277 [Avahi] avahi_timeout_update
14:12:05.0340 [CI] Slot 0: reset requested
14:12:05.0343 [CI] flush
14:12:05.0344 [CI] ci inserted in slot 0
14:12:05.0355 [CI] Slot 1: reset requested
14:12:05.0355 [CI] flush
14:12:05.0356 [CI] ci inserted in slot 1
========== Enigma2 log ends ==========

hate to say it but flash to ViX 6.0 and lets see how it goes
 
I'm still using a plugin that's not fully compatible with PY3 yet, that's why I'm still with a PY2 image
 
I'm still using a plugin that's not fully compatible with PY3 yet, that's why I'm still with a PY2 image

Majority of plugins have moved over to py3 now though there's still a few that haven't and unlikely will as they haven't been maintained for a few years.
 
Speaking of plugins can developers produce py3 and pyo files without the need of .py files?

Sorry I realized that this wasn't in the testers thread, can this post be moved please?
 
Last edited:
Speaking of plugins can developers produce py3 and pyo files without the need of .py files?

You really need source, although obviously you can disassemble an ipk and get some python code
 
The IPTV Bouquet maker. There is a PY3 release but not downloading from the M3U4U editing site yet.
 
The IPTV Bouquet maker. There is a PY3 release but not downloading from the M3U4U editing site yet.

??
Huevos and I reworked that plugin to make it really work in py3, so the one in our 6.0 plugins should be fine, certainly has worked for us even with a difficult provider (redirected url‘s)
 
I tried the build in the feeds and it behaves the same as the build from BliNeR-KeY - It doesn't download from the M3U4U editor site. I don't know if it checks the link before downloading thereby triggering the flood protection or it doesn't like the format.
 
I tried the build in the feeds and it behaves the same as the build from BliNeR-KeY - It doesn't download from the M3U4U editor site. I don't know if it checks the link before downloading thereby triggering the flood protection or it doesn't like the format.

Perhaps you can enlighten me as to what the M3U4U editor site does for/with the IPTV Bouquet Maker -pm me if there are issues not for discussion here. Just interested because the e2m3u2 bouquets generated are pretty easily modified.
 
It's a channel/group sorter and EPG source. The site downloads the M3U or API from the host, then you can sort the channels or assign EPG for channels that do not have it on the host server.

I have used the override file for sorting but find the M3U4U site easier. It's also useful for servers that have blocked M3U download, you can download the API and then use the M3U4U M3U file in the bouquet maker.

You can use the M3U4U site for free if you wanted to have a look and see what's happening.
 
It's a channel/group sorter and EPG source. The site downloads the M3U or API from the host, then you can sort the channels or assign EPG for channels that do not have it on the host server.

I have used the override file for sorting but find the M3U4U site easier. It's also useful for servers that have blocked M3U download, you can download the API and then use the M3U4U M3U file in the bouquet maker.

You can use the M3U4U site for free if you wanted to have a look and see what's happening.
So you are using the M3u4u online facilities to edit and then get the IPTV Bouquet Maker to read and generate the bouquets?
 
That's pretty much it, yes.

so how do you tell e2m3u2bouquet to process it ? in the config.xml ? and if so what doesn't e2m3u2bouqet dislike?
you can post an edited e2m3u2bouquet log and E2 debug log if that helps

just trying to fix the issue for you!
 
I'll take this off the open forum so I can share more detail.
 
OK, thanks to twol, I now have a good IPTV Bouquet maker so have upgraded to Openvix 6. I still have the crash problem, this time it happened whilst making an image backup.

Last few log entries below
Code:
16:41:19.8948 [ImageManager] Stage4: Complete.
16:41:20.7600 [ImageManager] Stage5: Moving from work to backup folders
16:41:20.8544 [ImageManager] Stage5: Removing Swap.
16:41:20.8740 [ImageManager] Stage5: Image created in /media/usb/imagebackups/ViX-Ultimo4K-release-6.0.002-20211116_163134
16:41:20.8741 [ImageManager] Stage5: Complete.
16:41:21.8922 [Console] command: cd /media/usb/imagebackups/ViX-Ultimo4K-release-6.0.002-20211116_163134 && zip -r /media/usb/imagebackups/ViX-Ultimo4K-release-6.0.002-20211116_163134.zip *
16:41:21.8924 [eConsoleAppContainer] Starting /bin/sh
16:41:41.0227 [gRC] main thread is non-idle! display spinner!
16:41:49.5576 [Avahi] watch activated: 0x1
16:41:49.5795 [Avahi] avahi_timeout_update
16:41:50.7433 [Avahi] timeout elapsed
16:41:50.7789 [Avahi] avahi_timeout_update
16:41:51.3633 [AVSwitch] setting aspect: 16:9
 
OK, thanks to twol, I now have a good IPTV Bouquet maker so have upgraded to Openvix 6. I still have the crash problem, this time it happened whilst making an image backup.

Last few log entries below
Code:
16:41:19.8948 [ImageManager] Stage4: Complete.
16:41:20.7600 [ImageManager] Stage5: Moving from work to backup folders
16:41:20.8544 [ImageManager] Stage5: Removing Swap.
16:41:20.8740 [ImageManager] Stage5: Image created in /media/usb/imagebackups/ViX-Ultimo4K-release-6.0.002-20211116_163134
16:41:20.8741 [ImageManager] Stage5: Complete.
16:41:21.8922 [Console] command: cd /media/usb/imagebackups/ViX-Ultimo4K-release-6.0.002-20211116_163134 && zip -r /media/usb/imagebackups/ViX-Ultimo4K-release-6.0.002-20211116_163134.zip *
16:41:21.8924 [eConsoleAppContainer] Starting /bin/sh
16:41:41.0227 [gRC] main thread is non-idle! display spinner!
16:41:49.5576 [Avahi] watch activated: 0x1
16:41:49.5795 [Avahi] avahi_timeout_update
16:41:50.7433 [Avahi] timeout elapsed
16:41:50.7789 [Avahi] avahi_timeout_update
16:41:51.3633 [AVSwitch] setting aspect: 16:9

That just shows it completing, so what happens next? It freezes or ??
 
Those are the final entries in the log. As before, the TV output switches off, the front display has just a green stripe on the bottom quarter and it needs a hard reboot to recover
 
Telnet into the box and reboot would be a safer option.
 

OpenViX Feeds Status

Back
Top