Skip to content
linux-nerds.org

linux-nerds.org
  1. Übersicht
  2. Pine64
  3. ROCKPro64
  4. Armbian
  5. Armbian 20.08 (Caple) released

Armbian 20.08 (Caple) released

Armbian
1 1 400
  • FrankMF

    Downloads -> https://www.armbian.com/download/

    Finished projects

    [AR-45] - Make first login more user friendly
[AR-71] - Create a document: How we will use Jira
[AR-182] - Unify / merge kernel configs
[AR-201] - Introduce CI autotest facility
[AR-227] - Move Espressobin current to K5.6
[AR-313] - Ability to work in offline mode
[AR-320] - Initial support for Rockpi E
[AR-324] - Add Rockchip RK322X SoC support
[AR-328] - Meson64 move current to 5.7.y
[AR-329] - Switch sunxi dev target to kernel 5.7
[AR-331] - Enable kernel boot splash as an option
[AR-335] - Improve patch making
[AR-392] - Add Odroid N2+
[AR-402] - Add Helios64

    Solved bugs

    [AR-282] - Rockpi 4B 1Gb doesn't boot modern kernel / u-boot
[AR-295] - Odroid C2: no more USB devices after upgrade
[AR-298] - Missing default SElinux policy
[AR-303] - Create a download page for BPI M2 zero
[AR-305] - K-worker creates load on Allwinner devices
[AR-319] - Armbian config failed to switch kernels
[AR-330] - Shell check bugs
[AR-332] - When making all kernels - building sometimes fails
[AR-337] - Odroid XU4 Memcopy Slow on all Kernel 5.x 80MB/sec instead of 370+MB/sec
[AR-338] - Bananapi R2 does not boot at all
[AR-340] - Fix WiFi on Nanopi M4V2
[AR-348] - Confirm RK3399 TcpOffloading bug
[AR-352] - Fix Random MAC on H3 boards
[AR-354] - Support User Provided EDID Firmware
[AR-355] - backport Linux v5.8 fbtft/fb_st7789v invert colors, proper gamma
[AR-356] - Building multiple u-boot targets breaks
[AR-371] - CPU frequency scaling broken on H6
[AR-378] - Increase address room for initial ramdisk
[AR-381] - selinux-policy-default missing on Debian Bullseye
[AR-393] - Ask for setting locale at first run

    Closed tasks

    [AR-28] - Added new GCC compilers
[AR-225] - Introduce PACKAGE_LIST for BOARD and FAMILY
[AR-300] - Enable HDMI audio for OrangePi 4
[AR-317] - Move Odroid XU4 dev to mainline + patches
[AR-318] - Upgrade Odroid XU4 legacy kernel
[AR-321] - Upgrade Meson (C1) current to 5.7.y
[AR-323] - Allow install to SD NAND for Rockpi S
[AR-326] - Make USB3 support of ROCK Pi E on par with other rk3328 boards
[AR-327] - Bump imx6 current kernel to 5.7.y
[AR-333] - Update Odroid XU4 kernels
[AR-334] - Cleanup boot environment files
[AR-336] - Add support for cheap 2.5GB USB network dongles
[AR-341] - Follow-up N2 CPU Affinity
[AR-349] - Update mainline u-boot to v2020.07 for rockchip64 and rk3399
[AR-357] - IRQ affinity improvements for G12B
[AR-358] - Added initial support for Neo 3
[AR-361] - Update Odroid XU4 boot.ini
[AR-362] - HDMI sound support for Allwinner A10, A20, A31
[AR-364] - Change sunxi legacy to 5.4.y, current to 5.7.y
[AR-366] - Move rockchip/64 current to 5.7.y
[AR-383] - Upgrades for Tapatalk plugin
[AR-389] - Add PACKAGE_LIST_BOARD_REMOVE option

    Quelle: https://www.armbian.com/newsflash/armbian-20-08-caple/

    Im Fediverse -> @FrankM@nrw.social

    1. NanoPi R5S
    2. Quartz64 Model B, 4GB RAM
    3. Quartz64 Model A, 4GB RAM
    4. RockPro64 v2.1
    0
Anmelden zum Antworten

  • FrankMF

    ROCKPro64 - Kernel 5.6 und Wireguard 1.0

    ROCKPro64 linux rockpro64 wireguard
    1
    0 Stimmen
    1 Beiträge
    352 Aufrufe
    Niemand hat geantwortet
  • FrankMF

    Wireguard

    Verschoben Wireguard linux rockpro64 wireguard
    4
    0 Stimmen
    4 Beiträge
    974 Aufrufe
    FrankMF
    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!
  • FrankMF

    Mainline 4.20.0-rc6

    ROCKPro64 rockpro64
    1
    0 Stimmen
    1 Beiträge
    452 Aufrufe
    Niemand hat geantwortet
  • FrankMF

    ROCKPro64 - Stromverbrauch

    Hardware hardware rockpro64
    1
    0 Stimmen
    1 Beiträge
    842 Aufrufe
    Niemand hat geantwortet
  • FrankMF

    Neue Artikel im Pine64 Shop (August 2018)

    Hardware hardware rockpro64
    2
    0 Stimmen
    2 Beiträge
    823 Aufrufe
    FrankMF
    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
  • FrankMF

    IPFire auf dem ROCKPro64

    ROCKPro64 rockpro64
    2
    1
    0 Stimmen
    2 Beiträge
    678 Aufrufe
    FrankMF
    Falls es jemanden da draußen interessiert, hier eine Liste der Dinge die funktionieren GREEN Die LAN-Schnittstelle wird einwandfrei erkannt Webserver läuft, Weboberfläche erreichbar Das war's dann mit den positiven Daten jede Menge Kernelfehler iptables Fehler Modul fehlt?? kein LAN-Adapter, WLan-Adapter wird erkannt Lizenzverbindungen lassen sich nicht bestätigen nach der Installation ist die Konsole weg usw. usf
  • FrankMF

    stretch-minimal-rockpro64

    Verschoben Linux rockpro64
    3
    0 Stimmen
    3 Beiträge
    1k Aufrufe
    FrankMF
    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
  • FrankMF

    4GB Version - Out of stock

    Verschoben Archiv rockpro64
    1
    1
    0 Stimmen
    1 Beiträge
    747 Aufrufe
    Niemand hat geantwortet