public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Colquhoun <paulcol@andor.dropbear.id.au>
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	[thread overview]
Message-ID: <4377678.WRVoGkbejG@bluering> (raw)
In-Reply-To: <20130825040413.GA3342@solfire>

[-- 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 --]

  parent reply	other threads:[~2013-08-25 10:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-25  4:04 [gentoo-user] Makeing /dev/rtc1 accessible as soon as possible - how? meino.cramer
2013-08-25  4:18 ` Mark David Dumlao
2013-08-25  4:28   ` William Kenworthy
2013-08-25  4:54     ` meino.cramer
2013-08-26  1:40       ` Mark David Dumlao
2013-08-26  6:03         ` Pandu Poluan
2013-08-25  9:02 ` Paul Colquhoun [this message]
2013-08-25 10:35   ` meino.cramer
2013-08-25 11:41     ` Mick
2013-08-25 12:50       ` meino.cramer
2013-08-25 13:15         ` William Kenworthy
2013-08-25 15:24           ` meino.cramer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4377678.WRVoGkbejG@bluering \
    --to=paulcol@andor.dropbear.id.au \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox