Problems to set time and conflict with debian systems

Topic: Problems to set time and conflict with debian systems (Read 7539 times) previous topic - next topic

0 Members and 2 Guests are viewing this topic.

Re: Problems to set time and conflict with debian systems

Reply #30 – 02 January 2018, 15:59:41

and again after restart and turn off pc

kaos kaos # hwclock
mar 02 ene 2018 14:55:29 UTC  -1.038452 segundos
kaos kaos # date
mar ene  2 14:55:41 UTC 2018
kaos kaos #

Re: Problems to set time and conflict with debian systems

Reply #31 – 02 January 2018, 16:02:23

sorry i forgot this too:

Code: [Select]

kaos kaos # dpkg-reconfigure tzdata

Current default time zone: 'America/New_York'
Local time is now:      Tue Jan  2 10:00:59 EST 2018.
Universal Time is now:  Tue Jan  2 15:00:59 UTC 2018.

kaos kaos #

Nothing work

Re: Problems to set time and conflict with debian systems

Reply #32 – 03 January 2018, 09:46:44

@keos One more time: have you symlinked your time zone to /etc/localtime?

Code: [Select]

# ln -s /usr/share/zoneinfo/America/New_York /etc/localtime

If yes and date still shows wrong time, fix debian. Don't use hwclock for reporting; date and date -u are much more readable.

Re: Problems to set time and conflict with debian systems

Reply #33 – 03 January 2018, 14:54:30

From Artix:

Code: [Select]

[kaos keos]# date -u
mié ene  3 13:51:03 UTC 2018
[kaos keos]# hwclock
2018-01-03 08:51:19.225841-0500

[kaos keos]# LANG=C ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
ln: failed to create symbolic link '/etc/localtime': File exists
[kaos keos]#

From Debian:

Code: [Select]

kaos kaos # date -u
mié ene  3 14:02:53 UTC 2018
kaos kaos # hwclock
mié 03 ene 2018 09:03:15 EST  -0.280624 segundos

kaos kaos # LANG=C ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
ln: failed to create symbolic link '/etc/localtime': File exists
kaos kaos #

i want to say -just in case - one more time ... that time in debian is o'k, (when i fix it) while still in debian, but once i change to Arch ... the same in arch, when i fix time, both arch works fine but when change to debian ...

Thanks.

Re: Problems to set time and conflict with debian systems

Reply #34 – 03 January 2018, 19:39:04

sorry, from LinuxMint:

Code: [Select]

kaos kaos # date -u
mié ene  3 18:35:45 UTC 2018
kaos kaos # date
mié ene  3 13:35:51 EST 2018
kaos kaos #

Code: [Select]

kaos kaos # LANG=C ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
ln: failed to create symbolic link '/etc/localtime': File exists
kaos kaos #

and of course the file already exist:

Code: [Select]

  GNU nano 2.2.6           Archivo: /etc/localtime                              

