[gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?

[gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?

[meino.cramer]

Hi,

There are two RTCs in my system:
/dev/rtc0 and /dev/rtc1

rtc0 is not powered by a battery and forgets time/date
with system shutdown and rtc1 is a I2C-rtc (DS3231) which
is powered by a battery. It is extremly accurate in comparison
with rtc0.

rtc0 is accessible with system boot - rtc1 is not (current state).

To make rtc1 completly know to the system, I have to do a 
    echo ds3231 0x68 >! /sys/bus/i2c/devices/i2c-1/new_device
    hwclock -f /dev/rtc1 -s
in beforehand.

I wrote a script for /etc/init.d, which does exactly this, and 
the system login screen shows the correct tome/date information
even without ntp-client (the system should become independantly
from lan/internet). The script was added to the boot service 
and executed after dev and modules.

The kernel is configured to use /dev/rtc1 and the driver for the
ds1307, which also handles the ds3231, is included into the kernel
(no module).

But it seems, that setting the system time this way is too late,
since there are still (for example) log files under /var/log
with a timestamp of the 1.1.1970.

Are there any other way to make rtc1 known and accessible earlier 
to the system as the hack via a script in /etc/init.d ?

Thank you very much in advance for any help!
Best regards,
mcc

Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?

[Mark David Dumlao]

Which runlevel did you put your script on?
You probably want it on sysinit, rather than default.

Also, you can put rc_before= and rc_after= in the corresponding
/etc/conf.d/ file and make sure it runs before your syslog but after
your sysfs.

On Sun, Aug 25, 2013 at 12:04 PM,  <meino.cramer@gmx.de> wrote:
> Hi,
>
> There are two RTCs in my system:
> /dev/rtc0 and /dev/rtc1
>
> rtc0 is not powered by a battery and forgets time/date
> with system shutdown and rtc1 is a I2C-rtc (DS3231) which
> is powered by a battery. It is extremly accurate in comparison
> with rtc0.
>
> rtc0 is accessible with system boot - rtc1 is not (current state).
>
> To make rtc1 completly know to the system, I have to do a
>     echo ds3231 0x68 >! /sys/bus/i2c/devices/i2c-1/new_device
>     hwclock -f /dev/rtc1 -s
> in beforehand.
>
> I wrote a script for /etc/init.d, which does exactly this, and
> the system login screen shows the correct tome/date information
> even without ntp-client (the system should become independantly
> from lan/internet). The script was added to the boot service
> and executed after dev and modules.
>
> The kernel is configured to use /dev/rtc1 and the driver for the
> ds1307, which also handles the ds3231, is included into the kernel
> (no module).
>
> But it seems, that setting the system time this way is too late,
> since there are still (for example) log files under /var/log
> with a timestamp of the 1.1.1970.
>
> Are there any other way to make rtc1 known and accessible earlier
> to the system as the hack via a script in /etc/init.d ?
>
> Thank you very much in advance for any help!
> Best regards,
> mcc
>
>
>
>



-- 
This email is:    [ ] actionable   [ ] fyi        [ ] social
Response needed:  [ ] yes          [ ] up to you  [ ] no
Time-sensitive:   [ ] immediate    [ ] soon       [ ] none

Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?

[William Kenworthy]

or if you have an initramfs do it there before control is passed to the
OS.  You may also be able to set rtc0 to the current time in the
initramfs as well.

BillK



On 25/08/13 12:18, Mark David Dumlao wrote:
> Which runlevel did you put your script on?
> You probably want it on sysinit, rather than default.
> 
> Also, you can put rc_before= and rc_after= in the corresponding
> /etc/conf.d/ file and make sure it runs before your syslog but after
> your sysfs.
> 
> On Sun, Aug 25, 2013 at 12:04 PM,  <meino.cramer@gmx.de> wrote:
>> Hi,
>>
>> There are two RTCs in my system:
>> /dev/rtc0 and /dev/rtc1
>>
>> rtc0 is not powered by a battery and forgets time/date
>> with system shutdown and rtc1 is a I2C-rtc (DS3231) which
>> is powered by a battery. It is extremly accurate in comparison
>> with rtc0.
>>
>> rtc0 is accessible with system boot - rtc1 is not (current state).
>>
>> To make rtc1 completly know to the system, I have to do a
>>     echo ds3231 0x68 >! /sys/bus/i2c/devices/i2c-1/new_device
>>     hwclock -f /dev/rtc1 -s
>> in beforehand.
>>
>> I wrote a script for /etc/init.d, which does exactly this, and
>> the system login screen shows the correct tome/date information
>> even without ntp-client (the system should become independantly
>> from lan/internet). The script was added to the boot service
>> and executed after dev and modules.
>>
>> The kernel is configured to use /dev/rtc1 and the driver for the
>> ds1307, which also handles the ds3231, is included into the kernel
>> (no module).
>>
>> But it seems, that setting the system time this way is too late,
>> since there are still (for example) log files under /var/log
>> with a timestamp of the 1.1.1970.
>>
>> Are there any other way to make rtc1 known and accessible earlier
>> to the system as the hack via a script in /etc/init.d ?
>>
>> Thank you very much in advance for any help!
>> Best regards,
>> mcc
>>
>>
>>
>>
> 
> 
> 

Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?

[meino.cramer]

William Kenworthy <billk@iinet.net.au> [13-08-25 06:32]:
> or if you have an initramfs do it there before control is passed to the
> OS.  You may also be able to set rtc0 to the current time in the
> initramfs as well.
> 
> BillK
> 
> 
> 
> On 25/08/13 12:18, Mark David Dumlao wrote:
> > Which runlevel did you put your script on?
> > You probably want it on sysinit, rather than default.
> > 
> > Also, you can put rc_before= and rc_after= in the corresponding
> > /etc/conf.d/ file and make sure it runs before your syslog but after
> > your sysfs.
> > 
> > On Sun, Aug 25, 2013 at 12:04 PM,  <meino.cramer@gmx.de> wrote:
> >> Hi,
> >>
> >> There are two RTCs in my system:
> >> /dev/rtc0 and /dev/rtc1
> >>
> >> rtc0 is not powered by a battery and forgets time/date
> >> with system shutdown and rtc1 is a I2C-rtc (DS3231) which
> >> is powered by a battery. It is extremly accurate in comparison
> >> with rtc0.
> >>
> >> rtc0 is accessible with system boot - rtc1 is not (current state).
> >>
> >> To make rtc1 completly know to the system, I have to do a
> >>     echo ds3231 0x68 >! /sys/bus/i2c/devices/i2c-1/new_device
> >>     hwclock -f /dev/rtc1 -s
> >> in beforehand.
> >>
> >> I wrote a script for /etc/init.d, which does exactly this, and
> >> the system login screen shows the correct tome/date information
> >> even without ntp-client (the system should become independantly
> >> from lan/internet). The script was added to the boot service
> >> and executed after dev and modules.
> >>
> >> The kernel is configured to use /dev/rtc1 and the driver for the
> >> ds1307, which also handles the ds3231, is included into the kernel
> >> (no module).
> >>
> >> But it seems, that setting the system time this way is too late,
> >> since there are still (for example) log files under /var/log
> >> with a timestamp of the 1.1.1970.
> >>
> >> Are there any other way to make rtc1 known and accessible earlier
> >> to the system as the hack via a script in /etc/init.d ?
> >>
> >> Thank you very much in advance for any help!
> >> Best regards,
> >> mcc
> >>
> >>
> >>
> >>
> > 
> > 
> > 
> 
> 

Hi Mark, hi William,

the script ds3231 in /etc/init.d is -- according to rc-update --
set as folows:

               ds3231 | boot                         

There is no corresponding file in /etc/conf.d since the script
onlu consist of two commands (see previous posting). There is no
initramfs.

Since hwclock needs /dev/rtc1 to work, the script cannot be executed
before /dev/. is up.

Is there an text/tutorial/... or such somewhere on the net, which
shows the sequence, in which the usual services/scripts in /etc/init.d 
get started/executed while the system boots?

Best regads,
mcc

Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?

[Mark David Dumlao]

On Sun, Aug 25, 2013 at 12:54 PM,  <meino.cramer@gmx.de> wrote:
> Hi Mark, hi William,
>
> the script ds3231 in /etc/init.d is -- according to rc-update --
> set as folows:
>
>                ds3231 | boot

Long and short of it, here's the boot order:
sysinit -> boot -> (single) -> default

rc(8) tells me that sysinit is for bringing up system specific stuff
such as /dev, /proc, /sys. So it's appropriate for a special device
file such as yours, with the caveat that you want it up AFTER any
dependencies such as sysfs.

Now how to do that is to make your script openrc compliant, so...

>
> There is no corresponding file in /etc/conf.d since the script
> onlu consist of two commands (see previous posting). There is no
> initramfs.

Since openrc is running your script, it will check /etc/conf.d/same-name
for any script with environment variables. Or you can put it in the init
script itself. Mind you, I don't know where to find documentation on
how openrc implements this, unlike, say, some controversial init system
on this list...

-- 
This email is:    [ ] actionable   [x] fyi        [ ] social
Response needed:  [ ] yes          [x] up to you  [ ] no
Time-sensitive:   [ ] immediate    [ ] soon       [x] none

Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?

[Pandu Poluan]

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

On Aug 26, 2013 8:41 AM, "Mark David Dumlao" <madumlao@gmail.com> wrote:
>
> On Sun, Aug 25, 2013 at 12:54 PM,  <meino.cramer@gmx.de> wrote:
> > Hi Mark, hi William,
> >
> > the script ds3231 in /etc/init.d is -- according to rc-update --
> > set as folows:
> >
> >                ds3231 | boot
>
> Long and short of it, here's the boot order:
> sysinit -> boot -> (single) -> default
>
> rc(8) tells me that sysinit is for bringing up system specific stuff
> such as /dev, /proc, /sys. So it's appropriate for a special device
> file such as yours, with the caveat that you want it up AFTER any
> dependencies such as sysfs.
>
> Now how to do that is to make your script openrc compliant, so...
>
> >
> > There is no corresponding file in /etc/conf.d since the script
> > onlu consist of two commands (see previous posting). There is no
> > initramfs.
>
> Since openrc is running your script, it will check /etc/conf.d/same-name
> for any script with environment variables. Or you can put it in the init
> script itself. Mind you, I don't know where to find documentation on
> how openrc implements this, unlike, say, some controversial init system
> on this list...
>

Just to add some info:

To the best of my knowledge, scripts in init.d will source the relevant
file in conf.d. So, whether or not an initscript requires a conf.d file
totally depends on the initscript in question.

Rgds,
--

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

Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?

[Paul Colquhoun]

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

On Sun, 25 Aug 2013 06:04:13 meino.cramer@gmx.de wrote:
> Hi,
> 
> There are two RTCs in my system:
> /dev/rtc0 and /dev/rtc1
> 
> rtc0 is not powered by a battery and forgets time/date
> with system shutdown and rtc1 is a I2C-rtc (DS3231) which
> is powered by a battery. It is extremly accurate in comparison
> with rtc0.
> 
> rtc0 is accessible with system boot - rtc1 is not (current state).


I know this might be obvious, but just in case:

Have you checked to see if the dud RTC can be disabled in the BIOS?

Or completely remove its drivers from the kernel?


-- 
Reverend Paul Colquhoun, ULC.     http://andor.dropbear.id.au/
  Asking for technical help in newsgroups?  Read this first:
     http://catb.org/~esr/faqs/smart-questions.html#intro


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

Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?

[meino.cramer]

Paul Colquhoun <paulcol@andor.dropbear.id.au> [13-08-25 12:04]:
> On Sun, 25 Aug 2013 06:04:13 meino.cramer@gmx.de wrote:
> > Hi,
> > 
> > There are two RTCs in my system:
> > /dev/rtc0 and /dev/rtc1
> > 
> > rtc0 is not powered by a battery and forgets time/date
> > with system shutdown and rtc1 is a I2C-rtc (DS3231) which
> > is powered by a battery. It is extremly accurate in comparison
> > with rtc0.
> > 
> > rtc0 is accessible with system boot - rtc1 is not (current state).
> 
> 
> I know this might be obvious, but just in case:
> 
> Have you checked to see if the dud RTC can be disabled in the BIOS?
> 
> Or completely remove its drivers from the kernel?
> 
> 
> -- 
> Reverend Paul Colquhoun, ULC.     http://andor.dropbear.id.au/
>   Asking for technical help in newsgroups?  Read this first:
>      http://catb.org/~esr/faqs/smart-questions.html#intro
> 

Hi Paul,

I cannot remove rtc0 since it is integrated into the CPU. I cannot
remove the CPU for various reasons... ;)

I put the script (see previous mail) into /etc/init.d and call it now
at sysinit times. This works so far...but I still have entries in /sys
and /proc which show 1.1.1970.

Is there any way to get rid of the need to use "echo..bla..bla" into
files of the sysfs but to give the kernel the needed informations
directly, so rtc1 is available to the kernel...?

Best regards,
mcc

Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1486 bytes --]

