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, <[email protected]> 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
