Search the Community

Hello fellow Armbian folk, I've been a happy armbian user for many years. Recently, I've been trying to upgrade to bookworm from bullseye on my cubietruck, however have been hampered by Hash Sum mismatch errors from multiple armbian mirrors. I have followed all instructions on clearing the /var/lib/apt/files, apt clean, but nothing seems to help. I've tried multiple armbian mirrors with no luck. So now I'm seeking some community support.

Sorry, don't have the Armbianmonitor info handy but wanted to get this started... I'm trying to bring up a Libre Renegade RK3328-CC for use as a media center. Armbian's performance is absolutely wonderful compared to the other builds I've tried on this box. Unfortunately, I want the HDMI output going to a Samsung Frame TV, and resolution negotiation fails badly -- I get obvious rasters with black between them, nowhere near the 4K that this TV model is capable of and not even a smooth conversion (Note that the eyes here suggests that the black line is occurring every third raster or something like that...) What information I have gathered so far: TV: Samsung 43" “The Frame”, model QN43LS03BAFXZA Firmware T-PTMAKVC-1622.4, BT-S 4K native resolution, but should be able to upconvert edid-decode (hex): 00 ff ff ff ff ff ff 00 4c 2d 7f 72 00 0e 00 01 01 20 01 03 80 5f 36 78 0a b3 61 ab 4f 46 a8 27 0b 50 54 bd ef 80 71 4f 81 c0 81 00 81 80 95 00 a9 c0 b3 00 d1 c0 04 74 00 30 f2 70 5a 80 b0 58 8a 00 50 1d 74 00 00 1e 56 5e 00 a0 a0 a0 29 50 30 20 35 00 50 1d 74 00 00 1a 00 00 00 fd 00 18 4b 0f 51 1e 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 41 4d 53 55 4e 47 0a 20 20 20 20 20 01 9f 02 03 51 f0 52 5f 10 1f 04 13 05 14 20 21 22 5d 5e 62 64 07 16 03 12 2f 0d 57 07 09 07 07 15 07 50 57 07 01 67 54 03 83 0f 00 00 e2 00 4f e3 05 c3 01 6e 03 0c 00 30 00 b8 44 20 00 80 01 02 03 04 e3 06 0d 01 e5 0e 60 61 65 66 e5 01 8b 84 90 01 02 3a 80 18 71 38 2d 40 58 2c 45 00 50 1d 74 00 00 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ea Block 0, Base EDID: EDID Structure Version & Revision: 1.3 Vendor & Product Identification: Manufacturer: SAM Model: 29311 Serial Number: 16780800 Made in: week 1 of 2022 Basic Display Parameters & Features: Digital display Maximum image size: 95 cm x 54 cm Gamma: 2.20 RGB color display First detailed timing is the preferred timing Color Characteristics: Red : 0.6699, 0.3115 Green: 0.2734, 0.6591 Blue : 0.1533, 0.0449 White: 0.3125, 0.3291 Established Timings I & II: IBM : 720x400 70.081663 Hz 9:5 31.467 kHz 28.320000 MHz DMT 0x04: 640x480 59.940476 Hz 4:3 31.469 kHz 25.175000 MHz Apple : 640x480 66.666667 Hz 4:3 35.000 kHz 30.240000 MHz DMT 0x05: 640x480 72.808802 Hz 4:3 37.861 kHz 31.500000 MHz DMT 0x06: 640x480 75.000000 Hz 4:3 37.500 kHz 31.500000 MHz DMT 0x09: 800x600 60.316541 Hz 4:3 37.879 kHz 40.000000 MHz DMT 0x0a: 800x600 72.187572 Hz 4:3 48.077 kHz 50.000000 MHz DMT 0x0b: 800x600 75.000000 Hz 4:3 46.875 kHz 49.500000 MHz Apple : 832x624 74.551266 Hz 4:3 49.726 kHz 57.284000 MHz DMT 0x10: 1024x768 60.003840 Hz 4:3 48.363 kHz 65.000000 MHz DMT 0x11: 1024x768 70.069359 Hz 4:3 56.476 kHz 75.000000 MHz DMT 0x12: 1024x768 75.028582 Hz 4:3 60.023 kHz 78.750000 MHz DMT 0x24: 1280x1024 75.024675 Hz 5:4 79.976 kHz 135.000000 MHz Apple : 1152x870 75.061550 Hz 192:145 68.681 kHz 100.000000 MHz Standard Timings: DMT 0x15: 1152x864 75.000000 Hz 4:3 67.500 kHz 108.000000 MHz DMT 0x55: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz DMT 0x1c: 1280x800 59.810326 Hz 16:10 49.702 kHz 83.500000 MHz DMT 0x23: 1280x1024 60.019740 Hz 5:4 63.981 kHz 108.000000 MHz DMT 0x2f: 1440x900 59.887445 Hz 16:10 55.935 kHz 106.500000 MHz DMT 0x53: 1600x900 60.000000 Hz 16:9 60.000 kHz 108.000000 MHz (RB) DMT 0x3a: 1680x1050 59.954250 Hz 16:10 65.290 kHz 146.250000 MHz DMT 0x52: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz Detailed Timing Descriptors: DTD 1: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz (1872 mm x 1053 mm) Hfront 176 Hsync 88 Hback 296 Hpol P Vfront 8 Vsync 10 Vback 72 Vpol P DTD 2: 2560x1440 59.950550 Hz 16:9 88.787 kHz 241.500000 MHz (1872 mm x 1053 mm) Hfront 48 Hsync 32 Hback 80 Hpol P Vfront 3 Vsync 5 Vback 33 Vpol N Display Range Limits: Monitor ranges (GTF): 24-75 Hz V, 15-81 kHz H, max dotclock 300 MHz Display Product Name: ‘SAMSUNG’ Extension blocks: 1 Checksum: 0x9f Block 1, CTA-861 Extension Block: Revision: 3 Underscans IT Video Formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 Native detailed modes: 0 Video Data Block: VIC 95: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz VIC 16: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz VIC 31: 1920x1080 50.000000 Hz 16:9 56.250 kHz 148.500000 MHz VIC 4: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz VIC 19: 1280x720 50.000000 Hz 16:9 37.500 kHz 74.250000 MHz VIC 5: 1920x1080i 60.000000 Hz 16:9 33.750 kHz 74.250000 MHz VIC 20: 1920x1080i 50.000000 Hz 16:9 28.125 kHz 74.250000 MHz VIC 32: 1920x1080 24.000000 Hz 16:9 27.000 kHz 74.250000 MHz VIC 33: 1920x1080 25.000000 Hz 16:9 28.125 kHz 74.250000 MHz VIC 34: 1920x1080 30.000000 Hz 16:9 33.750 kHz 74.250000 MHz VIC 93: 3840x2160 24.000000 Hz 16:9 54.000 kHz 297.000000 MHz VIC 94: 3840x2160 25.000000 Hz 16:9 56.250 kHz 297.000000 MHz VIC 98: 4096x2160 24.000000 Hz 256:135 54.000 kHz 297.000000 MHz VIC 100: 4096x2160 30.000000 Hz 256:135 67.500 kHz 297.000000 MHz VIC 7: 1440x480i 59.940060 Hz 16:9 15.734 kHz 27.000000 MHz VIC 22: 1440x576i 50.000000 Hz 16:9 15.625 kHz 27.000000 MHz VIC 3: 720x480 59.940060 Hz 16:9 31.469 kHz 27.000000 MHz VIC 18: 720x576 50.000000 Hz 16:9 31.250 kHz 27.000000 MHz Audio Data Block: Linear PCM: Max channels: 6 Supported sample rates (kHz): 192 96 48 44.1 32 Supported sample sizes (bits): 24 20 16 Linear PCM: Max channels: 2 Supported sample rates (kHz): 48 44.1 32 Supported sample sizes (bits): 24 20 16 AC-3: Max channels: 6 Supported sample rates (kHz): 48 44.1 32 Maximum bit rate: 640 kb/s Enhanced AC-3 (DD+): Max channels: 8 Supported sample rates (kHz): 48 44.1 32 Supports Joint Object Coding MAT (MLP): Max channels: 8 Supported sample rates (kHz): 192 96 48 Supports Dolby TrueHD, object audio PCM and channel-based PCM Hash calculation not required for object audio PCM or channel-based PCM Speaker Allocation Data Block: FL/FR - Front Left/Right LFE1 - Low Frequency Effects 1 FC - Front Center BL/BR - Back Left/Right Video Capability Data Block: YCbCr quantization: No Data RGB quantization: Selectable (via AVI Q) PT scan behavior: No Data IT scan behavior: Supports both over- and underscan CE scan behavior: Supports both over- and underscan Colorimetry Data Block: xvYCC601 xvYCC709 BT2020YCC BT2020RGB Reserved MD0 Vendor-Specific Data Block (HDMI), OUI 00-0C-03: Source physical address: 3.0.0.0 Supports_AI DC_36bit DC_30bit DC_Y444 Maximum TMDS clock: 340 MHz Extended HDMI video details: HDMI VICs: HDMI VIC 1: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz HDMI VIC 2: 3840x2160 25.000000 Hz 16:9 56.250 kHz 297.000000 MHz HDMI VIC 3: 3840x2160 24.000000 Hz 16:9 54.000 kHz 297.000000 MHz HDMI VIC 4: 4096x2160 24.000000 Hz 256:135 54.000 kHz 297.000000 MHz HDR Static Metadata Data Block: Electro optical transfer functions: Traditional gamma - SDR luminance range SMPTE ST2084 Hybrid Log-Gamma Supported static metadata descriptors: Static metadata type 1 YCbCr 4:2:0 Video Data Block: VIC 96: 3840x2160 50.000000 Hz 16:9 112.500 kHz 594.000000 MHz VIC 97: 3840x2160 60.000000 Hz 16:9 135.000 kHz 594.000000 MHz VIC 101: 4096x2160 50.000000 Hz 256:135 112.500 kHz 594.000000 MHz VIC 102: 4096x2160 60.000000 Hz 256:135 135.000 kHz 594.000000 MHz Vendor-Specific Video Data Block (HDR10+), OUI 90-84-8B: Application Version: 1 Detailed Timing Descriptors: DTD 3: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz (1872 mm x 1053 mm) Hfront 88 Hsync 44 Hback 148 Hpol P Vfront 4 Vsync 5 Vback 36 Vpol P Checksum: 0xea I understand that Armbian is an experimental build and this combination may simply not work.... but if there's anything I can try to do to help the driver and monitor reconcile with each other, or to help you debug this, please let me know. (BTW, I don't mind the security timeout/rechecking on this webform, but having it drag focus back to that checkbox is somewhat disruptive.)

