Re: Something Wicked (with my hdwr clock) This Way Comes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2007-12-27 at 01:36 -0800, Dean S. Messing wrote:
> As root, I just tried doing: `hwclock --show' for the first time on my
> new Dell Precision 490 running F7 and it just hung.  Cntl-C broke me out.
> 
> I then tried `hwclock --show  --debug' and got:
> 
>   hwclock from util-linux-2.13-pre7
>   Using /dev/rtc interface to clock.
>   Last drift adjustment done at 1198717263 seconds after 1969
>   Last calibration done at 1198717263 seconds after 1969
>   Hardware clock is on UTC time
>   Assuming hardware clock is kept in UTC time.
>   Waiting for clock tick...
>   /dev/rtc does not have interrupt functions. 
>   Waiting in loop for time from /dev/rtc to change
Yout problem is (compared to my results) on the line /dev/rtc does not
have interrupt function.
The end of my output is as follows:

> 
--Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2007/12/27 08:00:14
Hw clock time : 2007/12/27 08:00:14 = 1198764014 seconds since 1969
Thu 27 Dec 2007 08:00:14 AM CST  -0.605349 seconds

I would then look at the characteristics of /dev/rtc for the answer.
On my machine:
[root@cyrus ~]# ls -l /dev/rtc
crw-r--r-- 1 root root 10, 135 2007-12-27 01:37 /dev/rtc

 =======================================================================
The average income of the modern teenager is about 2 a.m.
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@xxxxxxxxxxxxx



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux