Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-ppc-user
Navigation:
Lists: gentoo-ppc-user: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-ppc-user@g.o
From: "Flisk ." <f.flisk@...>
Subject: Hwclock error
Date: Sun, 26 Mar 2006 17:11:58 -0300
<div>Hi folks,</div>
<div>&nbsp;&nbsp;&nbsp; Here where I work we received a G4 computer and I started to install a Gentoo 2006.0. The computer is a G4 2 CPU's 512MB of memory 2 HD, I started to install Gentoo 2006.0 from stage 1 and everything gone well. I installed with cpu flag as G4 and O2. 
</div>
<div>&nbsp;&nbsp;&nbsp; But when the computer restarted a problem appeared with hwclock, when I execute the hwclock an error appear. The error is something like: &quot;select() to /dev/rtc to wait for clock tick timed out&quot; and the date in Linux stay 1970, the bios time is correctly because when I boot the Gento CD the hwclock work perfectly. I already recompiled the kernel with many options but nothing solve the problem. 
</div>
<div>&nbsp;&nbsp;&nbsp; I believe that the problem is with some kernel option that I forgot or some patch, because in the Gentoo CD the hwclock works perfectly. What kernel option or patch can be solve the problem? Hints?</div>
<div>&nbsp;&nbsp;&nbsp; Best regards.</div>
<div>&nbsp;</div>
<div>------------------------</div>
<div>Fernando Simon</div>
<div>Brazil</div>
<div>------------------------</div>
Replies:
Re: Hwclock error
-- David Gurvich
Re: Hwclock error
-- Joseph Jezak
Navigation:
Lists: gentoo-ppc-user: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Udev events break ALSA?
Next by thread:
Re: Hwclock error
Previous by date:
unsubscribe
Next by date:
Re: Hwclock error


Updated Jun 17, 2009

Summary: Archive of the gentoo-ppc-user mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.