artifact-uboot: include BOOTCONFIG in u-boot artifact version hash artifact-uboot: include BOOTCONFIG in u-boot artifact version hash HOW did we get this far without this? should cause rebuild of all u-boots, hopefully View the full article

Unfortunately yes Igor, the issue is still happening. Perhaps, I could try another armbian mirror. My steps included clearing the /var/lib/apt/lists directory, sudo apt clean, sudo apt update (all fine), sudo apt upgrade --no-new-pkgs (resulting in armbian Hash Sum mismatch errors)

I was observing similar issues on four systems, two Odroid HC1 and two Odroid MC1, all running Armbian Odroid XU4 image. I think they were all upgraded from Bullseye to Bookworm at some point, but not recently. They run updates once per day, and it looks like the first failure was 2 days and 16 hours before time of writing. I observed "Hash Sum mismatch" errors and 404 errors, similar to OP, on each host, yesterday. Automatic updates started succeeding again about an hour ago. My assessment is that one more more mirrors were probably broken for a few days, and just got fixed. On the other hand, the openmediavault forum has thread 51654 on what looks like similar errors, and they seem to have recognized a problem with this upgrade path and applied a known fix to resolve. If you don't find that updates are suddenly working, now, I would check whether their solution applies to your situation.

Thanks all, I did try the suggested upgrade fix below, but unfortunately no luck with my armbian upgrade. The armbian files that fail Hash Sum mismatch are: Err:1 https://au.sbcmirror.org/armbian/apt bookworm/main armhf base-files armhf 24.2.1-12.4+deb12u5-bookworm Err:2 https://au.sbcmirror.org/armbian/apt bookworm/main armhf armbian-config all 24.2.1 While other armbian download files result in the following: Err:3 http://au.sbcmirror.org/armbian/apt bookworm/main armhf armbian-firmware-full all 24.2.1 File has unexpected size (433621460 != 433621492). Mirror sync in progress? [IP: 95.111.218.236 443] Err:8 https://au.sbcmirror.org/armbian/apt bookworm/main armhf linux-dtb-current-sunxi armhf 24.2.1 404 Not Found [IP: 95.111.218.236 443] E: Failed to fetch https://au.sbcmirror.org/armbian/apt/pool/main/b/base-files/base-files_24.2.1-12.4%2bdeb12u5-bookworm_armhf__1-bookworm-1armbian1-Ba4f9-U12.4--deb12u5-R55fa.deb Hash Sum mismatch Note: all the debian bookmark mirror files were all fine.

Hello, I apologize for my bad English. I have a NanoPi R6S and a NanoPC T6. Both Nano devices have Armbian images. Both devices use a processor: CPU Model: Rockchip RK3588 Number of Cores: Quad-core ARM Cortex-A76 + Quad Core Cortex-A55 Frequency: Cortex-A76 (up to 2.4GHz), Cortex-A55 (up to 1.8GHz) A few things struck me On NanoPi R6S in the dts file, the frequency of A76 cores is up to 2.4GHz you can see the frequencies at which each core works cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 2016000 2208000 2352000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 2016000 2208000 2352000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 2016000 2208000 2256000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 2016000 2208000 2256000 governors: cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_governors conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil On NanoPi T6 in the dts file, the frequency of A76 cores is up to 2.2GHz - I fixed it /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies - this is missing. /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_governors - this is missing, having instead cat /sys/devices/system/cpu/cpuidle/available_governors ladder menu teo NanoPi R6S is currently running kernel 5.10.110-rockchip-rk3588 NanoPC T6 is currently running kernel 6.8.0-rc6-edge-rockchip-rk3588 I also noticed differences in CPU cache. NanoPI R6S Architecture: aarch64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 3 Vendor ID: ARM Model: 0 Model name: Cortex-A55 Stepping: r2p0 CPU max MHz: 2352.0000 CPU min MHz: 408.0000 BogoMIPS: 48.00 L1d cache: 256 KiB L1i cache: 256 KiB L2 cache: 1 MiB L3 cache: 3 MiB Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Vulnerability Spectre v1: Mitigation; __user pointer sanitization Vulnerability Spectre v2: Vulnerable: Unprivileged eBPF enabled Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp NanoPC T6 Architecture: aarch64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Vendor ID: ARM Model name: Cortex-A55 Model: 0 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 Stepping: r2p0 BogoMIPS: 48.00 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp Model name: Cortex-A76 Model: 0 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 Stepping: r4p0 BogoMIPS: 48.00 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp Caches (sum of all): L1d: 384 KiB (8 instances) L1i: 384 KiB (8 instances) L2: 2.5 MiB (8 instances) L3: 3 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-7 Vulnerabilities: Gather data sampling: Not affected Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec rstack overflow: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1: Mitigation; __user pointer sanitization Spectre v2: Vulnerable: Unprivileged eBPF enabled Srbds: Not affected Tsx async abort: Not affected When using the command: cpufreq-info NanoPI R6S cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:76.72%, 600 MHz:6.69%, 816 MHz:0.31%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:16.29% (11087717) analyzing CPU 1: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:76.72%, 600 MHz:6.69%, 816 MHz:0.31%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:16.29% (11087717) analyzing CPU 2: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:76.72%, 600 MHz:6.69%, 816 MHz:0.31%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:16.29% (11087717) analyzing CPU 3: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:76.72%, 600 MHz:6.69%, 816 MHz:0.31%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:16.29% (11087717) analyzing CPU 4: driver: cpufreq-dt CPUs which run at the same hardware frequency: 4 5 CPUs which need to have their frequency coordinated by software: 4 5 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.35 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.35 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.35 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:85.33%, 600 MHz:1.13%, 816 MHz:0.40%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:0.00%, 2.21 GHz:0.00%, 2.35 GHz:13.14% (2586948) analyzing CPU 5: driver: cpufreq-dt CPUs which run at the same hardware frequency: 4 5 CPUs which need to have their frequency coordinated by software: 4 5 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.35 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.35 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.35 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:85.33%, 600 MHz:1.13%, 816 MHz:0.40%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:0.00%, 2.21 GHz:0.00%, 2.35 GHz:13.14% (2586948) analyzing CPU 6: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.26 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:92.30%, 600 MHz:0.44%, 816 MHz:0.16%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:0.00%, 2.21 GHz:0.00%, 2.26 GHz:7.10% (1012245) analyzing CPU 7: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.26 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:92.30%, 600 MHz:0.44%, 816 MHz:0.16%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:0.00%, 2.21 GHz:0.00%, 2.26 GHz:7.10% (1012245) NanoPC T6 cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 4: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 5: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 6: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 7: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. The CPU driver appears to be missing. When using the command: cpu-info NanoPI R6S cpu-info Packages: 0: Unknown Microarchitectures: 4x Cortex-A76 4x Cortex-A55 Cores: 0: 1 processor (0), ARM Cortex-A76 1: 1 processor (1), ARM Cortex-A76 2: 1 processor (2), ARM Cortex-A76 3: 1 processor (3), ARM Cortex-A76 4: 1 processor (4), ARM Cortex-A55 5: 1 processor (5), ARM Cortex-A55 6: 1 processor (6), ARM Cortex-A55 7: 1 processor (7), ARM Cortex-A55 NanoPC T6 cpu-info Packages: 0: Unknown Microarchitectures: 8x Cortex-A55 Cores: 0: 1 processor (0), ARM Cortex-A55 1: 1 processor (1), ARM Cortex-A55 2: 1 processor (2), ARM Cortex-A55 3: 1 processor (3), ARM Cortex-A55 4: 1 processor (4), ARM Cortex-A55 5: 1 processor (5), ARM Cortex-A55 6: 1 processor (6), ARM Cortex-A55 7: 1 processor (7), ARM Cortex-A55 My question is the following. Are the differences because of the dts file or because of the kernel. Anyone else using a NanoPC T6 and would like to help fix this? At the moment, I'm not using NanoPC T6 as a server yet, and I have the opportunity to experiment. It will be used as a small server for graphics, tftp and others. Is there any additional information needed. Regards,

