Fedora KDE 43 - Installation feedback

Ask Fedora
, ,
1
  • Date/time is incorrect. Timezone is the expected one, though. The current time on the system tray and on the installer are different, and both are very wrong; neither the hour nor the minute match the current time, and it’s behind by many hours. I didn’t pay attention to the date…
  • Installation summary at the end: The word “format” is used for the ESP partition even if it’s not really formatting the partition — it’s reusing an existing one. Another user has mentioned it here.
2

I’ve seen that for years and even earlier today :stuck_out_tongue:

  • Usually I reset CMOS before OS installs, so I get the factory BIOS date in RTC
  • Booting from Windows is local vs utc
  • In all cases the time/date usually flips correct in a minute with NTP sync
  • Iirc I saw GNOME’s top bar, GNOME Settings, and timedatectl all report something different before the NTP sync (everything syncs up eventually a short time post-install)
1 Like
3

Best practice is to set the bios date and time to utc.
If you dual book with Windows config windows to know thw bios clock is in utc.
Then use the timedatectl command to tell fedora the rtc is in utc.

Now you should find no odd times are displayed.

1 Like
4

It doesn’t help that Fedora defaults to localtime for the RTC when it detects a Windows installation. I always have to change it back to UTC after the installation.

I did not know that Windows could be configured to use UTC. I just found this Arch wiki page explaining how, and I’ll surely try that later. All this time I’ve been using a scheduled task to sync the Windows time on startup, but it’s not very reliable.

Thanks!

5

I raised a bug on this, asking for an option where the user can override Anaconda’s guess and specify whether the RTC is in localtime or UTC.

1 Like
6

Windows knows how to do NTP out-of-the-box so that security protocols work. But maybe does not work if the time is too far out from correct, whoch your script would have fixed I’m guessing.

7

I run this on any fresh install to check:

timedatectl 'set-ntp' 'true' && sudo hwclock --systohc && timedatectl status

And set it (0 if timedatectl mentions not UTC, or 1 dual-boot or Windows expected):

sudo timedatectl set-local-rtc '0'

I go between Windows and Linux a lot but haven’t had to mess with set-local-rtc in years (I usually single-OS and start with wiped drive/no Windows detected)

8

Here is the info from Arch docs on how to set the Windows time to UTC.

You can do this from an Administrator Command Prompt running:

C:\>reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation" /v RealTimeIsUniversal /d 1 /t REG_DWORD /f

I run all my dual boot Windows desktop this way and time just-works.

9

That’s what I’m using now, and it seems to work! :grinning_face:

I’ve exported the registry change as a file named rtc-to-utc.reg, so I can easily apply it when reinstalling.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
"RealTimeIsUniversal"=dword:00000001

Thanks, everyone.

1 Like