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

Lokale Einstellungen

ROCKPro64

528

Anmelden zum Antworten

FrankM zuletzt editiert von FrankM
Bei den Images vom Kamil muss man folgende Sachen noch einstellen, damit es für uns in D passt.

locale settings
```
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LANG = "de_DE.UTF-8"
    are supported and installed on your system.
```
Wie bekommt man das weg?
```
 sudo locale-gen
 sudo dpkg-reconfigure locales
```
Zeitzone setzen
```
sudo timedatectl set-timezone Europe/Berlin
```
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
Antworten Zitieren 0

ROCKPro64 - Samsung Portable SSD T5 500GB
Hardware • rockpro64 • • FrankM

1

0
Stimmen

1
Beiträge

236
Aufrufe

Niemand hat geantwortet
ROCKPro64 - USB-C -> LAN
ROCKPro64 • rockpro64 • • FrankM

1

0
Stimmen

1
Beiträge

255
Aufrufe

Niemand hat geantwortet
Wireguard
Wireguard • linux rockpro64 wireguard • • FrankM

4

0
Stimmen

4
Beiträge

689
Aufrufe

Etwas schnellerer Weg den Tunnel aufzubauen, Voraussetzung
wireguard modul installiert Keys erzeugt
Danach dann einfach
ip link add wg0 type wireguard wg setconf wg0 /etc/wireguard/wg0.conf Datei /etc/wireguard/wg0.conf [Interface] PrivateKey = <Private Key> ListenPort = 60563 [Peer] PublicKey = <Public Key Ziel> Endpoint = <IPv4 Adresse Zielrechner>:58380 AllowedIPs = 10.10.0.1/32
Die Rechte der Dateien von wireguard müssen eingeschränkt werden.
sudo chmod 0600 /etc/wireguard/wg0.conf
Das ganze per rc.local beim Booten laden. Datei /root/wireguard_start.sh
############################################################################################### # Autor: Frank Mankel # Startup-Script # Wireguard # Kontakt: frank.mankel@gmail.com # ############################################################################################### ip link add wg0 type wireguard ip address add dev wg0 10.10.0.1/8 wg setconf wg0 /etc/wireguard/wg0.conf ip link set up dev wg0
Danach Datei ausführbar machen
chmod +x /root/wireguard_start.sh
In rc.local
/root/wireguard_start.sh
eintragen - Fertig!
ROCKPro64 - i2c Bus
Hardware • rockpro64 • • FrankM

1

0
Stimmen

1
Beiträge

422
Aufrufe

Niemand hat geantwortet
ROCKPro64 (4GB) - Probleme mit der PCIe SATA-Karte??
ROCKPro64 • rockpro64 • • FrankM

8

0
Stimmen

8
Beiträge

1054
Aufrufe

Die Verlinkung hatte ich überlesen, sorry.

Es gibt nur eine Handvoll Karten, die im PCIe Port funktionieren. Warum, kann ich dir leider nicht beantworten. Es liegt aber mit Sicherheit an falschen Einstellungen im Kernel und an fehlenden Treibern. Ich habe hier auch eine andere Karte rumliegen, die erzeugt immer nur eine Kernel Panic 😞

In diesem Thread steht einiges was geht und was nicht.

PCI-E add-on Success & Failures
Recover Button
Hardware • hardware rockpro64 • • FrankM

2

0
Stimmen

2
Beiträge

728
Aufrufe

Ich hab das mal ausprobiert.