When I run the Linux kernel on the Odroid XU4 board, it enters a loop with this error during boot: U-Boot 2017.05-00008-g6a9ddb8303-dirty (May 19 2020 - 19:48:01 +0900) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: xu4 DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 MMC Device 0 ( SD ): 29.7 GiB mmc_init: -5, time 4 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 reading /boot.ini 2401 bytes read in 4 ms (585.9 KiB/s) ## Executing script at 43e00000 reading config.ini 6911 bytes read in 5 ms (1.3 MiB/s) ini: Imported macaddr as 00:1e:06:61:7a:39 ini: Imported vout as hdmi ini: Imported HPD as true ini: Imported cecenable as false ini: Imported disable_vu7 as false ini: Imported ddr_freq as 825 ini: Imported overlay_resize as 16384 ini: Imported overlay_profile as ini: Imported overlays as spi0 i2c0 i2c1 uart0 No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! reading zImage 7299952 bytes read in 490 ms (14.2 MiB/s) reading exynos5422-odroidxu4.dtb 88559 bytes read in 11 ms (7.7 MiB/s) reading overlays/spi0.dtbo 691 bytes read in 5 ms (134.8 KiB/s) reading overlays/i2c0.dtbo 224 bytes read in 5 ms (43 KiB/s) reading overlays/i2c1.dtbo 226 bytes read in 5 ms (43.9 KiB/s) reading overlays/uart0.dtbo 227 bytes read in 6 ms (36.1 KiB/s) Kernel image @ 0x40008000 [ 0x000000 - 0x6f6370 ] ## Flattened Device Tree blob at 44000000 Booting using the fdt blob at 0x44000000 reserving fdt memory region: addr=44000000 size=2c000 Using Device Tree in place at 44000000, end 4402efff Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x100 [ 0.000000] Linux version 6.1.77+ (odroid@odroid) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP PREEMPT Wed Mar 6 17:56:35 -03 2024 [ 0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=30c5387d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: Hardkernel ODROID XU4 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] cma: Reserved 128 MiB at 0x00000000b6800000 [ 0.000000] Samsung CPU ID: 0xe5422001 [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000040000000-0x000000006fffffff] [ 0.000000] HighMem [mem 0x0000000070000000-0x00000000be9fffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000040000000-0x00000000be9fffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000be9fffff] [ 0.000000] Running under secure firmware. [ 0.000000] percpu: Embedded 17 pages/cpu s39124 r8192 d22316 u69632 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 516928 [ 0.000000] Kernel command line: console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes net.ifnames=0 HPD=true vout=hdmi e [ 0.000000] hdmi: using HDMI mode [ 0.000000] Unknown kernel command line parameters "false HPD=true vout=hdmi", will be passed to user space. [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] Memory: 1903668K/2074624K available (12288K kernel code, 1139K rwdata, 2940K rodata, 2048K init, 363K bss, 39884K reserved, 131072K cma-reserved, 1157120K highmem) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.000000] trace event string verifier disabled [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] GIC: Using split EOI/Deactivate mode [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.000000] Switching to timer-based delay loop, resolution 41ns [ 0.000000] clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns [ 0.000002] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns [ 0.000032] genirq: irq_chip COMBINER did not update eff. affinity mask of irq 57 [ 0.001509] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.001535] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.001555] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.001572] Ignoring duplicate/late registration of read_current_timer delay [ 0.002351] Console: colour dummy device 80x30 [ 0.003109] printk: console [tty1] enabled [ 0.003176] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000) [ 0.003223] CPU: Testing write buffer coherency: ok [ 0.003313] pid_max: default: 32768 minimum: 301 [ 0.003464] LSM: Security Framework initializing [ 0.003658] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.003711] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.005467] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100 [ 0.006882] cblist_init_generic: Setting adjustable number of callback queues. [ 0.006928] cblist_init_generic: Setting shift to 3 and lim to 1. [ 0.007116] cblist_init_generic: Setting adjustable number of callback queues. [ 0.007151] cblist_init_generic: Setting shift to 3 and lim to 1. [ 0.007359] Setting up static identity map for 0x40200000 - 0x40200060 [ 0.007711] ARM CCI driver probed [ 0.008305] Exynos MCPM support installed [ 0.008707] rcu: Hierarchical SRCU implementation. [ 0.008734] rcu: Max phase no-delay instances is 1000. [ 0.010012] smp: Bringing up secondary CPUs ... [ 0.011171] CPU1: thread -1, cpu 1, socket 1, mpidr 80000101 [ 0.012478] CPU2: thread -1, cpu 2, socket 1, mpidr 80000102 [ 0.013707] CPU3: thread -1, cpu 3, socket 1, mpidr 80000103 [ 0.014902] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.014919] CPU4: detected I-Cache line size mismatch, workaround enabled [ 0.014927] CPU4: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.015018] CPU4: Spectre BHB: enabling loop workaround for all CPUs [ 0.016286] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.016300] CPU5: detected I-Cache line size mismatch, workaround enabled [ 0.016307] CPU5: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.017624] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.017638] CPU6: detected I-Cache line size mismatch, workaround enabled [ 0.017645] CPU6: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.018922] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.018937] CPU7: detected I-Cache line size mismatch, workaround enabled [ 0.018945] CPU7: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.019180] smp: Brought up 1 node, 8 CPUs [ 0.019244] SMP: Total of 8 processors activated (384.00 BogoMIPS). [ 0.019276] CPU: All CPU(s) started in HYP mode. [ 0.019297] CPU: Virtualization extensions available. [ 0.020752] devtmpfs: initialized [ 0.042523] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 [ 0.042807] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.042850] futex hash table entries: 2048 (order: 5, 131072 bytes, linear) [ 0.045974] pinctrl core: initialized pinctrl subsystem [ 0.048866] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.052562] DMA: preallocated 2048 KiB pool for atomic coherent allocations [ 0.054296] audit: initializing netlink subsys (disabled) [ 0.054571] audit: type=2000 audit(0.050:1): state=initialized audit_enabled=0 res=1 [ 0.055157] thermal_sys: Registered thermal governor 'step_wise' [ 0.055436] cpuidle: using governor menu [ 0.055910] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.055941] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.185987] EXYNOS5420 PMU initialized [ 0.292725] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible. [ 0.294707] fbcon: Taking over console [ 0.296476] iommu: Default domain type: Translated [ 0.296501] iommu: DMA domain TLB invalidation policy: lazy mode [ 0.296909] usbcore: registered new interface driver usbfs [ 0.296979] usbcore: registered new interface driver hub [ 0.297050] usbcore: registered new device driver usb [ 0.297807] s3c-i2c 12c70000.i2c: slave address 0x00 [ 0.297837] s3c-i2c 12c70000.i2c: bus frequency set to 378 KHz [ 0.298170] s3c-i2c 12c70000.i2c: i2c-0: S3C I2C adapter [ 0.298383] s3c-i2c 12c80000.i2c: slave address 0x00 [ 0.298412] s3c-i2c 12c80000.i2c: bus frequency set to 65 KHz [ 0.298719] s3c-i2c 12c80000.i2c: i2c-2: S3C I2C adapter [ 0.299209] mc: Linux media interface: v0.10 [ 0.299295] videodev: Linux video capture interface: v2.00 [ 0.299921] Advanced Linux Sound Architecture Driver Initialized. [ 0.301010] clocksource: Switched to clocksource mct-frc [ 0.301481] VFS: Disk quotas dquot_6.6.0 [ 0.301559] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.315803] NET: Registered PF_INET protocol family [ 0.316073] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.317886] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear) [ 0.317937] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.318036] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) [ 0.318132] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear) [ 0.318434] TCP: Hash tables configured (established 8192 bind 8192) [ 0.318557] UDP hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.318617] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.318871] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.318931] NET: Registered PF_XDP protocol family [ 0.320817] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available [ 0.322010] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available [ 0.324097] Initialise system trusted keyrings [ 0.324437] workingset: timestamp_bits=14 max_order=19 bucket_order=5 [ 0.333908] romfs: ROMFS MTD (C) 2007 Red Hat, Inc. [ 0.421548] NET: Registered PF_ALG protocol family [ 0.421584] Key type asymmetric registered [ 0.421605] Asymmetric key parser 'x509' registered [ 0.421839] bounce: pool size: 64 pages [ 0.421992] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247) [ 0.422397] io scheduler mq-deadline registered [ 0.422425] io scheduler kyber registered [ 0.422681] io scheduler bfq registered [ 0.424520] samsung-pinctrl 13400000.pinctrl: Failed to create device link (0x180) with soc [ 0.426837] samsung-usb2-phy 12130000.phy: supply vbus not found, using dummy regulator [ 0.427839] exynos5_usb3drd_phy 12100000.phy: supply vbus not found, using dummy regulator [ 0.428032] exynos5_usb3drd_phy 12100000.phy: supply vbus-boost not found, using dummy regulator [ 0.428460] exynos5_usb3drd_phy 12500000.phy: supply vbus not found, using dummy regulator [ 0.428634] exynos5_usb3drd_phy 12500000.phy: supply vbus-boost not found, using dummy regulator [ 0.436864] dma-pl330 3880000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.436898] dma-pl330 3880000.dma-controller: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6 [ 0.439976] dma-pl330 121a0000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.440008] dma-pl330 121a0000.dma-controller: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 0.443083] dma-pl330 121b0000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.443116] dma-pl330 121b0000.dma-controller: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 0.444270] dma-pl330 10800000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.444300] dma-pl330 10800000.dma-controller: DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32 [ 0.461998] dma-pl330 3880000.dma-controller: PM domain MAU will not be powered off [ 0.533568] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 0.536218] 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (irq = 124, base_baud = 0) is a S3C6400/10 [ 0.536771] 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 125, base_baud = 0) is a S3C6400/10 [ 1.553526] printk: console [ttySAC2] enabled [ 1.560131] exynos-trng 10830600.rng: Exynos True Random Number Generator. [ 1.567245] exynos-mixer 14450000.mixer: Adding to iommu group 0 [ 1.574772] exynos-drm-g2d 10850000.g2d: Adding to iommu group 1 [ 1.581147] exynos-rotator 11c00000.rotator: Adding to iommu group 2 [ 1.587248] exynos-scaler 12800000.scaler: Adding to iommu group 3 [ 1.593888] exynos-scaler 12810000.scaler: Adding to iommu group 4 [ 1.600295] exynos-scaler 12820000.scaler: Adding to iommu group 5 [ 1.607009] exynos-drm-gsc 13e00000.video-scaler: Adding to iommu group 6 [ 1.613211] exynos-drm-gsc 13e00000.video-scaler: drm gsc registered successfully. [ 1.620298] exynos-drm-gsc 13e10000.video-scaler: Adding to iommu group 7 [ 1.627466] exynos-drm-gsc 13e10000.video-scaler: drm gsc registered successfully. [ 1.652020] brd: module loaded [ 1.654773] usbcore: registered new device driver r8152-cfgselector [ 1.659902] usbcore: registered new interface driver r8152 [ 1.665405] usbcore: registered new interface driver cdc_ether [ 1.671186] usbcore: registered new interface driver cdc_subset [ 1.677065] usbcore: registered new interface driver r8153_ecm [ 1.685749] phy phy-12130000.phy.6: phy_power_on was called before phy_init [ 1.691276] exynos-ehci 12110000.usb: EHCI Host Controller [ 1.696714] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 1 [ 1.704845] exynos-ehci 12110000.usb: irq 133, io mem 0x12110000 [ 1.731064] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00 [ 1.735818] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 [ 1.743876] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.751068] usb usb1: Product: EHCI Host Controller [ 1.755880] usb usb1: Manufacturer: Linux 6.1.77+ ehci_hcd [ 1.761370] usb usb1: SerialNumber: 12110000.usb [ 1.766665] hub 1-0:1.0: USB hub found [ 1.769693] hub 1-0:1.0: 3 ports detected [ 1.774988] phy phy-12130000.phy.6: phy_power_on was called before phy_init [ 1.780583] exynos-ohci 12120000.usb: USB Host Controller [ 1.786000] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 2 [ 1.793806] exynos-ohci 12120000.usb: irq 133, io mem 0x12120000 [ 1.865293] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01 [ 1.872132] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.879280] usb usb2: Product: USB Host Controller [ 1.884074] usb usb2: Manufacturer: Linux 6.1.77+ ohci_hcd [ 1.889502] usb usb2: SerialNumber: 12120000.usb [ 1.894774] hub 2-0:1.0: USB hub found [ 1.897855] hub 2-0:1.0: 3 ports detected [ 1.904077] UDC core: dbgp: couldn't find an available UDC [ 1.908531] mousedev: PS/2 mouse device common for all mice [ 1.915382] i2c_dev: i2c /dev entries driver [ 1.943247] vdd_ldo9: Bringing 3300000uV into 3000000-3000000uV [ 1.960292] vddq_mmc2: Bringing 3300000uV into 2800000-2800000uV [ 1.979785] vdd_sd: Bringing 3300000uV into 2800000-2800000uV [ 2.049199] s5m-rtc s2mps14-rtc: registered as rtc0 [ 2.054487] s5m-rtc s2mps14-rtc: setting system clock to 2000-01-01T00:00:08 UTC (946684808) [ 2.061844] s2mps11-clk s2mps11-clk: DMA mask not set [ 2.076557] exynos-tmu 10060000.tmu: More trip points than supported by this TMU. [ 2.082622] exynos-tmu 10060000.tmu: 2 trip points should be configured in polling mode. [ 2.092426] exynos-tmu 10064000.tmu: More trip points than supported by this TMU. [ 2.098440] exynos-tmu 10064000.tmu: 2 trip points should be configured in polling mode. [ 2.108348] exynos-tmu 10068000.tmu: More trip points than supported by this TMU. [ 2.114407] exynos-tmu 10068000.tmu: 2 trip points should be configured in polling mode. [ 2.124320] exynos-tmu 1006c000.tmu: More trip points than supported by this TMU. [ 2.130338] exynos-tmu 1006c000.tmu: 2 trip points should be configured in polling mode. [ 2.140250] exynos-tmu 100a0000.tmu: More trip points than supported by this TMU. [ 2.146302] exynos-tmu 100a0000.tmu: 6 trip points should be configured in polling mode. [ 2.155544] s3c2410-wdt 101d0000.watchdog: watchdog inactive, reset disabled, irq disabled [ 2.163331] device-mapper: uevent: version 1.0.3 [ 2.167537] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com [ 2.191451] sdhci: Secure Digital Host Controller Interface driver [ 2.196199] sdhci: Copyright(c) Pierre Ossman [ 2.201064] Synopsys Designware Multimedia Card Interface Driver [ 2.208067] dwmmc_exynos 12220000.mmc: IDMAC supports 32-bit address mode. [ 2.208115] dwmmc_exynos 12200000.mmc: IDMAC supports 32-bit address mode. [ 2.220477] dwmmc_exynos 12220000.mmc: Using internal DMA controller. [ 2.224492] s5p-secss 10830000.sss: s5p-sss driver registered [ 2.226796] dwmmc_exynos 12220000.mmc: Version ID is 250a [ 2.232750] dwmmc_exynos 12200000.mmc: Using internal DMA controller. [ 2.234102] hid: raw HID events driver (C) Jiri Kosina [ 2.238124] dwmmc_exynos 12220000.mmc: DW MMC controller at irq 144,64 bit host data width,64 deep fifo [ 2.244291] dwmmc_exynos 12200000.mmc: Version ID is 250a [ 2.264162] dwmmc_exynos 12200000.mmc: DW MMC controller at irq 145,64 bit host data width,64 deep fifo [ 2.268759] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 2.275936] dwmmc_exynos 12200000.mmc: allocated mmc-pwrseq [ 2.292675] exynos-nocp: new NoC Probe device registered: 10ca1000.nocp [ 2.297970] exynos-nocp: new NoC Probe device registered: 10ca1400.nocp [ 2.304571] exynos-nocp: new NoC Probe device registered: 10ca1800.nocp [ 2.305514] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 2.312086] exynos-nocp: new NoC Probe device registered: 10ca1c00.nocp [ 2.327451] exynos-ppmu: new PPMU device registered 10d00000.ppmu (ppmu-event3-dmc0-0) [ 2.335102] exynos-ppmu: new PPMU device registered 10d10000.ppmu (ppmu-event3-dmc0-1) [ 2.342974] exynos-ppmu: new PPMU device registered 10d60000.ppmu (ppmu-event3-dmc1-0) [ 2.350839] exynos-ppmu: new PPMU device registered 10d70000.ppmu (ppmu-event3-dmc1-1) [ 2.361081] exynos5-dmc 10c20000.memory-controller: error -ENXIO: IRQ drex_0 not found [ 2.367518] exynos5-dmc 10c20000.memory-controller: error -ENXIO: IRQ drex_1 not found [ 2.375591] exynos5-dmc 10c20000.memory-controller: DMC initialized, in irq mode: 0 [ 2.384755] mmc_host mmc0: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0) [ 2.394797] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s [ 2.397011] mmc0: new ultra high speed SDR104 SDHC card at address aaaa [ 2.407340] NET: Registered PF_PACKET protocol family [ 2.409624] mmcblk0: mmc0:aaaa SE32G 29.7 GiB [ 2.412797] NET: Registered PF_KEY protocol family [ 2.422627] Key type dns_resolver registered [ 2.426187] mmcblk0: p1 p2 [ 2.426754] Registering SWP/SWPB emulation handler [ 2.434051] registered taskstats version 1 [ 2.437817] Loading compiled-in X.509 certificates [ 2.443116] Key type .fscrypt registered [ 2.446464] Key type fscrypt-provisioning registered [ 2.457336] Key type encrypted registered [ 2.588749] exynos-chipid 10000000.chipid: cpu0 opp0, freq: 1500 missing [ 2.594193] exynos-chipid 10000000.chipid: cpu4 opp0, freq: 2100 missing [ 2.600762] exynos-chipid 10000000.chipid: Exynos: CPU[EXYNOS5800] PRO_ID[0xe5422000] REV[0x1] Detected [ 2.617722] OF: graph: no port node found in /soc/hdmi@14530000 [ 2.624147] [drm] Exynos DRM: using 14450000.mixer device for DMA mapping operations [ 2.630520] exynos-drm exynos-drm: bound 14450000.mixer (ops 0xc0e7bc8c) [ 2.637165] exynos-drm exynos-drm: bound 14530000.hdmi (ops 0xc0e7c26c) [ 2.643884] exynos-drm-g2d 10850000.g2d: The Exynos G2D (ver 4.1) successfully registered. [ 2.651958] exynos-drm exynos-drm: bound 10850000.g2d (ops 0xc0e7d27c) [ 2.658441] exynos-rotator 11c00000.rotator: The exynos rotator has been probed successfully [ 2.666855] exynos-drm exynos-drm: bound 11c00000.rotator (ops 0xc0e7db08) [ 2.673723] exynos-scaler 12800000.scaler: The exynos scaler has been probed successfully [ 2.681842] exynos-drm exynos-drm: bound 12800000.scaler (ops 0xc0e7e250) [ 2.688607] exynos-scaler 12810000.scaler: The exynos scaler has been probed successfully [ 2.696755] exynos-drm exynos-drm: bound 12810000.scaler (ops 0xc0e7e250) [ 2.703526] exynos-scaler 12820000.scaler: The exynos scaler has been probed successfully [ 2.711662] exynos-drm exynos-drm: bound 12820000.scaler (ops 0xc0e7e250) [ 2.718396] exynos-drm-gsc 13e00000.video-scaler: The exynos gscaler has been probed successfully [ 2.727314] exynos-drm exynos-drm: bound 13e00000.video-scaler (ops 0xc0e7eb24) [ 2.734594] exynos-drm-gsc 13e10000.video-scaler: The exynos gscaler has been probed successfully [ 2.743425] exynos-drm exynos-drm: bound 13e10000.video-scaler (ops 0xc0e7eb24) [ 2.791131] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 2.838676] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 2.878753] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 2.907827] Console: switching to colour frame buffer device 180x56 [ 2.973325] exynos-drm exynos-drm: [drm] fb0: exynosdrmfb frame buffer device [ 2.984476] [drm] Initialized exynos 1.1.0 20180330 for exynos-drm on minor 0 [ 3.004351] mali 11800000.gpu: GPU identified as 0x0620 r0p1 status 0 [ 3.010719] mali 11800000.gpu: Protected mode not available [ 3.018316] mali 11800000.gpu: Probed as mali0 [ 3.026735] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller [ 3.030849] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 3 [ 3.039677] xhci-hcd xhci-hcd.8.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010 [ 3.048138] xhci-hcd xhci-hcd.8.auto: irq 153, io mem 0x12000000 [ 3.054235] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller [ 3.059294] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 4 [ 3.066981] xhci-hcd xhci-hcd.8.auto: Host supports USB 3.0 SuperSpeed [ 3.073679] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 [ 3.081733] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.088855] usb usb3: Product: xHCI Host Controller [ 3.093692] usb usb3: Manufacturer: Linux 6.1.77+ xhci-hcd [ 3.099147] usb usb3: SerialNumber: xhci-hcd.8.auto [ 3.105733] hub 3-0:1.0: USB hub found [ 3.108240] hub 3-0:1.0: 1 port detected [ 3.113412] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [ 3.120627] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01 [ 3.128666] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.135843] usb usb4: Product: xHCI Host Controller [ 3.140461] usb usb4: Manufacturer: Linux 6.1.77+ xhci-hcd [ 3.148036] usb usb4: SerialNumber: xhci-hcd.8.auto [ 3.153685] hub 4-0:1.0: USB hub found [ 3.157741] hub 4-0:1.0: 1 port detected [ 3.169399] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller [ 3.175224] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 5 [ 3.183781] xhci-hcd xhci-hcd.9.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010 [ 3.193572] xhci-hcd xhci-hcd.9.auto: irq 154, io mem 0x12400000 [ 3.200100] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller [ 3.205886] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 6 [ 3.213785] xhci-hcd xhci-hcd.9.auto: Host supports USB 3.0 SuperSpeed [ 3.220664] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 [ 3.229213] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.236762] usb usb5: Product: xHCI Host Controller [ 3.241897] usb usb5: Manufacturer: Linux 6.1.77+ xhci-hcd [ 3.247575] usb usb5: SerialNumber: xhci-hcd.9.auto [ 3.253145] hub 5-0:1.0: USB hub found [ 3.257072] hub 5-0:1.0: 1 port detected [ 3.261543] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM. [ 3.269904] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01 [ 3.278421] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.285801] usb usb6: Product: xHCI Host Controller [ 3.290803] usb usb6: Manufacturer: Linux 6.1.77+ xhci-hcd [ 3.292505] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 3.294925] usb usb6: SerialNumber: xhci-hcd.9.auto [ 3.314476] hub 6-0:1.0: USB hub found [ 3.318373] hub 6-0:1.0: 1 port detected [ 3.324905] s3c-rtc 101e0000.rtc: rtc disabled, re-enabling [ 3.330709] s3c-rtc 101e0000.rtc: registered as rtc1 [ 3.340796] exynos-bus: new bus device registered: soc:bus-wcore ( 88700 KHz ~ 532000 KHz) [ 3.345656] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 3.348273] exynos-bus: new bus device registered: soc:bus-noc ( 66600 KHz ~ 111000 KHz) [ 3.370263] exynos-bus: new bus device registered: soc:bus-fsys-apb (111000 KHz ~ 222000 KHz) [ 3.379488] exynos-bus: new bus device registered: soc:bus-fsys2 ( 75000 KHz ~ 200000 KHz) [ 3.388608] exynos-bus: new bus device registered: soc:bus-mfc ( 83250 KHz ~ 333000 KHz) [ 3.397524] exynos-bus: new bus device registered: soc:bus-gen ( 88700 KHz ~ 266000 KHz) [ 3.406667] exynos-bus: new bus device registered: soc:bus-peri ( 66600 KHz ~ 66600 KHz) [ 3.411109] usb 3-1: new high-speed USB device number 2 using xhci-hcd [ 3.419851] exynos-bus: new bus device registered: soc:bus-g2d ( 83250 KHz ~ 333000 KHz) [ 3.431814] exynos-bus: new bus device registered: soc:bus-g2d-acp ( 66500 KHz ~ 266000 KHz) [ 3.440249] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 3.440969] exynos-bus: new bus device registered: soc:bus-jpeg ( 75000 KHz ~ 300000 KHz) [ 3.460397] exynos-bus: new bus device registered: soc:bus-jpeg-apb ( 83250 KHz ~ 166500 KHz) [ 3.469573] exynos-bus: new bus device registered: soc:bus-disp1-fimd (120000 KHz ~ 200000 KHz) [ 3.478997] exynos-bus: new bus device registered: soc:bus-disp1 (120000 KHz ~ 300000 KHz) [ 3.487932] exynos-bus: new bus device registered: soc:bus-gscl-scaler (150000 KHz ~ 300000 KHz) [ 3.497582] exynos-bus: new bus device registered: soc:bus-mscl ( 84000 KHz ~ 666000 KHz) [ 3.508589] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 3.535680] ALSA device list: [ 3.539420] #0: ODROID-XU4 [ 3.544075] Waiting for root device UUID=e139ce78-9841-40fe-8823-96a304a09859... [ 3.605856] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=22.23 [ 3.615230] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.623491] usb 3-1: Product: USB2.0 Hub [ 3.628491] usb 3-1: Manufacturer: GenesysLogic [ 3.682358] hub 3-1:1.0: USB hub found [ 3.689564] hub 3-1:1.0: 2 ports detected [ 3.751499] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd [ 3.794759] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616, bcdDevice=22.23 [ 3.805887] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.815965] usb 4-1: Product: USB3.0 Hub [ 3.822775] usb 4-1: Manufacturer: GenesysLogic [ 3.858309] hub 4-1:1.0: USB hub found [ 3.863915] hub 4-1:1.0: 2 ports detected [ 4.061238] usb 3-1.1: new low-speed USB device number 3 using xhci-hcd [ 4.206144] usb 3-1.1: New USB device found, idVendor=046d, idProduct=c077, bcdDevice=72.00 [ 4.221958] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4.233307] usb 3-1.1: Product: USB Optical Mouse [ 4.238474] usb 3-1.1: Manufacturer: Logitech [ 4.371238] usb 6-1: new SuperSpeed USB device number 2 using xhci-hcd [ 4.391069] usb 3-1.2: new low-speed USB device number 4 using xhci-hcd [ 4.412822] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00 [ 4.422627] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 4.431336] usb 6-1: Product: USB 10/100/1000 LAN [ 4.437514] usb 6-1: Manufacturer: Realtek [ 4.443094] usb 6-1: SerialNumber: 000001000000 [ 4.536824] usb 3-1.2: New USB device found, idVendor=1a2c, idProduct=2d23, bcdDevice= 1.10 [ 4.549773] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4.559722] usb 3-1.2: Product: USB Keyboard [ 4.564096] usb 3-1.2: Manufacturer: USB [ 4.677461] r8152-cfgselector 6-1: reset SuperSpeed USB device number 2 using xhci-hcd [ 4.733246] r8152 6-1:1.0: Direct firmware load for rtl_nic/rtl8153a-3.fw failed with error -2 [ 4.742982] r8152 6-1:1.0: unable to load firmware patch rtl_nic/rtl8153a-3.fw (-2) [ 4.793138] r8152 6-1:1.0 eth0: v1.12.13 [ 4.939315] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 5.000498] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 5.060339] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 5.119528] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 5.459354] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 5.522765] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 5.578951] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 5.635751] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 5.979379] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 6.042260] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 6.098485] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 6.157505] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 6.498761] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 6.556671] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 6.612113] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 6.668707] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 7.009370] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 7.070667] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 7.126100] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 7.183829] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250)

