KemoNine

  • Content Count

    5
  • Joined

  • Last visited

About KemoNine

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I ended up deploying monit to track and respond to the clock jump. I ended up telling monit to reboot the system whenever the clock jumps ahead too far to keep some of my services I have deployed happy. At the link below you'll find my monit config file for the time jump as well as a small python script that's run by monit to look for any time jumps over 3 months into the future. You can tune the python script to look for larger jumps as well as the monit config to restart ntp instead of performing a full reboot. https://paste.lollipopcloud.solutions/?4e7e74d941e2c77d#ck/F7Tv6UBadp
  2. I'm also seeing this behavior on a sopine that I recently deployed. It's seemingly inconsistent as well. I checked the kernel config and it appears the CONFIG_FSL_ERRATUM_A008585 is enabled cat /boot/config-4.19.38-sunxi64 | grep -i CONFIG_FSL_ERRATUM_ CONFIG_FSL_ERRATUM_A008585=y And it's a very recent Arbian as well. 4.19.38-sunxi64 #5.83 Short of tracking the date every minute or so in something like Monit to fire off a reboot... does anyone know of a practical work around?
  3. I will dig around and see if I can work on enhancing the 4.x series drivers based on the data sheet as well as longsleeps existing driver. I only glanced over some of the code in the drivers. I understand. I wasn't trying to imply I expected help or a mentor. I was hoping others who know more about the kernel dtb stuff as well as driver dev could nudge me in a direction or two (as you did above). I understand the time scales and I apologize for using too strong of a word. That's a good approach. Would you recommend starting with the drivers an
  4. I've gotten that impression as I've dug into things on the Pine64[+] side. I'm a heavy Orange Pi user and the Pine64's power circuitry related to battery support is compelling for a current build of mine. I've been using Armbian base images for the last ~12 months for Orange Pi boards (of various forms) and finally hit a bit of a wall on my understanding thanks to the 4.x kernels missing dtb things for the Pine64[+]. The Pine64 series has been a thorn in my side since I started working with it. I've spent a lot of time digging into what's going on and it seems the dtb's are missing pieces/part
  5. I'm currently working with Armbian on a Pine64 and it looks like both the 4.14.x kernels and 4.19.x kernels are missing some dtb definitions related to the axp803 powersupply for /sys/class/power_supply to work properly. From what I can tell this thread: https://forum.pine64.org/archive/index.php?thread-1430-1.html Has a bunch of dtb related pieces missing from 4.x kernels Would someone be able to help me decipher the differences and put together a dtb overlay to hopefully sort this out? I'm willing to release the purple smoke (if things go awry)