If you haven’t read part 1 yet, make sure you start there.
Hooray! I am not alone, and it does indeed appear to be a Pine64-specific issue. That means I’m not crazy. Or at least, this issue doesn’t prove my craziness.
Looking at martinayotte‘s suggestions, since he seems to have been through what I’m going through right now…
[email protected]:/boot# grep CONFIG_FSL_ERRATUM_A008585 /boot/config-4.14.26 # CONFIG_FSL_ERRATUM_A008585 is not set
Okay, so just in case they fixed it already, let’s just try…
[email protected]:/boot# apt update && apt upgrade Ign:1 http://deb.debian.org/debian stretch InRelease Hit:2 http://deb.debian.org/debian stretch Release Ign:3 http://download.webmin.com/download/repository sarge InRelease Hit:4 http://download.webmin.com/download/repository sarge Release Ign:5 http://webmin.mirror.somersettechsolutions.co.uk/repository sarge InRelease Hit:7 http://webmin.mirror.somersettechsolutions.co.uk/repository sarge Release Get:8 http://ftp.debian.org/debian stretch-backports InRelease [91.8 kB] Ign:10 https://repo.foxiehost.eu/debian stretch InRelease Ign:11 https://apt.izzysoft.de/ubuntu generic InRelease Err:13 https://apt.izzysoft.de/ubuntu generic Release server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none Err:14 https://repo.foxiehost.eu/debian stretch Release server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none Reading package lists... Done E: Release file for http://ftp.debian.org/debian/dists/stretch-backports/InRelease is expired (invalid since 34744d 15h 16min 5s). Updates for this repository will not be applied. E: The repository 'https://apt.izzysoft.de/ubuntu generic Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'https://repo.foxiehost.eu/debian stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.
Hmm, it seems apt doesn’t like time travelers like me. So … [le gasp]…
[email protected]:/boot# reboot Connection to 10.0.0.155 closed by remote host. Connection to 10.0.0.155 closed.
Wait for it….
[email protected]:~$ ssh [email protected] ssh: connect to host 10.0.0.155 port 22: No route to host
Like trying to play my 8-track cassettes in a Blu-Ray player, apparently some services don’t play nicely 95 years in the future. DHCP is showing locally on the TTY splash screen as 127.0.0.1, and the only way to recover will be to re-flash to a point before the NTP issue struck.
What’s next? Read Part 4: