[gentoo-user] System won't boot if CMOS clock is slow

[gentoo-user] System won't boot if CMOS clock is slow

[Grant Edwards]

I'm having problems with one of my Gentoo systems who's motherboard
clock is a little slow.  When the system comes up, the system time is
set from the motherboard clock.  If that's slow, something in the init
system seems to panic because some file or other has a timestamp in
the future.

Just to make it extra convenient, it clears the console screen when
that happens so there's no actual record of what went wrong or which
component in th init process is failing.

Going into the BIOS setup and setting the time ahead a minute or two
will allow the system to start up normally.

Is there any way to disable this "feature"?

-- 
Grant Edwards               grant.b.edwards        Yow! ... I don't like FRANK
                                  at               SINATRA or his CHILDREN.
                              gmail.com            

Re: [gentoo-user] System won't boot if CMOS clock is slow

[Bruce Hill]

On Wed, Jan 16, 2013 at 04:43:16PM +0000, Grant Edwards wrote:
> I'm having problems with one of my Gentoo systems who's motherboard
> clock is a little slow.  When the system comes up, the system time is
> set from the motherboard clock.  If that's slow, something in the init
> system seems to panic because some file or other has a timestamp in
> the future.
> 
> Just to make it extra convenient, it clears the console screen when
> that happens so there's no actual record of what went wrong or which
> component in th init process is failing.
> 
> Going into the BIOS setup and setting the time ahead a minute or two
> will allow the system to start up normally.
> 
> Is there any way to disable this "feature"?

Replace your CMOS battery.

Default behavior of agetty is to clear now. In /etc/inittab make sure you have
--noclear in tty1 like this:

# TERMINALS
c1:12345:respawn:/sbin/agetty --noclear 38400 tty1 linux

Bruce
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

Re: [gentoo-user] System won't boot if CMOS clock is slow

[Michael Mol]

On Wed, Jan 16, 2013 at 12:52 PM, Bruce Hill
<daddy@happypenguincomputers.com> wrote:
> On Wed, Jan 16, 2013 at 04:43:16PM +0000, Grant Edwards wrote:
>> I'm having problems with one of my Gentoo systems who's motherboard
>> clock is a little slow.  When the system comes up, the system time is
>> set from the motherboard clock.  If that's slow, something in the init
>> system seems to panic because some file or other has a timestamp in
>> the future.
>>
>> Just to make it extra convenient, it clears the console screen when
>> that happens so there's no actual record of what went wrong or which
>> component in th init process is failing.
>>
>> Going into the BIOS setup and setting the time ahead a minute or two
>> will allow the system to start up normally.
>>
>> Is there any way to disable this "feature"?
>
> Replace your CMOS battery.

His system clock runs slow, it's not a matter of the CMOS battery
being dead. If it were dead, the clock would be years off.

>
> Default behavior of agetty is to clear now. In /etc/inittab make sure you have
> --noclear in tty1 like this:
>
> # TERMINALS
> c1:12345:respawn:/sbin/agetty --noclear 38400 tty1 linux


-- 
:wq

Re: [gentoo-user] System won't boot if CMOS clock is slow

[Bruce Hill]

On Wed, Jan 16, 2013 at 12:55:56PM -0500, Michael Mol wrote:
> 
> His system clock runs slow, it's not a matter of the CMOS battery
> being dead. If it were dead, the clock would be years off.

Experience has shown that when the voltage gets low, this happens. Here's an
article ... first hit:

http://www.ehow.com/how_5011717_check-cmos-battery.html
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

Re: [gentoo-user] System won't boot if CMOS clock is slow

[Michael Mol]

On Wed, Jan 16, 2013 at 1:04 PM, Bruce Hill
<daddy@happypenguincomputers.com> wrote:
> On Wed, Jan 16, 2013 at 12:55:56PM -0500, Michael Mol wrote:
>>
>> His system clock runs slow, it's not a matter of the CMOS battery
>> being dead. If it were dead, the clock would be years off.
>
> Experience has shown that when the voltage gets low, this happens. Here's an
> article ... first hit:
>
> http://www.ehow.com/how_5011717_check-cmos-battery.html

