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

Re: Cannot access the Hardware Clock via any known method

On Wed, 2008-01-30 at 12:21 -0500, Bill Nottingham wrote:
> Hans de Goede (j w r degoede hhs nl) said: 
> > I'm no where near sure that this is the correct fix. I wonder if /dev/rtc 
> > is needed during the initrd at all, and if it isn't I think that the initrd 
> > should not create it all. Then rc.sysinit should be modified to run hwclock 
> > after udev, or if there are reasons not to, create the /dev entry and load 
> > the driver itself.
> The idea is to set the clock as early as possible, to ensure coordination
> among log messages, etc. After udev by definition isn't as early as
> possible.
> That being said, we *could*:
> - move clock setting later
> - set the clock from a udev rule
> Ideally, we could use the kernel support for automatically setting the
> clock when the rtc driver is initialized, but that would require everyone
> to have their clocks set in UTC, or have the kernel reading a userspace
> config file.

Wouldn't be bad to start requiring to have the clock in UTC.
But I guess dual-boot systems are the problem ?


Simo Sorce * Red Hat, Inc * New York

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