Mailing List Archive

Something on your system is what's going on? Mine works perfectly. Are you dual booting Windows? If so set the /etc/rc.conf clock to local and make sure the bios is local.

Also check this list for an extensive thread - actually several on this subject.

>
> From: "Yogi-CH" <yogich@sc2000.net>
> Date: 2004/09/14 Tue PM 03:46:32 GMT
> To: <gentoo-user@lists.gentoo.org>
> Subject: [gentoo-user] clock won't stay put
>
> If there is one thing that isn't making any points with me, it is Gentoo's seeming inability to know what time it is. Every time I boot I have to set the clock ...and my 'other distro' on the same box shows the correct time. If I correct the time in Gentoo, the 'other distro' shows the wrong time by the same amount of the correction. The hdwe clock is set to UTC, and Gentoo is the only distro which doesn't care whether I link CST6CDT or UTC to /etc/localtime ...the clock is wrong.
>
> What the devil is going on, here!?
>
> ..."Yogi" CH
> Namaste Yoga Studio
>
>


--
gentoo-user@gentoo.org mailing list

----- Original Message -----
From: <brettholcomb@charter.net>
To: <gentoo-user@lists.gentoo.org>
Sent: Tuesday, September 14, 2004 10:57 AM
Subject: Re: [gentoo-user] clock won't stay put


> Something on your system is what's going on? Mine works perfectly. Are
you dual booting Windows? If so set the /etc/rc.conf clock to local and
make sure the bios is local.
>
> Also check this list for an extensive thread - actually several on this
subject.
>
Actually, I am dual-booting Linux. SuSE/Gentoo. The only prob SuSE has
w/the clock is when it is corrected in Gentoo. The box just came back from
repair, so I hesitate to think it didn't get repaired.

..."Yogi" CH
Namaste Yoga Studio


--
gentoo-user@gentoo.org mailing list

On Tue, 14 Sep 2004 11:04:12 -0500, Yogi-CH <yogich@sc2000.net> wrote:
> ----- Original Message -----
> From: <brettholcomb@charter.net>
> To: <gentoo-user@lists.gentoo.org>
> Sent: Tuesday, September 14, 2004 10:57 AM
> Subject: Re: [gentoo-user] clock won't stay put
>
> > Something on your system is what's going on? Mine works perfectly. Are
> you dual booting Windows? If so set the /etc/rc.conf clock to local and
> make sure the bios is local.
> >
> > Also check this list for an extensive thread - actually several on this
> subject.
> >
> Actually, I am dual-booting Linux. SuSE/Gentoo. The only prob SuSE has
> w/the clock is when it is corrected in Gentoo. The box just came back from
> repair, so I hesitate to think it didn't get repaired.
>

Like the main said, check the archives. Almost nobody (a very few)
have reported any problems with maintaining the clock on gentoo.

--
/\/\
(CR) Collins Richey
\/\/ "I hear you're single again." "Spouse 2.0 had fewer bugs than
Spouse 1.0, but the maintenance ... was too much for my OS."
- Glitch (tm)

--
gentoo-user@gentoo.org mailing list

<SNIP>
> Like the main said, check the archives. Almost nobody (a very few)
> have reported any problems with maintaining the clock on gentoo.
<SNIP>

<hehe!> But those of us who have reported problems continue to have them. ;-)

To Yogi-CH - I have this problem on one of my 4 Gentoo boxes. The
other 3 work perfectly. The one that has the problem is the newest and
has a new chipset. I think maybe it's a chipset problem where the
kernel hasn't caught up yet.

To get around the problem I was given the hint to try running
ntp-client at default level in rc-update. This has effectively solved
the problem for me, but only works if your machine has a network
connection at boot time.

disappointing that there isn't a better answer...

Cheers,
Mark

--
gentoo-user@gentoo.org mailing list

