Skip to content
linux-nerds.org

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

Images 0.9.x

Images
  • FrankMF

    0.9.0: gitlab-ci-linux-build-142 released

    • 0.9.0: Build Ubuntu/Disco (transitional release) and Debian/Buster (to replace Stretch),
    • 0.9.0: Update kernel branch to 4.4.184,

    Buster & Disco Images sind ab jetzt dabei, wie hier schon berichtet.

    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.9.3: gitlab-ci-linux-build-145 released

    • 0.9.3: Update kernel branch to 4.4.185,
    • 0.9.3: Disable OMV5 for now,
    • 0.9.2: Fix linux-package release due to fpm being broken,
    • 0.9.1: Build OMV5 (Debian/Buster),
    • 0.9.1: Fix ppas for Debian/Buster and Ubuntu/Disco,

    Link Preview Image
    Release 0.9.3: gitlab-ci-linux-build-145 · ayufan-rock64/linux-build

    Rock64 Linux build scripts, tools and instructions - Release 0.9.3: gitlab-ci-linux-build-145 · ayufan-rock64/linux-build

    favicon

    GitHub (github.com)

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

    Hallo, ich habe noch intermediate Release von den 0.8.x
    Kann ich von denen auf das aktuelle upgraden?
    Gruß,
    Christoph

    0
  • FrankMF

    Hallo @cnaed ,

    Release Versionen aktualisiert er ja sowieso, auf eine Pre-Release Version zu aktualisieren bedarf etwas Handarbeit.

    nano /etc/apt/sources.list.d/ayufan-rock64.list

    Inhalt der Datei

    deb http://deb.ayufan.eu/orgs/ayufan-rock64/releases /

