DietPi
DietPi copied to clipboard
MichaIng
Image | NanoPi Zero2
Creating an image request
NanoPi Zero2 1G~2G
Formal device information
- Device name | NanoPi Zero2
- Official product URL | https://wiki.friendlyelec.com/wiki/index.php/NanoPi_Zero2
- GitHub resource URL (if available) | https://github.com/friendlyarm
- Image download URL | https://drive.google.com/drive/folders/1TbhufnT6NITr35uEvn_UsvnZPx6PbMEL
Is the SBC officially supported by the Debian installer?
- Not sure.
If not, is a reliable 3rd party Debian image available for this SBC?
- Product wiki provide debian bookworm image.
Please add the support. The Zero is also already supported.
nano pi zero 2?
As long as there is no own image, you can use the Debian image from Friendlyelec (rk3528-sd-debian-bookworm-core-6.1-arm64-20241112.img) and turn it into a DietPi system afterwards. (generic device)
https://wiki.friendlyelec.com/wiki/index.php/NanoPi_Zero2#Downloads
This is working on my NanoPi Z2 without issues.
As long as there is no own image, you can use the Debian image from Friendlyelec (rk3528-sd-debian-bookworm-core-6.1-arm64-20241112.img) and turn it into a DietPi system afterwards. (generic device)
https://wiki.friendlyelec.com/wiki/index.php/NanoPi_Zero2#Downloads
This is working on my NanoPi Z2 without issues.
nice, good to know^^
Collaborator
I’m getting error messages when trying to turn it into a DietPi. Do you happen to have a small guide?
I tried it with mentioned Bookworm Image and Generic Device method for DietPi today. It’s not working for me. The NanoPi Zero2 is not reachable by SSH afterwards. IP address is fetched by DHCP.
Don’t have a UART dongle to check the serial console.
I guess the FriendlyELEC image is of this type with 8 (or is it now 9?) partitions, no access to boot or kernel config, and an overlayfs as root filesystem, right?
Yes you are right. It’s 9. A fresh IMG looks like this
/dev/mmcblk0p9: LABEL="userdata" UUID="b97bccf8-5f70-442f-ade9-758c211d01d5" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="userdata" PARTUUID="2d9e7b61-1b31-47e7-ee0d-8cec26d42ef6"
/dev/mmcblk0p8: LABEL="rootfs" UUID="908324b8-1b2e-4704-81ff-185f6f834c10" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="b2af085d-a675-48c6-c437-f6d557ff4744"
/dev/mmcblk0p7: PARTLABEL="recovery" PARTUUID="2bfee623-d83c-426a-ab80-21732c9bb7d3"
/dev/mmcblk0p5: PARTLABEL="kernel" PARTUUID="24eeb649-277f-4c11-ffeb-d9f20027a83b"
/dev/mmcblk0p3: PARTLABEL="dtbo" PARTUUID="43784a32-a03d-4ade-92c6-ede64ff9b794"
/dev/mmcblk0p1: PARTLABEL="uboot" PARTUUID="b750e44e-833f-4a30-c38c-b117241d84d4"
/dev/mmcblk0p6: PARTLABEL="boot" PARTUUID="1cac805f-726a-495a-fd35-821355a6e7e8"
/dev/mmcblk0p4: PARTLABEL="resource" PARTUUID="000b305f-484a-4582-9090-4ad0099d47bd"
/dev/mmcblk0p2: PARTLABEL="misc" PARTUUID="a1c81622-7741-47ad-b846-c6972488d396"
@Joulinar how do you get it to run? Did you choose Dev, Beta or Master release of Generic Installer?
I haven't managed to get it to work so far, tried all three, none worked dev beta master > @Joulinar how do you get it to run? Did you choose Dev, Beta or Master release of Generic Installer?
just tested it again without issues. All default and standard, I used the option Flash Official OS to eMMC to install Debian image to eMMC initially.
I can confirm. It’s working now. I had trouble with the ssh connect to dropbear at the end. Using OpenSSH now and all works. Thanks
An earlier comment that I made that the conversion script ran against rk3528-eflasher-debian-bookworm-core-6.1-arm64-20250211.img on the NanoPi Zero2 had not worked was, in fact, incorrect. The script worked brilliantly- it was just that the IP address had changed.
Still, an official image for the Zero2 would be most welcome.
Yes. Please. An official image for the NanoPi zero2 would be nice 👍
Need this more than ever :(
