Anyone else had issues with the latest Raspberry Pi image of DietPi?
I was trying to check up on the issues reported in the thread concerning Audiophonics i-Sabre DAC and its non-latching power button.
I didn’t get that far… My Raspberry Pi 2B which is contained in the RaspDAC LTE chassi cannot initialize itself as it cannot get in touch with the NTPD (Time-server). I tried different time servers, none gives any response and i am stuck in a loop.
It does however perform all the necessary connection checks with dietpi.com etc. And i can continue the setup using manual override…
I had the same problem on the weekend when I went to check for updates. I just gave up for the time being and was going to look at it again on the weekend.
Well, i just thought i’d update my Tinkerboard so i retrieved the latest DietPi image and etched it to a microSD. The NPTD issues are still here, no way of getting in touch with any NTP server for me. However the behaviour with the Tinkerboard is a bit different? Maybe @Dan_Knight did some changes? Here the Override option is directly available in the NTP dialogue. Seems to have a lot of errors during initialization also.
Issues with locales also, just like in the Raspberry image… Defaulting to british i think.
The install/upgrades seem to complete successfully though, and the Tinkerboard reboots after getting up to 6.6.
A lot of these it seems?:
After the previous message about the non-trusted cert, your command gives this reply:
root@DietPi:~# apt-get install debian-archive-keyring -y
Reading package lists… Done
Building dependency tree
Reading state information… Done
debian-archive-keyring is already the newest version (2017.5).
debian-archive-keyring set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@DietPi:~#
And it worked just fine? Didn’t expect that… But after the required reboot after getting up to date:
(This is my NanoPi NEO2)
It seems i CAN get on with my install after all…
Edit:
It looks like the connection issues were related to the previous NPTD problems.They are evident here too, but after setting locale, time zone and setting date and time it works!