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

Problem accessing RTC on QNAP TS-209

HI All,
I'm having a problems with the Real Time Clock on my QNAP TS-209 pro II.
/sbin/hwclock --systohc --localtime hangs the system for approx 15 mins before timing out on both boot/shutdown.

I experience the same problem with hwclock with the --directisa switch. I found that other users on ubuntu solved the above problem using that switch.

Some info:
root@NAS:~/>uname -a
Linux NAS 2.6.26-1-orion5x #1 Thu Sep 11 13:28:52 UTC 2008 armv5tel GNU/Linux

root@NAS:~/>hwclock --systohc
Cannot access the Hardware Clock via any known method.

root@NAS:~/>hwclock --debug
hwclock from util-linux-ng
Using /dev interface to clock.
Last drift adjustment done at 1217000000 seconds after 1969
Last calibration done at 1217000000 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
Timed out waiting for time change.
...got clock tick

root@NAS:~?>dmesg | grep rtc
[42949375.800000] rtc-s35390a 0-0030: rtc core: registered rtc-s35390a as rtc0
[42949375.920000] rtc-s35390a 0-0030: setting system clock to 2008-09-22 19:32:40 UTC (1222111960)

Module                  Size  Used by
ipv6                  287604  16
loop                   14092  0
evdev                   8672  0
ehci_hcd               32044  0
usbcore               127740  2 ehci_hcd
mv643xx_eth            20772  0
mii                     5504  1 mv643xx_eth
gpio_keys               3264  0
ext3                  122472  2
jbd                    45268  1 ext3
mbcache                 7936  1 ext3
raid1                  21184  3
md_mod                 80212  4 raid1
sd_mod                 25200  8
sata_mv                24492  6
libata                153852  1 sata_mv
scsi_mod              149892  2 sd_mod,libata

Notice no rtc is listed - modprobe rtc returns FATAL: Module rtc not found.

Any idea on this?
Have i simply got a hardware problem or am i missing something really obvious??
There is something posted in this bug report about setting ACPI to off in the kernel boot parameters.
But i'm reluctant to do this, mostly because I don' know how just yet, but also because no other users have reported this problem on this architecture afaik.

Thanks in advance for any comments/help.

Reply to: