Thanks Thanks:  0
Seite 2 von 2 ErsteErste 12
Ergebnis 11 bis 17 von 17
  1. #11
    Anfänger
    Registriert seit
    25.09.2017
    Beiträge
    20
    Thanks (gegeben)
    0
    Thanks (bekommen)
    0
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Hello,
    Zitat Zitat von s3n0 Beitrag anzeigen
    You need to update everything or nothing.
    The present case shows that is not true. Of course the updater loaded all new files related to given, selected extention/plugin, but not all new system files.
    Now all works fine. After bad experiences I did not want to do unnecessary updates.
    Regards

    •   Alt Advertising

       

  2. #12
    Senior Mitglied Avatar von s3n0
    Registriert seit
    02.01.2017
    Beiträge
    1.150
    Thanks (gegeben)
    71
    Thanks (bekommen)
    281
    Total Downloaded
    323,0 KB
    Total Downloaded
    323,0 KB
    ReceiverDankeAktivitäten
    Box 1:
    Formuler F3
     
     
    Box 2:
    Vu+ Solo SE V2
     
     
    Box 3:
    Formuer F4-TURBO
     
     
    There is always a great deal of updates parallel to each other. Quite often, individual components are dependent on each other. Choosing just one thing to update can cause problems. The probability is low, but it can go wrong, especially when you wait for it the least. That's why the best way to update everything is just one thing.
    Formuler F3 (BCM 7362-A0, 2x 750 MHz, mips)
    Formuler F4 TURBO (BCM 7362-5, 2x 750 MHz, mips)
    Vu+ Solo SE V2 (BCM 7429, 2x 1300 MHz, mips)

  3. #13
    Anfänger
    Registriert seit
    31.12.2017
    Beiträge
    29
    Thanks (gegeben)
    13
    Thanks (bekommen)
    2
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Box 1:
    Octagon SF4008
     
     
    Box 2:
    Octagon SF8008
     
     
    Box 3:
    Amiko Viper Combo
     
     
    Box 4:
    Amiko Viper 4k V30
     
     
    Hi,

    I have the same problem with an Amiko Viper Combo. The front display freezes after startup showing a fixed value 100P (probably very similar with the LOAD above). The problem seem to come from the used skin... until now I have found only one skin that works well... Metrix-atv. With every other skin freezes the front panel to the value 100P. This happens even with the "default" one.

    1. Could this be a bug?
    2. There is any workaround for this? Like a skin part from the Metrix-atv that can be copied to the other ones?

  4. #14
    Senior Mitglied Avatar von s3n0
    Registriert seit
    02.01.2017
    Beiträge
    1.150
    Thanks (gegeben)
    71
    Thanks (bekommen)
    281
    Total Downloaded
    323,0 KB
    Total Downloaded
    323,0 KB
    ReceiverDankeAktivitäten
    Box 1:
    Formuler F3
     
     
    Box 2:
    Vu+ Solo SE V2
     
     
    Box 3:
    Formuer F4-TURBO
     
     
    You could also insert both of your DebugLOG here.

    A BUG has recently been detected with an inactive "timeout" when updating time over the Internet (via NTP). It is possible that this is also related to the problem of displaying time on the LED display. Repeated NTP synchronization over the Internet, unless the synchronization process fails, causes Standby mode failure throughout the Enigma. If the process fails as soon as the Enigma 2 starts, the display time is not displayed, but rather the "frozen" standby mode ("LOAD" message on the display). So if you use time synchronization via NTP (via the internet), try switching the time synchronization setting to the satellite transponder (instead of synchronizing via NTP) and reboot the box.

    I do not know if it will help. It's just my estimation of the possible cause of the problem - correct time display on the front LED display. Currently there is one small BUG that NTP synchronization has no timeout. When NTP synchronization fails, it will always be "frozen". Theoretically, it could also cause a problem :). Please try it, but it will not help :).
    Formuler F3 (BCM 7362-A0, 2x 750 MHz, mips)
    Formuler F4 TURBO (BCM 7362-5, 2x 750 MHz, mips)
    Vu+ Solo SE V2 (BCM 7429, 2x 1300 MHz, mips)

  5. #15
    Anfänger
    Registriert seit
    31.12.2017
    Beiträge
    29
    Thanks (gegeben)
    13
    Thanks (bekommen)
    2
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Box 1:
    Octagon SF4008
     
     
    Box 2:
    Octagon SF8008
     
     
    Box 3:
    Amiko Viper Combo
     
     
    Box 4:
    Amiko Viper 4k V30
     
     
    Thanks for your reply but I do not think that the NTP bug affects the front panel. This because I already have the transponder time set and the hour is updated also because I do not see how this NTP bug could only affect some of the skins. There must be something else.

  6. #16
    Senior Mitglied Avatar von s3n0
    Registriert seit
    02.01.2017
    Beiträge
    1.150
    Thanks (gegeben)
    71
    Thanks (bekommen)
    281
    Total Downloaded
    323,0 KB
    Total Downloaded
    323,0 KB
    ReceiverDankeAktivitäten
    Box 1:
    Formuler F3
     
     
    Box 2:
    Vu+ Solo SE V2
     
     
    Box 3:
    Formuer F4-TURBO
     
     
    Zitat Zitat von numerci Beitrag anzeigen
    also because I do not see how this NTP bug could only affect some of the skins.
    Kein „wirkliches“ Standby nach Update 24./25.12 - Bug o. Feature?!

    It could of course be.

    For example, a part of the SKIN or some part of the executable code for displaying data on the LED display will send a request to determine the current time. Another code to detect and synchronize time can be shut down while the time is synchronized over NTP. Of course, during synchronization, the time may be paused or bugged (with an infinite "timeout"). Due to some random error, the code for the time control does not start. This will leave only residual information on the LED display. Depending on how the programmer programmed the code, the sequence will continue to be followed and if the programmer did not count on this, the display will show the total mich match information instead of the real time.

    There is a lot of possibility why synchronization of time could cause a problem with showing the time on the display. It was just my rough estimate. I am not the developer of Enigma 2 and I do not know exactly how time synchronization works through the tool that uses OpenATV 6.1 (synchronization tools of the time exist in the Linux / Unix world of many: rdate, ntpdate, ntpd, and others - each of them works differently).
    Formuler F3 (BCM 7362-A0, 2x 750 MHz, mips)
    Formuler F4 TURBO (BCM 7362-5, 2x 750 MHz, mips)
    Vu+ Solo SE V2 (BCM 7429, 2x 1300 MHz, mips)

  7. #17
    Anfänger
    Registriert seit
    31.12.2017
    Beiträge
    29
    Thanks (gegeben)
    13
    Thanks (bekommen)
    2
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Box 1:
    Octagon SF4008
     
     
    Box 2:
    Octagon SF8008
     
     
    Box 3:
    Amiko Viper Combo
     
     
    Box 4:
    Amiko Viper 4k V30
     
     
    Still do not think is related to the new NTP issue. To check this I have installed an older image from 12.12.2017 and the same problem is there. Unless the NTP is much older than 24/25.12.2017


Seite 2 von 2 ErsteErste 12

Stichworte

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •  
Alle Zeitangaben in WEZ +1. Es ist jetzt 18:52 Uhr.
Powered by vBulletin® Version 4.2.5 (Deutsch)
Copyright ©2021 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.
Resources saved on this page: MySQL 6,25%
Parts of this site powered by vBulletin Mods & Addons from DragonByte Technologies Ltd. (Details)
vBulletin Skin By: PurevB.com