BIOS time and Puppy time (ANSWERED)

[Mercedes350se]

L18L,

I have never thought that my Puppy was buggy. Just curious why, as asked previously, why the user has the option/necessity to set Puppy time when it (Puppy) could pick up BIOS time?

[nooby]

Yes it is unusual but the Dev most likely wanted to be nice?

I am twisted or torn or undecided about all this. Sure I can try to get into BIOS or use some program that is able to look and report bios time but the result is very confusing due to me not logical enough?

And I had that error of one hour for years and now finally it always show right time so why fix something that is broken if it keeps the illusion it is the right time? confusing it is to me at least, look here?

# hwclock --show --utc
Sat 03 Sep 2011 02:40:48 PM CEST -0.856308 seconds

# hwclock --show --localtime
Sat 03 Sep 2011 12:41:24 PM CEST -0.548380 seconds
#

I guess it has to do with Day time savings Summer time going on until October and such?

But it should be the other way around. My local time is two hours earlier than UTC as I get it. We have +1 hour,

When it is 1PM UTC it is then 2PM at my local time but now in Summer we are 3PM instead while that report I quoted says the opposite?

[L18L]

Mercedes350se,
sorry that I had misinterpreted your questions as a request for an easy bugfix.

Is there a reason that Puppy 3.01 does not automatically adopt BIOS time? Is it a Linux trait in general?

The reason I ask is that, when doing a e2fsck check, I have received a "Superblock write in the future" message. Easy enough to fix, just correct Puppy time.

I also had "Superblock write in the future" fixed by spending 2 hours without puppy

And now I have fixed my BIOS time, easy enough for you and me but not for nooby

nooby,
when you start your Computer there is a message
Press Del to enter setup
I think your swedish keyboard the 'Del' key has another text,
on a German keyboard it is 'Entf' (Abbreviation of 'Entfernen').
There in the BIOS you can easily correct your BIOS time.

Mercedes350se,
your questions have produced useful informations
and now it is clear for me
- choosing time zone from GMT or region does not matter
- puppy changes the sign of GMT because it thinks I am thinking wrong.

L

edited: nooby, I have written this before seeing your post

[nooby]

There in the BIOS you can easily correct your BIOS time.

yes but then I have to start anew again or can I just reset the clock maybe? Hm I am dense. I guess I only have to reset the clock once?

Okay I give it a try. That goes fast just a reboot and to into BIOS and adjust and save and then boot and adjust again?

[L18L]

There in the BIOS you can easily correct your BIOS time.

yes but then I have to start anew again or can I just reset the clock maybe? Hm I am dense. I guess I only have to reset the clock once?

Okay I give it a try. That goes fast just a reboot and to into BIOS and adjust and save and then boot and adjust again?

yes, only once
and maybe again when summer time will be over

[nooby]

Thanks your a friendly guy, much appreciated and forgive me for derailing the thread. I have learned a lot so I got carried away happy to know more about why my computer acted up.

I guess I leave this thread now.

Set it as solved like this ?
BIOS time and Puppy time [Solved]

[disciple]

Oh, look. There is a "secret" option which doesn't show up in `hwclock --help`. I wonder why they made it "secret"... and for that matter, why they didn't make it `hwclock --verbose`.

Code: Select all

~# hwclock --debug
hwclock from util-linux-2.13-pre7
Using /dev/rtc interface to clock.
Last drift adjustment done at 1301813704 seconds after 1969
Last calibration done at 1301813704 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2011/09/04 22:50:54
Hw clock time : 2011/09/04 22:50:54 = 1315133454 seconds since 1969
Sun 04 Sep 2011 22:50:54 NZST  -0.207908 seconds

[disciple]

The reason I ask is that, when doing a e2fsck check, I have received a "Superblock write in the future" message. Easy enough to fix, just correct Puppy time.

I'm a bit concerned because I don't think anything we've discussed so far actually explains this error. I think there is/was essentially a bug in Puppy whereby the filesystem is checked before the system clock is set (N.B. in my old version of Puppy it is set by /etc/rc.d/rc.country). If the BIOS clock is in local time, the error message will be generated because at this point the filesystem checker thinks that the BIOS clock is in UTC. This would be essentially the same problem as https://bugs.gentoo.org/142850?id=142850. One of the guys there was recompiling his kernel twice a year for daylight saving, which doesn't seem very sustainable

But it looks like they have found the workaround for this problem in comment 42. Since the default is for Puppy to use a BIOS clock set to local time, if the system clock can't be set sooner, that config file should be present by default. The man page for e2fsck.conf provides more explanation.
But really, we should be encouraging people to set their BIOS clock to UTC, instead of following Microsoft's stupidity.

[disciple]

If anyone getting that error message is actually running a recent Puppy, please report it as a bug.

