All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clark Williams <williams@redhat.com>
To: Mark Knecht <markknecht@gmail.com>
Cc: RT <linux-rt-users@vger.kernel.org>
Subject: Re: 2.6.26.8-rt12 - No hwclock - works under 2.6.24-rt1
Date: Sat, 31 Jan 2009 08:52:21 -0600	[thread overview]
Message-ID: <20090131085221.7fc4458d@torg> (raw)
In-Reply-To: <5bdc1c8b0901301600k13a06b0laf048293f037374c@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 30 Jan 2009 16:00:27 -0800
Mark Knecht <markknecht@gmail.com> wrote:

> I'm just getting around to trying 2.6.26.8-rt12 from the Gentoo
> pro-audio overlay. I built the kernel using an older .config and make
> oldconfig so maybe it didn't catch something correctly. Anyway, at
> boot the system is complaining about all file times are in the future
> and later on I see a message that it couldn't set the clock and I'll
> have to do that by hand. The machine then finishes booting and I get
> as far as X. Haven't tested anything more than that.
> 
> the issue seems to be that the system cannot find my hardware clock,
> and frankly neither can I in make menuconfig so maybe someone can tell
> me where is the hardware clock? I'm hoping it's just misconfiguration
> and not something more devious.
> 
> Motherboard is an Asus A8N-E which is nVidia based. More info provided
> if need be.
> 
> Thanks,
> Mark
> 
> [NEW KERNEL]
> 
> lightning ~ # uname -a
> Linux lightning 2.6.26.8-rt12 #1 PREEMPT RT Fri Jan 30 12:39:38 PST
> 2009 x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
> lightning ~ # hwclock -r
> Cannot access the Hardware Clock via any known method.
> Use the --debug option to see the details of our search for an access method.
> lightning ~ #

As I recall this was a change in the rtc driver where it uses classes
(and you can have multiple rtc device instances).  The result is that
the rtc driver no longer creates /dev/rtc but rather /dev/rtc0. 

You might try just creating a symlink in /dev from rtc -> rtc0 and see
if that makes your startup logic happy. I don't think that using udev
to create your symlink on the fly is an option, because most distros
access the RTC before udev gets run.

You might also make sure that CONFIG_RTC_DRV_CMOS=y, so that you don't
have to load a module from an initrd to get to the cmos clock.

Clark

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)

iEYEARECAAYFAkmEZakACgkQHyuj/+TTEp2DRACfetL2DJO0oRz9ZTb8hbIbXl1t
crEAoLNbX6hzFcbsozOObAxTkcdEAdqi
=0X1+
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2009-01-31 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31  0:00 2.6.26.8-rt12 - No hwclock - works under 2.6.24-rt1 Mark Knecht
2009-01-31  7:35 ` Norval Watson
2009-01-31 14:52 ` Clark Williams [this message]
2009-01-31 17:58   ` Mark Knecht
2009-01-31 19:20     ` Clark Williams
2009-01-31 22:36       ` Mark Knecht
2009-02-01 16:21         ` Mark Knecht

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=20090131085221.7fc4458d@torg \
    --to=williams@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=markknecht@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.