Interesting! The things you learn...

-- 
:wq

[gentoo-user] Re: System won't boot if CMOS clock is slow

[Grant Edwards]

On 2013-01-16, Bruce Hill <daddy@happypenguincomputers.com> wrote:
> On Wed, Jan 16, 2013 at 04:43:16PM +0000, Grant Edwards wrote:
>> I'm having problems with one of my Gentoo systems who's motherboard
>> clock is a little slow.  When the system comes up, the system time is
>> set from the motherboard clock.  If that's slow, something in the init
>> system seems to panic because some file or other has a timestamp in
>> the future.
>> 
>> Just to make it extra convenient, it clears the console screen when
>> that happens so there's no actual record of what went wrong or which
>> component in th init process is failing.
>> 
>> Going into the BIOS setup and setting the time ahead a minute or two
>> will allow the system to start up normally.
>> 
>> Is there any way to disable this "feature"?
>
> Replace your CMOS battery.

I'll try that.

I enabled init logging and did more testing, and I now don't think
it's actually the motherboard clock that's causing the problem. It
seems that a second reboot without changing the clock usually fixes
the problem also.

I have had systems in the past who refused to boot because the
motherboard time was off, and at first it looked like that was the
problem again.

> Default behavior of agetty is to clear now. In /etc/inittab make sure you have
> --noclear in tty1 like this:

Yup, figured that one out once I realized that in the normal case it's
agetty rather than the init system itself that clears the screen.

But, in the failures I've been seeing today, it's not getting to
agetty. The "clear screen and halt" happens at the "waiting for udev
events" step...

-- 
Grant Edwards               grant.b.edwards        Yow! You should all JUMP
                                  at               UP AND DOWN for TWO HOURS
                              gmail.com            while I decide on a NEW
                                                   CAREER!!

Re: [gentoo-user] Re: System won't boot if CMOS clock is slow

[Paul Hartman]

On Wed, Jan 16, 2013 at 1:36 PM, Grant Edwards
<grant.b.edwards@gmail.com> wrote:
>
> But, in the failures I've been seeing today, it's not getting to
> agetty. The "clear screen and halt" happens at the "waiting for udev
> events" step...

FWIW I have also noticed on my machine that somewhere in the middle of
the OpenRC boot process, the screen gets cleared. Haven't completely
tracked it down yet.

You can enable logging in your rc.conf to log all of the openrc
output, that might help you see what was on-screen before it got
cleared away. You also might be able to enable interactive mode and go
through it step-by-step to see what's happening in real-time at your
own pace.

Re: [gentoo-user] Re: System won't boot if CMOS clock is slow

[Alan McKinnon]

On Wed, 16 Jan 2013 14:29:04 -0600
Paul Hartman <paul.hartman+gentoo@gmail.com> wrote:

> On Wed, Jan 16, 2013 at 1:36 PM, Grant Edwards
> <grant.b.edwards@gmail.com> wrote:
> >
> > But, in the failures I've been seeing today, it's not getting to
> > agetty. The "clear screen and halt" happens at the "waiting for udev
> > events" step...
> 
> FWIW I have also noticed on my machine that somewhere in the middle of
> the OpenRC boot process, the screen gets cleared. Haven't completely
> tracked it down yet.

In /etc/inittab you need to change stuff like this

c1:12345:respawn:/sbin/agetty 38400 tty1 linux

to this

c1:12345:respawn:/sbin/agetty 38400 tty1 linux --noclear


There's a clear elog about this at the end of the util-linux emerge,
perhaps you missed it



> 
> You can enable logging in your rc.conf to log all of the openrc
> output, that might help you see what was on-screen before it got
> cleared away. You also might be able to enable interactive mode and go
> through it step-by-step to see what's happening in real-time at your
> own pace.
> 



-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: System won't boot if CMOS clock is slow

[Paul Hartman]

