The new Raspberry Pi 4

General Discussion
21

Here you go (I’ve the 2GB Version of the Rpi4:

│ Benchmarks completed:                                                                             │
   │  - CPU Performance : Duration = 44.87 seconds (lower is faster)                                   │
   │  - CPU Temp        : Idle = 71'c | Full load = 74'c                                               │
   │  - RootFS          : Write = 13 MiB/s | Read = 33 MiB/s                                           │
   │  - RAM             : Write = 81 MiB/s | Read = 154 MiB/s

and with sdram_freq=3200:

 Benchmarks completed:                                                                             │
   │  - CPU Performance : Duration = 44.38 seconds (lower is faster)                                   │
   │  - CPU Temp        : Idle = 73'c | Full load = 74'c                                               │
   │  - RootFS          : Write = 11 MiB/s | Read = 33 MiB/s                                           │
   │  - RAM             : Write = 80 MiB/s | Read = 156 MiB/s

I’m guessing the reason my results are much lower than other’s is because my idle temp is very high. I’m not really sure why that is, I only have passive cooling though and no heatsink but one is in the mail and so is a 40mm fan which should really help.

EDIT: For anyone wondering wtf is causing the temps. I’m still a little confused myself as this is all I have running on the device:

[ SUB2 ] DietPi-Services > start
[  OK  ] DietPi-Services | start : fail2ban
[  OK  ] DietPi-Services | start : nmbd
[  OK  ] DietPi-Services | start : smbd
[  OK  ] DietPi-Services | start : php7.3-fpm
[  OK  ] DietPi-Services | start : lighttpd
[  OK  ] DietPi-Services | start : qbittorrent
[  OK  ] DietPi-Services | start : rpimonitor
[  OK  ] DietPi-Services | start : cron

Still trying to work out how to get Wireguard to cover the whole device or just qBittorrent.

22

wow! Mine are way off, I thought they were low but now that I see others it’s apparently worst. IIRC there should be no thermal throttling at this temp.

 Benchmarks completed:  
   │  - CPU Performance : Duration = 22.15 seconds (lower is faster)
   │  - CPU Temp        : Idle = 63'c | Full load = 67'c 
   │  - RootFS          : Write = 6 MiB/s | Read = 40 MiB/s
   │  - RAM             : Write = 171 MiB/s | Read = 353 MiB/s

huh,

DietPi:~ $ sudo vcgencmd get_config sdram_freq
sdram_freq=0




DietPi:~ $ sudo vcgencmd get_config int
arm_freq=1500
audio_pwm_mode=514
config_hdmi_boost=5
core_freq=500
core_freq_min=250
disable_commandline_tags=2
disable_l2cache=1
disable_overscan=1
disable_splash=1
display_lcd_rotate=-1
enable_gic=1
force_eeprom_read=1
force_pwm_open=1
framebuffer_depth=16
framebuffer_ignore_alpha=1
framebuffer_swap=1
gpu_freq=500
gpu_freq_min=500
init_uart_clock=0x2dc6c00
lcd_framerate=60
pause_burst_frames=1
program_serial_random=1
temp_limit=65
hdmi_force_cec_address:0=65535
hdmi_force_cec_address:1=65535
hdmi_pixel_freq_limit:0=0x11e1a300
hdmi_pixel_freq_limit:1=0x11e1a300
23

derders

That’s weird. I have the same SD-card but 32 GB only. You’re getting a lot better speeds than I do!

24

I do not know if it is relevant, but I read that 32GB is an U1 and 64GB + 128GB are U3 cards

I get this on Windows with my Trancend TS-RDF5 adapter on USB 3.0

25

Benchmarks completed:
CPU Performance : Duration = 8.54 seconds (lower is faster)
CPU Temp : Idle = 47’c | Full load = 54’c
RootFS : Write = 31 MiB/s | Read = 40 MiB/s
RAM : Write = 357 MiB/s | Read = 677 MiB/s


Using Sandisc Extreme 64g A2 card SDSQXA2-064G-GN6MA It was the fastest card I tried.

https://www.amazon.com/SanDisk-Extreme-microSD-UHS-I-Adapter/dp/B07FCMBLV6/ref=sr_1_1?gclid=CjwKCAjwyqTqBRAyEiwA8K_4O5gla5CpFH8A3VHZ9pAAPvt6zcSNJV3ekQYMiztLg1cRSzRydJWHOhoCQcwQAvD_BwE&hvadid=294879052296&hvdev=c&hvlocphy=9033325&hvnetw=g&hvpos=1t1&hvqmt=e&hvrand=18245015659191297424&hvtargid=aud-646675773986%3Akwd-489883584196&hydadcr=18008_9429944&keywords=sdsqxa2-064g-gn6ma&qid=1565098422&s=gateway&sr=8-1

I also have the heatsink aluminum case as well - https://www.ebay.com/itm/264378837329

26

Well I got a Noctua NF-A4x10 5V Fan which runs very quickly and kinda loud (~4500 rpm). Also I am sure that the fans are spinning in the wrong direction but the device has some ‘polarity protection’ that is meant to prevent the fans being plugged in the wrong way. So I dunno. I did see people on Youtube having them spin both ways but I cbf’ed trying to investigate further.

NB! I don’t really recommend this fan even though it cut my temps by 32C because it comes with a 3 pin connector, which needs to be plugged into a 2pin that it also comes with, so it can fit on (and doesn’t break) the GPIO pins it needs to be plugged into. Leaving you with a ridiculously long amount of cable left that doesn’t fit in ANY case what-so-ever so I had to break a hole in my case to let the cable out as there was no way I could force it all inside. I realise could cut the cable off, put a much shorter one on and put a plug on the end but I’d rather not.

Anyway my temps have gone from about 72C before, now to as low as 36C but absolutely no higher than 39C at idle.

So here are my new results, note that they are leagues better than before.
I’ve now got the lowest temps, second fastest rootfs speed here tested and second fastest RAM. I’m starting to think that the 2GB Pi has 15% slower RAM speed than the 4GB. At least from these benchmarks it seems that way.

Results:

┌─────────────────────────────────────────────────┤ DietPi-Benchmark ├─────────────────────────────────────────────────┐
│                                                                                                                      │
│ Benchmarks completed:                                                                                                │
│  - CPU Performance : Duration = 8.93 seconds (lower is faster)                                                       │
│  - CPU Temp        : Idle = 38'c | Full load = 47'c                                                                  │
│  - RootFS          : Write = 25 MiB/s | Read = 34 MiB/s                                                              │
│  - RAM             : Write = 361 MiB/s | Read = 656 MiB/s                                                            │
│                                                                                                                      │
│ Compare these results online with other users, using the link below:                                                 │
│  - https://dietpi.com/survey#benchmark                                                                               │
│                                                                                                                      │
│                                                        <Ok>                                                          │
│                                                                                                                      │
└──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

tl;dr - Get a fan people! My results more than quadrupled. The Raspberry Pi 4 is way, way, way too hot on its own without a fan.

EDIT:

Here is:

vcgencmd get_config int


arm_freq=1500
audio_pwm_mode=514
config_hdmi_boost=5
core_freq=500
core_freq_min=250
disable_commandline_tags=2
disable_l2cache=1
disable_overscan=1
disable_splash=1
display_lcd_rotate=-1
enable_gic=1
force_eeprom_read=1
force_pwm_open=1
framebuffer_depth=16
framebuffer_ignore_alpha=1
framebuffer_swap=1
gpu_freq=500
gpu_freq_min=500
hdmi_blanking=1
init_uart_clock=0x2dc6c00
lcd_framerate=60
pause_burst_frames=1
program_serial_random=1
temp_limit=65
hdmi_force_cec_address:0=65535
hdmi_force_cec_address:1=65535
hdmi_ignore_hotplug:0=1
hdmi_pixel_freq_limit:0=0x11e1a300
hdmi_pixel_freq_limit:1=0x11e1a300

and

vcgencmd get_config sdram_freq


sdram_freq=0
27

Hey guys, for reference: https://github.com/MichaIng/DietPi/issues/3046

Since RPi4 runs even hotter than RPi3 without cooling, raising the CPU temp limit to 75 °C (like our default on RPi3) makes sense, via dietpi-config > Performance Options, to avoid too early clock throttling.
You can slower the ARM minimum frequency via /DietPi/config.txt, e.g. arm_freq_min=300 works very well and should reduce idle CPU temp a bid. By default ondemand sample rate is 25 ms, so it only takes max 25 ms for the CPU to raise clocks when usage is rising, thus I see no downside in doing this.

I mentioned some other minor enhancements to reduce loaded hardware parts. Enabling headless mode via dietpi-config > Display Options > Display Resolution and disabling BT/WiFi via dtoverlay and RPi camera related modules: https://github.com/MichaIng/DietPi/issues/3046#issuecomment-519947771
Of course only in case the related part is not required :wink:.

However what I as well got from official Raspberry Pi forum is that a fan is simply required in most cases, or some large heatsink as linked by morphious.

What we need to find out, is why the RAM benchmarks are not better (even worse, in average) than on RPi3: https://dietpi.com/survey/#bench_ram
The LPDDR4 should be faster of course. Perhaps something else is limiting the R/W speeds to tmpfs, which is how be do this benchmark.
What I also find strange is that sdram_freq is reported to be 0 while default value according to official docs is 3200. I guess this is hardcoded for the RPi4, however some clarification, also if/that the sdram_freq has no effect, would be great.

If I find time I will forward the above questions to the RPi firmware devs.

28

ok, I got my site up on the new pi4

GTmatrix results show a ~50% drop in the load times from the Pi3 set up.

from 4-7 seconds average with Pi3
to 1.9-2.5 seconds with PI4

It’s a Wordpress site with heavy 2K+ image and graphic sizes throughout. http://EI.house

-D

29

Do you have an idea why Kali already has a full working 64bits buster img ready to use when neither debian or raspbian (and so dietpi) have it yet ? (64bits supported on rpi2 (1.2), rpi3 & rpi4…
https://images.offensive-security.com/arm-images/kali-linux-2019.3a-rpi3-nexmon-64.img.xz

https://www.offensive-security.com/kali-linux-arm-images/

30

Hello guys,

I am going to reinstall dietpi on my Pi4. Apt-get update/upgrade gives me a perl-error (unconfigured?). But perhaps this is solvable with a command? (reinstalling perl gives me the same error). sudo apt-get install -f doesn’t solve the problem.


root@Pi4:~# sudo apt-get update
Get:1 https://archive.raspberrypi.org/debian buster InRelease [25.2 kB]
Get:2 https://mirror.netcologne.de/raspbian/raspbian buster InRelease [15.0 kB]
Get:3 https://archive.raspberrypi.org/debian buster/main armhf Packages [229 kB]
Get:4 https://mirror.netcologne.de/raspbian/raspbian buster/contrib armhf Packages [58.7 kB]
Get:5 https://mirror.netcologne.de/raspbian/raspbian buster/non-free armhf Packages [103 kB]
Get:6 https://mirror.netcologne.de/raspbian/raspbian buster/rpi armhf Packages [1,360 B]
Get:7 https://mirror.netcologne.de/raspbian/raspbian buster/main armhf Packages [13.0 MB]
Fetched 13.4 MB in 6s (2,258 kB/s)
Reading package lists... Done
root@Pi4:~# sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
debconf: Perl may be unconfigured (Fcntl.pm did not return a true value at /usr/lib/arm-linux-gnueabihf/perl/5.28/IO/Seekable.pm line 11.
BEGIN failed--compilation aborted at /usr/lib/arm-linux-gnueabihf/perl/5.28/IO/Seekable.pm line 11.
Compilation failed in require at /usr/lib/arm-linux-gnueabihf/perl/5.28/IO/File.pm line 10.
BEGIN failed--compilation aborted at /usr/lib/arm-linux-gnueabihf/perl/5.28/IO/File.pm line 10.
Compilation failed in require at /usr/share/perl/5.28/FileHandle.pm line 9.
Compilation failed in require at (eval 1) line 3.
BEGIN failed--compilation aborted at (eval 1) line 3.
) -- aborting
Setting up tzdata (2019c-0+deb10u1) ...
Fcntl.pm did not return a true value at /usr/lib/arm-linux-gnueabihf/perl/5.28/POSIX.pm line 11.
BEGIN failed--compilation aborted at /usr/lib/arm-linux-gnueabihf/perl/5.28/POSIX.pm line 17.
Compilation failed in require at /usr/share/perl5/Debconf/Template.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Template.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Question.pm line 8.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Question.pm line 8.
Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10.
Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 7.
Compilation failed in require at /usr/share/debconf/frontend line 6.
BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6.
dpkg: error processing package tzdata (--configure):
 installed tzdata package post-installation script subprocess returned error exit status 255
Setting up proftpd-basic (1.3.6-4+deb10u1) ...
Fcntl.pm did not return a true value at /usr/lib/arm-linux-gnueabihf/perl/5.28/POSIX.pm line 11.
BEGIN failed--compilation aborted at /usr/lib/arm-linux-gnueabihf/perl/5.28/POSIX.pm line 17.
Compilation failed in require at /usr/share/perl5/Debconf/Template.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Template.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Question.pm line 8.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Question.pm line 8.
Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10.
Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 7.
Compilation failed in require at /usr/share/debconf/frontend line 6.
BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6.
dpkg: error processing package proftpd-basic (--configure):
 installed proftpd-basic package post-installation script subprocess returned error exit status 255
Errors were encountered while processing:
 tzdata
 proftpd-basic
E: Sub-process /usr/bin/dpkg returned an error code (1)

ps: services i have running:
-smb
-homeassistant (lighttpd)
-syncthing

(i also tried to install proftp)

31

ThAnEb
DietPi is based on Raspbian, and Raspbian is currently on a x32 OS + repo. Raspbian x64 is under development, but might take still a while.

pakikje
Hmm, could you paste the exact perl error you face? I sometimes get these in combination with a file system corruption, where perl module files are broken. APT behaves a bid bad there, as it tries to finish all marked installs/configurations first, before it applies reinstalls, even if those would fix the broken files. This is indeed nasty to solve, but lets see the exact error first.

32

Hello MichaIng,

I though that i copied/pasted all the errors? (perl error is in there)

Greetz: Patrick

33

Ah sorry, my failt, jep everything is there.

Could you try:
dpkg --configure perl-base
And, in case:
dpkg-reconfigure perl-base

If those two do not help, try to reinstall the package manually outside of APT:

cd /tmp
wget http://raspbian.raspberrypi.org/raspbian/pool/main/p/perl/perl-base_5.28.1-6_armhf.deb
dpkg -i perl-base_5.28.1-6_armhf.deb
rm perl-base_5.28.1-6_armhf.deb
34

Thanks for the clarification, as it is write “from debian” on your github, I was thinking it would have been faster than if it is based on raspbian…

I think I will give a try to your script PREP_SYSTEM_FOR_DIETPI.sh on the kali, as kali is a debian, that should work isn’t it ?

35

x64 is not really faster than x32. The difference is minimal and only measurable if the software is programmed to get advantages from it. This is also the reason why Raspbian x64 development didn’t have much priority. Other limitations due not apply e.g. since RPi does not have more than max 4G RAM.

Sadly DietPi-PREP will not work as long as you don’t select “Generic device” which leads to losing some RPi special features. When selecting RPi, it will try to turn it into Raspbian by switching the repo accordingly, which most likely does not work well as x32 and x64 packages are mixed.

Would be an interesting experiment as at least the RPi firmware repo has an arm64 branch, but I guess it still has some limitations and more work to finish on it.

36

Hello MichaIng,

None of it worked. (last install worked but the errors remain after reboot & apt-get…)

Reinstalling DietPi…

Greetz… Patrick

root@Pi4:~# sudo apt-get update
Get:1 https://archive.raspberrypi.org/debian buster InRelease [25.1 kB]
Get:2 https://mirror.netcologne.de/raspbian/raspbian buster InRelease [15.0 kB]
Get:3 https://archive.raspberrypi.org/debian buster/main armhf Packages [234 kB]
Get:4 https://mirror.netcologne.de/raspbian/raspbian buster/contrib armhf Packages [58.7 kB]
Get:5 https://mirror.netcologne.de/raspbian/raspbian buster/rpi armhf Packages [1,360 B]
Get:6 https://mirror.netcologne.de/raspbian/raspbian buster/non-free armhf Packages [103 kB]
Get:7 https://mirror.netcologne.de/raspbian/raspbian buster/main armhf Packages [13.0 MB]
Fetched 13.4 MB in 7s (1,793 kB/s)
Reading package lists... Done
root@Pi4:~# sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libdrm-etnaviv1 libllvm6.0
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
debconf: Perl may be unconfigured (Fcntl.pm did not return a true value at /usr/lib/arm-linux-gnueabihf/perl/5.28/IO/Seekable.pm line 11.
BEGIN failed--compilation aborted at /usr/lib/arm-linux-gnueabihf/perl/5.28/IO/Seekable.pm line 11.
Compilation failed in require at /usr/lib/arm-linux-gnueabihf/perl/5.28/IO/File.pm line 10.
BEGIN failed--compilation aborted at /usr/lib/arm-linux-gnueabihf/perl/5.28/IO/File.pm line 10.
Compilation failed in require at /usr/share/perl/5.28/FileHandle.pm line 9.
Compilation failed in require at (eval 1) line 3.
BEGIN failed--compilation aborted at (eval 1) line 3.
) -- aborting
Setting up tzdata (2019c-0+deb10u1) ...
Fcntl.pm did not return a true value at /usr/lib/arm-linux-gnueabihf/perl/5.28/POSIX.pm line 11.
BEGIN failed--compilation aborted at /usr/lib/arm-linux-gnueabihf/perl/5.28/POSIX.pm line 17.
Compilation failed in require at /usr/share/perl5/Debconf/Template.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Template.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Question.pm line 8.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Question.pm line 8.
Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10.
Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 7.
Compilation failed in require at /usr/share/debconf/frontend line 6.
BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6.
dpkg: error processing package tzdata (--configure):
 installed tzdata package post-installation script subprocess returned error exit status 255
Setting up proftpd-basic (1.3.6-4+deb10u1) ...
Fcntl.pm did not return a true value at /usr/lib/arm-linux-gnueabihf/perl/5.28/POSIX.pm line 11.
BEGIN failed--compilation aborted at /usr/lib/arm-linux-gnueabihf/perl/5.28/POSIX.pm line 17.
Compilation failed in require at /usr/share/perl5/Debconf/Template.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Template.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Question.pm line 8.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Question.pm line 8.
Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10.
Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 7.
Compilation failed in require at /usr/share/debconf/frontend line 6.
BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6.
dpkg: error processing package proftpd-basic (--configure):
 installed proftpd-basic package post-installation script subprocess returned error exit status 255
Errors were encountered while processing:
 tzdata
 proftpd-basic
E: Sub-process /usr/bin/dpkg returned an error code (1)
37

So…
kali rpi arm64 on a SSD (samsung pro 840, 256Gb with a usb 3 adapter jmicron
boot through the cmdline.txt /dev/sda2
modified /etc/os-release to :

root@kali:~# cat /etc/os-release
PRETTY_NAME=“Kali GNU/Linux 10 (buster)”
…
VERSION_ID=“10”
VERSION_CODENAME=buster

Dietpi PREP script run, few issues to fix and solve, 0 change related to cpu/mem/freq settings, and after reboot the benchmark… :

Benchmarks completed:
CPU Performance : Duration = 7.32 seconds (lower is faster)
- CPU Temp 	: Idle = 38'c | Full load = 45'c
- RootFS 	: Write = 115 MiB/s | Read = 244 MiB/s 
- RAM 		: Write = 469 MiB/s | Read = 1158 MiB/s

Using a Raspberry PI 4 4GB with a case like this (the 5V noisy dual fans couple removed and a replaced by a single 8cm 12V@5V gpio powered):

1500×1500 132 KB

38

so Kali is better for ramspeed? (and using an ssd is beter for rootfs speed offcourse). I would very much like to know how other programs perform on Kali (smb/homeassistant/lighttpd) Perhaps i will try this as well…

39

UPDATE:
For now, the conversion is “unstable”, remember that Kali is built on unstable branch of debian, and the dietpi PREP script switch apt to debian stable branch… so some packages may need to be removed and installed again to downgrade (but it seems impossible for some of them, in that case we have to wait for debian to release updated packages).
Samba and pihole are working.
During test, I learned that Kali has a service masking policy very strict in order to hide the system the most they can, for exemple, I had to use " systemctl enable resolvconf " to enable dns resolution services (so it could be required to do same for other service you may install).
Bluetooth can be activated from dietpi-conf (I didn’t try to configure it yet, but dmesg claims it’s ok), but I still don’t find how to make the wifi working (same lacking driver whereas it’s fully operational at first under kali).
If someone wants to test, here’s the dietpi img i made in order to restart test faster (made with dietpi img scrip, so it will be same as new dietpi, with first boot setup) :
EDIT LINK REMOVED (uncomplete image that leads to frustration (no wifi and many bugs))
Root partition reduced to 1.3Gb with Gparted before re-applying the PREP script, but it still required a 8Gb sdcard or usb key, compressed with xz --threads=4 (happy to see the 4 cores working at 100% under htop).

40

ok, I should be able to provide you with a new img that can allow you to test home assistant by dietpi…
I tested a migration from a ubuntu arm64 18.04 and it seems more complicated than the kali (which is too much “in the future” for allowing dietpi to install home assistant)… so I tried something else, that should solves many dependency issue :
forcing the PREP script to work with the kali repo, and so, getting a system based on the debian unstable branch…
I will test home assistant install tomorrow ^^