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 interrupted to execute fsck and then I reboot, the BIOS does not get corrupted.
Riccardo
