the above mesasage appears at boot, when running hwclock. in fact is reproducible also after, with the command: gentoo64 ~ # hwclock --debug hwclock from util-linux-ng 2.14.1 hwclock: Open of /dev/rtc failed, errno=2: No such file or directory. No usable clock interface found. Cannot access the Hardware Clock via any known method. gentoo64 ~ # lsmod | grep rtc gentoo64 ~ # because no rtc driver is loaded. gentoo64 ~ # modprobe rtc-cmos gentoo64 ~ # dmesg|tail rtc_cmos 00:03: RTC can wake from S4 rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs gentoo64 ~ # ls -al /dev/rtc* lrwxrwxrwx 1 root root 4 Dec 27 19:07 /dev/rtc -> rtc0 crw-r--r-- 1 root root 246, 0 Dec 27 19:07 /dev/rtc0 gentoo64 ~ # hwclock --debug hwclock from util-linux-ng 2.14.1 Using /dev interface to clock. Last drift adjustment done at 1230332845 seconds after 1969 Last calibration done at 1230332845 seconds after 1969 Hardware clock is on local time Assuming hardware clock is kept in local time. Waiting for clock tick... /dev/rtc does not have interrupt functions. Waiting in loop for time from /dev/rtc to change ...got clock tick Time read from Hardware Clock: 2008/12/27 18:07:26 Hw clock time : 2008/12/27 18:07:26 = 1230397646 seconds since 1969 Sat Dec 27 18:07:26 2008 -0.543837 seconds gentoo64 ~ # loading an rtc driver, hwclock works. I think the initrd should try to detect one (?) before hwclock runs or this is a bug of udev, not hotplugging rtc early enough? see also the URL field, which contains link about discussion about this and a bug @ fedora project.
*** This bug has been marked as a duplicate of bug 251453 ***
