Skip to content
linux-nerds.org

linux-nerds.org
  1. Übersicht
  2. Pine64
  3. ROCKPro64
  4. Images
  5. Images 0.10.x

Images 0.10.x

Angeheftet Images
  • FrankMF

    0.10.2: gitlab-ci-linux-build-170 released

    HIGHLY EXPERIMENTAL AND NOT WORKING!!!
    THIS RELEASE HAS BROKEN BOOT

    Quelle: https://github.com/ayufan-rock64/linux-build/releases/

    Nein, man kann noch nichts nutzen! 🙂

    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
  • FrankMF

    0.10.3: gitlab-ci-linux-build-171 released

    • HIGHLY EXPERIMENTAL AND NOT WORKING!!!

    • PRE-RELEASE: unstable and should be only used for testing purposes

      • 0.10.3: Hopefully OMV will compile,
      • 0.10.3: ADd SPI boot on RockPro64
      • 0.10.3: Add NVME/SATA boot on RockPro64
      • 0.10.2: Update partition scheme to use /boot/efi, /boot and /
      • 0.10.2: Configure /etc/fstab with all partitions
      • 0.10.2: Compile buster/containers instead of focal/containers

    Das sollte jetzt auch auf einigen Geräten booten. Aber heute wird nichts mehr getestet - Feierabend! 🙂

    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
  • FrankMF

    0.10.6: gitlab-ci-linux-build-174 released

    • 0.10.6: Maybe build OMV5
    • 0.10.6: Use u-boot instead of u-boot-rockchip
    • 0.10.6: Fix focal/armhf build
    • 0.10.5: Revert systemd-networkd change
    • 0.10.5: Maybe support USB3 boot on Rock64
    • 0.10.5: Maybe build OMV5

    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
  • FrankMF

    0.10.7: gitlab-ci-linux-build-175 released

    • 0.10.7: Maybe Pinebook Pro will work, thanks Manjaro 🙂
    • 0.10.7: Maybe Desktop will boot
    • 0.10.7: Maybe OMV5 will run
    • 0.10.7: Maybe gl4es will work

    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
  • FrankMF

    0.10.7 ist im Moment nicht funktional. Nach dem Boot ist keine eth0 Schnittstelle vorhanden.

    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
  • FrankMF

    0.10.8: gitlab-ci-linux-build-177 released

    • 0.10.8: Make rootfs sticky
    • 0.10.8: Update sizes of images
    • 0.10.8: Enable by default C.UTF-8 and en_US.UTF-8 and use dpkg-reconfigure locales
    • 0.10.8: Run update-command-not-found
    • 0.10.8: Better handle /etc/resolv.conf (do not remove it, if it become system controlled)
    • 0.10.8: Load dptx.alt.bin to make it possible to ship also on buster

    Viele neue Images

    • Ubuntu Focal LXDE
    • Ubuntu Focal Mate
    • Ubuntu Focal Minimum
    • Debian Buster OMV

    Viele Sachen zum Testen 🙂

    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
  • FrankMF

    0.10.9 - 0.10.9: gitlab-ci-linux-build-180 released

    • 0.10.9: Shrink created images to reduce write time
    • 0.10.9: Enable work/diy LEDs on boot for RockPro64/PinebookPro
    • 0.10.9: Fix excessive log messages on OMV5
    • 0.10.8: Make rootfs sticky
    • 0.10.8: Update sizes of images

    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
  • FrankMF

    0.10.10: gitlab-ci-linux-build-181 released

    • 0.10.10: Do not compile OMV5 for armhf, only arm64
    • 0.10.10: Fix fstab issue introduced in 0.10.9
    • 0.10.10: Do more cleanups during image creation to reduce size
    • 0.10.10: Enable u-boot HDMI output for RockPro64
    • 0.10.10: Support HDMI modeline with pclck 32MHz (ie. 1024x600@43)
    • 0.10.10: Support automated resize when booting from nvme

    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
  • FrankMF

    0.10.11: gitlab-ci-linux-build-183 released

    • 0.10.11: Support wifi/bt on Pinebook Pro
    • 0.10.11: Add install_kernel script
    • 0.10.11: Fix support for rockchip/dptx.bin
    • 0.10.11: Try Gnome, KDE, XFCE4 additionally to LXDE, Mate

    Neue Desktops werden auf Basis von Ubuntu Focal unterstützt.

    • KDE
    • XFCE4
    • Gnome

    Mal gespannt, was davon rund läuft 😉 Kann leider jetzt nichts testen, meine Testmaschine ist mit einem Raid Resync beschäftigt. OK, dann die Tage..

    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
  • FrankMF

    0.10.12: gitlab-ci-linux-build-184 released

    • 0.10.12: Be strict on any qemu failures
    • 0.10.12: Build by default mate/lxde/gnome/xfce4
    • 0.10.12: Add pcie scan delay from @nuumio
    • 0.10.12: Add ubuntu-mate-lightdm-theme where possible

    Ich komme gar nicht mehr mit dem Testen hinterher 🙂

    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

  • FrankMF

    Ayufan Release 0.7.12

    ROCKPro64
    3
    0 Stimmen
    3 Beiträge
    410 Aufrufe
    FrankMF

    Dafür andere Probleme 🙂

    Link Preview Image 0.7.12_with_pcie_nvme_ssd - Pastebin.com

    Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

    favicon

    Pastebin (pastebin.com)

    Aktuell nicht zu empfehlen!

  • FrankMF

    Kamil's 4.20.x

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

    ROCKPro64 updaten

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

    eMMC Modul

    Hardware
    1
    0 Stimmen
    1 Beiträge
    2k Aufrufe
    Niemand hat geantwortet
  • FrankMF

    ROCKPro64 - kein WLan-Modul möglich?

    ROCKPro64
    4
    0 Stimmen
    4 Beiträge
    2k Aufrufe
    FrankMF

    Heute, 5 Monate später, kann ich bestätigen das WLan möglich ist 🙂 Getestet auf einem ROCKPro64 v2.1 mit 2GB RAM.

    Eine Vorabversion von Recalbox machte es das erste Mal für mich möglich das WLan zu benutzen. Bericht

    Und PCIe ist abgeschaltet im dts File.

    pcie-phy { compatible = "rockchip,rk3399-pcie-phy"; #phy-cells = <0x0>; rockchip,grf = <0x15>; clocks = <0x8 0x8a>; clock-names = "refclk"; resets = <0x8 0x87>; reset-names = "phy"; status = "disabled"; phandle = <0x8b>; }; pcie@f8000000 { compatible = "rockchip,rk3399-pcie"; #address-cells = <0x3>; #size-cells = <0x2>; aspm-no-l0s; clocks = <0x8 0xc5 0x8 0xc4 0x8 0x147 0x8 0xa0>; clock-names = "aclk", "aclk-perf", "hclk", "pm"; bus-range = <0x0 0x1f>; max-link-speed = <0x2>; linux,pci-domain = <0x0>; msi-map = <0x0 0x89 0x0 0x1000>; interrupts = <0x0 0x31 0x4 0x0 0x0 0x32 0x4 0x0 0x0 0x33 0x4 0x0>; interrupt-names = "sys", "legacy", "client"; #interrupt-cells = <0x1>; interrupt-map-mask = <0x0 0x0 0x0 0x7>; interrupt-map = <0x0 0x0 0x0 0x1 0x8a 0x0 0x0 0x0 0x0 0x2 0x8a 0x1 0x0 0x0 0x0 0x3 0x8a 0x2 0x0 0x0 0x0 0x4 0x8a 0x3>; phys = <0x8b>; phy-names = "pcie-phy"; ranges = <0x83000000 0x0 0xfa000000 0x0 0xfa000000 0x0 0x1e00000 0x81000000 0x0 0xfbe00000 0x0 0xfbe00000 0x0 0x100000>; reg = <0x0 0xf8000000 0x0 0x2000000 0x0 0xfd000000 0x0 0x1000000>; reg-names = "axi-base", "apb-base"; resets = <0x8 0x82 0x8 0x83 0x8 0x84 0x8 0x85 0x8 0x86 0x8 0x81 0x8 0x80>; reset-names = "core", "mgmt", "mgmt-sticky", "pipe", "pm", "pclk", "aclk"; status = "disabled";

    Also bleibt weiterhin ungeklärt, ob auch beides zusammen möglich ist. Also gleichzeitig das WLan-Modul und eine PCIe Karte.

  • FrankMF

    Lokale Einstellungen

    Verschoben ROCKPro64
    1
    0 Stimmen
    1 Beiträge
    563 Aufrufe
    Niemand hat geantwortet
  • FrankMF

    Mainline Commits

    ROCKPro64
    2
    0 Stimmen
    2 Beiträge
    687 Aufrufe
    FrankMF

    Mal diesen alten Thread wieder ausgraben.

    Qualcomm Snapdragon 835 SoC support along with the HiSilicon Hi3670, many NVIDIA Tegra improvements, GTA04A5 phone support, and more. There is also now mainline ARM SBC support for the Orange Pi Zero Plus2, Orange Pi One Plus, Pine64 LTS, Banana Pi M2+ H5, 64-bit Banana Pi M2+ H3, ASUS Tinker Board S, RockPro64, Rock960, and ROC-RK-3399-PC.
    Quelle: https://www.phoronix.com/scan.php?page=article&item=linux-420-features&num=1

    Im Pine64 Forum gefunden.

  • FrankMF

    stretch-minimal-rockpro64

    Verschoben Linux
    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