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?