Welcome!

Please read this important information about Spectre and Meltdown vulnerabilities.
Please read this important information about MX sources lists.
News
  • MX Linux on social media: here
  • Mepis support still here
Current releases
  • MX-17 Final release info here
  • MX-16.1 release info here
  • antiX-17 release info here
    New users
    • Please read this first, and don't forget to add system and hardware information to posts!
    • Read Forum Rules

Thinking about time

Help for Current Versions of MX
Message
Author
User avatar
dreamer
Forum Novice
Forum  Novice
Posts: 19
Joined: Sun Oct 15, 2017 11:34 am

Thinking about time

#1 Postby dreamer » Thu Jan 11, 2018 12:52 pm

I noticed when booting into MX 16.1 that there is a warning saying "hardware clock is set in the future less than a day" or something like that. When I shut down there is a line with info that hardware clock has been updated.

I have more than one OS on the disk and would like MX Linux to leave the BIOS clock alone. I started by disabling that which was possible to disable in "timesetgui". I still got time related messages during boot and shut down. Then I uninstalled ntp (network time protocol). It was two packages plus timesetgui as a dependency.

My question is if it is possible to make a Debian based distro such as MX Linux ignore time completely during boot and shut down and just read the BIOS clock but never write to it. In a multi-boot scenario it's better if just one OS controls time. In Ubuntu I can't uninstall ntp packages because they have crazy dependencies. Ubuntu also interacts with (writes to) BIOS clock during boot regardless of ntp settings.

genericmeatsack
Forum Novice
Forum  Novice
Posts: 3
Age: 41
Joined: Thu Dec 21, 2017 2:23 am

Re: Thinking about time

#2 Postby genericmeatsack » Thu Jan 11, 2018 1:02 pm

i have mx/win7 dual boot. i set the bios clock to UTC. on the RARE occasion i need to boot win7, i set the bios clock back to local first.
eeePC 1005ha N280 Atom 2gb ram MX 17

User avatar
dreamer
Forum Novice
Forum  Novice
Posts: 19
Joined: Sun Oct 15, 2017 11:34 am

Re: Thinking about time

#3 Postby dreamer » Thu Jan 11, 2018 1:36 pm

I have Windows 10, Ubuntu and MX Linux 16.1 all set to local, because it's easier for me to relate to than UTC.
The boot message is something like this ...(checking file system on MX Linux partition)
"superblock write time is in the future, probably because BIOS clock is set to wrong time less than a day"

To put it bluntly I just want to know if BIOS clock modification is part of the Debian/MX Linux boot/shut down routine.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 7324
Joined: Sun Dec 16, 2007 1:17 pm

Re: Thinking about time

#4 Postby dolphin_oracle » Thu Jan 11, 2018 2:11 pm

yes it is, although if everything is set to "local" it shouldn't be a problem.'

that said, you can prevent the updated of the hardware clock by editing

/etc/init.d/hwclock.sh

and remove the

Code: Select all

0 6


in the Default-Stop line in the header. Then run

Code: Select all

sudo update-rc.d hwclock.sh defaults


and it should stop the script from running at reboot or shutdown.
http://www.youtube.com/runwiththedolphin
eeepc 904ha antix 15 32 bit (streaming media player)
acer c720p chromebook - chromeos / MX15-64 (custom snapshot) live USB.
lenovo s21e - antiX-16 MX16(live-usb)

User avatar
dreamer
Forum Novice
Forum  Novice
Posts: 19
Joined: Sun Oct 15, 2017 11:34 am

Re: Thinking about time

#5 Postby dreamer » Thu Jan 11, 2018 2:54 pm

dolphin_oracle wrote:yes it is, although if everything is set to "local" it shouldn't be a problem.'

that said, you can prevent the updated of the hardware clock by editing

/etc/init.d/hwclock.sh

and remove the

Code: Select all

0 6


in the Default-Stop line in the header. Then run

Code: Select all

sudo update-rc.d hwclock.sh defaults


and it should stop the script from running at reboot or shutdown.


Thanks for your help. I edited the file by deleting 0 6 and then pasted your code in the terminal. This is the output:

Code: Select all

insserv: warning: current stop runlevel(s) (0 6) of script `hwclock.sh' overrides LSB defaults (empty).


I don't think my edits were accepted. I haven't rebooted.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 7324
Joined: Sun Dec 16, 2007 1:17 pm

Re: Thinking about time

#6 Postby dolphin_oracle » Thu Jan 11, 2018 3:11 pm

Its a cryptic message but I think the change went thru.
http://www.youtube.com/runwiththedolphin
eeepc 904ha antix 15 32 bit (streaming media player)
acer c720p chromebook - chromeos / MX15-64 (custom snapshot) live USB.
lenovo s21e - antiX-16 MX16(live-usb)

User avatar
dreamer
Forum Novice
Forum  Novice
Posts: 19
Joined: Sun Oct 15, 2017 11:34 am

Re: Thinking about time

#7 Postby dreamer » Thu Jan 11, 2018 3:52 pm

dolphin_oracle wrote:Its a cryptic message but I think the change went thru.


Yes, probably. The boot message is the same, actually:
"Name of MX partition: Superblock last write time is in the future, probably because BIOS clock is wrong (by less than a day)"
Not really sure what to make of this, but it's just a message not an action so it doesn't really matter.

The shut down message has changed from "hardware clock updated" to "system clock/time saved" so this indicates that hardware clock is no longer changed. Although, I have to wonder why system clock needs to be saved. BIOS is what normally keeps time between reboots. Maybe it's just a message for logging when system was shut down.

I'm lucky to use a HDD otherwise I wouldn't be able to see this. Anyway, thanks for helping me with this.

User avatar
arjaybe
Forum Guide
Forum Guide
Posts: 1579
Joined: Wed Jul 12, 2006 6:51 pm

Re: Thinking about time

#8 Postby arjaybe » Thu Jan 11, 2018 4:21 pm

How does the time compare in your three OSes? Are they radically different?
Intel Celeron 1007U with integrated HD Graphics 2500, 4GB RAM

The question is half the size of the universe, and the answer takes up the other half.

Green Comet

User avatar
dreamer
Forum Novice
Forum  Novice
Posts: 19
Joined: Sun Oct 15, 2017 11:34 am

Re: Thinking about time

#9 Postby dreamer » Thu Jan 11, 2018 5:07 pm

No, same time in all OSes. If time is off (like mixing local and UTC) what can happen is that you lose your Internet connection when your IP address refreshes. This happened to me and then I set MX Linux to local.

User avatar
dreamer
Forum Novice
Forum  Novice
Posts: 19
Joined: Sun Oct 15, 2017 11:34 am

Re: Thinking about time

#10 Postby dreamer » Thu Jan 11, 2018 6:22 pm

Oops, this goes deeper. I just did a reboot and there are quite a few lines displayed in the shut down sequence. Now my eyes caught the line that said "hardware clock updated to xxxxxxxxxx UTC". So there still seems to be a problem with BIOS clock updates during shut down/restart.

I'm sure there are pros and cons with the OS taking control of the BIOS clock. I think BIOS write access should require user permission. I'm not going to spend time with this today, but if anyone has suggestions feel free to post. This is something I want to solve, because BIOS is sacred. ;) Uninstalling Network Time Protocol packages should be enough I think.


Return to “MX Help”

Who is online

Users browsing this forum: penguin48 and 10 guests