On Tuesday 14 September 2004 15:43, Mark Knecht wrote:
> <SNIP>
>
> > Like the main said, check the archives. Almost nobody (a very few)
> > have reported any problems with maintaining the clock on gentoo.
>
> <SNIP>
>
> <hehe!> But those of us who have reported problems continue to have them.
> ;-)
>
> To Yogi-CH - I have this problem on one of my 4 Gentoo boxes. The
> other 3 work perfectly. The one that has the problem is the newest and
> has a new chipset. I think maybe it's a chipset problem where the
> kernel hasn't caught up yet.
>
> To get around the problem I was given the hint to try running
> ntp-client at default level in rc-update. This has effectively solved
> the problem for me, but only works if your machine has a network
> connection at boot time.
>
> disappointing that there isn't a better answer...
>
> Cheers,
> Mark
>
> --
> gentoo-user@gentoo.org mailing list
Yep... disappointing is a word & a half. I was hoping to find a solution
other than ntp or ntpdate but if that is the way it is, I'll have to live
with it, I guess. Funny thing, though, since I'm also running a new SuSE
distro on the same box & it has no prob.
--
..."Yogi" CH
Namasté Yoga Studio
"If music be the food of love, why can't rabbits sing?"


--
gentoo-user@gentoo.org mailing list

I'm new to this list, so forgive me if someone has suggested this
before. I had a problem similar to this when I installed gentoo on my
laptop a few months back, it turns out that CLOCK="UTC" was set in my
/etc/rc.conf. Have you checked this?


On Tue, 14 Sep 2004 17:23:52 -0500, C Hamel <yogich@sc2000.net> wrote:
>
>
> On Tuesday 14 September 2004 15:43, Mark Knecht wrote:
> > <SNIP>
> >
> > > Like the main said, check the archives. Almost nobody (a very few)
> > > have reported any problems with maintaining the clock on gentoo.
> >
> > <SNIP>
> >
> > <hehe!> But those of us who have reported problems continue to have them.
> > ;-)
> >
> > To Yogi-CH - I have this problem on one of my 4 Gentoo boxes. The
> > other 3 work perfectly. The one that has the problem is the newest and
> > has a new chipset. I think maybe it's a chipset problem where the
> > kernel hasn't caught up yet.
> >
> > To get around the problem I was given the hint to try running
> > ntp-client at default level in rc-update. This has effectively solved
> > the problem for me, but only works if your machine has a network
> > connection at boot time.
> >
> > disappointing that there isn't a better answer...
> >
> > Cheers,
> > Mark
> >
> > --
> > gentoo-user@gentoo.org mailing list
> Yep... disappointing is a word & a half. I was hoping to find a solution
> other than ntp or ntpdate but if that is the way it is, I'll have to live
> with it, I guess. Funny thing, though, since I'm also running a new SuSE
> distro on the same box & it has no prob.
> --
> ..."Yogi" CH
> Namasté Yoga Studio
> "If music be the food of love, why can't rabbits sing?"
>
>
>
>
> --
> gentoo-user@gentoo.org mailing list
>
>

--
gentoo-user@gentoo.org mailing list

On Tue, 14 Sep 2004 17:23:52 -0500
C Hamel <yogich@sc2000.net> wrote:

> Yep... disappointing is a word & a half. I was hoping to find a solution
> other than ntp or ntpdate but if that is the way it is, I'll have to live
> with it, I guess. Funny thing, though, since I'm also running a new SuSE
> distro on the same box & it has no prob.
> --
> .."Yogi" CH

can you give us the following:

grep CLOCK /etc/rc.conf
ls -l /etc/localtime
ls -l (whatever /etc/localtime points to)
rc-status boot|grep clock

also, what does suse think the hardware clock is set to? UTC or your
locality?



--
Nick Rout <nick@rout.co.nz>


--
gentoo-user@gentoo.org mailing list

Hi Nick,
From my dual-boot machine. This machien must remain dual-bootable,
but I run Gentoo 90% of the time so it should be set up to be nice to
Linux. Also, please see the comment at the end. And now, on to the
show:

>
> grep CLOCK /etc/rc.conf

