On Thu, 24 Mar 2011 22:26:59 +0800
wu zhangjin <wuzhang...@gmail.com> wrote:

> So, is your /dev/rtc0 broken? please check it or recreate one like this:
> 
> $ rm /dev/rtc0
> $ mknod /dev/rtc0 c 254 0

I did not do that (but see below).

> 
> And can you read the date out from /proc/driver/rtc
> or /sys/class/rtc/rtc0/time?

I checked three times:

# cat /proc/driver/rtc
rtc_time        : 16:13:52
rtc_date        : 2011-03-21
alrm_time       : 00:00:00
alrm_date       : 1970-01-01
alarm_IRQ       : no
alrm_pending    : no
24hr            : yes
periodic_IRQ    : no
update_IRQ      : no
HPET_emulated   : no
BCD             : no
DST_enable      : no
periodic_freq   : 1024
batt_status     : dead
# cat /proc/driver/rtc
rtc_time        : 16:13:59
rtc_date        : 2011-03-21
alrm_time       : 00:00:00
alrm_date       : 1970-01-01
alarm_IRQ       : no
alrm_pending    : no
24hr            : yes
periodic_IRQ    : no
update_IRQ      : no
HPET_emulated   : no
BCD             : no
DST_enable      : no
periodic_freq   : 1024
batt_status     : okay
# cat /proc/driver/rtc
rtc_time        : 16:14:10
rtc_date        : 2011-03-21
alrm_time       : 00:00:00
alrm_date       : 1970-01-01
alarm_IRQ       : no
alrm_pending    : no
24hr            : yes
periodic_IRQ    : no
update_IRQ      : no
HPET_emulated   : no
BCD             : no
DST_enable      : no
periodic_freq   : 1024
batt_status     : okay

--

Note that at the first time, it said "batt_status: dead", but then changed to
okay. But the most interesting of all, that after this (not doing anything
else) "hwclock --systohc" and "hwclock -r" started to work with no error. And
they now continue to work also across a reboot and poweroff.
Strange, but well, ok. :)

-- 
With respect,
Roman

Attachment: signature.asc
Description: PGP signature

Reply via email to