On Sunday 25 Aug 2013 11:35:29 meino.cramer@gmx.de wrote:
> Paul Colquhoun <paulcol@andor.dropbear.id.au> [13-08-25 12:04]:
> > On Sun, 25 Aug 2013 06:04:13 meino.cramer@gmx.de wrote:
> > > Hi,
> > > 
> > > There are two RTCs in my system:
> > > /dev/rtc0 and /dev/rtc1
> > > 
> > > rtc0 is not powered by a battery and forgets time/date
> > > with system shutdown and rtc1 is a I2C-rtc (DS3231) which
> > > is powered by a battery. It is extremly accurate in comparison
> > > with rtc0.
> > > 
> > > rtc0 is accessible with system boot - rtc1 is not (current state).
> > 
> > I know this might be obvious, but just in case:
> > 
> > Have you checked to see if the dud RTC can be disabled in the BIOS?
> > 
> > Or completely remove its drivers from the kernel?
> 
> Hi Paul,
> 
> I cannot remove rtc0 since it is integrated into the CPU. I cannot
> remove the CPU for various reasons... ;)
> 
> I put the script (see previous mail) into /etc/init.d and call it now
> at sysinit times. This works so far...but I still have entries in /sys
> and /proc which show 1.1.1970.
> 
> Is there any way to get rid of the need to use "echo..bla..bla" into
> files of the sysfs but to give the kernel the needed informations
> directly, so rtc1 is available to the kernel...?

