linux-nerds.org

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

stretch-minimal-rockpro64

Verschoben Linux

3 Beiträge 1 Kommentatoren 1.0k Aufrufe

F Offline
F Offline
FrankM
schrieb am zuletzt editiert von FrankM

#1
INFO'S
- Image Name: stretch-minimal-rockpro64
- Inhalt: Debian 9 Stretch mit Minimalausstattung
- Downloadlink: https://github.com/ayufan-rock64/linux-build/releases
- Autor: Ayufan
ANWENDUNG

Das Image auf eine SD-Karte schreiben, den ROCKPro64 damit starten.

Status

Startet nicht - Fehler!
Im Fediverse -> @FrankM@nrw.social
1. NanoPi R5S
2. Quartz64 Model B, 4GB RAM
3. Quartz64 Model A, 4GB RAM
4. RockPro64 v2.1
1 Antwort Letzte Antwort
0

FrankM

schrieb am

Mit 0.7.2 startet das Image. LAN ok.

rock64@rockpro64:~$ iperf3 -c 192.168.3.213
Connecting to host 192.168.3.213, port 5201
[  4] local 192.168.3.9 port 33558 connected to 192.168.3.213 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec   116 MBytes   970 Mbits/sec    0    938 KBytes       
[  4]   1.00-2.00   sec   112 MBytes   942 Mbits/sec    0   1012 KBytes       
[  4]   2.00-3.00   sec   112 MBytes   942 Mbits/sec    0   1.00 MBytes       
[  4]   3.00-4.00   sec   112 MBytes   941 Mbits/sec    0   1.11 MBytes       
[  4]   4.00-5.00   sec   112 MBytes   941 Mbits/sec    0   1.11 MBytes       
[  4]   5.00-6.00   sec   112 MBytes   941 Mbits/sec    0   1.11 MBytes       
[  4]   6.00-7.00   sec   106 MBytes   890 Mbits/sec    0   6.01 MBytes       
[  4]   7.00-8.00   sec   113 MBytes   952 Mbits/sec    0   6.01 MBytes       
[  4]   8.00-9.00   sec   112 MBytes   941 Mbits/sec    0   6.01 MBytes       
[  4]   9.00-10.00  sec   112 MBytes   942 Mbits/sec    0   6.01 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  1.09 GBytes   940 Mbits/sec    0             sender
[  4]   0.00-10.00  sec  1.09 GBytes   937 Mbits/sec                  receiver

iperf Done.
rock64@rockpro64:~$ iperf3 -s              
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 192.168.3.213, port 51756
[  5] local 192.168.3.9 port 5201 connected to 192.168.3.213 port 51758
[ ID] Interval           Transfer     Bandwidth
[  5]   0.00-1.00   sec   110 MBytes   923 Mbits/sec                  
[  5]   1.00-2.00   sec   112 MBytes   941 Mbits/sec                  
[  5]   2.00-3.00   sec   112 MBytes   942 Mbits/sec                  
[  5]   3.00-4.00   sec   112 MBytes   941 Mbits/sec                  
[  5]   4.00-5.00   sec   112 MBytes   941 Mbits/sec                  
[  5]   5.00-6.00   sec   112 MBytes   941 Mbits/sec                  
[  5]   6.00-7.00   sec   112 MBytes   942 Mbits/sec                  
[  5]   7.00-8.00   sec   112 MBytes   941 Mbits/sec                  
[  5]   8.00-9.00   sec   112 MBytes   941 Mbits/sec                  
[  5]   9.00-10.00  sec   112 MBytes   942 Mbits/sec                  
[  5]  10.00-10.02  sec  1.79 MBytes   931 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  5]   0.00-10.02  sec  0.00 Bytes  0.00 bits/sec                  sender
[  5]   0.00-10.02  sec  1.10 GBytes   940 Mbits/sec                  receiver
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
^Ciperf3: interrupt - the server has terminated

FrankM

schrieb am

Mal ein Test was der Speicher so kann.

rock64@rockpro64:~/tinymembench$ ./tinymembench
tinymembench v0.4.9 (simple benchmark for memory throughput and latency)

