[OpenPandora] time setting: weird behaviour and lost after reboot

Hello

It is now 6:00 am and my OpenPandora running RiscOS pretends it is 8:00 am.
So, I set the time in the Time & Date dialog box to 6:00 am as follow:

• Set manually
• Locality: UTC+00:00 Western Union
• “DST Active” not selected

Unfortunatelly, after reboot, RiscOS again pretends it is 8:00 am…

If, when I set the time to 6:00, I check the “DST Active” option, after confirming the setting by selecting the “Set” button, I see on the Icon Bar the time set to 5:00 am (????). WHen I reboot, houra!!!, the time is now 6:00… but, in the Date and Time dialog, the “DST Active” is now unselected.

Does anyone could explain this weird behaviour?

Thanks four your help.

François

when I set the time to 6:00, I check the “DST Active” option, after confirming the setting by selecting the “Set” button, I see on the Icon Bar the time set to 5:00 am

Somehow that makes sense to me, because I assume you’re not in the Western European time zone (UTC+00:00 – for the UK) but the Central European one (UTC+01:00 – for Belgium, The Netherlands, France, etc.). What happens if you set that time zone and select ‘DST Active’?

I’m not sure I understand the problem correctly. In my opinion it is a general problem of time if you do not use UTC +0:00.
For the Pandora: For me it is such that a clock (either Linux or RISC OS) always goes wrong. I get the Pandora is not configured so that both operating systems show the same time.

@Frank
If you do so, after a reboot DST is inactiv. I mean ist works only when you safe the cmos.

Hi Franck

Indeed, it is correct i should have choosen Central European (+01:00).

I did so, but, as Raik pointed, after reboot the DST Active is unchecked. But at least, my problem of time seems now solved.

Cheers

François

I would like to document what should happen, if only so that I understand it myself! There are several interacting components – whether CMOS is saved or not (and whether it is a file ‘cmos’ or saved within the ROM), how the time setting is configured, whether there is a real time clock, whether network time is visible or not, what territory setting is used, whether daylight saving time is ticked or not, and probably another that I have forgotten.

It would be nice to have a diagnostic utility that sat quietly in boot somewhere so that whenever a user had a time problem or loss of CMOS settings or whatever, you could say ’look at !Boot.somewhere.Log tell us what it says.

It could then have such things as:
‘Entry point of ROM implies BCM2835 | OMAP4 | Beagleboard | Pandora | Iyonix | …’
‘CMOS settings read from ROM | hardware | SDcard | default [only one of these] and being saved in ROM | widget | physical CMOS memory | SDcard [sometimes more than one of these]’
‘Last known shutdown (CMOS saved) at xx:xx on xx-xx-xx UTC’
‘Network time read | not found, time set manually | network | hardware’
‘Time 00:00 xx-xx-xx UTC’
‘Local time is UTC+01:00, DST is set and Summer | Winter time making local time 00:00.’

Each possibility could be interrogated using an appropriate system call (or noted during start up in a magic location). This would greatly simplify support now that we have so many hardware platforms as it would ask and answer all the obvious questions in one go.

With a bit more information, I could write such a utility…

@François

And now check your Linux time.

@Chris
I not understand all of your post :-( My problem.
The timeproblem was not in 5.18. It came later with 5.19, not with the first 5.19 ROMs.
I’m not sure why the settings (DST, Clock analog/digital) are lost after a reboot. But it is with my xM and RPi also.

@Raik

indeed, the time in linux is screwed! It is now 08:21 am in Linux instead of 10:21… On riscos it is well 10:21 am.

As I do not use linux but only RiscOS on my OpenPadora, i can live with it. But this should definitively be fixed in a future release…

ROOL, could look at this and fix it?

François

Any information are lost in my first answer. My copy & paste error :-(
I set the time on the Pandora under Linux and RISC OS manually. Not via nettime etc. I use UTC+0:00 in RISC OS and I mean London in Linux and set my local time.