@SteeMan indeed this needs to be split in its own thread, but to sum up, I'd like to either have USB-C DP alt mode working on a current Armbian build (I tried and it does not seem to work but that would be the best outcome if it can work), or have 3D acceleration/video decoding acceleration on the 4.4 kernel as DP alt mode works on it. Thanks for the help to get the media kernel working, I'll try that when I have some time, thanks!

Hey guys, looks like the devs are heavily busy with other stuff. As we can read they are currently massively struggling with a lack of ... basically everything. So let's try to support them by helping ourselves and share it with the community . I have not read anything anywhere about an approach to create an Armbian image for the M1S, so lets try to sum up, what we have and what is needed. I am really not an expert in all that - really NOT! But I like to contribute as far as I can! I've read somewhere that someone has tried to boot the M1 image on a M1S which kind of "worked" surprisingly, but failed in many ways like HDMI output and so on. This makes me think that the required modifications are mainly regarding entire hardware definitions - the device tree. There is already an official Home Assistant image for the M1S where the most changes are also regarding the device tree (see link above). So my idea for the next steps would be: take the M1 Armbian image as a starting point replace the Device tree be the one from Home Assistant and see if/how far it starts. Does this approach make sense and has it chance to work?! The problem I have: when I download the Home Assistant image and mount it locally I just can not find any DTB file. The same applies to the M1 Armbian image. Does anyone know where to find the DTB files right after downloading the images? Let's bring this forward guys. We have a sound software base to start from and the omnipotent Armbian build system. If we get people onboard who know better about the bootloader/device tree stuff than me, we should be able to do it . Cheers

