StefanH.

Members
  • Content Count

    6
  • Joined

  • Last visited

About StefanH.

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. After I set the CPU speed as described above the issue never came back
  2. wow, I wasn't notified about all the replies here since I posted in May 2019. Unfortunately the problem has now occured 3 times since April. I have gone through all the dist-upgrades but the issue still persists. This is soooo annoying as I run my home automation system on the Orange Pi. The WAF is going dramatically down :-( Will try the CPU speed setting as well, but usually it takes a few months for the issue to re-appear on my side
  3. hi, I found this topic by searching for "armbian 1978". out of the sudden my OrangePi Plus 2E was set to 1978 and the system was unusuable. couldn't ssh into it and even at the local console the screen/monitor didn't show anything but black screen. So I was forced to hard-reboot it. The only thing I noticed was this email from cron daemon: /etc/cron.hourly/fake-hwclock: Time travel detected! fake-hwclock release date is in the future: 2016-04-15 00:00:00 Current system time: 1978-05-27 23:17:02 To force the saved system clock backwards in time anyway, use "force" Is this a known bug?
  4. I've upgraded as well (apt-get update / upgrade). Was running on old 5.38 Now /etc/armbian-release points now to 5.73 although dpkg -l lists packages like: ii linux-image-sun8i 5.75 armhf Linux kernel, version 3.4.113-sun8i reboot (especially systemd-tmpfiles-setup.service) worked fine and services like SSH were started successfully. The official documentation states that the systemd bug was solved in 5.74 https://docs.armbian.com/Release_Changelog/ Once more, thanks!
  5. @thexman thanks a lot for your downgrade instruction! you saved me hours of trial and error!!! btw: you wrote earlier that you upgraded to the new kernel but then downgraded again. is this still the current situation or did you overcome all issues you had with the next kernel?