DietPi OS for ROCK64
#1
[Image: dietpi-logo_192x192.png]

DietPi is an extremely lightweight Debian-based OS. It is highly optimised for minimal CPU and RAM resource usage, ensuring your ROCK64 always runs at its maximum potential.

Use dietpi-software to quick and easy install Ready to Run & Optimised applications for your system. DietPi will do all the necessary configurations, including starting the services.

DietPi images are available for PINE A64PINE H64PinebookROCK64 and ROCKPro64.

Our PINE64 images are based on the great kernel and firmware, developed by Armbian. However, if you face any issues, please contact us via forum or GitHub issue first.

Website: https://dietpi.com/
Download images: https://dietpi.com/#download
Documentation: https://dietpi.com/docs/
Forums: https://dietpi.com/phpbb/
GitHub repository: https://github.com/MichaIng/DietPi

DietPi is a free and open-source project. We are be happy if you consider to:
  Reply
#2
Hi MichaIng!

This looks awesome! I have some questions if you don't mind:

1. It mentions "minimal CPU and RAM resource usage", care to put some numbers on it?

2. Regarding packages, does this use the debian aptitude packages?

3. Is the "ZeroPi" compatible with the Orange Pi Zero? It seems like it from the specs, but it's not too clear.

4. You support the PineBook that runs on the A64, do you also support the PineTab? I believe the PineTab is very similar to the PinePhone hardware wise, so if you support one then you would support the other (in theory).

5. Can you provide screenshot of the "simple interface" you provide? I've got no idea what to expect... Is that running on top of X, or is this a terminal only setup?
  Reply
#3
@Michalng if you haven't already, feel free to add the info/links for the devices' Software Release wiki pages.
  Reply
#4
@barray

Many thanks for your kind feedback. Let me answer to your questions in a different order, I'll try to tie those into the first post as well:

DietPi uses the regular Debian APT repositories, which I think you mean by "aptitude packages". The aptitude package is not installed by default, but can be with the apt commands, if preferred: apt update; apt install aptitude

Our images come with a very minimal set of pre-installed packages, i.e. the essential system packages (apt, util-linux, kernel, firmware, init system of course, ...) and a small set of additional packages we find important enough, e.g. OOTB SSH and WiFi support, most archive types, keyboard, time zone and localisation. Here is a list, below that kernel, firmware and WiFi-related packages: https://github.com/MichaIng/DietPi/blob/...#L681-L712
Those pull dependencies of course, but if you run apt-mark showmanual in DietPi and a fresh Debian (minimal), Armbian (non-desktop image) or Raspbian Lite, you'll notice the difference. This influences the amount of background processes and hence the RAM usaged by a fresh DietPi, which is around 25-30 MiB and 9 background services (check via htop) when connecting via local console.

So the approach is to start very minimal but making it easy to install additional software on demand, especially such which cannot be installed simply via apt but require 3rd party repositories, runtime systems or custom source builds. The scripts we use (including configuration scripts, drive management, backup and much more) are slim bash scripts which do in sum not take more than 1.3 MiB space. They are based on whiptail dialogues, so run in console without an X server or similar required. Here you get an impression: https://dietpi.com/docs/dietpi_tools/
But a desktop of course is easy to install as well Wink.

I'm also not sure about the compatibility of the images you mentioned. If the SoC and the RAM type matches, it should boot, but the device tree to access all hardware features might differ. Aside of simply testing it, another approach is to install either a fresh Armbian or Debian (at least with Bullseye a large set of SBCs is supported OOTB by the installer) and run our image preparation script on it: https://dietpi.com/docs/dietpi_sbc/#make...stribution
OrangePi Zero is still in the list, otherwise "Generic device" should work. Kernel packages are detected and kept automatically.
In case of PineTab and especially PinePhone, we definitely need to rework a few things to assure that on first boot the dialogues work with touch input. From all I know, with whiptail this does not work and also text is much too small for phones Wink. But I think especially the PinePhone was an awesome step to kickstart/boost the Linux smartphone community and potentially create alternatives for Android. Awesome how many distributors quickly released compatible versions for the PinePhone. We are a very small team with lets say 1.5 actual code developers, so it is not easily possible for us without loosing to much time on the SBC support and development we came from.

@tophneal
I'll do that, I already wanted to, but my wiki account got broken. NB: Do not change "Preferences" > "Appearance" > "Skin", otherwise => HTTP error 500 Big Grin. But it got sorted by great help on discord already.
  Reply
#5
@Michalng Thank you for your reply!

> In case of PineTab and especially PinePhone, we definitely need to rework a few things to assure that on first boot the dialogues work with touch input.