root@flash ~ # grep CLOCK /etc/rc.conf
# Set CLOCK to "UTC" if your system clock is set to UTC (also known as
# Greenwich Mean Time). If your clock is set to the local time, then set CLOCK
CLOCK="local"
root@flash ~ #

> ls -l /etc/localtime

root@flash ~ # ls -l /etc/localtime
lrwxrwxrwx 1 root root 39 Mar 30 09:49 /etc/localtime ->
/usr/share/zoneinfo/America/Los_Angeles
root@flash ~ #

> ls -l (whatever /etc/localtime points to)

root@flash ~ # ls -al /usr/share/zoneinfo/America/Los_Angeles
-rw-r--r-- 4 root root 1017 Aug 14 13:11
/usr/share/zoneinfo/America/Los_Angeles
root@flash ~ #

> rc-status boot|grep clock

root@flash ~ # rc-status boot | grep clock
clock [ started ]

In my case this set of data does not capture the data I found. In my case:

a) Set the time in Linux to some distant future date
b) Write system time to the hardware clock
c) reboot into BIOS and look at the time. A distant future date is
correctly shown...

However, if I:

a) Boot the system into BIOS
b) Set the BIOS clock to some distant date in the past or future
c) Boot into Linux

then the clock incorrectly shows the last date that was used in Linux
and was saved at shutdown

So, in my case the system seems to clearly NOT read the BIOS clock on
startup but rather reads some file that was saved when the system last
shutdown.

At no time in this process did I boot to Windows.

Thanks for looking at this with us,
Mark

--
gentoo-user@gentoo.org mailing list

On Tue, 14 Sep 2004, Mark Knecht wrote:

> # Set CLOCK to "UTC" if your system clock is set to UTC (also known as
> # Greenwich Mean Time). If your clock is set to the local time, then set CLOCK
> CLOCK="local"

Change to CLOCK="UTF"
reboot
set the correct time
reboot to SuSe
reboot to Gentoo to check if the time is correct

To me it looks like SuSe is using UTC and Gentoo local time, hence the
differences.

HTH

--
T.G.

--
gentoo-user@gentoo.org mailing list

On Wed, 15 Sep 2004 05:05:02 +0300 (EEST), Tero Grundström
<tero@vuosaari.hai.fi> wrote:
> On Tue, 14 Sep 2004, Mark Knecht wrote:
>
> > # Set CLOCK to "UTC" if your system clock is set to UTC (also known as
> > # Greenwich Mean Time). If your clock is set to the local time, then set CLOCK
> > CLOCK="local"
>
> Change to CLOCK="UTF"
> reboot
> set the correct time
> reboot to SuSe
> reboot to Gentoo to check if the time is correct
>
> To me it looks like SuSe is using UTC and Gentoo local time, hence the
> differences.
>
> HTH

Hi,
I'm not the Suse user, I'm the Windows user.

None of that stuff effects me. I've done all the options. My
problem is that the boot process doesn't even read my BIOS clock. It's
reading some unknown file that saved the previous shutdown time.

Bummer...

Thanks for helping though!

Cheers,
Mark

--
gentoo-user@gentoo.org mailing list

On Wed, 15 Sep 2004 05:05:02 +0300 (EEST)
Tero Grundström <tero@vuosaari.hai.fi> wrote:

> On Tue, 14 Sep 2004, Mark Knecht wrote:
>
> > # Set CLOCK to "UTC" if your system clock is set to UTC (also known as
> > # Greenwich Mean Time). If your clock is set to the local time, then set CLOCK
> > CLOCK="local"
>
> Change to CLOCK="UTF"
> reboot
> set the correct time
> reboot to SuSe
> reboot to Gentoo to check if the time is correct
>
> To me it looks like SuSe is using UTC and Gentoo local time, hence the
> differences.

for the record it doesn't matter a toss to linux wheher you set your
bios clock to local or to UTC, as long as you follow these rules:

