Dietpi 6.17 image for Orange Pi Zero H2+

[twilight]

As some may already know/aware of, recently some devices were dropped from being offered a direct DietPi image download, simply because the PREP script now supports a lot of devices. And for good reason because this eases of maintenance from developers.

So I 've built my own instead using Armbian Stretch, then cloned it in an image file, added missing xr819 firmware, shrunk it with this script, then uploaded into my dropbox:

https://www.dropbox.com/s/jzf6eld3j3gb3 ... 17.7z?dl=0

MD5 checksum included.

[WarHawk]

Most awesome!! Thanks!

Nice so the copying of the xr819 to the firmware allowed the drivers to be modprobed into the kernel...sweet!

The images I did were using armbian installs...then run the Prep script from github

I think a debian port would be nice too

Great job!

[twilight]

The images I did were using armbian installs...then run the Prep script from github

I think a debian port would be nice too

That's exactly what I 've done, too. But there are some drawbacks compared to the original Dietpi image offered.

There is no FAT32 partition (afaik) to configure various stuff including the kernel parameters and the DietPi first-time txt file for starting a session exclusively from wireless connection.

Also, I don't think original Debian would be too different, for me it might be reduntant to have one built.

[WarHawk]

Right...I still say with the fat32 boot partition it's easier to do a scan of a corrupted partition in case of accidental reboot...
Otherwise I have to pull the card..stick in a working linux machine, then do a gparted scan on it...then boot again.

I would use a linux machine to do any editing of the non fat32 partitioned armbian builds...but not everyone has an old crusty laptop running linux on it...

I had/found a script from an older Smoothwall 2.0 (when I was a developer from a LOOOOOOONG time ago) build that would detect an issue and then start a scan on the OS partition...so even if it was corrupt it would scan it, then reboot and it would always come up

This was under /etc/rc.sysinit on the old smoothwall...

Code: Select all

STRING="Checking root filesystem"

fsck -R -T -a -C /
RC=$?  

if [ "$RC" = "0" ]; then
	echo "$STRING: Success"
elif [ "$RC" = "1" ]; then
	echo "$STRING: Passed"
fi

# A return of 2 or higher means there were serious problems.
if [ $RC -gt 1 ]; then
    export PS1="(Repair filesystem) \# # "
    if [ $RC -lt 4 ]; then
        echo "$STRING: Repaired."
        echo "*** Reboot required. The system will reboot in 30seconds."
        sulogin -t 30
    else
        echo "$STRING: Failed"
        echo "*** An error occurred during the file system check."
        echo "*** Dropping you to a shell; the system will reboot"
        echo "*** when you leave the shell."
        sulogin
    fi
    echo "Unmounting filesystems"
    umount -a
    mount -n -o remount,ro /
    echo "Automatic reboot in progress."
    reboot -f
fi


echo "Mounting root read/write"
mount -n -o remount,rw /
echo "Clearing mtab"
>/etc/mtab
echo "Marking root as mounted"
mount -f /

STRING="Checking other filesystems"
fsck -R -T -a -C -A
RC=$?  

if [ "$RC" = "0" ]; then
        echo "$STRING: Success"
elif [ "$RC" = "1" ]; then
        echo "$STRING: Passed"
fi
  
# A return of 2 or higher means there were serious problems.
if [ $RC -gt 1 ]; then
        echo "$STRING: Failed"
        echo "*** An error occurred during the file system check."
  	echo "*** Dropping you to a shell; the system will reboot"
  	echo "*** when you leave the shell."
  	export PS1="(Repair filesystem) \# # "
  	sulogin
  	echo "Unmounting filesystems"
  	umount -a
  	mount -n -o remount,ro /
	echo "Automatic reboot in progress."
  	reboot -f
fi

but not sure how useful it would be for our dev guys to do something like this...who knows if it will help

You wouldn't have "stock" debian images for the other Orange pi hardware would you?