From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Subject: 2.3.51 Trashes RTC on Beige G3 Mini-tower
Date: Tue, 14 Mar 2000 11:28:49 +0000 [thread overview]
Message-ID: <200003141133.LAA09460@hyperion.valhalla.net> (raw)
Hi,
at boot time {with options vmode=atyfb, vmode:16,code:32 single }
the usual "rtc time is" ... prints the correct date...
then we get "setting time to ... some time in Feb 1932...
from then on the RTC is wrong although using 'date' to set the correct time
behaves as expected on the running system.
Is this a library problem? (I'm using 2.3.51 with a system installed from
linuxPPC Q3 - but I've also updated to glibc-2.1.3 - j).
also the caps-lock is set on (although this may have no relevance - and
works perfectly OK afterwards).
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-03-14 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-14 11:28 Iain Sandoe [this message]
2000-03-15 14:49 ` 2.3.51 Trashes RTC on Beige G3 Mini-tower Christiaan Welvaart
-- strict thread matches above, loose matches on Subject: below --
2000-03-15 15:15 Iain Sandoe
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=200003141133.LAA09460@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).