I have a dual-boot setup, so I wanted to fix the issue of Windows time being wrong once booting back in after using Linux.
Since I really didn’t want to give up on using Windows Time service syncronization, I decided to set RTC to local on EndeavourOS as it seemed the easiest.
But once done that my Logitech G502 turns off after GRUB and is no longer detected in the system. Setting the RTC back to use UTC fixes the issue.
In the end I do can set up Windows to use UTC RTC and just use an external application for time syncing, but I am really curious why setting rtc to local on EndeavourOS breaks the mouse detection.
I’ve read on a thread in AskUbuntu that without disabling it Windows will be writing local time to rtc on shutdown regardless of the setting, so I was worried Windows might now overcompensate the hour other way around after restart (since linux seems to sync just fine no matter what time Windows writes to the rtc), but you might be right that I am just worrying in advance before testing it. I’ll set up UTC in Windows next time I log onto it and let you know if in fact I didn’t had to worry about disabling the time service at all.
When I still had Windows with Linux (then Fedora) in a dual boot, I used time-snyc to get the correct time in Windows. Maybe you can have a look at the program.
Yep, in fact, my Windows was overcompensating for the UTC–Local time difference on restart after saving local time to rtc on shutdown, so I disabled the time service and downloaded a third-party tool. I don’t know why I have such problems on this machine, as it seems my brother never faced similar issue on his laptop with dual boot despite his Fedora and Windows using different rtc settings, so it looks like it’s kind of hardware related?
@shadow359 thanks, I’ve already downloaded NetTime and it seems to work great from the get-go, so I’ll just stick to it unless I experience some problems with it in the future.
In the end I am still surprised why setting local rtc on linux killed the mouse on booting the kernel, but I guess I’ll just accept it as yet another quirk of my already-a-bit-old hw setup