On Wed, Jan 16, 2013 at 2:52 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Wed, 16 Jan 2013 14:29:04 -0600
> Paul Hartman <paul.hartman+gentoo@gmail.com> wrote:
>
>> On Wed, Jan 16, 2013 at 1:36 PM, Grant Edwards
>> <grant.b.edwards@gmail.com> wrote:
>> >
>> > But, in the failures I've been seeing today, it's not getting to
>> > agetty. The "clear screen and halt" happens at the "waiting for udev
>> > events" step...
>>
>> FWIW I have also noticed on my machine that somewhere in the middle of
>> the OpenRC boot process, the screen gets cleared. Haven't completely
>> tracked it down yet.
>
> In /etc/inittab you need to change stuff like this
>
> c1:12345:respawn:/sbin/agetty 38400 tty1 linux
>
> to this
>
> c1:12345:respawn:/sbin/agetty 38400 tty1 linux --noclear
>
>
> There's a clear elog about this at the end of the util-linux emerge,
> perhaps you missed it

I already had that set. :) I'm not talking about clearing the screen
at the login prompt; it clears mid-OpenRC during/after the udev step
(as Grant also described), though in my case it does not halt but
continues printing the rest of the OpenRC messages and eventually gets
to the login prompt. I'm thinking it may be fbcondecor responsible for
the blanking there. I'll need to experiment more with it.

Re: [gentoo-user] Re: System won't boot if CMOS clock is slow

[Bruce Hill]

On Thu, Jan 17, 2013 at 02:35:50PM -0600, Paul Hartman wrote:
> 
> I already had that set. :) I'm not talking about clearing the screen
> at the login prompt; it clears mid-OpenRC during/after the udev step
> (as Grant also described), though in my case it does not halt but
> continues printing the rest of the OpenRC messages and eventually gets
> to the login prompt. I'm thinking it may be fbcondecor responsible for
> the blanking there. I'll need to experiment more with it.

When KMS kicks in?
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

Re: [gentoo-user] Re: System won't boot if CMOS clock is slow

[Alan McKinnon]

On Thu, 17 Jan 2013 14:45:13 -0600
Bruce Hill <daddy@happypenguincomputers.com> wrote:

> On Thu, Jan 17, 2013 at 02:35:50PM -0600, Paul Hartman wrote:
> > 
> > I already had that set. :) I'm not talking about clearing the screen
> > at the login prompt; it clears mid-OpenRC during/after the udev step
> > (as Grant also described), though in my case it does not halt but
> > continues printing the rest of the OpenRC messages and eventually
> > gets to the login prompt. I'm thinking it may be fbcondecor
> > responsible for the blanking there. I'll need to experiment more
> > with it.
> 
> When KMS kicks in?

I've never seen KMS clear the screen there for either nvidia or radeon
cards so I doubt it's that. All it does at that point that is visible
to the user is set the resolution and paint on the $GO_FAST stripes.

Now fbcondecor, that's a likely area to look in. I personally no
longer use fancy fb and boot splash type things (I like my Alt-F1
console to look like a console and not get in my way) so I doubt I can
be of much help further on this. 

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: System won't boot if CMOS clock is slow

[Kevin Chadwick]

> I have had systems in the past who refused to boot because the
> motherboard time was off, and at first it looked like that was the
> problem again.

OpenBSD takes the time from the filesystem in that case and boots. I
wish linux did. I had a mate who used to ring me up everytime his mother
in law unplugged the laptop and it was a laptop that's cmos was a pain
to replace. I believe he ended up in 2034 or something after a few
months because I told him the bios key and meant he could avoid
fsck that sometimes gave him various problems =-)

He was anti slow machines (Vista) and liked linux after being
skeptical. I can't see him trying linux again now :-(

-- 
_______________________________________________________________________

'Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
universal interface'

(Doug McIlroy)
_______________________________________________________________________

Re: [gentoo-user] Re: System won't boot if CMOS clock is slow

[Volker Armin Hemmann]

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

So it is Linux' fault, that your mate used crap Hardware? That is great!
let us blame it for the weather too. And stubbed toes.
Am 16.01.2013 21:43 schrieb "Kevin Chadwick" <ma1l1ists@yahoo.co.uk>:

