Re: System clock problem

[dann frazier <dannf@dannf.org>]

On Tue, Jan 06, 2009 at 10:11:45AM -0700, dann frazier wrote:
> On Mon, Jan 05, 2009 at 10:20:30PM +0100, ?meric Maschino wrote:
> > Hi Gang and Happy New Year!
> > 
> > For several kernel builds now (I don't remember exactly when this first
> > appeared), I'm getting the following error at boot time:
> > 
> > Setting the system clock.
> > Cannot access the Hardware Clock via any known method.
> > Use the --debug option to see the details of our search for an access
> > method.
> > Unable to set system Clock to: Mon Jan 5 13:40:36 CET 2008 (warning).
> > 
> > hwclock --debug gives the following output:
> > 
> > hwclock from util-linux-ng 2.13.1.1
> > hwclock: Open of /dev/efirtc failed, errno=2: No such file or directory.
> > No usable clock interface found.
> > Cannot access the Hardware Clock via any known method.
> > 
> > Is this a known issue on Debian ia64? I can't find a bug report.
> > 
> > I've tried to insert the efirtc module, but it doesn't seem to exist on
> > current linux-image-2.6-mckinley build. The only rtc-related drivers that I
> > can find on my system are:
> > 
> > emeric@longspeak:~$ ls /lib/modules/2.6.26-1-mckinley/kernel/drivers/rtc/
> > rtc-ds1307.ko  rtc-ds1742.ko   rtc-m48t86.ko   rtc-r9701.ko     rtc-v3020.ko
> > rtc-ds1374.ko  rtc-fm3130.ko   rtc-max6900.ko  rtc-rs5c348.ko   rtc-x1205.ko
> > rtc-ds1511.ko  rtc-isl1208.ko  rtc-max6902.ko  rtc-rs5c372.ko
> > rtc-ds1553.ko  rtc-m41t80.ko   rtc-pcf8563.ko  rtc-s35390a.ko
> > rtc-ds1672.ko  rtc-m48t59.ko   rtc-pcf8583.ko  rtc-stk17ta8.ko
> > 
> > Should I insert one of those to fix this issue?
> > 
> > I've experienced a clock-related issue in the past with Fedora ia64 (
> > https://bugzilla.redhat.com/show_bug.cgi?id=182597 and
> > https://bugzilla.redhat.com/show_bug.cgi?id=182598 for details), but it was
> > due to SELinux IIRC. I don't run SELinux on my Debian installation.
> > 
> > Any input? Thanks.
> 
> Ah - this is actually because the common config has switched to
> RTC_CLASS drivers, and that cause the other rtc drivers to be
> disabled (including efirtc).
> 
> I've got a simple rtc-efi module working, I'll try and get it
> accepted.

Should be fixed in 2.6.26-13.


-- 
dann frazier