Beiträge von adrik

    Using the latest dreamos 2.5 image on my DM7080, I notice the clock time doens't get updated properly.

    It seems the kernel only allows the clock to be adjust forward, but never backwards!

    This causes the time difference to only grow larger and larger.

    This happens both with a manual update or an automatic clock update from enigma2 .

    root@dm7080:/bin$ date

    Mon Dec 23 18:04:18 CET 2019

    root@dm7080:/bin$ date -s 18:10

    Mon Dec 23 18:10:00 CET 2019

    root@dm7080:/bin$ date

    Mon Dec 23 18:10:02 CET 2019

    root@dm7080:/bin$ date -s 18:04

    Mon Dec 23 18:04:00 CET 2019

    root@dm7080:/bin$ date

    Mon Dec 23 18:10:21 CET 2019

    root@dm7080:/bin$

    Dez 23 06:00:50 dm7080 enigma2[264]: [eDVBLocalTimeHandler] Receiver time is 'Mon Dec 23 06:00:50 2019'

    Dez 23 06:00:50 dm7080 enigma2[264]: [eDVBLocalTimeHandler] Transponder time is 'Mon Dec 23 06:00:02 2019'

    Dez 23 06:00:50 dm7080 enigma2[264]: [eDVBLocalTimeHandler] diff is -48

    Dez 23 06:00:02 dm7080 enigma2[264]: [eDVBLocalTimeHandler] diff < 120 .. use Transponder Time

    Dez 23 06:00:02 dm7080 enigma2[264]: [eDVBLocalTimeHandler] update RTC

    Dez 23 06:00:02 dm7080 enigma2[264]: [eDVBLocalTimeHandler] time_difference is -48

    Dez 23 06:00:50 dm7080 enigma2[264]: [eDVBLocalTimeHandler] update Linux Time

    Dez 23 06:05:33 dm7080 enigma2[264]: [eDVBLocalTimeHandler] Receiver time is 'Mon Dec 23 06:05:33 2019'

    Dez 23 06:05:33 dm7080 enigma2[264]: [eDVBLocalTimeHandler] Transponder time is 'Mon Dec 23 06:04:45 2019'

    Dez 23 06:05:33 dm7080 enigma2[264]: [eDVBLocalTimeHandler] diff is -48

    Dez 23 06:04:45 dm7080 enigma2[264]: [eDVBLocalTimeHandler] diff < 120 .. use Transponder Time

    Dez 23 06:04:45 dm7080 enigma2[264]: [eDVBLocalTimeHandler] update RTC

    Dez 23 06:05:33 dm7080 enigma2[264]: [eDVBLocalTimeHandler] time_difference is -48

    Dez 23 06:05:33 dm7080 enigma2[264]: [eDVBLocalTimeHandler] update Linux Time


    How can I get the clock running in sync?

    You can 'fish' for a solution as long as you want! Even if you own a card for the specific services Dream does *not* support it and never will from a official point of view! Dream only supports DreamCrypt (as a 'hook-up' how to implement a softcam) and CI modules (if the box has a CI slot.


    All other options are deemed illegal since Dream holds no further licences...


    If you want you can change the image in your box that *does* support your desired functions..

    You need to fix or change the SOC drivers, which is not possible, unless you have a license or NDA agreement with BroadCom.
    So the only one who can make any changes is Dream Property.


    It has nothing to do with legal/illegal issues.
    There is an already implemented ioctl() in the drivers, which has a bug!
    It seems to me a bug for existing functionality needs to be fixed.

    I removed the plugin and installed exactly the same version again.
    Now it works as expected, so I think there must have been a problem replacing the bitratecalc.so file when updating an already installed plugin.
    Probably because the file would be 'in use', do it being loaded into memory and referenced by the plugin, when enigma2 starts.

    When using the enigma2-plugin-extensions-bitrateviewer plugin on my DM7080HD with the latest update of enigma2 4.3.1r125, I always get a green screen with a segmentation fault.
    This problem also existed with previous enigma2 versions.
    Is this a know problem or does anyone know a solution?


    @dhwz


    How can it be a configuration problem on my side?
    With enigma2 4.3.1r8 everything is working correctly.
    After upgrading to enigma 4.3.1r9 and NO changes to the configuration, the USALS rotor stops working.
    I have checked my tuner configuration and they are the same as before.
    I also see lots of comments in the new NimManager.py and Satconfig.py for enigma2 4.3.1r9

    Python
    # FIXMEE
    # no support for satpos depends, equal to and loopthough setting for nims with
    # with multiple inputs and multiple channels


    Also I see removed code like

    Python
    if nimHaveRotor:

    I didn't change anything in the configuration or setup.
    I updated from the previous version from 21-06-2017 (enigma2 4.3.1r8).
    I have set the rotor speed a long time before.
    When I look in the log, I see


    Code
    RotorCmd ffffffff, lastRotorCmd ffffffff

    so I seems enigma2 is sending invalid commands to the rotor in the last version?

    Since the last update from 17-07-2017, my USALS rotor doesn't turn anymore and I am stuck at watching only one satellite.
    Before the update, everything was working fine and I have not changed any settings or configuration.
    This is the log from enigma2, showing errors during zapping and I never see the USALS rotor turning.


    enigma2.log


    Is this a know problem and how can I fix it?


    Adri.

    I recently experienced a problem with MyTube.
    When searching, often results are found and displayed, but sometimes no results are displayed and the screen shows 'fetching search entries' forever.
    Making an enigma2 log, the cause seems to be an unhandled exception in /usr/lib/enigma2/python/Plugins/SystemPlugins/TubeLib/youtube/Videos.py.
    This is the crashlog.



    The problem might be caused by missing 'statistics' in the YouTube search results, but since the communication is secured https, I have no easy way of intercepting and examining the results.


    Has anyone noticed this problem or have a clue how we can fix it?
    Perhaps Stephan Reichholf ( Reichi)?


    Adri.

    I am using the latest OE 2.5 image on my DM7080.
    When I enable IPv6 as auto in the network setup, it works and aquires an address using DHCP6.
    But then it continues to send a DHCP6 request every 2 seconds, even though the lease time is much larger (12 hours).
    I see the following messages on my OpenWRT router:


    OE 2.5 seems to send a SOLICIT message every 2 seconds to find routers, followed by a REQUEST message to get configuration information.
    Why is this done every 2 seconds, even when the router includes a life-time in the response?


    Is this a know problem?

    Ich bekomme meinen LG auch nicht dazu das er beim Ausschalten mit ausgeht. Einschalten geht 1a. Bei den Einstellungen habe ich eigentlich alle Varianten durch.

    Das selbe passiert mit meine Pioneer TV. :frowning_face:
    Wann ich "Reagiere auf empfangene CEC Ereignisse" abschalte, functioniert es.