[postfs1]

To reedit up to date.

[Béèm]

In polarpup in var/log/messages I am already 5 september.

[nooby]

... If the BIOS clock is in local time, the error message will be generated because at this point the filesystem checker thinks that the BIOS clock is in UTC.

This would be essentially the same problem as https://bugs.gentoo.org/142850?id=142850. One of the guys there was recompiling his kernel twice a year for daylight saving, which doesn't seem very sustainable

But it looks like they have found the workaround for this problem in comment 42.

Since the default is for Puppy to use a BIOS clock set to local time, ...we should be encouraging people to set their BIOS clock to UTC, instead of following Microsoft's stupidity.

I have set my Bios time to UTC now. So I don't have to recompile Gento. Hahah what a core.

So as long as one have Bios to UTC then everything will be okay?

Sounds assuring

[nooby]

Damn I fail to get this. I mean logically but okay I always fail with logic.

Local time here is 22.01 or so I did this some minute ago.
# hwclock --show --utc
Sun 04 Sep 2011 11:59:19 PM CEST -0.585188 seconds
#
UTC is also known as Universal Coordinated Time
Current Time Sunday, 4 September 2011, 20:01:31

that is the true UTC and that was what I told BIOS to set it too.

So this hwclock --show --utc seems to not give true time of the hardware
or the hardware are reset to puppy time when puppy boot up?

What is going on?
Ooops should say that after correcting BIOS then puppy was one hour wrong so I corrected that one and now it show this gross error.

[tasmod]

Beware, hwclock reads the bios time BUT reports in localtime format.


Using GMT has always caused problems in Puppy, not least because Puppy reverses the notation + to - and vice versa.
It is best to run the locale setting to your location. i.e. Europe/London

The problem also shows because the 'clock' in the tray is another app that reads the time and 'plays' with it in script.

I'm not sure about 3.1 but maybe try my app Psync from the forum Additional Software/system section to see if it will run in 3.1.
Set your locale (reboot) and run the app, select a Region nearest to you (probably UK) and the app will do the rest. your time will be synchronised to within millisecs to 'standard' time. It will correct up to a day out !!

If it works it's also worth clicking the Help button for explanation on 'time'.

[nooby]

Rob tasmod what you say now goes 180 degree counter to another member in the thread.

So whom should I trust apart from me maybe misunderstood.

can not you and him talk about it and explain to each other why you come to opposite conclutions?

disciple here
http://www.murga-linux.com/puppy/viewto ... 988#559988

To go out on internet and get sync time is to have a constant thing going on. It is not something I like at all. Can one set it to do it at boot up and maybe at shut down or something . Not all the time.

[nooby]

edit went wrong

[MinHundHettePerro]

nooby,

do you have a file /etc/clock?

What's the output of

Code: Select all

# cat /etc/clock

?
I'd wager it's "HWCLOCKTIME=localtime" and not "HWCLOCKTIME=utc".

hth /MHHP

[nooby]

# cat /etc/clock
#Set this to either 'utc' or 'localtime' based on which one your computer's
#hardware clock uses.
HWCLOCKTIME=localtime
#HWCLOCKTIME=utc

#
I do it again
# cat /etc/clock
#Set this to either 'utc' or 'localtime' based on which one your computer's
#hardware clock uses.
HWCLOCKTIME=localtime
#HWCLOCKTIME=utc

It gives both or what?
How can I change.

And what to do about Disciple saying one thing and tazmod Rob something opposite and I fail to get what both talk about

I guess it means you are right but where do I change that one then.

okay personal settings most likely. I take a look

[MinHundHettePerro]

nooby,

either you change

Code: Select all

HWCLOCKTIME=localtime
#HWCLOCKTIME=utc 

to

Code: Select all

#HWCLOCKTIME=localtime
HWCLOCKTIME=utc 

and restart, or you could see if you have the depicted utility in your menu (it's there in slacko-499.1, think I've seen it in other recent pups).

(You did set your BIOS/HW clock to correct utc-time, but your puppy was not told that your HW-clock now is set to utc instead of localtime.)

hth /MHHP

[nooby]

Thanks your an Angel but that one ask if the hardware should follow the software or software the hardware.

I had no idea? Que? So I accepted the first and that set the clock to 01.30 instead of 11.30 PM # cat /etc/clock

#Set this to either 'utc' or 'localtime' based on which one your computer's
#hardware clock uses.
HWCLOCKTIME='utc'
#HWCLOCKTIME=utc

And I have clicked on time and changed back to Sunday and 23.32 something

But we still have that conflict between Disciple telling me that UTC is the way to do it
and Rob tazmod that tells me that local time is the way to go.

I have no idea whom to trust?

I have to go to bed soon. Thanks for caring about me