I noticed you mentioned rtc0 is not powered by a battery, but that's what the 
CMOS battery does.  I'm curious why you don't add a new CMOS battery to your 
MoBo?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?

[meino.cramer]

Mick <michaelkintzios@gmail.com> [13-08-25 13:44]:
> On Sunday 25 Aug 2013 11:35:29 meino.cramer@gmx.de wrote:
> > Paul Colquhoun <paulcol@andor.dropbear.id.au> [13-08-25 12:04]:
> > > On Sun, 25 Aug 2013 06:04:13 meino.cramer@gmx.de wrote:
> > > > Hi,
> > > > 
> > > > There are two RTCs in my system:
> > > > /dev/rtc0 and /dev/rtc1
> > > > 
> > > > rtc0 is not powered by a battery and forgets time/date
> > > > with system shutdown and rtc1 is a I2C-rtc (DS3231) which
> > > > is powered by a battery. It is extremly accurate in comparison
> > > > with rtc0.
> > > > 
> > > > rtc0 is accessible with system boot - rtc1 is not (current state).
> > > 
> > > I know this might be obvious, but just in case:
> > > 
> > > Have you checked to see if the dud RTC can be disabled in the BIOS?
> > > 
> > > Or completely remove its drivers from the kernel?
> > 
> > Hi Paul,
> > 
> > I cannot remove rtc0 since it is integrated into the CPU. I cannot
> > remove the CPU for various reasons... ;)
> > 
> > I put the script (see previous mail) into /etc/init.d and call it now
> > at sysinit times. This works so far...but I still have entries in /sys
> > and /proc which show 1.1.1970.
> > 
> > Is there any way to get rid of the need to use "echo..bla..bla" into
> > files of the sysfs but to give the kernel the needed informations
> > directly, so rtc1 is available to the kernel...?
> 
> I noticed you mentioned rtc0 is not powered by a battery, but that's what the 
> CMOS battery does.  I'm curious why you don't add a new CMOS battery to your 
> MoBo?
> -- 
> Regards,
> Mick