1. all operating systems must be set to the same, ie all to local or all
to UTC
2. windows can only be set to local
3. as a corollary to that if you boot the machine to windows, all other
OSes must be set to local
4. for the avoidance of doubt, and as a further corollary to 1 & 2, if
you don't boot to windows you can set your OSes to local or UTC as long
as they are all the same.
5. having said that I don't know about OS/2 and there may be obscure
OSes other than windows that are inflexible in the way described in 2.

see further here:
http://marc.theaimsgroup.com/?l=gentoo-user&m=109450639313994&w=2

I agree that Mark Knecht's symptoms are a little bizarre, Mark, are you
sure that when you did this:

> However, if I:
>
> a) Boot the system into BIOS
> b) Set the BIOS clock to some distant date in the past or future
> c) Boot into Linux
>
> then the clock incorrectly shows the last date that was used in Linux
> and was saved at shutdown

that you in fact saved the bios settings?


--
Nick Rout <nick@rout.co.nz>


--
gentoo-user@gentoo.org mailing list

On Wed, 15 Sep 2004, Nick Rout wrote:

> for the record it doesn't matter a toss to linux wheher you set your
> bios clock to local or to UTC, as long as you follow these rules:
>
> 1. all operating systems must be set to the same, ie all to local or all
> to UTC

Yes. My post was all about making sure Gentoo and SuSe to use same
settings i.e. UTC in this case. But of course he could just as well set
both to use local time.

I'm not sure if this is the issue though...

--
T.G.

--
gentoo-user@gentoo.org mailing list

> I agree that Mark Knecht's symptoms are a little bizarre, Mark, are you
> sure that when you did this:
>
> > However, if I:
> >
> > a) Boot the system into BIOS
> > b) Set the BIOS clock to some distant date in the past or future
> > c) Boot into Linux
> >
> > then the clock incorrectly shows the last date that was used in Linux
> > and was saved at shutdown
>
> that you in fact saved the bios settings?
>

Absolutely. I even booted into Windows at one time to see if Windows
saw the distant future date. It did. I came back to Linux and got the
old shutdown date.

I'm convincend, until I learn more, that upon shutdown my system is
writing a file somewhere with the last time the machine operated. If
you image a system with no hardware clock it would make sense this
way.

And, as I've said in other threads on this subject, I have 4 Gentoo
boxes (well, now that I think of it, 5 Gentoo boxes) all set up the
same way. (or so I think...) This laptop is the only one that has this
problem. It's also the only one that required a >2.6.3 kernel to get
DMA support for the hard drive. I just suspect that it's some
oversight in the way this machine's chipset works, but that's a total
guess.

--
gentoo-user@gentoo.org mailing list

On Tuesday 14 September 2004 17:30, Abraham Al-Saleh wrote:
> I'm new to this list, so forgive me if someone has suggested this
> before. I had a problem similar to this when I installed gentoo on my
> laptop a few months back, it turns out that CLOCK="UTC" was set in my
> /etc/rc.conf. Have you checked this?
>
Yes. It is supposed to be UTC. Thanks. :-)
--
..."Yogi" CH
Namasté Yoga Studio
"If music be the food of love, why can't rabbits sing?"


--
gentoo-user@gentoo.org mailing list

On Tuesday 14 September 2004 19:42, Mark Knecht wrote:
<SNIP>
> In my case this set of data does not capture the data I found. In my case:
>
> a) Set the time in Linux to some distant future date
> b) Write system time to the hardware clock
> c) reboot into BIOS and look at the time. A distant future date is
> correctly shown...
>
> However, if I:
>
> a) Boot the system into BIOS
> b) Set the BIOS clock to some distant date in the past or future
> c) Boot into Linux
>
> then the clock incorrectly shows the last date that was used in Linux
> and was saved at shutdown
>
> So, in my case the system seems to clearly NOT read the BIOS clock on
> startup but rather reads some file that was saved when the system last
> shutdown.
>
> At no time in this process did I boot to Windows.
>
> Thanks for looking at this with us,
> Mark
>
> --
> gentoo-user@gentoo.org mailing list
That is the first place I looked, actually --in BIOS. I'm afraid I cannot
humor you & look at the time in BIOS. Weird. This BIOS setup is so
bare-bones as to be completely laughable. After the Toshiba I had, I am
sadly disappointed in the inability to set things.