Den Recover Button so lange drücken, bis folgendes erscheint.
In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: Pine64 RockPro64 rockchip_dnl_mode = 1 mode rockchip_dnl_mode = 2 mode rockchip_dnl_mode = 3 mode rockchip_dnl_mode = 4 mode entering maskrom mode...
RKFlashTool clonen
root@thinkpad:/home/frank/test# git clone https://github.com/rockchip-linux/rkflashtool Klone nach 'rkflashtool' ... remote: Counting objects: 663, done. remote: Total 663 (delta 0), reused 0 (delta 0), pack-reused 663 Empfange Objekte: 100% (663/663), 114.94 KiB | 0 bytes/s, Fertig. Löse Unterschiede auf: 100% (367/367), Fertig.
In das Verzeichnis wechseln
root@thinkpad:/home/frank/test# cd rkflashtool/
Inhalt
root@thinkpad:/home/frank/test/rkflashtool# ls doc Makefile rkcrc.h rkflashtool.h rkparametersblock examples README rkflashall rkmisc rkunpack.c fixversion.sh release.sh rkflashloader rkpad rkunsign flashuboot rkcrc.c rkflashtool.c rkparameters version.h
RKFlashtool bauen
root@thinkpad:/home/frank/test/rkflashtool# make gcc -O2 -W -Wall -I/usr/include/libusb-1.0 rkflashtool.c -o rkflashtool -lusb-1.0 gcc -O2 -W -Wall -I/usr/include/libusb-1.0 rkcrc.c -o rkcrc -lusb-1.0 gcc -O2 -W -Wall -I/usr/include/libusb-1.0 rkunpack.c -o rkunpack -lusb-1.0
Ich habe ein USB-A to USB-A Kabel vom USB-C Port des ROCKPro64 zu meinem Notebook hergestellt.
root@thinkpad:/home/frank/test/rkflashtool# sudo ./rkflashtool v rkflashtool: info: rkflashtool v5.2 rkflashtool: info: Detected RK3399... rkflashtool: info: interface claimed rkflashtool: info: MASK ROM MODE rkflashtool: info: chip version: -..-
Ok, Verbindung steht.

Eine Übersicht der Befehle
root@thinkpad:/home/frank/test/rkflashtool# sudo ./rkflashtool rkflashtool: info: rkflashtool v5.2 rkflashtool: fatal: usage: rkflashtool b [flag] reboot device rkflashtool l <file load DDR init (MASK ROM MODE) rkflashtool L <file load USB loader (MASK ROM MODE) rkflashtool v read chip version rkflashtool n read NAND flash info rkflashtool i offset nsectors >outfile read IDBlocks rkflashtool j offset nsectors <infile write IDBlocks rkflashtool m offset nbytes >outfile read SDRAM rkflashtool M offset nbytes <infile write SDRAM rkflashtool B krnl_addr parm_addr exec SDRAM rkflashtool r partname >outfile read flash partition rkflashtool w partname <infile write flash partition rkflashtool r offset nsectors >outfile read flash rkflashtool w offset nsectors <infile write flash rkflashtool p >file fetch parameters rkflashtool P <file write parameters rkflashtool e partname erase flash (fill with 0xff) rkflashtool e offset nsectors erase flash (fill with 0xff)
ROCKPro64 updaten
ROCKPro64 • rockpro64 • • FrankM

1

0
Stimmen

1
Beiträge

535
Aufrufe

Niemand hat geantwortet
stretch-minimal-rockpro64
Linux • rockpro64 • • FrankM

3

0
Stimmen

3
Beiträge

926
Aufrufe

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

1 / 1

Lokale Einstellungen

locale settings

Zeitzone setzen

ROCKPro64 - Samsung Portable SSD T5 500GB Hardware • rockpro64 • • FrankM

ROCKPro64 - USB-C -> LAN ROCKPro64 • rockpro64 • • FrankM

Wireguard Wireguard • linux rockpro64 wireguard • • FrankM

ROCKPro64 - i2c Bus Hardware • rockpro64 • • FrankM

ROCKPro64 (4GB) - Probleme mit der PCIe SATA-Karte?? ROCKPro64 • rockpro64 • • FrankM

Recover Button Hardware • hardware rockpro64 • • FrankM

ROCKPro64 updaten ROCKPro64 • rockpro64 • • FrankM

stretch-minimal-rockpro64 Linux • rockpro64 • • FrankM

ROCKPro64 - Samsung Portable SSD T5 500GB
Hardware • rockpro64 • • FrankM

ROCKPro64 - USB-C -> LAN
ROCKPro64 • rockpro64 • • FrankM

Wireguard
Wireguard • linux rockpro64 wireguard • • FrankM

ROCKPro64 - i2c Bus
Hardware • rockpro64 • • FrankM

ROCKPro64 (4GB) - Probleme mit der PCIe SATA-Karte??
ROCKPro64 • rockpro64 • • FrankM

Recover Button
Hardware • hardware rockpro64 • • FrankM

ROCKPro64 updaten
ROCKPro64 • rockpro64 • • FrankM

stretch-minimal-rockpro64
Linux • rockpro64 • • FrankM