uzair

Members
  • Content Count

    3
  • Joined

  • Last visited

  1. @gprovost Yes! That solved the problem. Thanks.
  2. @gprovost This is what I get: root@helios4:~# date Tue Apr 23 10:38:43 CEST 2019 root@helios4:~# hwclock -r 2019-04-23 10:38:47.165966+0200 @aprayoga That's the whole point. I've been checking logs, uninstalling plugins and stopping services to find out what event causes the system to reboot but from what I've seen there doesn't seem to be anything that's logged anywhere that says "Hey I'm causing the reboot", atleast from my perspective. I executed the 2 lines you mentioned and this is what I got from the serial interface: I've used OMV's standby mode, in RTCwake Standby - ACPI state S1 and Suspend-to-RAM - ACPI state S3, autoshutdown's suspend and systemctl suspend in the CLI. All have the same problem. I can send the syslog, boot, daemon and authorization logs if that's helpful.
  3. Hi, I seem to have a problem with my batch 2 Helios4 that I'm unable to figure out why it happens. every time I put it in standby mode, it does not stay in standby but restarts after approx. a minute. I've tested it with 2 different SD-cards, one with a clean install. During the standby I also tested it with disconnecting the network cable, so it seems the it's an internal trigger or crash which makes the Helios4 restart. I'm using the latest Armbian version: 5.77 and kernel 4.14.106. One thing I've noticed is that the system time is always incorrect after the forced restart. after a normal restart the time is correct. Could it be related? I don't know, I'm out of ideas and it's driving me crazy for the last few days. Hope you guys can help.