So just a point of note, if i now want to do a fresh install because this device has more power under the hood i may do a docker setup instead of single app, i would download the fresh image and now switch the Tag to the dev branch as the zero branch has now been removed.
I presume the site will be updated on the download page when it’s released official as the board is Arm7 and the current description states not for zero models. So if i want a fresh install now do i pick the ARm7 version and switch tags after initial install?
At best change the Git branch to “dev” already before first boot in dietpi.txt, to skip the doubled update. I did a lot of testing today, so related changes should be fine now. After initial setup, you can change the branch back to beta or master to get an update notification automatically, once a beta/master (stable) release is available.
Ah yes we need to update the info on the download page then. Not sure how to call the old ones then to make things clear, Raspberry Pi Zero 1?
Followed the instructions, using Arm7 version, edit to dev and update, setup went smoothly, overclock profile applied okay, docker and btop running nicely, painless update process cheers
Only thing i noticed which may be correct i don’t know
When setting overclock profile it also entered a setting for core_freq=500
I presume this is meant to go in the overclocking section of config.txt instead it was entered in the Serial/UART section, which may be the correct place but might just be a cosmetic issue as obviously it does not matter where it is.
The wrong settings location will be fixed with new RPi images. On first boot, erroneously an informational comment in the UART section was replaced by a commented setting. This was fixed with DietPi v7.5: https://github.com/MichaIng/DietPi/commit/60ebdf6
But the RPi images are v7.4 and this DietPi-FirstBoot script runs before the update .
The chip of the Rpi Zero 2 is Arm8 , as far i saw…
ARM Cortex-A53
Computer processor
The ARM Cortex-A53 is one of the first two microarchitectures implementing the ARMv8-A 64-bit instruction set designed by ARM Holdings’ Cambridge design centre. The Cortex-A53 is a 2-wide decode superscalar processor, capable of dual-issuing some instructions.
Yep my logic to be fair was the ARMv8 dietpi version is 64bit only, as the unit doesent have oodles of ram and it’s only running a few docker containers the 32bit version was sufficient enough for my use case and is running just fine
I tried to get a fresh install going with the ARMv8 image yesterday, using 2 new Pi zero 2 W’s and an USB to lan adapter.
For both RPI02Ws, after creating the SD card and adjusting the config (including changing the branch to beta), when I booted the RPI02Ws, they didn’t appear on the network .
Given that they’re headless, it’s hard to problem solve.
Is there anything else I can do to ensure this works? (I could of course go for ARMv6 or v7 images, but given that I’m starting from scratch on these, I’d prefer to use the v8 image)
[Just to clarify: I’ve been running 2 DietPi installations on RPI Zero W with USB to LAN adapters for quite a while now, running Pi-Hole and compiled Unbound]
Didn’t need to, I connected a USB to LAN adapter.
The problem lies with the dtb file that is missing in the image (as per the link in my previous post), once I did that, all worked.
Thanks very much for the tip regarding the dtb file. I had the exact same issue with my headless rpi zero 2 w (connect via wifi) and now it is up and running on the 64 bit dietpi image.
So it appears that the Pi Zero 2 W is now available.
When can we expect a release that supports this particular (and slightly different) hardware configuration?
I
DietPi themselves is just a set of bash scripts. We don’t do any kernel development. This is done by the base OS. In your case a Raspberry OS. Means kernel is developed by RPI devs.
Walked in the same “trap”. May be a hint on the download page would be nice
Edit: Download and copy bcm2710-rpi-zero-2.dtb has NOT worked! Only copy and rename the bcm2710-rpi-3-b.dtb file worked for me!