Red Hat Bugzilla – Bug 178745
Cannot access the Hardware Clock at startup
Last modified: 2007-11-30 17:11:21 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ia64; en-US; rv:1.8) Gecko/20060103 Fedora/1.5-4 Firefox/1.5
Description of problem:
At startup, I'm getting
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
Running /sbin/hwclock --debug as a user gives the same output. Here's the output of /sbin/hwclock --debug as root:
hwclock from util-linux-2.13-pre6
Using /dev/efirtc interface to clock.
Last drift adjustment done at 1138050546 seconds after 1969
Last calibration done at 1138050546 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
/dev/efirtc does not have interrupt functions. Waiting in loop for time from /dev/efirtc to change
...got clock tick
Time read from Hardware Clock: 2006/01/24 00:57:05
Hw clock time : 2006/01/24 00:57:05 = 1138060625 seconds since 1969
mar 24 jan 2006 00:57:05 CET -0.458688 seconds
I don't see any problem here, so maybe is it a synchronization issue at boot time (initscripts-related)?
I don't know when this problem appears since I'm only with Fedora since January 10th and this issue was already there.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot up Fedora Core IA-64 devel
I should add that the same message is displayed when shutting down the system,
not only at startup.
Please, try it with the latest devel version (>=util-linux-2.13-0.13).
The problem is still there with util-linux 2.13-0.14
Please, checks your logs for audit messages. It's possible that the problem is
based on missing access permissions to /dev/efirtc. For more details see bug
#182597 and bug #182598. Thanks.
*** This bug has been marked as a duplicate of 182597 ***