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 0C2E01381F3 for ; Sun, 25 Aug 2013 10:35:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CB165E0CB8; Sun, 25 Aug 2013 10:35:32 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B3D32E0B2C for ; Sun, 25 Aug 2013 10:35:31 +0000 (UTC) Received: from gmx.net ([84.133.158.32]) by mail.gmx.com (mrgmx101) with ESMTPA (Nemesis) id 0M1jKo-1W2TWq1D6g-00tnSF for ; Sun, 25 Aug 2013 12:35:30 +0200 Received: by gmx.net (nbSMTP-1.00) for uid 1001 meino.cramer@gmx.de; Sun, 25 Aug 2013 12:35:30 +0200 (CEST) Date: Sun, 25 Aug 2013 12:35:29 +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: <20130825103529.GA3355@solfire> References: <20130825040413.GA3342@solfire> <4377678.WRVoGkbejG@bluering> 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: <4377678.WRVoGkbejG@bluering> User-Agent: mutt-ng/devel-r804 (Linux) X-Provags-ID: V03:K0:0iKg9xASAEq423BWpdr4vyRQjxPkoLytgEWRXmWRvTNWQouVYUc wR5A6LIDHbvX1fybdp7GKEyM2ffiXA9+FrK+Cv/DLSRI8O+/I4N8M0uetTVEX7c9uO9dwKq ShMQYjcotGPOaCU5KqaRcAH/wONmdVE//9pEPpx+pU9iYwOqLdDjzCNohKqLA5ay1pBek15 6YjH3paoKfnk2NDA4Qs0w== X-Archives-Salt: 2b390dd8-36e0-494c-a4a8-63943d4c9d69 X-Archives-Hash: 18962da5cb7ea176862826081816f0f2 Paul Colquhoun [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