I think it would be a reasonable requirement for a non-GUI setup to require a USB keyboard.

> We are a very small team with lets say 1.5 actual code developers, so it is not easily possible for us without loosing to much time on the SBC support and development we came from.

Fair enough, your work is still highly appreciated Smile
  Reply
#6
(12-16-2020, 10:32 AM)barray Wrote: I think it would be a reasonable requirement for a non-GUI setup to require a USB keyboard.
In theory, shells can take touch input, when related drivers are installed. I never had a closer look, but htop takes mouse input, so it should not be difficult to make it recognise touch input as well. GPM could be a start: https://ostechnix.com/how-to-configure-m...-consoles/
Since console-setup is already pre-installed, we can adjust font size to be nicely readable on small screens and reduce our banner sizes a bid. Our console dialogue functions are abstracted already, hence what we then need is a touch-capable replacement for whiptail, or writing one ourselves, when we know how to enable mouse/touch input. I guess many of our menus and texts are too wide/long to display nicely at small screens without scrolling but that is a minor thing. Generally an aim is that our images come with everything that is needed to boot and configure every type of device without any additional hardware or peripheral needs, which is why WiFi support (pre-configurable via config file before first boot) and SSH is always pre-installed. So at least from my end, it shall be possible to use the native capabilities of a smartphone (respectively tablet) to set everything else up, before we ship an image.

@tophneal
Little question: After creating my account, I created three threads, before running into the new users limit, on Pinebook, PINE A64 and here. Yesterday the last two at PINE H64 and ROCKPro64 sub forums. While the last two are published already, the two in Pinebook and PINE A64 are not (yet). Are they still in a moderators review query or did I do something stupid that they are lost? I would re-create them but don't want to mess up with doubled threads Wink.
  Reply
#7
@MichaIng just took a look. I think someone may have accidentally deleted those posts in the mod queue. I'm restoring and pinning them now.  All posts are pinned, and the missing 2 have been restored+pinned.
  Reply
#8
I ordered this Rock64 from Amazon:
[color=var(--newCommunityTheme-linkText)]https://www.amazon.com/dp/B0868WSTXH?psc...asin_title[/color]

It is working fine using this image:
[color=var(--newCommunityTheme-linkText)][b]bionic-minimal-rock64-0.9.14-1159-arm64.img.xz[/b][/color]


But for whatever reason I cannot get dietpi boot. I much prefer dietpi if possible. Tried both dietpi versions from here and the below source, and neither booted:
[color=var(--newCommunityTheme-linkText)]https://wiki.pine64.org/wiki/ROCK64[/color]


[color=var(--newCommunityTheme-linkText)]Any ideas?[/color]
  Reply
#9
Which version of the Rock64 did you receive. V2 or V3.
  Reply
#10
@tophneal
Many thanks for restoring the threads!

@sr_guy
I updated the ROCK64 image on December 16 and the Wiki page on December 17 midday to point to that same image. That one failed on your board or did you probably use the older one? If it was the new image, could you go a bid more into detail on which boot step it fails, e.g. do you see any output on screen (or serial console, if attached)?
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) mara 110 47,639 02-28-2021, 01:52 PM
Last Post: Enig123
  openwrt for the rock64 wilsonYan 10 3,542 02-13-2021, 09:04 PM
Last Post: wilsonYan
  Linux Images (ROCK64) pineadmin 164 131,590 02-12-2021, 10:14 AM
Last Post: useful64
  Armbian for Rock64 pineadmin 26 16,179 12-25-2020, 11:07 PM
Last Post: lanefu
  RETRO-GAMING: UPDATED RELEASE OF RECALBOX FOR THE ROCK64 Mrfixit2001 31 19,561 12-21-2020, 08:17 AM
Last Post: hermes73
  RetroPie on Rock64 Luke 40 24,482 10-31-2020, 07:12 AM
Last Post: BigSkyEntertainment
  Lakka (retrogaming) os for rock64 Wizardknight 2 1,109 09-21-2020, 07:18 PM
Last Post: Wizardknight
  Debian (Vanilla) on Rock64 and eMMC - how ? as365n4 4 1,709 09-21-2020, 04:33 AM
Last Post: as365n4
Sad Rock64 crash randomly during usb 3 copy with RAID1 drive phalae 24 16,045 09-14-2020, 10:48 AM
Last Post: BrownLuther007
  Arch Linux ARM on the Rock64 V3 justinweiss 2 1,582 08-24-2020, 05:16 PM
Last Post: justinweiss

Forum Jump:


Users browsing this thread: 1 Guest(s)