Bonjour,
JamulusOS (USB key) allows me to shave a few milliseconds off my sessions compared to my Windows10 setup. I switch OS using the UEFI/BIOS program boot priorities (ASUS motherboard).
However everytime I reboot from JamulusOS to Windows, the system clock is 5 hours later. I'm in Montreal, QC, Canada, so Now = UTC - 5:00. Upon closing, JamulusOS seems to replace the system time Now with the UTC time and date.
Is anybody else having this problem ? @eleandar is there a solution ?
Thanks for any info.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Linux supposes the RealTimeClock (RTC) to show UTC. If the computer re-synchronizes time with NTP, Linux also adjusts the RTC. Windows however supposes the RTC to show local time.
The behaviour can be changed either on the Linux side or on the Windows side.
Change on the Linux side is not feasible, since, when you issue the command
timedatectl set-local-rtc 1
the RTC may already have be adjusted and perhaps the next adjustment of the RTC happens after your session is closed! You can reduce the probability that Linux adjusts the RTC after have to crate the directory ~/.config/autostart and put a bash script there with this command (and possibly others you want to rely on like for instance locking the caps lock key).
Of course, your thumbdrive has to know your time zone, otherwise your PC and your wall clock will differ again.
Change on the Windows side is done like this: create this key in the Windows Registry:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]"RealTimeIsUniversal"=dword:00000001
Your Windows system probably will reside on the hard disk. Your JamulusOS stick necessarily needs a big ext2-partition named casper-rw where Jamulus and related programs are created in the .rum step (the 5th one in the new delivery form after April 2, 2021). Unfortunately it is very easy to wreck the persistent partition casper-rw: If you pull the stick when the screen has just gone black after clicking on "shutdown", it most probably will be wrecked, because casper-rw is updated then. Other than a hard disk the USB stick does not make any noise and many USB sticks don't have LEDs any more showing that IO is happening.
Unfortunately the farewell-graphical screen with the rotating thing of JamulusOS comes somewhat after the black screen. Up to 15 seconds of an innocent screen with just a tiny blinking cursor. You might mistakenly take it for "ok, the computer is shut down". You have to wait until it explicitly tells you to remove the start medium and press Enter.
So unfortunately you will use more than one JamulusOS stick over time and if you forget to change them all, you experience "time shift" again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It should be noted that in Windows , some program do not verify how time zone/UTC is set so the few web site I visited suggest that it is better to change Linux than to change Windows.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My Unix days are a few decades old, but I figured if they built a graphic desktop onto it, it may have some functionalities similar to Windows, however different their user behavior are.
I found in the Desktop Menu > Applications > Settings (not Settings Manager) > Time and Date an entry to select time zone. Although mine (America/New York) was already displayed , there was no way to select another ; I don't know if it was already configured and had not "taken" or if this was new. The entry below allows "Manual"/"Keep synchronized with Internet servers" but I tried the synchronized option and a message displays there is no NTP server/service ; you have a choice of "Cancel" or "Install NTP service" but the install does not work, keeps displaying the same message. Maybe this Linux implantation does not have/know how to install / the NTP services (ICMP, other protocols ?)
I rebooted to Windows and the clock was OK. I will try again tomorrow to be sure a day passed does not affect the situation and post result here.
If it works , I would like to suggest to Laurent and Gilgongo to mention the solution* in the JamulusOS documentation and setup info as inadvertently rebooting to a bad date/time throws havoc on scheduled jobs and backups.
*Or at least mention not to forget to set the timezone properly at setup.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok ! I ran the command line in JamulusOS to set Ubuntu to local time and after a couple of alternating booting, it seems to hold !
I will check again tomorrow , to make sure date change does hold too !
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good ! The change seems to hold ! The date and time are correct between multiple boot.
None the less, I advise the developers / maintainers to mention this in the JamulusOS setup documentation .
Hope it helps others .
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Bonjour,
JamulusOS (USB key) allows me to shave a few milliseconds off my sessions compared to my Windows10 setup. I switch OS using the UEFI/BIOS program boot priorities (ASUS motherboard).
However everytime I reboot from JamulusOS to Windows, the system clock is 5 hours later. I'm in Montreal, QC, Canada, so Now = UTC - 5:00. Upon closing, JamulusOS seems to replace the system time Now with the UTC time and date.
Is anybody else having this problem ?
@eleandar is there a solution ?
Thanks for any info.
This topic ist discussed here: https://askubuntu.com/questions/169376/clock-time-is-off-on-dual-boot
Linux supposes the RealTimeClock (RTC) to show UTC. If the computer re-synchronizes time with NTP, Linux also adjusts the RTC. Windows however supposes the RTC to show local time.
The behaviour can be changed either on the Linux side or on the Windows side.
timedatectl set-local-rtc 1the RTC may already have be adjusted and perhaps the next adjustment of the RTC happens after your session is closed! You can reduce the probability that Linux adjusts the RTC after have to crate the directory
~/.config/autostartand put a bash script there with this command (and possibly others you want to rely on like for instance locking the caps lock key).Of course, your thumbdrive has to know your time zone, otherwise your PC and your wall clock will differ again.
Your Windows system probably will reside on the hard disk. Your JamulusOS stick necessarily needs a big ext2-partition named casper-rw where Jamulus and related programs are created in the .rum step (the 5th one in the new delivery form after April 2, 2021). Unfortunately it is very easy to wreck the persistent partition casper-rw: If you pull the stick when the screen has just gone black after clicking on "shutdown", it most probably will be wrecked, because casper-rw is updated then. Other than a hard disk the USB stick does not make any noise and many USB sticks don't have LEDs any more showing that IO is happening.
Unfortunately the farewell-graphical screen with the rotating thing of JamulusOS comes somewhat after the black screen. Up to 15 seconds of an innocent screen with just a tiny blinking cursor. You might mistakenly take it for "ok, the computer is shut down". You have to wait until it explicitly tells you to remove the start medium and press Enter.
So unfortunately you will use more than one JamulusOS stick over time and if you forget to change them all, you experience "time shift" again.
It should be noted that in Windows , some program do not verify how time zone/UTC is set so the few web site I visited suggest that it is better to change Linux than to change Windows.
Yes, I have also experienced this in Vancouver, BC. I'd love to find out how to prevent this.
My Unix days are a few decades old, but I figured if they built a graphic desktop onto it, it may have some functionalities similar to Windows, however different their user behavior are.
I found in the Desktop Menu > Applications > Settings (not Settings Manager) > Time and Date an entry to select time zone. Although mine (America/New York) was already displayed , there was no way to select another ; I don't know if it was already configured and had not "taken" or if this was new. The entry below allows "Manual"/"Keep synchronized with Internet servers" but I tried the synchronized option and a message displays there is no NTP server/service ; you have a choice of "Cancel" or "Install NTP service" but the install does not work, keeps displaying the same message. Maybe this Linux implantation does not have/know how to install / the NTP services (ICMP, other protocols ?)
I rebooted to Windows and the clock was OK. I will try again tomorrow to be sure a day passed does not affect the situation and post result here.
If it works , I would like to suggest to Laurent and Gilgongo to mention the solution* in the JamulusOS documentation and setup info as inadvertently rebooting to a bad date/time throws havoc on scheduled jobs and backups.
*Or at least mention not to forget to set the timezone properly at setup.
Nope ! Rebooting to JamulusOS then to Windows today replayed the same problem !
After some research, it seems that Ubuntu keeps time in UTC while Window keep time in local !
And there does not seem to be a standard to manage this in UEFI/BIOS , which I find strange !!
I will try to force Ubuntu to use local time instead of UTC (recommended) and give feedback here !
Ref.: https://www.howtogeek.com/323390/how-to-fix-windows-and-linux-showing-different-times-when-dual-booting/
Ok ! I ran the command line in JamulusOS to set Ubuntu to local time and after a couple of alternating booting, it seems to hold !
I will check again tomorrow , to make sure date change does hold too !
Good ! The change seems to hold ! The date and time are correct between multiple boot.
None the less, I advise the developers / maintainers to mention this in the JamulusOS setup documentation .
Hope it helps others .