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

Mainline 5.13.x
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben Images linux rockpro64
1

0 Stimmen

1 Beiträge

190 Aufrufe

Niemand hat geantwortet
F

Zwischenfazit April 2019
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben ROCKPro64 rockpro64
1

1 Stimmen

1 Beiträge

554 Aufrufe

Niemand hat geantwortet
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

ROCKPro64 - LAN Schnittstelle
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben ROCKPro64 rockpro64
1

0 Stimmen

1 Beiträge

380 Aufrufe

Niemand hat geantwortet
F

Armbian für den ROCKPro64
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben Armbian armbian rockpro64
1

0 Stimmen

1 Beiträge

529 Aufrufe

Niemand hat geantwortet
F

PCI-e X4 to M.2/NGFF NVMe SSD Interface Card
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben Hardware hardware rockpro64
1

0 Stimmen

1 Beiträge

654 Aufrufe

Niemand hat geantwortet
F

ROCKPro64 - Der Bootvorgang
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben Hardware hardware rockpro64
3

0 Stimmen

3 Beiträge

2k Aufrufe

F

Um einen neuen Kernel booten zu können, brauche ich diese 4 Dateien unter /boot
config-4.19.0-rc4-1065-ayufan-g72e04c7b3e06 initrd.img-4.19.0-rc4-1065-ayufan-g72e04c7b3e06 System.map-4.19.0-rc4-1065-ayufan-g72e04c7b3e06 vmlinuz-4.19.0-rc4-1065-ayufan-g72e04c7b3e06
Und den Ordner /boot/dtbs/4.19.0-rc4-1065-ayufan-g72e04c7b3e06 mit folgendem Inhalt
rock64@rockpro64v2_0:/boot/dtbs/4.19.0-rc4-1065-ayufan-g72e04c7b3e06$ ls -la total 104 drwxr-xr-x 26 root root 4096 Sep 30 09:54 . drwxr-xr-x 6 root root 4096 Sep 30 09:55 .. drwxr-xr-x 2 root root 4096 Sep 30 09:54 al drwxr-xr-x 2 root root 4096 Sep 30 09:54 allwinner drwxr-xr-x 2 root root 4096 Sep 30 09:54 altera drwxr-xr-x 2 root root 4096 Sep 30 09:54 amd drwxr-xr-x 2 root root 4096 Sep 30 09:54 amlogic drwxr-xr-x 2 root root 4096 Sep 30 09:54 apm drwxr-xr-x 2 root root 4096 Sep 30 09:54 arm drwxr-xr-x 4 root root 4096 Sep 30 09:54 broadcom drwxr-xr-x 2 root root 4096 Sep 30 09:54 cavium drwxr-xr-x 2 root root 4096 Sep 30 09:54 exynos drwxr-xr-x 2 root root 4096 Sep 30 09:54 freescale drwxr-xr-x 2 root root 4096 Sep 30 09:54 hisilicon drwxr-xr-x 2 root root 4096 Sep 30 09:54 lg drwxr-xr-x 2 root root 4096 Sep 30 09:54 marvell drwxr-xr-x 2 root root 4096 Sep 30 09:54 mediatek drwxr-xr-x 2 root root 4096 Sep 30 09:54 nvidia drwxr-xr-x 2 root root 4096 Sep 30 09:54 qcom drwxr-xr-x 2 root root 4096 Sep 30 09:54 renesas drwxr-xr-x 2 root root 4096 Sep 30 09:54 rockchip drwxr-xr-x 2 root root 4096 Sep 30 09:54 socionext drwxr-xr-x 2 root root 4096 Sep 30 09:54 sprd drwxr-xr-x 2 root root 4096 Sep 30 09:54 synaptics drwxr-xr-x 2 root root 4096 Sep 30 09:54 xilinx drwxr-xr-x 2 root root 4096 Sep 30 09:54 zte
Unter /boot/extlinux liegt dann die Datei extlinux.conf

Die sieht bei mir dann so aus
timeout 10 menu title select kernel label kernel-4.19.0-rc4-1065-ayufan-g72e04c7b3e06 kernel /boot/vmlinuz-4.19.0-rc4-1065-ayufan-g72e04c7b3e06 initrd /boot/initrd.img-4.19.0-rc4-1065-ayufan-g72e04c7b3e06 devicetreedir /boot/dtbs/4.19.0-rc4-1065-ayufan-g72e04c7b3e06 append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=TEST rootwait rootfstype=ext4 label kernel-4.19.0-rc4-1065-ayufan-g72e04c7b3e06-memtest kernel /boot/vmlinuz-4.19.0-rc4-1065-ayufan-g72e04c7b3e06 initrd /boot/initrd.img-4.19.0-rc4-1065-ayufan-g72e04c7b3e06 devicetreedir /boot/dtbs/4.19.0-rc4-1065-ayufan-g72e04c7b3e06 append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=TEST rootwait rootfstype=ext4 memtest
Darunter kommen dann evt. die alten Kernel die installiert waren, das habe ich hier im Beispiel weg gelassen.
F

Wiki zum ROCKPro64 veröffentlicht!
Beobachtet Ignoriert Geplant Angeheftet Gesperrt Verschoben ROCKPro64 rockpro64
1

0 Stimmen

1 Beiträge

1k Aufrufe

Niemand hat geantwortet

linux-nerds.org

stretch-minimal-rockpro64

INFO'S

ANWENDUNG

Status