Thx for your answer, Joekhoobyar. Yes, indeed, there are messages about "held BROKEN packages", but I did not put any packages on hold. Neither 'sudo apt-mark showhold' nor 'sudo apt-mark unhold' shows anything. What to do? I am a little bit of lost. What is the reason for this mismatch? How to get rid of it?

kernel drivers: replace all "branch:xxx" references with sha1; hash the whole of patch/misc stacktraces: introduce get_stacktrace_element_by_index() to get a specific stracktrace element git: fetch_from_repo(): introduce FETCH_FROM_REPO_CALLBACK_IF_REF_MUTABLE function defined in FETCH_FROM_REPO_CALLBACK_IF_REF_MUTABLE is called if reference is mutable which is anything that's not commit: or tag: and really there's no guarantee that tag: is immutable, but lets assume drivers-harness: hash the whole of patch/misc; throw error if driver does fetch_from_repo with mutable ref this should make drivers hash consistent, at the expense of being moar tiresome any changes at any patches or drivers-related bash code will cause all kernels to be rebuilt opposed to "some changes caused all kernels to be rebuilt" drivers_network: replace all "branch:xxx" references with sha1; add notice about it AR-1861 View the full article

Tried installing Armbian_23.11.1_Nanopineoplus2_jammy_current_6.1.63.img and it is super slow during first boot process regardless of SD type. Localization craps out with "Failed to set time zone: Transport endpoint is not connected". I boot with wired Ethernet and when I get to a prompt I can ping outside locations. apt update produces "Hash Sum mismatch" Anyways, doing my part testing legacy boards, hahahaha

