Hi,
Samuel Thibault wrote:
The default seems to be yes, according to /etc/init.d/hwclock.sh. You
could try to set it to no. Samuel
I set it to "no" and uncommented the line, i still have the problem.
It is interesting that a single-boot user too yields the problem.
However if booting gets int
Riccardo Mottola, le Wed 14 May 2014 16:07:19 +0200, a écrit :
> Samuel Thibault wrote:
> >Do you have HWCLOCKACCESS enabled in /etc/default/hwclock and rcS?
> >Otherwise I don't see how a BIOS manages to let an OS disturb its RTC...
> I don't have it, as I wrote, at least, the line is commented ou
Hi,
Samuel Thibault wrote:
Do you have HWCLOCKACCESS enabled in /etc/default/hwclock and rcS?
Otherwise I don't see how a BIOS manages to let an OS disturb its RTC...
I don't have it, as I wrote, at least, the line is commented out. What's
the default? shoul I explicitely set it to NO?
I noti
Hi,
Samuel Thibault wrote:
Do you have HWCLOCKACCESS enabled in /etc/default/hwclock and rcS?
Otherwise I don't see how a BIOS manages to let an OS disturb its RTC...
The line is commented out.
# Set this to yes if it is possible to access the hardware clock,
# or no if it is not.
#HWCLOCKACCE
Riccardo Mottola, le Mon 28 Apr 2014 15:03:13 +0200, a écrit :
> If I boot into the hurd, the clock settings are gone! The BIOS fails
> checksum and I need to reenter all the values.
Do you have HWCLOCKACCESS enabled in /etc/default/hwclock and rcS?
Otherwise I don't see how a BIOS manages to let