> > I have had systems in the past who refused to boot because the
> > motherboard time was off, and at first it looked like that was the
> > problem again.
>
> OpenBSD takes the time from the filesystem in that case and boots. I
> wish linux did. I had a mate who used to ring me up everytime his mother
> in law unplugged the laptop and it was a laptop that's cmos was a pain
> to replace. I believe he ended up in 2034 or something after a few
> months because I told him the bios key and meant he could avoid
> fsck that sometimes gave him various problems =-)
>
> He was anti slow machines (Vista) and liked linux after being
> skeptical. I can't see him trying linux again now :-(
>
> --
> _______________________________________________________________________
>
> 'Write programs that do one thing and do it well. Write programs to work
> together. Write programs to handle text streams, because that is a
> universal interface'
>
> (Doug McIlroy)
> _______________________________________________________________________
>
>

[-- Attachment #2: Type: text/html, Size: 1576 bytes --]

Re: [gentoo-user] Re: System won't boot if CMOS clock is slow

[Kevin Chadwick]

> So it is Linux' fault, that your mate used crap Hardware? That is great!
> let us blame it for the weather too. And stubbed toes.

Well the point was that if OpenBSD had an auto update function I could
have installed that and he would still be using OpenBSD happily. If
Linux did what OpenBSD does then he would be a happy linux user, well
aside from wanting Itunes, though I'm under the impression that's been
sorted quite well now.

As far as he was concerned he had a fscking watch, what's wrong with
this fscking piece of.. or words to that affect and really he was right.

The alternative was Vista which took and I mean no joke like 15 mins to
finish booting, despite a cleanup and the drive checked out ok. He had
just started a gym and couldn't afford extra ram at the time.

No need to get touchy, simply real facts, better aired than ignored. Not
a great loss or anything.

-- 
_______________________________________________________________________

'Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
universal interface'

(Doug McIlroy)
_______________________________________________________________________

Re: [gentoo-user] System won't boot if CMOS clock is slow

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

On Wed, 16 Jan 2013 16:43:16 +0000 (UTC), Grant Edwards wrote:

> I'm having problems with one of my Gentoo systems who's motherboard
> clock is a little slow.  When the system comes up, the system time is
> set from the motherboard clock.  If that's slow, something in the init
> system seems to panic because some file or other has a timestamp in
> the future.

Change the motherboard battery?

Set  clock_systohc="YES" in /etc/conf.d/hwclock

> Just to make it extra convenient, it clears the console screen when
> that happens so there's no actual record of what went wrong or which
> component in th init process is failing.

You can stop the console clearing by changing the first terminal line
in /etc/inittab to

c1:12345:respawn:/sbin/agetty --noclear 38400 tty1 linux


-- 
Neil Bothwick

Isn't 'Criminal Lawyer' rather redundant?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] System won't boot if CMOS clock is slow

[Stroller]

On 16 January 2013, at 16:43, Grant Edwards wrote:

> I'm having problems with one of my Gentoo systems who's motherboard
> clock is a little slow.  When the system comes up, the system time is
> set from the motherboard clock.  If that's slow, something in the init
> system seems to panic because some file or other has a timestamp in
> the future.

You've had lots of other suggestions here, but I think this is handled fine if you add ntp to the default runlevel (and assuming the system can connect to the net).

Stroller.

Re: [gentoo-user] System won't boot if CMOS clock is slow

[William Tomlinson]

[-- Attachment #1: Type: text/plain, Size: 744 bytes --]

I've had this problem before as well and can confirm that adding NTP to the
default run level solved it.
On Jan 17, 2013 10:08 AM, "Stroller" <stroller@stellar.eclipse.co.uk> wrote:

>
> On 16 January 2013, at 16:43, Grant Edwards wrote:
>
> > I'm having problems with one of my Gentoo systems who's motherboard
> > clock is a little slow.  When the system comes up, the system time is
> > set from the motherboard clock.  If that's slow, something in the init
> > system seems to panic because some file or other has a timestamp in
> > the future.
>
> You've had lots of other suggestions here, but I think this is handled
> fine if you add ntp to the default runlevel (and assuming the system can
> connect to the net).
>
> Stroller.
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 1082 bytes --]

Re: [gentoo-user] System won't boot if CMOS clock is slow

[Bruce Hill]

On Thu, Jan 17, 2013 at 03:06:23PM +0000, Stroller wrote:
> 
> On 16 January 2013, at 16:43, Grant Edwards wrote:
> 
> > I'm having problems with one of my Gentoo systems who's motherboard
> > clock is a little slow.  When the system comes up, the system time is
> > set from the motherboard clock.  If that's slow, something in the init
> > system seems to panic because some file or other has a timestamp in
> > the future.
> 
> You've had lots of other suggestions here, but I think this is handled fine if you add ntp to the default runlevel (and assuming the system can connect to the net).

The service would be ntpd (daemon) or ntp-client (client), but not ntp.

Still you should change your CMOS battery. ;)
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