Hi Mick,

this "MoBo" has neither a BIOS and therefore no BIOS battery.
I added the DS3231 rtc myself to get a battery buffered rtc.

Best regards,
mcc

Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?

[William Kenworthy]

On 25/08/13 20:50, meino.cramer@gmx.de wrote:
> Mick <michaelkintzios@gmail.com> [13-08-25 13:44]:
...
> Hi Mick,
> 
> this "MoBo" has neither a BIOS and therefore no BIOS battery.
> I added the DS3231 rtc myself to get a battery buffered rtc.
> 
> Best regards,
> mcc
> 
> 
> 
> 
> 

What is the device ... a raspberry pi?

A pi also has a rtc thats not battery backed so the first thing you need
to do is set the time as soon as the network comes up with the results
you describe ... nobody cares and the device works fine.

Under what circumstances is this a problem? - I see where you say some
files have an epoch date, but again thats normal for a pi and doesn't
cause any problems.

This might help us understand what you are trying to do ...

BillK

Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how?

[meino.cramer]

William Kenworthy <billk@iinet.net.au> [13-08-25 15:16]:
> On 25/08/13 20:50, meino.cramer@gmx.de wrote:
> > Mick <michaelkintzios@gmail.com> [13-08-25 13:44]:
> ...
> > Hi Mick,
> > 
> > this "MoBo" has neither a BIOS and therefore no BIOS battery.
> > I added the DS3231 rtc myself to get a battery buffered rtc.
> > 
> > Best regards,
> > mcc
> > 
> > 
> > 
> > 
> > 
> 
> What is the device ... a raspberry pi?
> 
> A pi also has a rtc thats not battery backed so the first thing you need
> to do is set the time as soon as the network comes up with the results
> you describe ... nobody cares and the device works fine.
> 
> Under what circumstances is this a problem? - I see where you say some
> files have an epoch date, but again thats normal for a pi and doesn't
> cause any problems.
> 
> This might help us understand what you are trying to do ...
> 
> BillK
> 
> 
> 
> 

Hi BillK,

nearly.... ;)
Its a Beaglebone Black...
Regarding the situation of rtcs it is the same as with the Raspi.

Changing between "bein connected to the internet" and "being not"
creates a chaos is correctly and incorrectly time stamped files.
Previously I got headaches while trying to figure out why certain
things (emerging, compiling etc.) does not work properly.
Secondly I feel be far more comfortably knowing that I do not
have to care about the correct time stamps.
Thirdly I dont like such a mess on my system...

But the question remains: How can I can introduce the existing
of a I2C device (the DS3231) to the system as soon as possible?
Since the kernel can be configured to not only care about rtc0 
but to use any other rtc, it must be possible to introduce/initiate
such a device to the kernel in a pre-filesystem-mount state of 
booting the system...I simply dont know how...

Best regards,
mcc