# uncomment to use pre-release kernels and compatibility packages
# deb http://deb.ayufan.eu/orgs/ayufan-rock64/pre-releases /

    Sollte selbsterklärend sein 😉

    Bei produktiven Systemen, vorher zweimal nachdenken, ob es sinnvoll ist das Update/Upgrade zu machen. Es kommt zwar aktuell selten vor, aber es gibt immer noch Probleme. z.B.: meine aktuelle Testinstallation mit SPI und USB3-Boot knallt ständig mit haufenweisen ext4 Fehler usw. Nicht so gut!

    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.9.4: gitlab-ci-linux-build-146 released

    • 0.9.4: Update kernel branch to 4.4.189,

    Link Preview Image
    Release 0.9.4: gitlab-ci-linux-build-146 · ayufan-rock64/linux-build

    Rock64 Linux build scripts, tools and instructions - Release 0.9.4: gitlab-ci-linux-build-146 · ayufan-rock64/linux-build

    favicon

    GitHub (github.com)

    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

    Aktuell sind wir im Moment bei 0.9.8: gitlab-ci-linux-build-151

    • 0.9.8: Fix BT audio (run on 1.5M),
    • 0.9.8: Use DMA on UART/SPI,
    • 0.9.8: Lower temperature thresholds for Pinebook Pro,
    • 0.9.8: Set default audio device for all devices,
    • 0.9.8: Fix OMV4 build,
    • 0.9.8: Automatically enable h264ify,
    • 0.9.7: Include a list of used packages,
    • 0.9.7: Fix regression on compositing performance,
    • 0.9.7: Force password to change on first login,
    • 0.9.6: Support Pinebook Pro v2.1,
    • 0.9.6: Optimise suspend on Pinebook Pro,
    • 0.9.6: Optimise Mate styling,
    • 0.9.6: Optimise Touchpad settings for Pinebook Pro,
    • 0.9.6: Support 2/1.5GHz OPP on Pinebook Pro,
    • 0.9.5: Build Debian/Stretch/OMV4,
    • 0.9.5: Improve install_container_linux.sh,

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

    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.9.9: gitlab-ci-linux-build-152 released

    • 0.9.9: Fix Firefox video playback,
    • 0.9.9: Remove libmali-rk-dev from default install,
    • 0.9.9: Align standby/work leds across all boards,
    • 0.9.9: Disable Debug UART on Pinebook Pro, as it causes stability issues,
    • 0.9.9: Fix Pinebook Pro SD card stability,
    • 0.9.9: Enable PCIE NVME support for Pinebook Pro,
    • 0.9.8: Fix BT audio (run on 1.5M),

    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.9.10: gitlab-ci-linux-build-154 released

    • 0.9.10: Fix support for power/standby LEDs for all boards,
    • 0.9.10: Fix rock64 gpu acceleration regression introduced in 0.9.9,
    • 0.9.10: Replace lxdm to use lightdm, as this allows password change on login,
    • 0.9.10: Remove gnome-screensaver to fix double lock screen,

    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.9.11: gitlab-ci-linux-build-155 released

    • 0.9.11: Install unity-greeter,

    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.9.12: gitlab-ci-linux-build-156 released

    • 0.9.12: Fix LXDE for Rock64,

    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.9.13: gitlab-ci-linux-build-157 released

    • 0.9.13: Bump sound volume for Pinebook Pro,
    • 0.9.13: Fix Firefox video playback,

    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.9.14: gitlab-ci-linux-build-159 released

    • 0.9.14: Bump kernel to 4.4.190,
    • 0.9.14: Fix Firefox video playback,

    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.9.16: gitlab-ci-linux-build-163 released

    0.9.x

    • 0.9.16: Bump kernel to 4.4.197,
    • 0.9.15: Bump kernel to 4.4.193,
    • 0.9.14: Bump kernel to 4.4.190,
    • 0.9.14: Fix Firefox video playback,
    • 0.9.13: Bump sound volume for Pinebook Pro,
    • 0.9.12: Fix LXDE for Rock64,
    • 0.9.10: Fix support for power/standby LEDs for all boards,

    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

    Images 0.11.x

    Images
    5
    0 Stimmen
    5 Beiträge
    323 Aufrufe
    FrankMF

    0.11.2: gitlab-ci-linux-build-187 released

    0.11.2: Update OMV install (to also be able to run OMV6)
  • FrankMF

    Images 0.8.x

    Images
    20
    0 Stimmen
    20 Beiträge
    1k Aufrufe
    FrankMF

    0.8.3: gitlab-ci-linux-build-141 released

    0.8.2: Be more strict what packages/kernels are being in use for 0.8.x branch, 0.8.1: The final pre-release,

    Kamil hat diesen Release als Latest release gekennzeichnet. Das heißt man kann jetzt vorhandenen Installationen auf diesen Build upgraden.

    # Pick one sudo apt-get update -y && sudo apt-get install linux-rock64-0.8 -y sudo apt-get update -y && sudo apt-get install linux-rockpro64-0.8 -y sudo apt-get update -y && sudo apt-get install linux-pinebookpro-0.8 -y # Upgrade all other packages sudo apt-get update -y && sudo apt-get dist-upgrade -y # Remove invalid X11 config, and fix bootloaders sudo rm /etc/X11/xorg.conf.d/20-armsoc.conf sudo new_extlinux_boot.sh rootfs sudo rock64_upgrade_bootloader.sh

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

    Kamil ist wohl jetzt mit dem Build so weit zufrieden 😉 Ich wüßte auch nicht wo es jetzt noch richtig klemmt. Eine Sache funktioniert noch nicht perfekt.

    PXE Boot USB3 Boot

    Aber Kamil hat im IRC geschrieben, das er das als nächstes in Angriff nehmen will.

  • FrankMF

    Lakka Image

    Images
    2
    0 Stimmen
    2 Beiträge
    824 Aufrufe
    FrankMF

    Lakka 2.2 Christmas Release

    lakka.png

    Quelle: http://www.lakka.tv/articles/2018/12/24/lakka-22-christmas-release/

  • FrankMF

    Recover Button

    Hardware
    2
    0 Stimmen
    2 Beiträge
    793 Aufrufe
    FrankMF

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

    Images 0.7.x

    Images
    22
    0 Stimmen
    22 Beiträge
    3k Aufrufe
    FrankMF

    Ayufan Images nutzen

    user: rock64 pw: rock64
  • FrankMF

    ROCKPro64 - Wo stehen wir?

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

    stretch-minimal-rockpro64

    Verschoben Linux
    3
    0 Stimmen
    3 Beiträge
    988 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

    Android 7.1.2 Stock Image using RK Flash tool [eMMC Boot] [20180518]

    Verschoben Android
    1
    0 Stimmen
    1 Beiträge
    722 Aufrufe
    Niemand hat geantwortet