On Sat, Mar 21, 2009 at 17:26:11 +0100, Arkadiusz Miskiewicz wrote: >> # hwclock --debug >> hwclock from util-linux-2.12r >> hwclock: Open of /dev/rtc failed, errno=19: No such device. >> No usable clock interface found. >> Cannot access the Hardware Clock via any known method. > > You seem to not use udev-core which is a problem.
Yes, it's production system and I cannot aford using such unreliable solutions. > Create > > crw-rw---- 1 root root 254, 0 03-20 19:27 /dev/rtc0 0 crw-r--r-- 1 root root 254, 0 Mar 21 20:12 /dev/rtc0 > with rtc major from /proc/devices # grep rtc /proc/devices 254 rtc Thnx, I've added it to dev-list, but I'm not sure what permissions are suitable, you've got 660 while /dev/rtc already has 664. # hwclock --debug hwclock from util-linux-2.12r hwclock: Open of /dev/rtc failed, errno=19: No such device. No usable clock interface found. Cannot access the Hardware Clock via any known method. however: # ./hwclock --debug hwclock from util-linux-ng 2.14.2 Using /dev interface to clock. Last drift adjustment done at 1237570798 seconds after 1969 Last calibration done at 1237570798 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2009/03/21 19:17:23 Hw clock time : 2009/03/21 19:17:23 = 1237663043 seconds since 1969 Sat Mar 21 20:17:23 2009 -0.519839 seconds is it enough to give kernel C: util-linux < 2.14 ? -- Tomasz Pala <[email protected]> _______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