I will check what I can, and get back to you as soon as possible. Since I am
working in SuSE (the working system) right now, I am unable to check.

--
..."Yogi" CH
Namasté Yoga Studio
"If music be the food of love, why can't rabbits sing?"


--
gentoo-user@gentoo.org mailing list

On Tuesday 14 September 2004 21:40, Tero Grundström wrote:
> On Wed, 15 Sep 2004, Nick Rout wrote:
> > for the record it doesn't matter a toss to linux wheher you set your
> > bios clock to local or to UTC, as long as you follow these rules:
> >
> > 1. all operating systems must be set to the same, ie all to local or all
> > to UTC
>
> Yes. My post was all about making sure Gentoo and SuSe to use same
> settings i.e. UTC in this case. But of course he could just as well set
> both to use local time.
>
> I'm not sure if this is the issue though...
>
> --
> T.G.
>
> --
> gentoo-user@gentoo.org mailing list
Nor am I, just now. I have been given some ideas, here, and will be able to
check them out tomorrow & let you all know what happens. Tonight, I logged
into Gentoo to play, a bit, and noted the clock said 05:32. I booted into
SuSE sometime later, and the clock read 23:00. FWIW, I know that both /etc/
localtime symlinks point to the same item in /usr/share/zoneinfo.
--
..."Yogi" CH
Namasté Yoga Studio
"If music be the food of love, why can't rabbits sing?"


--
gentoo-user@gentoo.org mailing list

On Tue, 14 Sep 2004 23:32:15 -0500
C Hamel <yogich@sc2000.net> wrote:

> On Tuesday 14 September 2004 21:40, Tero Grundström wrote:
> > On Wed, 15 Sep 2004, Nick Rout wrote:
> > > for the record it doesn't matter a toss to linux wheher you set your
> > > bios clock to local or to UTC, as long as you follow these rules:
> > >
> > > 1. all operating systems must be set to the same, ie all to local or all
> > > to UTC
> >
> > Yes. My post was all about making sure Gentoo and SuSe to use same
> > settings i.e. UTC in this case. But of course he could just as well set
> > both to use local time.
> >
> > I'm not sure if this is the issue though...
> >
> > --
> > T.G.
> >
> > --
> > gentoo-user@gentoo.org mailing list
> Nor am I, just now. I have been given some ideas, here, and will be able to
> check them out tomorrow & let you all know what happens. Tonight, I logged
> into Gentoo to play, a bit, and noted the clock said 05:32. I booted into
> SuSE sometime later, and the clock read 23:00. FWIW, I know that both /etc/
> localtime symlinks point to the same item in /usr/share/zoneinfo.

one thing you still haven't answered: does suse save the hardware clock
in utc or local?

> --
> ..."Yogi" CH
> Namasté Yoga Studio
> "If music be the food of love, why can't rabbits sing?"
>
>
> --
> gentoo-user@gentoo.org mailing list

--
Nick Rout <nick@rout.co.nz>


--
gentoo-user@gentoo.org mailing list

Webmin as a nice, easy to use interface fro ntp. Just one click and you can
set your hardware and system clock perfectly in sync and accurate. A couple
more clicks and its configured to correct itself every week/day etc etc

Kevin.


On Tuesday 14 September 2004 23:23, C Hamel wrote:
On Tuesday 14 September 2004 15:43, Mark Knecht wrote:
> <SNIP>
>
> > Like the main said, check the archives. Almost nobody (a very few)
> > have reported any problems with maintaining the clock on gentoo.
>
> <SNIP>
>
> <hehe!> But those of us who have reported problems continue to have them.
> ;-)
>
> To Yogi-CH - I have this problem on one of my 4 Gentoo boxes. The
> other 3 work perfectly. The one that has the problem is the newest and
> has a new chipset. I think maybe it's a chipset problem where the
> kernel hasn't caught up yet.
>
> To get around the problem I was given the hint to try running
> ntp-client at default level in rc-update. This has effectively solved
> the problem for me, but only works if your machine has a network
> connection at boot time.
>
> disappointing that there isn't a better answer...
>
> Cheers,
> Mark
>
> --
> gentoo-user@gentoo.org mailing list