==========================================================================
== Memory bandwidth tests                                               ==
==                                                                      ==
== Note 1: 1MB = 1000000 bytes                                          ==
== Note 2: Results for 'copy' tests show how many bytes can be          ==
==         copied per second (adding together read and writen           ==
==         bytes would have provided twice higher numbers)              ==
== Note 3: 2-pass copy means that we are using a small temporary buffer ==
==         to first fetch data into it, and only then write it to the   ==
==         destination (source -> L1 cache, L1 cache -> destination)    ==
== Note 4: If sample standard deviation exceeds 0.1%, it is shown in    ==
==         brackets                                                     ==
==========================================================================

 C copy backwards                                     :   2812.7 MB/s
 C copy backwards (32 byte blocks)                    :   2811.9 MB/s
 C copy backwards (64 byte blocks)                    :   2632.8 MB/s
 C copy                                               :   2667.2 MB/s
 C copy prefetched (32 bytes step)                    :   2633.5 MB/s
 C copy prefetched (64 bytes step)                    :   2640.8 MB/s
 C 2-pass copy                                        :   2509.8 MB/s
 C 2-pass copy prefetched (32 bytes step)             :   2431.6 MB/s
 C 2-pass copy prefetched (64 bytes step)             :   2424.1 MB/s
 C fill                                               :   4887.7 MB/s (0.5%)
 C fill (shuffle within 16 byte blocks)               :   4883.0 MB/s
 C fill (shuffle within 32 byte blocks)               :   4889.3 MB/s
 C fill (shuffle within 64 byte blocks)               :   4889.2 MB/s
 ---
 standard memcpy                                      :   2807.3 MB/s
 standard memset                                      :   4890.4 MB/s (0.3%)
 ---
 NEON LDP/STP copy                                    :   2803.7 MB/s
 NEON LDP/STP copy pldl2strm (32 bytes step)          :   2802.1 MB/s
 NEON LDP/STP copy pldl2strm (64 bytes step)          :   2800.7 MB/s
 NEON LDP/STP copy pldl1keep (32 bytes step)          :   2745.5 MB/s
 NEON LDP/STP copy pldl1keep (64 bytes step)          :   2745.8 MB/s
 NEON LD1/ST1 copy                                    :   2801.9 MB/s
 NEON STP fill                                        :   4888.9 MB/s (0.3%)
 NEON STNP fill                                       :   4850.1 MB/s
 ARM LDP/STP copy                                     :   2803.8 MB/s
 ARM STP fill                                         :   4893.0 MB/s (0.5%)
 ARM STNP fill                                        :   4851.7 MB/s

==========================================================================
== Framebuffer read tests.                                              ==
==                                                                      ==
== Many ARM devices use a part of the system memory as the framebuffer, ==
== typically mapped as uncached but with write-combining enabled.       ==
== Writes to such framebuffers are quite fast, but reads are much       ==
== slower and very sensitive to the alignment and the selection of      ==
== CPU instructions which are used for accessing memory.                ==
==                                                                      ==
== Many x86 systems allocate the framebuffer in the GPU memory,         ==
== accessible for the CPU via a relatively slow PCI-E bus. Moreover,    ==
== PCI-E is asymmetric and handles reads a lot worse than writes.       ==
==                                                                      ==
== If uncached framebuffer reads are reasonably fast (at least 100 MB/s ==
== or preferably >300 MB/s), then using the shadow framebuffer layer    ==
== is not necessary in Xorg DDX drivers, resulting in a nice overall    ==
== performance improvement. For example, the xf86-video-fbturbo DDX     ==
== uses this trick.                                                     ==
==========================================================================

 NEON LDP/STP copy (from framebuffer)                 :    602.5 MB/s
 NEON LDP/STP 2-pass copy (from framebuffer)          :    551.6 MB/s
 NEON LD1/ST1 copy (from framebuffer)                 :    667.1 MB/s
 NEON LD1/ST1 2-pass copy (from framebuffer)          :    605.6 MB/s
 ARM LDP/STP copy (from framebuffer)                  :    445.3 MB/s
 ARM LDP/STP 2-pass copy (from framebuffer)           :    428.8 MB/s

==========================================================================
== Memory latency test                                                  ==
==                                                                      ==
== Average time is measured for random memory accesses in the buffers   ==
== of different sizes. The larger is the buffer, the more significant   ==
== are relative contributions of TLB, L1/L2 cache misses and SDRAM      ==
== accesses. For extremely large buffer sizes we are expecting to see   ==
== page table walk with several requests to SDRAM for almost every      ==
== memory access (though 64MiB is not nearly large enough to experience ==
== this effect to its fullest).                                         ==
==                                                                      ==
== Note 1: All the numbers are representing extra time, which needs to  ==
==         be added to L1 cache latency. The cycle timings for L1 cache ==
==         latency can be usually found in the processor documentation. ==
== Note 2: Dual random read means that we are simultaneously performing ==
==         two independent memory accesses at a time. In the case if    ==
==         the memory subsystem can't handle multiple outstanding       ==
==         requests, dual random read has the same timings as two       ==
==         single reads performed one after another.                    ==
==========================================================================

