Difference between revisions of "Problems with hwclock"

From ThinkWiki
Jump to: navigation, search
(Added X60s to the list)
Line 21: Line 21:
 
*Thinkpad {{T60p}}
 
*Thinkpad {{T60p}}
 
*Thinkpad {{X60s}}
 
*Thinkpad {{X60s}}
 +
*Thinkpad {{Z61m}}
  
 
== Affected Operating Systems ==
 
== Affected Operating Systems ==
  
*Linux, all flavours. Tested with kernel 2.6.18 and 2.6.19
+
*Linux, all flavours. Tested with kernel 2.6.18, 2.6.19, 2.6.20.6

Revision as of 21:03, 16 April 2007

This page discusses the problem with /dev/rtc on certain models.

Problem description

On bootup,a message like this shows up:

select() to /dev/rtc to wait for clock tick timed out


The RTC kernel driver can't handle the system clock.

Possible solutions

The hwclock command knows the parameter --directisa to access the system clock directly. To make this the default behavior, move /sbin/hwclock (or whereever it is located on your system) to /sbin/hwclock.dist and create the following shell script on the previous location:

#!/bin/sh
/sbin/hwclock.dist --directisa $*

Make the script executable (apply the same permissions you had for hwclock before) and keep your packaging system from overwriting it on updates.

Affected Models

Affected Operating Systems

  • Linux, all flavours. Tested with kernel 2.6.18, 2.6.19, 2.6.20.6