View previous topic :: View next topic |
Author |
Message |
gtbX Tux's lil' helper

Joined: 11 Oct 2003 Posts: 125
|
Posted: Tue Jun 14, 2011 7:39 pm Post subject: hwclock broken with recent update |
|
|
I recently updated the kernel and baselayout on a couple of my Sparc boxes, and this error appeared on both of them after rebooting:
Code: |
* Setting system clock using the hardware clock [UTC] ...
* Timed out waiting for time change.
The Hardware Clock does not contain a valid time, so we cannot adjust it.Timed out waiting for time change.
The Hardware Clock does not contain a valid time, so we cannot set the System Time from it.
* Failed to set clock You will need to set the clock yourself * [ !! ]
|
I'm not sure which update did it, and the system time was corrected by ntp, but I'd still like to correct this error. Running hwclock directly gives a similar message:
Code: |
Timed out waiting for time change.
The Hardware Clock registers contain values that are either invalid (e.g. 50th day of month) or beyond the range we can h
andle (e.g. Year 2095).
|
|
|
Back to top |
|
 |
audiodef Watchman


Joined: 06 Jul 2005 Posts: 6567 Location: /usr/lib64/lv2
|
Posted: Tue Jun 14, 2011 8:17 pm Post subject: |
|
|
This isn't a solution, but when you said you're not sure which update did it, I thought I'd share this.
Before I do a world update, I always do
Code: |
date >> /home/user/Portage.log
emerge -pvuDN world >> /home/user/Portage.log
|
This way, when something breaks, I can check the log and at least know that it was something in the last entry that did it. That narrows it down a great deal. I can then roll something back and if necessary, mask the offending package version. _________________ Gentoo Studio: https://gentoostudio.org
Github: https://github.com/Gentoo-Music-and-Audio-Technology
Mantis: https://gentoostudio.org/mantis/
Discord: https://discord.gg/73XV24dNPN |
|
Back to top |
|
 |
gtbX Tux's lil' helper

Joined: 11 Oct 2003 Posts: 125
|
Posted: Sun Jul 03, 2011 11:35 pm Post subject: |
|
|
Well it turns out I still had baselayout-2 masked (I was updating my other machines, must've forgot this one) so it seems to be some difference between kernels 2.6.35 and 2.6.38  |
|
Back to top |
|
 |
McTango n00b


Joined: 11 Dec 2004 Posts: 66 Location: Formosa - Argentina
|
Posted: Wed Aug 17, 2011 1:11 pm Post subject: |
|
|
I have the same problem here, in all my SPARC boxes.
All boxes have Baselayout2 and Openrc.
With kernel 2.6.37-gentoo-r4, "hwclock" works ok.
But, after upgrading kernel to 2.6.38-gentoo-r6, "hwclock" gives that errors. _________________ Charly Tango
Formosa - Argentina
‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾
To emerge, or not to emerge: that is the question.
_________________ |
|
Back to top |
|
 |
Polynomial-C Retired Dev


Joined: 01 Jun 2003 Posts: 1432 Location: Germany
|
Posted: Sun Nov 06, 2011 6:11 pm Post subject: |
|
|
try this fix. It helped on my sparc machine with kernel 2.6.39.4. _________________ The manual said "Requires Windows10 or better" so I installed GNU/Linux...
my portage overlay
Need a stage1 tarball? (Unofficial builds) |
|
Back to top |
|
 |
|