block size : single random read / dual random read
      1024 :    0.0 ns          /     0.0 ns 
      2048 :    0.0 ns          /     0.0 ns 
      4096 :    0.0 ns          /     0.0 ns 
      8192 :    0.0 ns          /     0.0 ns 
     16384 :    0.0 ns          /     0.0 ns 
     32768 :    0.0 ns          /     0.0 ns 
     65536 :    4.5 ns          /     7.2 ns 
    131072 :    6.8 ns          /     9.7 ns 
    262144 :    9.8 ns          /    12.8 ns 
    524288 :   11.4 ns          /    14.7 ns 
   1048576 :   16.0 ns          /    22.6 ns 
   2097152 :  114.0 ns          /   175.3 ns 
   4194304 :  161.7 ns          /   219.9 ns 
   8388608 :  190.7 ns          /   241.5 ns 
  16777216 :  205.3 ns          /   250.5 ns 
  33554432 :  212.9 ns          /   255.5 ns 
  67108864 :  222.3 ns          /   271.1 ns

F

RockPro64 - Mainline Kernel 6.8.0-rc3
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben ROCKPro64 rockpro64 linux mainline
1

0 Stimmen

1 Beiträge

229 Aufrufe

Niemand hat geantwortet
F

ROCKPro64 - Anpassen resize_rootfs.sh
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben ROCKPro64 rockpro64
3

0 Stimmen

3 Beiträge

457 Aufrufe

F

Seit Release 0.10.10 ist das automatische Vergrößern der Root Partition mit drin 🙂
0.10.10: Support automated resize when booting from nvme
Einfach das Image auf die NVMe SSD schreiben, ab in den ROCKPro64 und fertig! Nach dem Booten wird die Partition dann automatisch auf die maximal mögliche Größe erweitert.

Kamil hat das Script auch ein wenig angepasst.
case $dev in /dev/mmcblk?p?) DISK=${dev:0:12} PART=${dev:13} NAME="sd/emmc" ;; /dev/sd??) DISK=${dev:0:8} PART=${dev:8} NAME="hdd/ssd" ;; /dev/nvme?n?p?) DISK=${dev:0:12} PART=${dev:13} NAME="pcie/nvme" ;;
Das Resultat bei einer Samsung 979 EVO mit 500GB Speicher
rock64@rockpro64:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 918M 0 918M 0% /dev tmpfs 192M 5.2M 187M 3% /run /dev/nvme0n1p4 459G 1.2G 439G 1% / tmpfs 957M 0 957M 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 957M 0 957M 0% /sys/fs/cgroup /dev/nvme0n1p3 229M 44M 169M 21% /boot /dev/nvme0n1p2 12M 0 12M 0% /boot/efi tmpfs 192M 0 192M 0% /run/user/1000
Perfekt. Danke Kamil!
F

ROCKPro64 - Netflix?
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben ROCKPro64 rockpro64
2

0 Stimmen

2 Beiträge

407 Aufrufe

F

Anleitung von Kamil
# Netflix Starting with 0.8.0rc13 it is possible to use Netflix on all **Ubuntu/armf** desktop images using regular Chromium browser. Due to Google policies images do not ship Widevine CDM required by Netflix to decrypt videos. Currently, Widevine CDM is only available for **armhf** and **Ubuntu**. You have to install Widevine CDM with: ```bash install_widevine_drm.sh ``` This will take between 5 to 15 mins depending on the performance of SD-card, and your Internet connection.
F

ROCKPro64 - Eine Einführung für Einsteiger
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben ROCKPro64 rockpro64
1

0 Stimmen

1 Beiträge

476 Aufrufe

Niemand hat geantwortet
F

Neue Artikel im Pine64 Shop (August 2018)
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben Hardware hardware rockpro64
2

0 Stimmen

2 Beiträge

735 Aufrufe

F

Neue Artikel im Pine64 Shop
ABS Gehäuse https://www.pine64.org/?product=rockpro64-abs-enclosure Gehäuse für einen ROCKPro64 und einen LCD-Bildschirm https://www.pine64.org/?product=rockpro64-playbox-enclosure
F

ROCKPro64 - PCIe SATA Karte
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben Hardware hardware rockpro64
13

0 Stimmen

13 Beiträge

4k Aufrufe

F

@elRadix : With pine64 sata-card you can use two hdd's. https://www.pine64.org/?product=rockpro64-pci-e-to-dual-sata-ii-interface-card

For working cards please look into this thread before you buy anything.
F

u-boot-flash-spi-rockpro64.img.xz
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben Tools rockpro64
1

0 Stimmen

1 Beiträge

1k Aufrufe

Niemand hat geantwortet
F

stretch-openmediavault-rockpro64
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben Linux rockpro64
1

0 Stimmen

1 Beiträge

805 Aufrufe

Niemand hat geantwortet

linux-nerds.org

stretch-minimal-rockpro64

INFO'S

ANWENDUNG

Status