Description The idea is to generate output/git_sources.json file that will contain url, branch and commit hash combo. The easiest way to generate file for all devices is to run ./compile.sh targets. Then at the time of release we will copy the output/info/git_sources.json file to config/sources/git_sources.json. Once the file is copied, the hash information from the file will be used to fetch resources for git repositories where branches are specified instead of tags or commits. There can be other ways to do this as well. I am just too tired to experiment more on the same. Raising it to be a communication starter. Jira reference number AR-2087 Based on: https://github.com/armbian/build/pull/6272 How Has This Been Tested? [ ] Tested output/git_sources.json file generation using ./compile.sh targets command [ ] Copied generated file to config/sources and modified it to use a different commit hash for 6.6 kernel. Then tested that kernel is being built from that hash instead of the latest available 6.6 kernel. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

rockchip-rk3588: add -Wno-error=enum-int-mismatch to u-boot CFLAGS so it builds with gcc 13+ rockchip-rk3588: add -Wno-error=enum-int-mismatch to u-boot CFLAGS so it builds with gcc 13+ this applies to all u-boots in this family View the full article

Well, after taking a break with fighting with this board for a couple months, I just tried to catch up. You may recall I have this board: I downloaded the server image from https://armdev.pixeldrift.net/transpeed/8k618-t, wrote it to a uSD, added the brcmfmac4335 drivers as described previously. For some reason I could not get the serial console running at 1,500,000 bps. Garbled - probably a baud rate mismatch? This worked for me a few months back. Oh well, a text session was usable on hdmi and keyboard, so I continued there. Neither ethernet or wifi was working. - The kernel finds dwmac-sun8i, but it fails to initialize "dwmac-sun8i 5030000.ethernet eth0: stmmac_dvr_remove: removing driver" Debugging beyond this is way over my head. - On wifi, the kernel was erroring out looking for brcmfmac4334-sdio driver files. I thought this board used brcmfmac4335?? I found what I believe are the correct 4334 *.bin, *.txt, and *.clm_blob files, and placed them in /lib/firmware/brcm - based on kernel error messages. But still No Go. I do not see any error messages in the kernel log, but no network device is created. Another dead end for my ability. I tried plugging in a cheap USB to ethernet dongle I had lying around, and IT WORKS! "usbcore: registered new interface driver cdc_ether" It is slow, attached to a USB-2 link (480mbit/sec) but OK for light work. (The switch port says it's attached at 1Gbit - yea sure!) Thanks to Nick A, apritzel, pixdrift & probably others for their work getting this far - alot more stuff is working now than last time I looked, and with the enet dongle, I can actually start playing with the system. I ran out of time today to further explore https://github.com/warpme/miniarch. I did NOT try to install & boot from emmc, although I see the device at mmcblk2. BTW, that is my serial console attached with the loose wires above. The pins are actually labelled GND TX RX on my board. Different from nicrolack's board.

Please this Error context msg [ Check MD5 sum of installed packages failed ] what is the reason? https://paste.next.armbian.com/gigojaropu

