It's now 2'nd or 3rd time my PP CE boots up woth a date in year 2115 (why 2115)
The cure is to do a : hwclock -s
So the hwclock is correct , but the sysclock is waaaayy off.
If this wasn't a battery device NTP would be the solution , but here a hwclock -s seems to be the fix
I'm on "latest" apt-get update/upgrade as of today 2020-07-15
Fresh ssh after reboot
mobian@mobian:~$ date
Fri Sep 6 23:43:51 CEST 2115
mobian@mobian:~$ sudo -i
[sudo] password for mobian:
root@mobian:~#
root@mobian:~# hwclock -s
root@mobian:~# date
Wed Jul 15 17:43:51 CEST 2020
root@mobian:~#
root@mobian:~# uname -a
Linux mobian 5.7-pinephone #5.7.0+pinephone8 SMP PREEMPT Sun Jul 12 18:21:59 CEST 2020 aarch64 GNU/Linux
root@mobian:~#
/Bingo
OOpzz
Might be a bit fast (in being on the latest)
I did an apt update just before reboot , it "barfed" at me.
I did an apt-get update + upgrade , and it installed a few things.
Then i discovered the date was wrong, and wrote the above.
But now
apt update shows 70 packages can be upgraded
Will do them asap
But the hwclock -s might not be fixed ... Anyone ?
/Bingo
Well that took a few reboots
I still have 4 packages held back, even w. dist-upgrade
Any hints ??
root@mobian:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
mobian-base mobian-phosh-base mobian-phosh-games mobian-phosh-phone
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
root@mobian:~# uname -a
Linux mobian 5.7-pinephone #5.7.0+pinephone8 SMP PREEMPT Sun Jul 12 18:21:59 CEST 2020 aarch64 GNU/Linux
root@mobian:~#
Are they held back because of unstable ??
root@mobian:~# apt list --upgradable
Listing... Done
mobian-base/unstable,unstable,unstable 0.1.7 all [upgradable from: 0.1.5]
mobian-phosh-base/unstable,unstable,unstable 0.1.7 all [upgradable from: 0.1.5]
mobian-phosh-games/unstable,unstable,unstable 0.1.7 all [upgradable from: 0.1.5]
mobian-phosh-phone/unstable,unstable,unstable 0.1.7 all [upgradable from: 0.1.5]
/Bingo
The cure is to do a : hwclock -s
So the hwclock is correct , but the sysclock is waaaayy off.
If this wasn't a battery device NTP would be the solution , but here a hwclock -s seems to be the fix
I'm on "latest" apt-get update/upgrade as of today 2020-07-15
Fresh ssh after reboot
mobian@mobian:~$ date
Fri Sep 6 23:43:51 CEST 2115
mobian@mobian:~$ sudo -i
[sudo] password for mobian:
root@mobian:~#
root@mobian:~# hwclock -s
root@mobian:~# date
Wed Jul 15 17:43:51 CEST 2020
root@mobian:~#
root@mobian:~# uname -a
Linux mobian 5.7-pinephone #5.7.0+pinephone8 SMP PREEMPT Sun Jul 12 18:21:59 CEST 2020 aarch64 GNU/Linux
root@mobian:~#
/Bingo
OOpzz
Might be a bit fast (in being on the latest)
I did an apt update just before reboot , it "barfed" at me.
I did an apt-get update + upgrade , and it installed a few things.
Then i discovered the date was wrong, and wrote the above.
But now
apt update shows 70 packages can be upgraded
Will do them asap
But the hwclock -s might not be fixed ... Anyone ?
/Bingo
Well that took a few reboots
I still have 4 packages held back, even w. dist-upgrade
Any hints ??
root@mobian:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
mobian-base mobian-phosh-base mobian-phosh-games mobian-phosh-phone
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
root@mobian:~# uname -a
Linux mobian 5.7-pinephone #5.7.0+pinephone8 SMP PREEMPT Sun Jul 12 18:21:59 CEST 2020 aarch64 GNU/Linux
root@mobian:~#
Are they held back because of unstable ??
root@mobian:~# apt list --upgradable
Listing... Done
mobian-base/unstable,unstable,unstable 0.1.7 all [upgradable from: 0.1.5]
mobian-phosh-base/unstable,unstable,unstable 0.1.7 all [upgradable from: 0.1.5]
mobian-phosh-games/unstable,unstable,unstable 0.1.7 all [upgradable from: 0.1.5]
mobian-phosh-phone/unstable,unstable,unstable 0.1.7 all [upgradable from: 0.1.5]
/Bingo