From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B737D1381F3 for ; Sun, 25 Aug 2013 04:54:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DC17AE0CB5; Sun, 25 Aug 2013 04:54:54 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B33B8E0C50 for ; Sun, 25 Aug 2013 04:54:53 +0000 (UTC) Received: from gmx.net ([84.133.158.32]) by mail.gmx.com (mrgmx003) with ESMTPA (Nemesis) id 0MaqqY-1VTSnW0kVG-00KNBJ for ; Sun, 25 Aug 2013 06:54:52 +0200 Received: by gmx.net (nbSMTP-1.00) for uid 1001 meino.cramer@gmx.de; Sun, 25 Aug 2013 06:54:52 +0200 (CEST) Date: Sun, 25 Aug 2013 06:54:51 +0200 From: meino.cramer@gmx.de To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how? Message-ID: <20130825045451.GA25561@solfire> References: <20130825040413.GA3342@solfire> <521987F3.20808@iinet.net.au> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <521987F3.20808@iinet.net.au> User-Agent: mutt-ng/devel-r804 (Linux) X-Provags-ID: V03:K0:3pgGEvEXmruis/r6MS0mBcU+sMbcOxwM1k5OxCcEK8Am58idCfN 7A9qNOZ/nMv6qwSaEvUWT7OITiPh+ighWx4IndG05l8SJ1J4/TuDXkRqw40NQv48cPhhqF3 Jdfo+zVsCu+RLA6Vaj27Fb5wavwqDKUrkda1bauDTnN5aW5s7vqsbsMmw0sRDy0fcrBlJDC daW8TWhYojIQRFfk4qEng== X-Archives-Salt: 898af92e-1246-4d6d-a451-bf444f91467d X-Archives-Hash: a09063af7b6d5b9e5d0ca26df1cb4cb9 William Kenworthy [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, 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