TZif2^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^D^@^@^@^D^@^@^@^@^@^@^@�^@^@^@^D^@^@^$
@p��9`ˈ�p҈#�p҈`��ӈu䈱�Ԉ@݈�ՈUƈ�  �� 5��؈^@��و^U��و���ڈ��pۈ�e�܈މpݩ�` kp߉d`��MpቱiF`≱~$
��`^K��p^L٢ 
�gp^N���^O���^P�f�^Q�e�^RyH�^SiG�^TY*�^UI)�^V9^L�^W)^K�^X")`^Y^H��^Z^B^K`^Z�
p^[��`^\��p^]��`^^��p^_��` v^@�!��`"U��#j��$5��%J��&^U��'*s�'��p)
U�)ޥp* 7 +��p,ӥT`-�ip.�6`/~Kp0�^X`1gg�2r�`3GI�4Rܥ`5'+�62�`7^G
�8^[��8���9���:���;۞�<�p=���>�Оp?�b�@o�pA�^?`BO�pCda`D/vpEDC`E���G-_�Gӊ�I
A�I�l�J�#�K��pL�@`M|kpN�"`O\MpP�^D`Q</pRu�`S^\^QpTU�`T��pV5�`V�^O�X^^��X���Y���$
xpeG/`e�Zpg'^Q`g�<pi^F�`i�^^pj��`k�:�l���mv^\�n���oU��p���q5��ro��s^U��tOy�t��p$
@p������9`����ˈ�p����҈#�p����҈`������ӈu䈱�����Ԉ@݈�����ՈUƈ�����  ������ 5������؈^@�$
��`^@^@^@^@^K��p^@^@^@^@^L٢ ^@^@^@^@
�gp^@^@^@^@^N���^@^@^@^@^O���^@^@^@^@^P�f�^@^@^@^@^Q�e�^@^@^@^@^RyH�^@^@^@^@^Si$
p^@^@^@^@^[��`^@^@^@^@^\��p^@^@^@^@^]��`^@^@^@^@^^��p^@^@^@^@^_��`^@^@^@^@ v^@�$
U�^@^@^@^@)ޥp^@^@^@^@* 7ॱ^@^@^@^@+��p^@^@^@^@,ӥT`^@^@^@^@-�ip^@^@^@^@.�6`^@^@^@$
�^@^@^@^@8^[��^@^@^@^@8���^@^@^@^@9���^@^@^@^@:���^@^@^@^@;۞�^@^@^@^@<�p^@^@^@^A�^@^@^@^@I�l�^@^@^@^@J�#�^@^@^@^@K��p^@^@^@^@L�@`^@^@^@^@M|kp^@^@^@^@N�"`^@^@^$
xp^@^@^@^@eG/`^@^@^@^@e�Zp^@^@^@^@g'^Q`^@^@^@^@g�<p^@^@^@^@i^F�`^@^@^@^@i�^^p^@$
EST5EDT,M3.2.0,M11.1.0

              [ 18 líneas leídas (Convertidas desde formato Mac) ]
^G Ver ayuda ^O Guardar   ^R Leer fich.^Y Pág. ant. ^K Cortar Tex^C Posición
^X Salir     ^J Justificar^W Buscar    ^V Pág. sig. ^U PegarTxt  ^T Ortografía

what I'm I doing wrong?

Re: Problems to set time and conflict with debian systems

Reply #35 – 04 January 2018, 16:13:25

Code: [Select]

# ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime

Re: Problems to set time and conflict with debian systems

Reply #36 – 04 January 2018, 19:27:33

from Mint after apply this new command modification and reboot...

Code: [Select]

kaos kaos # date
jue ene  4 13:23:44 EST 2018
kaos kaos # date -u
jue ene  4 18:23:51 UTC 2018
kaos kaos # hwclock
jue 04 ene 2018 08:24:08 EST  -0.563136 segundos
kaos kaos #

Re: Problems to set time and conflict with debian systems

Reply #37 – 04 January 2018, 21:18:19

Looks like solved.

Re: Problems to set time and conflict with debian systems

Reply #38 – 05 January 2018, 14:36:45

No is not solved, as before, when i change to Arch the time is going wrong ...

Re: Problems to set time and conflict with debian systems

Reply #39 – 05 January 2018, 23:56:59

Quote from: keos – on 04 January 2018, 19:27:33

from Mint after apply this new command modification and reboot...

Code: [Select]
kaos kaos # date
jue ene  4 13:23:44 EST 2018
kaos kaos # date -u
jue ene  4 18:23:51 UTC 2018
kaos kaos # hwclock
jue 04 ene 2018 08:24:08 EST  -0.563136 segundos
kaos kaos #

This looks F@@@ed, it is adding 5 to UTC instead of subtracting 5 from UTC (London time).
Maybe the problem is in BIOS time. Why don't you switch BIOS time to UTC if it is on real time EST, or vice versa.

You seem to be on Pakistan time or is it W. Kazakhstan?

This is crazy, I've had a similar problem before but somehow it worked itself out after a couple of rounds of fixing.
Maybe you should lie to systemd on your whereabouts and make it think you are 5hrs ahead of UTC

You may have a Borat virus.

Re: Problems to set time and conflict with debian systems

Reply #40 – 06 January 2018, 16:29:24

Hi,

The Bios here do not have any other option that: «system time», which is set at newyork time, EAST.

The last thing that have to think about it is a virus since everything is fine WHILE i do not change from debian to arch or from arch systems to debian ...
systemd? ... LinuxMint Rosa do not have systemd neither Artix or Archlabs, as far as i know.

The only thing that i never said here because i think it is irrelevant is that Windows was installed before in this pc (not anymore) and i had a similar problem between Linux and windows till i apply some commands in Mint that someone else recomeded (i forgot those orders) and the problem was fixed.

The last solution if nobody here can help will be to uninstall Linuxmint ... -- in the near future they are not going to support anymore Rosa without systemd.

Thanks!

Re: Problems to set time and conflict with debian systems

Reply #41 – 06 January 2018, 19:29:06

So what you had done then was to make mint cope with MS craziness subtracting 5 hrs from machine to produce a UTC figure and then use that UTC to figure EST. With MS out of the way the machine time is pushed to UTC and stays that way only Mint is reading it and adding 5hrs to it and throwing it all off.

Maybe there is a package that feeds from an internet time server and overrides all this craziness.

[about Mint]
I thought all mint was based on debian and some ubuntu. Before you kill it, I don't know much about Rosa, it may be worth your while to switch the debian repositories to devuan, maybe ascii (https://sourceforge.net/projects/refracta/files/testing/) which is parallel to stretch (current Debian stable). Maybe I am thinking of LMDE, but still ubuntu is based on debian packaging plus some custom ubu stuff. Maybe Rosa was based on wheezy and its support is ending next year and this is why you have Mint without systemd. Which means your init system should be sysvinit/sysv-rc. Devuan uses the same and OpenRC is as simple as installing it and uninstalling sysv-rc. The whole thing boots up in a fraction of time than debian, almost as good as Artix, less than half the idling RAM on the desktop.

See if that holds together for you. If mint repositories are separate and in addition to debian/ubu then it may work. If mint incorporates those other repositories in its own then it will be impossible to clear out the way debian pkg works. Arch prioritizes repositories of preference, debian doesn't.

I never touched ubuntu or mint. I hate funky crowded desktops.

Re: Problems to set time and conflict with debian systems

Reply #42 – 06 January 2018, 21:29:45

What package causes this problem in Mint? Try to use whatever you use for package management to search for installed packages relating to 'time' 'clock' or 'ntp'. If you don't get stopped by dependency issues, you might be able to identify which one causes the problem by removing them one by one and testing on reboots to see if the problem goes away. Then you could use an alternative or at least have a better idea where to look, the package might have man pages with suggestions too.
This is perhaps slightly risky in terms of breaking Mint so proceed with caution, but less drastic than deleting it.
In the simplest case it might just be set at early boot by sysvinit and could depend on what locale is set, don't uninstall sysvinit. The boot scripts might show what is happening a little.
" i apply some commands in Mint that someone else recomeded (i forgot those orders) and the problem was fixed."
You can 'purge' packages to remove existing config files, then reinstall them. Possibly you can reconfigure them to standard too, I can't remember offhand.
Those commands might be in here, depending how long this file was set up to be in the terminal settings in Mint:
$ cd ~/
$ nano .bash_history
Also if you installed any additional packages, there should be some sort of logs for apt somewhere, possibly /var/log/apt?

Sometimes the CMOS battery fails and the BIOS clock is unset on every boot, then it might get reset to the last known time cached on the HDD which can give odd effects, and some packages synchronize the time from an online source.

Re: Problems to set time and conflict with debian systems

Reply #43 – 06 January 2018, 21:52:03

I am amazed that the op has the fortitude to continue trying to resolve this issue....kudos. Personally I would bite the bullet and choose which distro I want to run, and go with it.
Dual booting is problematic at the best of times....case in point.

I hope you can resolve this, one way or the other.

Best regards.

Re: Problems to set time and conflict with debian systems

Reply #44 – 07 January 2018, 15:24:30

From here:
https://help.ubuntu.com/community/UbuntuTime#Make_Linux_use_.27Local.27_time

To tell your Ubuntu system that the hardware clock is set to 'local' time:
Pre-Ubuntu 15.04 systems (e.g. Ubuntu 14.04 LTS):
edit /etc/default/rcS
add or change the following section
# Set UTC=yes if your hardware clock is set to UTC (GMT)
UTC=no

Ubuntu 15.04 systems and above (e.g. Ubuntu 16.04 LTS):
open a terminal and execute the following command
timedatectl set-local-rtc 1

If the time zone is wrong, further up on that same page it says:

Using the command line, you can use sudo dpkg-reconfigure tzdata.
Open a terminal window by going to Applications>Accessories>Terminal
sudo dpkg-reconfigure tzdata
Follow the directions in the terminal.
The timezone info is saved in /etc/timezone - which can be edited or used below

I am guessing you have set Mint to use local time for the hardware / BIOS / CMOS clock, to work with Windows which also uses localtime by default. Mint probably has some time syncing thing installed like ntp or ntpd. (This might have it's own conf file too, if it still isn't fixed above, and there's also some Gnome desktop time thing that may or may not have an effect.) So it starts up, sets the OS clock initially from whatever the BIOS clock is set to. Then it checks to see if the OS clock is correct, also on local time, and resets the BIOS clock as well if it isn't where it thinks it should be.
Artix meanwhile uses UTC / GMT (unless that has been set to something different) because Linux uses this by default, and sets local time for the OS as an offset to what it wrongly believes is UTC (but is actually local time) on the BIOS clock.
Of my suggestions in the earlier post, I think now looking in .bash_history to find out what you did to configure the time on Mint is the most useful approach. If you have had that install for years it may not be in there, or you could have changed it using desktop settings menus. I think you must have done something clever to make it use local time for Windows though.