Skip to content
linux-nerds.org

linux-nerds.org
  1. Übersicht
  2. Pine64
  3. ROCKPro64
  4. Images
  5. Linux
  6. Debian Minimal von Mr.Fixit2001

Debian Minimal von Mr.Fixit2001

Linux
  • FrankMF

    Das erste Image mit funktionierendem WiFi !

    Aus dem Readme

    MrFixIt's custom kernel which has been optimized for usage for retro-gaming and 4k high definition media playback. It also allows for the use of Wifi, Bluetooth, and PCIe all at the same time.

    Ja, leider bekomme ich das so nicht ans Laufen. Alle meine PCIe-Karten funktionieren nicht und produzieren meistens irgendeine Kernel-Panic. Habe Mr.Fixit eine Menge Logs geschickt, mal sehen ob sie das Problem gefixt bekommen und es dann hoffentlich in allen Images funktioniert.

    Quelle: https://github.com/mrfixit2001/debian_builds/releases

    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

    Neue Version

    • Supports ROCK64 Rev 3 Booting from SD Card
    • AUFS drivers embedded into kernel
    • LOTS of additional mainline back-ports and custom fixes
    • Improved Networking Performance
    • Additional drivers included in kernel, including (but not limited to):
      • LOTS of networking stuff, such as VLAN and IPv6
      • Requirements for DOCKER containers
      • RAID support

    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

    Und wieder ein paar Verbesserungen

    UPDATE May 19, 2019 - Added RockPro64 Release - Includes same Updates as Rock64, plus:

    • Suspend and Resume support is now included
    • CDN-DP firmware loading fixed
    • Additional PCIe driver fixes - Gen2 training now works
    • Additional Intel PCIe drivers

    May 14, 2019 - ROCK64:

    • ROCK64 Rev 3 Booting from SD Card Fixed
      * AUFS drivers embedded into kernel
      * LOTS of additional mainline back-ports and custom fixes
      * Improved Networking Performance
      * Additional drivers included in kernel, including (but not limited to):
      * LOTS of networking stuff, such as VLAN and IPv6
      * Requirements for DOCKER containers
      * RAID support

    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

    Release 190531 - Updated Debian Minimal Release

    • Kernel Updated to 4.4.180
    • Additional Kernel Fixes
    • U-Boot patched to fix weird issue where only some EMMC modules will not boot

    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

  • T

    OpenSuse auf RockPro64 V2.1

    Linux
    3
    0 Stimmen
    3 Beiträge
    211 Aufrufe
    T

    Bootet auch nichtg durch. Ist langsamer beim Bootversuch als mein Amiga von Diskette und gibt dann irgendwann etwas von "Bug Kernel image not alligned to 64k" aus.

    Wo kann ich ein 5er Image mit ayufan Kernel runterladen? Das waren die Einzigen, die wirklich zuverlässig sind. Selbst mein Fedora auf dem Odroid H2+ spuckt beim Booten etwas von Page Table State Bugs aus bootet aber durch. Und nachdem ich den Audio Silent Stream abgestellt habe, kann ich auch den Monitor mit meinem KVM Switch umschalten.

    Ich glaube, ich probiere mal wieder ein BSD, bis ich Antwort von Dir habe.

  • S

    Scanner unterLinux Mint 20.1.

    Linux
    7
    0 Stimmen
    7 Beiträge
    1k Aufrufe
    T

    @frankm
    Ja, das war die Fehlermeldung. Die Driver Plug-in installation habe ich vielfach probiert, konnte jedoch kein Plug-in herunterladen. Heute früh verlangte Mint eine Aktualisierung für hplib. Nach der Installation probierte ich erneut das Driver Plug-in zu installieren und da hat es endlich funktioniert. >>>> Problem gelöst!

  • S

    FAN control OMV Auyfan 0.10.12: gitlab-ci-linux-build-184, Kernel 5.6

    Linux
    12
    1 Stimmen
    12 Beiträge
    1k Aufrufe
    M

    Hi,

    since I'm currently change my rockpro64 setup I came across this.

    With the kernel from ayufan you need to set PWM_CTL to

    /sys/devices/platform/pwm-fan/hwmon/hwmon3/pwm1

    for my self compiled one I need

    /sys/devices/platform/pwm-fan/hwmon/hwmon0/pwm1

    But I got it only working with one entry for PWM_CTL e.g.

    PWM_CTL = "/sys/devices/platform/pwm-fan/hwmon/hwmon0/pwm1",

    after that you need to start ats again

    sudo systemctl stop ats sudo systemctl start ats

    initially the fan should start immediately for a short period of time.

    In case it is even a different one on your kernel you can find the right one using this command.

    sudo find /sys -name pwm1 | grep hwmon

    So far I'm not sure which kernel parameter or modul changes this.

    Martin

  • FrankMF

    Armbian Image

    Linux
    23
    0 Stimmen
    23 Beiträge
    2k Aufrufe
    F

    Hi @FrankM ,

    danke dir. Richtig, falschen Link zum Ayufan-Image gepostet.

    Ich bin gerade am ersten Testen mit dem 4.4er Armbian. Auf den ersten Blick scheint alles gut zu laufen. Positiv ist mir gleich einmal die I/O aufgefallen (128gb Samsung Evo Plus), offensichtlich kann man diese gut ausreizen. Zudem bin ich ebenso vom armbian-config begeistert, Plex und OMV laufen prima. Bis jetzt hab ich mich mit armbian eher mit nanopi&co herumgeschlagen, wo das kein Thema war.

    Leider habe ich offensichtlich vergessen die PCIe-Sata mitzubestellen, insofern musste ich mir nun eine beim großen A bestellen.

    Ich berichte dann gerne ausführlich darüber sobald bei mir alles läuft.

    Grüße,
    Flow

  • FrankMF

    Mainline Kernel 4.18.0-rc3

    Linux
    1
    0 Stimmen
    1 Beiträge
    961 Aufrufe
    Niemand hat geantwortet
  • 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
  • FrankMF

    bionic-lxde-rockpro64

    Verschoben Linux
    2
    0 Stimmen
    2 Beiträge
    913 Aufrufe
    FrankMF
    Neue Version 0.7.3 USB2

    Funktastur und Maus funktioniert.

    LED's

    Weiße LED leuchtet dauerhaft nach dem Starten

    Youtube

    Video läuft, aber nach einiger Zeit startet das System neu. Sieht nach Grafiktreiber aus. ALSA hat auch ein Problem, kein Ton. Aber das ist erst mal völlig unwichtig. Erst mal muss die Hardware laufen.

    0_1527276353347_Desktop.jpg

  • FrankMF

    bionic-containers-rockpro64

    Verschoben Linux
    2
    0 Stimmen
    2 Beiträge
    902 Aufrufe
    FrankMF

    Ich habe das jetzt mal endlich getestet 🙂

    https://forum.frank-mankel.org/topic/296/rockpro64-docker-image