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 56EC91381F3 for ; Sun, 25 Aug 2013 10:03:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DADA4E0C7D; Sun, 25 Aug 2013 10:03:09 +0000 (UTC) Received: from nskntmtas02p.mx.bigpond.com (nskntmtas02p.mx.bigpond.com [61.9.168.140]) by pigeon.gentoo.org (Postfix) with ESMTP id 748C0E0C3F for ; Sun, 25 Aug 2013 10:03:07 +0000 (UTC) Received: from nskntcmgw09p ([61.9.169.169]) by nskntmtas02p.mx.bigpond.com with ESMTP id <20130825100306.CAEO1968.nskntmtas02p.mx.bigpond.com@nskntcmgw09p> for ; Sun, 25 Aug 2013 10:03:06 +0000 Received: from bluering.localnet ([58.172.72.6]) by nskntcmgw09p with BigPond Outbound id Gy341m00H0884ze01y34jS; Sun, 25 Aug 2013 10:03:06 +0000 X-Authority-Analysis: v=2.0 cv=APSpfbFe c=1 sm=1 a=/VC9VB1ZLbbbzpNmbdgIbw==:17 a=HUl_Uy9HZZ8A:10 a=vikMBUQs3GcA:10 a=lwPTprVgKZEA:10 a=vPtwz2tBAAAA:8 a=LXL8el5rAAAA:8 a=CwYDwnwFtBLAgY2i2fgA:9 a=CjuIK1q_8ugA:10 a=rpZbK-ZXKSkA:10 a=_RhRFcbxBZMA:10 a=SSmOFEACAAAA:8 a=mH7IY0O9K3PIQZIlYQYA:9 a=_W_S_7VecoQA:10 a=frz4AuCg-hUA:10 a=_Y3Fyctw02XvOpaN:21 a=/VC9VB1ZLbbbzpNmbdgIbw==:117 From: Paul Colquhoun To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how? Date: Sun, 25 Aug 2013 19:02:03 +1000 Message-ID: <4377678.WRVoGkbejG@bluering> User-Agent: KMail/4.11 (Linux/3.10.0-gentoo; KDE/4.11.0; x86_64; ; ) In-Reply-To: <20130825040413.GA3342@solfire> References: <20130825040413.GA3342@solfire> 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: multipart/alternative; boundary="nextPart4906767.6b96FzgKN3" Content-Transfer-Encoding: 7Bit X-Archives-Salt: bf8b0176-e894-416b-a76e-d5357b45b01a X-Archives-Hash: f9529c39dee00a30570207677a611444 This is a multi-part message in MIME format. --nextPart4906767.6b96FzgKN3 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 --nextPart4906767.6b96FzgKN3 Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="us-ascii"

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

 

--nextPart4906767.6b96FzgKN3--