From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Christiaan Welvaart <C.J.Welvaart@phys.uu.nl>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.3.51 Trashes RTC on Beige G3 Mini-tower
Date: Wed, 15 Mar 2000 15:15:28 +0000 [thread overview]
Message-ID: <200003151515.PAA20192@hyperion.valhalla.net> (raw)
>
>> 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).
>
> On a beige G3 Dekstop, with the standard 2.3.51 sources, I don't see this
> problem At least there are no wrong dates set in /var/messages, though I
> only booted 2.3.51 twice. I use glibc-2.1.3-4a (with linux 2.2.14 now).
As of today's rsync - the trashing is no more...
It turns out the /etc/adjtime had got some very silly numbers in it - so I
can't tell at what point the problem went away.
> I did find a different problem: the builtin ethernet port doesn't work. It
> seems to work (almost?) perfectly from within linux (i.e. no errors), but
> no ethernet connection is made. The light on the hub stays off while the
> kernel reports that BMAC ethernet was succesfully initialized.
>
This problem I don't have - at least I connected to linuxppc.org quite
happily 5 minutes ago ;-)
swap .config files?
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-03-15 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 15:15 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-14 11:28 2.3.51 Trashes RTC on Beige G3 Mini-tower Iain Sandoe
2000-03-15 14:49 ` Christiaan Welvaart
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=200003151515.PAA20192@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=C.J.Welvaart@phys.uu.nl \
--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 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.