MichaIng
MichaIng
Many thanks for your report. Obviously the hourly time sync fails in your case. To check what's going on with that: ``` journalctl -u systemd-timesyncd ```
You sync time with your router at `192.168.0.2` and that seems to do it's job extremely bad. The time sync runs every hour at `:17` minutes system time correctly, but...
`timedatectl set-ntp true` should basically do `systemctl enable --now systemd-timesyncd`. However, with time sync mode 2 or 3 enabled, on each day or hour respectively, the service is restarted and...
Okay, that is a good reason. I run `schedutil` on all my devices, including RPi's and never saw something like this, but you can simply try to switch to performance...
Very interesting that reducing minimum frequency works in your case. Actually `arm_freq_min` currently should have no effect at all (it has none on my RPi2), as it caused completely handing...
That is a good finding. Could you try to combine 100 MHz with 0 overvoltage? That worked for me on RPi2 with the last kernel that supported it at all...
Indeed looks like the same.
Thanks for reporting. This is already the second report lately, probably something changed with a recent kernel upgrade on RPi 4 so that 300 MHz is causing such issue now...
Closing it here, investigation is done upstream: https://github.com/blakeblackshear/frigate/issues/3780
Many thanks for your report. ``` Job [email protected]/start failed with result 'dependency' ``` Can you show the output of: ```sh systemctl cat gpsdctl@ttyACM0 ```