Re: [gentoo-user] System won't boot if CMOS clock is slow

[Stroller]

On 17 January 2013, at 15:35, Bruce Hill wrote:
>> 
>> You've had lots of other suggestions here, but I think this is handled fine if you add ntp to the default runlevel (and assuming the system can connect to the net).
> 
> The service would be ntpd (daemon) or ntp-client (client), but not ntp.

Yes, obviously.

Stroller.

[gentoo-user] Re: System won't boot if CMOS clock is slow

[Grant Edwards]

On 2013-01-17, Stroller <stroller@stellar.eclipse.co.uk> wrote:
>
> On 16 January 2013, at 16:43, Grant Edwards wrote:
>
>> I'm having problems with one of my Gentoo systems who's motherboard
>> clock is a little slow.  When the system comes up, the system time is
>> set from the motherboard clock.  If that's slow, something in the init
>> system seems to panic because some file or other has a timestamp in
>> the future.
>
> You've had lots of other suggestions here, but I think this is
> handled fine if you add ntp to the default runlevel (and assuming the
> system can connect to the net).

It doesn't help problems that occur before ntpd has started and had a
chance to slew the clock.  By default, ntpd doesn't seem to want to do
a step correction to fix large clock errors on startup (there's
probably an option for that).

FWIW, I recently identified one rather obscure CMOS-clock-related
problem scenario (this isn't what happened the other day, but it did
waste about half a day a few months back):

 1) Your CMOS clock is ahead of the "real" time by several hours for
    some reason. There are a number of ways this can happen:
    dual-booting between systems that disagree over UTC vs localtime
    for the CMOS clock, broken ntpd config, mismanaged timezone
    settings, etc.

 2) Kernel comes up and sets system time from CMOS clock.

 3) Root filesystem gets fsck'ed because it's been mounted 28 times,
    and filesystem meta-data gets timestamp that is actually several
    hours in the future.

 4) System reboots after fsck is finished.

 5) Before the recently fsck'ed filesystem gets mounted, the CMOS
    clock gets reset to the correct time (by dual booting, booting
    from a rescue CD, or by simply running the BIOS setup and fixing
    it).

 6) The system boots again, and when it tries to mount the root
    filesystem, the filesystem meta-data has a timestamp that's in the
    future so the ext3 code in the kernel refuses to mount it.

 7) You futz around verifying that you have a good root fs backup,
    looking at S.M.A.R.T logs and all sorts of other irrelevant things
    for several hours trying to figure out what's wrong.

 8) The universe catches up to the filesystem meta-data timestamp, and
    suddenly, mysteriously, everything works fine.
    
-- 
Grant Edwards               grant.b.edwards        Yow! You mean you don't
                                  at               want to watch WRESTLING
                              gmail.com            from ATLANTA?

Re: [gentoo-user] Re: System won't boot if CMOS clock is slow

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 337 bytes --]

On Thu, 17 Jan 2013 22:47:17 +0000 (UTC), Grant Edwards wrote:

> By default, ntpd doesn't seem to want to do
> a step correction to fix large clock errors on startup (there's
> probably an option for that).