Yep... disappointing is a word & a half. I was hoping to find a solution
other than ntp or ntpdate but if that is the way it is, I'll have to live
with it, I guess. Funny thing, though, since I'm also running a new SuSE
distro on the same box & it has no prob.


--
gentoo-user@gentoo.org mailing list

On Tuesday 14 September 2004 23:46, Nick Rout wrote:
> On Tue, 14 Sep 2004 23:32:15 -0500
>
> C Hamel <yogich@sc2000.net> wrote:
> > On Tuesday 14 September 2004 21:40, Tero Grundström wrote:
> > > On Wed, 15 Sep 2004, Nick Rout wrote:
> > > > for the record it doesn't matter a toss to linux wheher you set your
> > > > bios clock to local or to UTC, as long as you follow these rules:
> > > >
> > > > 1. all operating systems must be set to the same, ie all to local or
> > > > all to UTC
> > >
> > > Yes. My post was all about making sure Gentoo and SuSe to use same
> > > settings i.e. UTC in this case. But of course he could just as well set
> > > both to use local time.
> > >
> > > I'm not sure if this is the issue though...
> > >
> > > --
> > > T.G.
> > >
> > > --
> > > gentoo-user@gentoo.org mailing list
> >
> > Nor am I, just now. I have been given some ideas, here, and will be able
> > to check them out tomorrow & let you all know what happens. Tonight, I
> > logged into Gentoo to play, a bit, and noted the clock said 05:32. I
> > booted into SuSE sometime later, and the clock read 23:00. FWIW, I know
> > that both /etc/ localtime symlinks point to the same item in
> > /usr/share/zoneinfo.
>
> one thing you still haven't answered: does suse save the hardware clock
> in utc or local?
>
> > --
> > ..."Yogi" CH
> > Namasté Yoga Studio
> > "If music be the food of love, why can't rabbits sing?"
> >
> >
> > --
> > gentoo-user@gentoo.org mailing list
Set to UTC. ..And I did answer that but you just couldn't find it! ;-)
Happens to me quite a lot.
--
..."Yogi" CH
Namasté Yoga Studio
"If music be the food of love, why can't rabbits sing?"


--
gentoo-user@gentoo.org mailing list

On Tuesday 14 September 2004 21:05, Tero Grundström wrote:
> On Tue, 14 Sep 2004, Mark Knecht wrote:
> > # Set CLOCK to "UTC" if your system clock is set to UTC (also known as
> > # Greenwich Mean Time). If your clock is set to the local time, then set
> > CLOCK CLOCK="local"
>
> Change to CLOCK="UTF"
> reboot
> set the correct time
> reboot to SuSe
> reboot to Gentoo to check if the time is correct
>
> To me it looks like SuSe is using UTC and Gentoo local time, hence the
> differences.
>
> HTH
>
> --
> T.G.
>
> --
> gentoo-user@gentoo.org mailing list
Seems that having grep'd the various suggested items the answer was that the
clock is, indeed, set to UTC (via SuSE, I suppose, since after dumping XP I
specifically set that up from SuSE) so I tried using UTF for /etc/localtime
and, upon booting Gentoo/SuSE/Gentoo/SuSE I find the clock is staying put,
finally ..for now.

One curious item, though: when I chrooted into Gentoo from SuSE the Gentoo
clock jumped ahead by five hours. Since I can't get an internet connection
from CLI I often use SuSE's, then emerge software so I don't have to fire up
the network specifically to connect. ...But that's another [unanswered] post,
alas.
--
..."Yogi" CH
Namasté Yoga Studio
"If music be the food of love, why can't rabbits sing?"


--
gentoo-user@gentoo.org mailing list