Hi Gents, I would like to ask for your help or tips and tricks in the following problem... Basically to keep the long story short, I have a custom board with RK3566 and 2 GB of RAM, 32 GB Samsung emmc on it ... basically if you are familliar it is a Linxdot Helium miner which has some problems with the onboard Lora module. I had tried to flash using RKDevTool a few Debian version that I found for Rk3566 but not all of them worked properly. All the time I was able to reflash it by using RKDevTool by pressing the button while I powered up the board but after flashing the Armbian minnimal for Orange Pi3B I can't use the RKDevTool anymore, it is simply not seeing the board anymore (No device found). I have an UART 3.5mm Jack type port, I had a homemade cable so I was able to create the user at the first boot, I am able to log in, but there is no HDMI, the ethernet port is no recognized, WiFi also not recognized, I am plug in a USB Flash stick and I am not seeing it in the lsblk command output, so basically I have now a very basic board. (I know, I am stupid, but I was thinking that I can't damage it because the RKDevTool was working fine under all previous circumstances). My question would be, if there is any possibility somehow to restore the functionality to be able to boot it in MaskMode for the RKDevTool or any other solution to make at least the Ethernet and USB ports to work? There are no other button, just 2, one reset and one user button on it. All the time I had to keep pressed the user button in order to be detected by the RK tool. There are no jumpers on the board (at least I can't find them) which I can short to stop the emmc from booting or similar things Many thanks in advance ! The booting process: ▒▒▒DDR V1.18 f366f69a7d typ 23/07/17-15:48:58 ln LP4/4x derate en, other dram:1x trefi ddrconfig:15 DDR4, 324MHz BW=32 Col=10 Bk=4 BG=2 CS0 Row=16 CS=1 Die BW=16 Size=2048MB tdqss: cs0 dqs0: 192ps, dqs1: 144ps, dqs2: 96ps, dqs3: 96ps, change to: 324MHz clk skew:0x8d change to: 528MHz clk skew:0x8d change to: 780MHz clk skew:0x8d change to: 1056MHz(final freq) clk skew:0x8d PHY drv:clk:37,ca:37,DQ:37,odt:139 vrefinner:50%, vrefout:61% dram drv:34,odt:120 cs 0: the read training result: DQS0:0x3c, DQS1:0x39, DQS2:0x36, DQS3:0x3b, min : 0x7 0xa 0xb 0x8 0x2 0x4 0x4 0x2 , 0x3 0x7 0x1 0x4 0x4 0x6 0x8 0x2 , 0x5 0x6 0x3 0x6 0x2 0x1 0x2 0x4 , 0x8 0x6 0x6 0x0 0x5 0x8 0x9 0x6 , mid :0x24 0x27 0x28 0x25 0x1f 0x21 0x21 0x1f ,0x21 0x23 0x1e 0x22 0x22 0x23 0x24 0x1f , 0x21 0x23 0x20 0x22 0x1f 0x1d 0x1f 0x21 ,0x26 0x23 0x23 0x1d 0x22 0x26 0x26 0x23 , max :0x42 0x45 0x46 0x43 0x3c 0x3e 0x3f 0x3c ,0x3f 0x40 0x3b 0x40 0x40 0x40 0x41 0x3d , 0x3e 0x40 0x3e 0x3f 0x3c 0x3a 0x3d 0x3e ,0x44 0x40 0x41 0x3a 0x40 0x44 0x44 0x41 , range:0x3b 0x3b 0x3b 0x3b 0x3a 0x3a 0x3b 0x3a ,0x3c 0x39 0x3a 0x3c 0x3c 0x3a 0x39 0x3b , 0x39 0x3a 0x3b 0x39 0x3a 0x39 0x3b 0x3a ,0x3c 0x3a 0x3b 0x3a 0x3b 0x3c 0x3b 0x3b , the write training result: DQS0:0xa6, DQS1:0xa0, DQS2:0x99, DQS3:0x99, min :0x8c 0x92 0x90 0x8f 0x88 0x89 0x8a 0x89 0x8f ,0x85 0x89 0x84 0x89 0x89 0x8b 0x8b 0x85 0x85 , 0x84 0x85 0x84 0x85 0x83 0x81 0x83 0x85 0x82 ,0x7f 0x7d 0x7c 0x7a 0x81 0x81 0x82 0x7e 0x7e , mid :0xa8 0xab 0xab 0xa9 0xa1 0xa4 0xa3 0xa2 0xa9 ,0x9f 0xa2 0x9e 0xa3 0xa2 0xa3 0xa4 0x9f 0x9f , 0x9e 0x9e 0x9f 0xa0 0x9c 0x9b 0x9a 0x9c 0x9d ,0x9b 0x97 0x97 0x95 0x9a 0x9c 0x9c 0x9a 0x99 , max :0xc5 0xc5 0xc7 0xc3 0xbb 0xc0 0xbc 0xbb 0xc4 ,0xba 0xbb 0xb8 0xbd 0xbb 0xbc 0xbe 0xba 0xb9 , 0xb9 0xb8 0xba 0xbb 0xb6 0xb5 0xb2 0xb4 0xb8 ,0xb7 0xb2 0xb3 0xb0 0xb3 0xb7 0xb6 0xb6 0xb5 , range:0x39 0x33 0x37 0x34 0x33 0x37 0x32 0x32 0x35 ,0x35 0x32 0x34 0x34 0x32 0x31 0x33 0x35 0x34 , 0x35 0x33 0x36 0x36 0x33 0x34 0x2f 0x2f 0x36 ,0x38 0x35 0x37 0x36 0x32 0x36 0x34 0x38 0x37 , out U-Boot SPL 2023.10-rc4-armbian (Feb 10 2024 - 01:24:45 +0000) Trying to boot from MMC1 ## Checking hash(es) for config config-1 ... OK ## Checking hash(es) for Image atf-1 ... sha256+ OK ## Checking hash(es) for Image u-boot ... sha256+ OK ## Checking hash(es) for Image fdt-1 ... sha256+ OK ## Checking hash(es) for Image atf-2 ... sha256+ OK ## Checking hash(es) for Image atf-3 ... sha256+ OK ## Checking hash(es) for Image atf-4 ... sha256+ OK ## Checking hash(es) for Image atf-5 ... sha256+ OK ## Checking hash(es) for Image atf-6 ... sha256+ OK INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-607-gbf602aff1:cl NOTICE: BL31: Built : 10:16:03, Jun 5 2023 INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: pmu v1 is valid 220114 INFO: dfs DDR fsp_param[0].freq_mhz= 1056MHz INFO: dfs DDR fsp_param[1].freq_mhz= 324MHz INFO: dfs DDR fsp_param[2].freq_mhz= 528MHz INFO: dfs DDR fsp_param[3].freq_mhz= 780MHz INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0xa00000 INFO: SPSR = 0x3c9 U-Boot 2023.10-rc4-armbian (Feb 10 2024 - 01:24:45 +0000) Model: Rockchip RK3566 OPi 3B DRAM: 2 GiB PMIC: RK8090 (on=0x40, off=0x00) Core: 338 devices, 32 uclasses, devicetree: separate MMC: mmc@fe2b0000: 1, mmc@fe2c0000: 2, mmc@fe310000: 0 Loading Environment from nowhere... OK In: serial@fe660000 Out: serial@fe660000 Err: serial@fe660000 Model: Rockchip RK3566 OPi 3B Net: eth0: ethernet@fe010000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 ** Booting bootflow 'mmc@fe310000.bootdev.part_1' with script Boot script loaded from mmc 0:1 204 bytes read in 12 ms (16.6 KiB/s) 8023386 bytes read in 204 ms (37.5 MiB/s) 35062272 bytes read in 767 ms (43.6 MiB/s) 166117 bytes read in 54 ms (2.9 MiB/s) Working FDT set to a100000 Failed to load '/boot/dtb/rockchip/overlay/rk35xx-fixup.scr' Unknown command 'kaslrseed' - try 'help' Moving Image from 0x2080000 to 0x2200000, end=4420000 ## Loading init Ramdisk from Legacy Image at 0a200000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8023322 Bytes = 7.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 0a100000 Booting using the fdt blob at 0xa100000 Working FDT set to a100000 Loading Ramdisk to 7c71d000, end 7cec3d1a ... OK ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) Loading Device Tree to 000000007c68c000, end 000000007c71cfff ... OK Working FDT set to 7c68c000 Starting kernel ... Armbian_community 24.5.0-trunk.6 Bookworm ttyFIQ0 orangepi3b login:

Description The idea is to generate output/git_sources.json file that will contain url, branch and commit hash combo. The easiest way to generate file for all devices is to run ./compile.sh targets. Then at the time of release we will copy the output/git_sources.json file to config/sources/git_sources.json. Once the file is copied, the hash information from the file will be used to fetch resources for git repositories where branches are specified instead of tags or commits. There can be other ways to do this as well. I am just too tired to experiment more on the same. Raising it to be a communication starter. I have also added the json file that I have generated today. I think it can be used to freeze sources for 24.02 release. Hence I have raised this PR again v24.02 branch How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [ ] Tested output/git_sources.json file generation using ./compile.sh targets command [ ] Copied generated file to config/sources and modified it to use a different commit hash for 6.6 kernel. Then tested that kernel is being built from that hash instead of the latest available 6.6 kernel. Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

@going After doing the following its done a load of downloads, then put me in the middle of a console kernel configuration Q&A ! ``` git clone --depth=120 --branch=pbs-master https://github.com/The-going/armbian-build cd armbian-build git pull mkdir userpatches cp config/templates/config-test.conf userpatches ./compile.sh test BUILD_ONLY=default ``` ``` * * Restart config... * * * Configure standard kernel features (expert users) * Configure standard kernel features (expert users) (EXPERT) [Y/n/?] y Enable 16-bit UID system calls (UID16) [Y/n/?] y Multiple users, groups and capabilities support (MULTIUSER) [Y/n/?] y sgetmask/ssetmask syscalls support (SGETMASK_SYSCALL) [N/y/?] n Sysfs syscall support (SYSFS_SYSCALL) [Y/n/?] y open by fhandle syscalls (FHANDLE) [Y/n/?] y Posix Clocks & timers (POSIX_TIMERS) [Y/n/?] y Enable support for printk (PRINTK) [Y/n/?] y BUG() support (BUG) [Y/n/?] y Enable ELF core dumps (ELF_CORE) [Y/n/?] y Enable full-sized data structures for core (BASE_FULL) [Y/n/?] y Enable futex support (FUTEX) [Y/n/?] y Enable eventpoll support (EPOLL) [Y/n/?] y Enable signalfd() system call (SIGNALFD) [Y/n/?] y Enable timerfd() system call (TIMERFD) [Y/n/?] y Enable eventfd() system call (EVENTFD) [Y/?] y Use full shmem filesystem (SHMEM) [Y/?] y Enable AIO support (AIO) [Y/n/?] y Enable IO uring support (IO_URING) [Y/?] y Enable madvise/fadvise syscalls (ADVISE_SYSCALLS) [Y/n/?] y Enable membarrier() system call (MEMBARRIER) [Y/?] y Load all symbols for debugging/ksymoops (KALLSYMS) [Y/?] y Test the basic functions and performance of kallsyms (KALLSYMS_SELFTEST) [N/y/?] (NEW) Y Include all symbols in kallsyms (KALLSYMS_ALL) [N/y/?] n * * Enable loadable module support * Enable loadable module support (MODULES) [Y/n/?] y Module debugging (MODULE_DEBUG) [N/y/?] (NEW) Y Module statistics (MODULE_STATS) [N/y/?] (NEW) y Debug duplicate modules with auto-loading (MODULE_DEBUG_AUTOLOAD_DUPS) [N/y/?] (NEW) Forced module loading (MODULE_FORCE_LOAD) [N/y/?] n Module unloading (MODULE_UNLOAD) [Y/n/?] y Forced module unloading (MODULE_FORCE_UNLOAD) [Y/n/?] y Tainted module unload tracking (MODULE_UNLOAD_TAINT_TRACKING) [N/y/?] n Module versioning support (MODVERSIONS) [N/y/?] n Source checksum for all modules (MODULE_SRCVERSION_ALL) [N/y/?] n Module signature verification (MODULE_SIG) [Y/?] y Require modules to be validly signed (MODULE_SIG_FORCE) [N/y/?] n Automatically sign all modules (MODULE_SIG_ALL) [Y/n/?] y Which hash algorithm should modules be signed with? > 1. Sign modules with SHA-1 (MODULE_SIG_SHA1) 2. Sign modules with SHA-224 (MODULE_SIG_SHA224) 3. Sign modules with SHA-256 (MODULE_SIG_SHA256) 4. Sign modules with SHA-384 (MODULE_SIG_SHA384) 5. Sign modules with SHA-512 (MODULE_SIG_SHA512) choice[1-5?]: 1 Module compression mode 1. None (MODULE_COMPRESS_NONE) 2. GZIP (MODULE_COMPRESS_GZIP) > 3. XZ (MODULE_COMPRESS_XZ) 4. ZSTD (MODULE_COMPRESS_ZSTD) choice[1-4?]: 3 Support in-kernel module decompression (MODULE_DECOMPRESS) [Y/n/?] y Allow loading of modules with missing namespace imports (MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS) [N/y/?] n Path to modprobe binary (MODPROBE_PATH) [/sbin/modprobe] /sbin/modprobe Trim unused exported kernel symbols (TRIM_UNUSED_KSYMS) [N/y/?] n * * Support for paging of anonymous memory (swap) * Support for paging of anonymous memory (swap) (SWAP) [Y/n/?] y Compressed cache for swap pages (ZSWAP) [Y/n/?] y Enable the compressed cache for swap pages by default (ZSWAP_DEFAULT_ON) [Y/n/?] y Default compressor 1. Deflate (ZSWAP_COMPRESSOR_DEFAULT_DEFLATE) 2. LZO (ZSWAP_COMPRESSOR_DEFAULT_LZO) 3. 842 (ZSWAP_COMPRESSOR_DEFAULT_842) 4. LZ4 (ZSWAP_COMPRESSOR_DEFAULT_LZ4) 5. LZ4HC (ZSWAP_COMPRESSOR_DEFAULT_LZ4HC) > 6. zstd (ZSWAP_COMPRESSOR_DEFAULT_ZSTD) choice[1-6?]: 6 Default allocator 1. zbud (ZSWAP_ZPOOL_DEFAULT_ZBUD) > 2. z3fold (ZSWAP_ZPOOL_DEFAULT_Z3FOLD) 3. zsmalloc (ZSWAP_ZPOOL_DEFAULT_ZSMALLOC) choice[1-3?]: 2 2:1 compression allocator (zbud) (ZBUD) [Y/n/m/?] y 3:1 compression allocator (z3fold) (Z3FOLD) [Y/?] y N:1 compression allocator (zsmalloc) (ZSMALLOC) [Y/m/?] y Export zsmalloc statistics (ZSMALLOC_STAT) [N/y/?] n Maximum number of physical pages per-zspage (ZSMALLOC_CHAIN_SIZE) [8] (NEW) * * SLAB allocator options * Choose SLAB allocator 1. SLAB (SLAB) > 2. SLUB (Unqueued Allocator) (SLUB) choice[1-2?]: 2 Configure SLUB for minimal memory footprint (SLUB_TINY) [N/y/?] (NEW) ```

I installed Armbian 23.11 Bookworm Kernel 6.1, Size: 482Mb, Release date: Nov 30, 2023. After installation, a CH340 based board was connected to my original Tinkerboard and recognized. Subsequently, I used armbian-config to provide the default desktop (Cinnamon flavor). Thereafter, the CH340 board is incompletely recognized. Specifically, no device is presented as /dev/ttyUSB?. The device appears in the list from lsusb, the kernel module ch341.ko loads, but no device in /dev. The forum search shows a previous instance of a similar issue many years back. I attempted to build the driver from wch.cn, but the kernel sources pulled from armbian-config were for the Linux tinkerboard 6.1.63-current-rockchip kernel and,so, a mismatch for the running kernel. uname -a Linux tinkerboard 6.1.68-current-rockchip #1 SMP PREEMPT Wed Dec 13 17:39:30 UTC 2023 armv7l GNU/Linux lsusb |grep -i ch34 Bus 001 Device 006: ID 1a86:7523 QinHeng Electronics CH340 serial converter lsmod | grep -i ch34 ch341 20480 0 usbserial 28672 1 ch341

artifact: kernel: force D0000 drivers hash for artifact_version if EXTRAWIFI=no artifact: kernel: force D0000 drivers hash for artifact_version if EXTRAWIFI=no View the full article

Description Unstable / testing packages sometimes contain hacks that are patching files. Fixing this in Debian Sid / Trixie Not sure why this happens, but we certainly don't need this check in rolling releases. [🐳|🌱] Checking MD5 sum of installed packages [ debsums ] [🐳|🔨] debsums: changed file /usr/sbin/start-stop-daemon (from dpkg package) [🐳|💥] Error 2 occurred in main shell [ at /armbian/lib/functions/logging/runners.sh:211 How Has This Been Tested? [x] Manual run Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

I found the program v4l2-compliance it has one failure : Format ioctls (Input 0): fail: v4l2-test-formats.cpp(263): fmtdesc.description mismatch: was 'Y/UV 4:2:0 (16x16 Linear)', expected 'Y/CbCr 4:2:0 (16x16 Linear)' test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: FAIL also very strange, I expected output like this instead I get this bruno@orangepione2:~$ v4l2-ctl -d 1 --list-ctrls --list-formats ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'BA81' (8-bit Bayer BGBG/GRGR) [1]: 'GBRG' (8-bit Bayer GBGB/RGRG) [2]: 'GRBG' (8-bit Bayer GRGR/BGBG) [3]: 'RGGB' (8-bit Bayer RGRG/GBGB) [4]: 'BG10' (10-bit Bayer BGBG/GRGR) [5]: 'GB10' (10-bit Bayer GBGB/RGRG) [6]: 'BA10' (10-bit Bayer GRGR/BGBG) [7]: 'RG10' (10-bit Bayer RGRG/GBGB) [8]: 'BG12' (12-bit Bayer BGBG/GRGR) [9]: 'GB12' (12-bit Bayer GBGB/RGRG) [10]: 'BA12' (12-bit Bayer GRGR/BGBG) [11]: 'RG12' (12-bit Bayer RGRG/GBGB) [12]: 'YUYV' (YUYV 4:2:2) [13]: 'YVYU' (YVYU 4:2:2) [14]: 'UYVY' (UYVY 4:2:2) [15]: 'VYUY' (VYUY 4:2:2) [16]: 'RGBP' (16-bit RGB 5-6-5) [17]: 'RGBO' (16-bit A/XRGB 1-5-5-5) [18]: 'HM12' (Y/UV 4:2:0 (16x16 Linear)) [19]: 'NV12' (Y/UV 4:2:0) [20]: 'NV21' (Y/VU 4:2:0) [21]: 'YU12' (Planar YUV 4:2:0) [22]: 'YV12' (Planar YVU 4:2:0) [23]: 'NV16' (Y/UV 4:2:2) [24]: 'NV61' (Y/VU 4:2:2) [25]: '422P' (Planar YUV 4:2:2) [26]: 'RGBP' (16-bit RGB 5-6-5) [27]: 'RGBR' (16-bit RGB 5-6-5 BE) [28]: 'JPEG' (JFIF JPEG, compressed) also bruno@orangepione2:~$ media-ctl -d 0 --print-topology Media controller API version 6.1.63 Media device information ------------------------ driver sun6i-csi model Allwinner A31 CSI Device serial bus info platform:1cb0000.camera hw revision 0x0 driver version 6.1.63 Device topology - entity 1: sun6i-csi (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: Sink <- "ov5640 1-003c":0 [ENABLED] - entity 5: ov5640 1-003c (1 pad, 1 link) type V4L2 subdev subtype Sensor flags 0 device node name /dev/v4l-subdev0 pad0: Source [fmt:UYVY8_2X8/640x480@1/30 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:full-range crop.bounds:(0,0)/2624x1964 crop:(0,4)/2624x1944] -> "sun6i-csi":0 [ENABLED]

I just want to add a few comments to this whole dtb overlay discussion. First I want to thank all of you involved in this discussion. You all have different view points and I think are tackling a very difficult problem to which there is no perfect solution. What comes out of this discussion should be applied to the other soc families as well, as they all suffer from some form of this issue as there is no standard in place that works for all use cases well. From what I have seen, good minds are thinking this through and I expect a good result to follow. The reason I am commenting at all, is because in my role as forum moderator, the basic question: "How do I enable feature x on my board" is one of, if not the most commonly asked question by end users of the forum. And when the answer is 'just write a dtb overlay', you have lost 95% of those users as they do not have the skills/knowledge to do that. The status of the dtb overlay's across Armbian supported and community maintained boards is poor. There is no standardization from family to family or board to board. And no testing of what does exist to ensure that it works. Now I'm not saying that all of this needs to be solved in what comes out of this design discussion. I'm just saying from my perspective as a moderator that this is an area that can use some attention, and in doing so, please try to make the end result usable by the typical end user of an sbc, trying to do common things. I realize also that I'm saying this when I only use these boards as servers and don't personally need any of the functionality the overlays provide. But as a forum moderator, I see the mismatch between what is being done and some common use cases that end users are looking for.