Hi,
I hope it’s the right place to post . I updated my RP4 to 9.2.0 and that basically worked well. I thried the same on the RP 5 but that did not work out sofar.
I tried to install Nextcloud on the RP4 , but as you can see from the screenshots it did not work out. Let’s wait for a few more hours and try again.
Hopefully the upgrade for the RP5 will come also. soon
Tks
DietPi version is not released for specific systems. It’s available on all systems at the same time.
Your issue is more related to incorrect system time. Seems to be out of sync by almost a day. You would need to update your system time to be up-to-date. Usually this happens once a day or on reboot (default settings) if not changed.
Btw, latest DietPi version is 9.1
9.2 is with Beta testing.
Tks for yr advise. And yes I know it’s Beta , I just followed the info on my screen " dietpi-update : Run now to update DietPi from v9.1.1 to v9.2.0 " Just curios…
The time issue has been resolved, wonder only why it did not update the time by itself. As it did before always.
As far as the PI5 is concerned : still error
[FAILED] DietPi-Update | Checking IPv4 network connectivity
- Command: ping -4nc 1 -W 10 IP
[ INFO ] DietPi-Update | Executing alternative command: ping -4nc 1 -W 10 192.168.1.47
PING 192.168.1.47 (192.168.1.47) 56(84) bytes of data.
From 192.168.1.25 icmp_seq=1 Destination Host Unreachable
--- 192.168.1.47 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
┌──────────────────────────────────────────────────┤ DietPi-Config ├───────────────────────────────────────────────────┐
│ Please select an option to change: │
│ │
│ ●─ Adapter Options ─────────────● │
│ Ethernet : Available | [On] | Connected │
│ WiFi : Not Found | [On] | Disconnected │
│ Onboard WiFi : [Off] │
│ ●─ Additional Options ──────────● │
│ IPv6 : [On] │
│ Proxy : [Off] │
│ Test : [Success] | Online │
│ │
│ │
│ <Ok> <Back> │
│ │
└──────────────────────────────────────────────────────
I checked connectivity before and after upgrade attempt
Tks
what IP your system is trying to ping to?
Hi,
to be honest I have no clue . The IP range assigned by the router is separated as follows :
192.168.1.1 → 1.50 for static IP’s from 1.51 → 1.120 for DHCP.
Nothing has been assigned to 192.168.1.47
can you run following
G_CHECK_NET
Does it succeed?
Hi,
pls see result :
can you check following.
cat /boot/dietpi.txt | grep CONFIG_CHECK_CONNECTION_IP
Hi,
surprise …
root@DietPi:~# cat /boot/dietpi.txt | grep CONFIG_CHECK_CONNECTION_IP
CONFIG_CHECK_CONNECTION_IP=192.168.1.47
CONFIG_CHECK_CONNECTION_IPV6=2620:fe::fe
root@DietPi:~#
did you adjust this yoursefl? Because it’s not our default value?
Hi,
def. not by me .
How can I change it to the desired value ?
The file dietpi.txt in /boot/ has the odd IP entry
in /boot/firmware/ it’s the original version with 9.9.9.9
So just copy the original over the copy ?
mysterious
This should do it
G_CONFIG_INJECT 'CONFIG_CHECK_CONNECTION_IP=' 'CONFIG_CHECK_CONNECTION_IP=9.9.9.9' /boot/dietpi.txt
G_CHECK_NET
Tks , all done and now upgrade worked as desired
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.