That's for ntp-client to do.


-- 
Neil Bothwick

Everything should be made as simple as possible, but no simpler.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-user] Re: System won't boot if CMOS clock is slow

[Grant Edwards]

On 2013-01-17, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 17 Jan 2013 22:47:17 +0000 (UTC), Grant Edwards wrote:
>
>> By default, ntpd doesn't seem to want to do
>> a step correction to fix large clock errors on startup (there's
>> probably an option for that).
>
> That's for ntp-client to do.

In additon to being a server, ntpd _is_ an ntp client.

Are you talking about running ntpclient
(http://doolittle.icarus.com/ntpclient) instead of ntpd?

-- 
Grant Edwards               grant.b.edwards        Yow! I invented skydiving
                                  at               in 1989!
                              gmail.com            

Re: [gentoo-user] System won't boot if CMOS clock is slow

[Stroller]

On 18 January 2013, at 18:08, Grant Edwards wrote:

> On 2013-01-17, Neil Bothwick <neil@digimed.co.uk> wrote:
>> On Thu, 17 Jan 2013 22:47:17 +0000 (UTC), Grant Edwards wrote:
>> 
>>> By default, ntpd doesn't seem to want to do
>>> a step correction to fix large clock errors on startup (there's
>>> probably an option for that).
>> 
>> That's for ntp-client to do.
> 
> In additon to being a server, ntpd _is_ an ntp client.
> 
> Are you talking about running ntpclient
> (http://doolittle.icarus.com/ntpclient) instead of ntpd?

I'm pretty sure he's talking about making larger corrections to fix larger clock errors on startup.

I believe I have both ntpd and ntp-client in the default runlevel on at least one system, although I won't swear to it.

Stroller.

Re: [gentoo-user] System won't boot if CMOS clock is slow

[Paul Klos]

Op vrijdag 18 januari 2013 18:47:31 schreef Stroller:
> 
> On 18 January 2013, at 18:08, Grant Edwards wrote:
> 
> > On 2013-01-17, Neil Bothwick <neil@digimed.co.uk> wrote:
> >> On Thu, 17 Jan 2013 22:47:17 +0000 (UTC), Grant Edwards wrote:
> >> 
> >>> By default, ntpd doesn't seem to want to do
> >>> a step correction to fix large clock errors on startup (there's
> >>> probably an option for that).
> >> 
> >> That's for ntp-client to do.
> > 
> > In additon to being a server, ntpd _is_ an ntp client.
> > 
> > Are you talking about running ntpclient
> > (http://doolittle.icarus.com/ntpclient) instead of ntpd?
> 
> I'm pretty sure he's talking about making larger corrections to fix larger clock errors on startup.
> 
> I believe I have both ntpd and ntp-client in the default runlevel on at least one system, although I won't swear to it.
> 
> Stroller.
> 
> 

I think you can either run ntp-client to set the time at startup, or ntpd -q. Both are run through ntp-client, but you can set it so that it uses ntpd to set the time. This is done by modifying /etc/conf.d/ntp-client. Mine looks like this, so you can see I'm actually using ntpd -q as ntp-client:

# /etc/conf.d/ntp-client

# Command to run to set the clock initially
# Most people should just leave this line alone ...
# however, if you know what you're doing, and you
# want to use ntpd to set the clock, change this to 'ntpd'
NTPCLIENT_CMD="ntpd"

# Options to pass to the above command
# This default setting should work fine but you should
# change the default 'pool.ntp.org' to something closer
# to your machine.  See http://www.pool.ntp.org/ or
# try running `netselect -s 3 pool.ntp.org`.
#NTPCLIENT_OPTS="-s -b -u \
#       0.gentoo.pool.ntp.org 1.gentoo.pool.ntp.org \
#       2.gentoo.pool.ntp.org 3.gentoo.pool.ntp.org"
NTPCLIENT_OPTS="-q"

Paul

Re: [gentoo-user] Re: System won't boot if CMOS clock is slow

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

On Fri, 18 Jan 2013 18:08:50 +0000 (UTC), Grant Edwards wrote:

> >> By default, ntpd doesn't seem to want to do
> >> a step correction to fix large clock errors on startup (there's
> >> probably an option for that).  
> >
> > That's for ntp-client to do.  
> 
> In additon to being a server, ntpd _is_ an ntp client.

But ntpd will not handle large jumps in time, such as when booting with a
broken CMOS clock. So you run /etc/init.d/ntp-client as well, which gets
the clock right at boot time, then ntpd can keep it right.

> Are you talking about running ntpclient
> (http://doolittle.icarus.com/ntpclient) instead of ntpd?

No.

% qlist net-misc/ntp | grep init.d
/etc/init.d/ntpd
/etc/init.d/ntp-client


-- 
Neil Bothwick

Did you hear about the blind prostitute? You have to hand it to her.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-user] Re: System won't boot if CMOS clock is slow

[Grant Edwards]

On 2013-01-18, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Fri, 18 Jan 2013 18:08:50 +0000 (UTC), Grant Edwards wrote:
>
>> >> By default, ntpd doesn't seem to want to do
>> >> a step correction to fix large clock errors on startup (there's
>> >> probably an option for that).  
>> >
>> > That's for ntp-client to do.  
>> 
>> In additon to being a server, ntpd _is_ an ntp client.
>
> But ntpd will not handle large jumps in time, such as when booting
> with a broken CMOS clock. So you run /etc/init.d/ntp-client as well,
> which gets the clock right at boot time, then ntpd can keep it right.

Doh!

I couldn't find a package named ntp-client or a program named
ntp-client and didn't think to look in /etc/init.d...

-- 
Grant Edwards               grant.b.edwards        Yow! If Robert Di Niro
                                  at               assassinates Walter Slezak,
                              gmail.com            will Jodie Foster marry
                                                   Bonzo??

Re: [gentoo-user] Re: System won't boot if CMOS clock is slow

[William Kenworthy]

On 19/01/13 06:36, Neil Bothwick wrote:
> On Fri, 18 Jan 2013 18:08:50 +0000 (UTC), Grant Edwards wrote:
> 
>>>> By default, ntpd doesn't seem to want to do
>>>> a step correction to fix large clock errors on startup (there's
>>>> probably an option for that).  
>>>
>>> That's for ntp-client to do.  
>>
>> In additon to being a server, ntpd _is_ an ntp client.
> 
> But ntpd will not handle large jumps in time, such as when booting with a
> broken CMOS clock. So you run /etc/init.d/ntp-client as well, which gets
> the clock right at boot time, then ntpd can keep it right.
> 
>> Are you talking about running ntpclient
>> (http://doolittle.icarus.com/ntpclient) instead of ntpd?
> 
> No.
> 
> % qlist net-misc/ntp | grep init.d
> /etc/init.d/ntpd
> /etc/init.d/ntp-client
> 
> 

It can handle large jumps, check out this in the "man ntp.conf":

tinker panic 0

or the -g option to ntpd (again, its in a man page.)

Basicly, you just need to read and configure it ... I have it working
even on a raspberry pi which has HW clock :)

Even the slew rate, or slew/jump can be set.

BillK

Re: [gentoo-user] System won't boot if CMOS clock is slow

[Bruce Hill]

On Wed, Jan 16, 2013 at 04:43:16PM +0000, Grant Edwards wrote:
> I'm having problems with one of my Gentoo systems who's motherboard
> clock is a little slow.  When the system comes up, the system time is
> set from the motherboard clock.  If that's slow, something in the init
> system seems to panic because some file or other has a timestamp in
> the future.
> 
> Just to make it extra convenient, it clears the console screen when
> that happens so there's no actual record of what went wrong or which
> component in th init process is failing.
> 
> Going into the BIOS setup and setting the time ahead a minute or two
> will allow the system to start up normally.
> 
> Is there any way to disable this "feature"?

One other thing no one mentioned, afaict. Check your kernel for RTC (Real Time
Clock). The RTC is used to initialize the software clock at bootup.

You'll probably need RTC_DRV_CMOS.
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting