The new Raspberry Pi 4

[ghettopi]

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

Code: Select all

│ 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:

Code: Select all

 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:

Code: Select all

[ 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.

[fr4nk1yn]

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.

Code: Select all

 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,

Code: Select all

DietPi:~ $ sudo vcgencmd get_config sdram_freq
sdram_freq=0

Code: Select all

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

[aftensleuk]

@derders

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

[derders]

@derders

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

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

[morphious]

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- ... way&sr=8-1

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

[ghettopi]

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:

Code: Select all

┌─────────────────────────────────────────────────┤ 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

Code: Select all

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

Code: Select all

sdram_freq=0

[MichaIng]

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/issu ... -519947771
Of course only in case the related part is not required .

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.

[morphious]

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

[ThAnEb]

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/a ... -64.img.xz

https://www.offensive-security.com/kali ... rm-images/

[pakikje]

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.

Code: Select all

[email protected]:~# 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
[email protected]:~# 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)