fever_wits

Hello, Thanks for the information. Even zfs version 2.3.1 supports maximum kernel version 6.13. I will wait for all the necessary dependencies to come out and test and write again if sharing information is useful for you. Regards,

Thanks for the suggestion, during my experience the zfs packages got updated. It turned out that zfs-zed has a new package, but it doesn't work because of zfsutils-linux which wants libzfs6linux, and zfs-zed wants libzfs4linux. After that there is a little hell :). Solution: aptitude install zfs-dkms=2.2.7-1~bpo12+1 zfsutils-linux=2.2.7-1~bpo12+1 libuutil3linux=2.2.7-1~bpo12+1 libnvpair3linux=2.2.7-1~bpo12+1 zfs-zed As my addition is not the right place please say and I will start a new thread. Maybe that will save someone a little headache.

I got up the courage to try (hahaha), got a little bug # aptitude install linux-dtb-edge-rockchip64 linux-headers-edge-rockchip64 linux-image-edge-rockchip64 linux-libc-dev-edge-rockchip64 linux-u-boot-nanopct6-edge The following NEW packages will be installed: linux-dtb-edge-rockchip64 linux-headers-edge-rockchip64 linux-image-edge-rockchip64 linux-libc-dev-edge-rockchip64 linux-u-boot-nanopct6-edge The following packages will be REMOVED: linux-libc-dev-current-rockchip-rk3588{a} linux-u-boot-nanopct6-current{a} 0 packages upgraded, 5 newly installed, 2 to remove and 0 not upgraded. Need to get 64.0 MB of archives. After unpacking 345 MB will be used. Do you want to continue? [Y/n/?] Y Get: 1 https://armbian.systemonachip.net/apt bookworm/main arm64 linux-libc-dev-edge-rockchip64 arm64 25.2.3 [1,388 kB] Get: 2 https://armbian.systemonachip.net/apt bookworm/main arm64 linux-dtb-edge-rockchip64 arm64 25.2.3 [397 kB] Get: 3 https://armbian.systemonachip.net/apt bookworm/main arm64 linux-headers-edge-rockchip64 arm64 25.2.3 [14.8 MB] Get: 4 https://armbian.systemonachip.net/apt bookworm/main arm64 linux-image-edge-rockchip64 arm64 25.2.3 [46.4 MB] Get: 5 https://armbian.systemonachip.net/apt bookworm/main arm64 linux-u-boot-nanopct6-edge arm64 25.2.3 [1,032 kB] Fetched 64.0 MB in 3s (21.1 MB/s) dpkg: linux-libc-dev-current-rockchip-rk3588:arm64: dependency problems, but removing anyway as you requested: libc6-dev:arm64 depends on linux-libc-dev; however: Package linux-libc-dev is not installed. Package linux-libc-dev-current-rockchip-rk3588:arm64 which provides linux-libc-dev is to be removed. (Reading database ... 76690 files and directories currently installed.) Removing linux-libc-dev-current-rockchip-rk3588:arm64 (24.11.2) ... Selecting previously unselected package linux-libc-dev-edge-rockchip64:arm64. (Reading database ... 75671 files and directories currently installed.) Preparing to unpack .../linux-libc-dev-edge-rockchip64_25.2.3_arm64.deb ... Unpacking linux-libc-dev-edge-rockchip64:arm64 (25.2.3) ... (Reading database ... 76695 files and directories currently installed.) Removing linux-u-boot-nanopct6-current (25.2.3) ... Selecting previously unselected package linux-dtb-edge-rockchip64. (Reading database ... 76684 files and directories currently installed.) Preparing to unpack .../linux-dtb-edge-rockchip64_25.2.3_arm64.deb ... Armbian 'linux-dtb-edge-rockchip64' for '6.14.0-edge-rockchip64': 'preinst' starting. Armbian 'linux-dtb-edge-rockchip64' for '6.14.0-edge-rockchip64': 'preinst' finishing. Unpacking linux-dtb-edge-rockchip64 (25.2.3) ... Selecting previously unselected package linux-headers-edge-rockchip64. Preparing to unpack .../linux-headers-edge-rockchip64_25.2.3_arm64.deb ... Armbian 'linux-headers-edge-rockchip64' for '6.14.0-edge-rockchip64': 'preinst' starting. Armbian 'linux-headers-edge-rockchip64' for '6.14.0-edge-rockchip64': 'preinst' finishing. Unpacking linux-headers-edge-rockchip64 (25.2.3) ... Selecting previously unselected package linux-image-edge-rockchip64. Preparing to unpack .../linux-image-edge-rockchip64_25.2.3_arm64.deb ... Armbian 'linux-image-edge-rockchip64' for '6.14.0-edge-rockchip64': 'preinst' starting. Armbian 'linux-image-edge-rockchip64' for '6.14.0-edge-rockchip64': 'preinst' finishing. Unpacking linux-image-edge-rockchip64 (25.2.3) ... Selecting previously unselected package linux-u-boot-nanopct6-edge. Preparing to unpack .../linux-u-boot-nanopct6-edge_25.2.3_arm64.deb ... Unpacking linux-u-boot-nanopct6-edge (25.2.3) ... Setting up linux-dtb-edge-rockchip64 (25.2.3) ... Armbian 'linux-dtb-edge-rockchip64' for '6.14.0-edge-rockchip64': 'postinst' starting. Armbian: DTB: symlinking /boot/dtb to /boot/dtb-6.14.0-edge-rockchip64... 'dtb' -> 'dtb-6.14.0-edge-rockchip64' Armbian 'linux-dtb-edge-rockchip64' for '6.14.0-edge-rockchip64': 'postinst' finishing. Setting up linux-libc-dev-edge-rockchip64:arm64 (25.2.3) ... Setting up linux-image-edge-rockchip64 (25.2.3) ... Armbian 'linux-image-edge-rockchip64' for '6.14.0-edge-rockchip64': 'postinst' starting. dkms: running auto installation service for kernel 6.14.0-edge-rockchip64. Sign command: /lib/modules/6.14.0-edge-rockchip64/build/scripts/sign-file Binary /lib/modules/6.14.0-edge-rockchip64/build/scripts/sign-file not found, modules won't be signed Running the pre_build script: checking for gawk... gawk checking metadata... META file checking build system type... aarch64-unknown-linux-gnu checking host system type... aarch64-unknown-linux-gnu checking target system type... aarch64-unknown-linux-gnu checking whether to enable maintainer-specific portions of Makefiles... no checking whether make supports nested variables... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a race-free mkdir -p... /usr/bin/mkdir -p checking whether make sets $(MAKE)... yes checking how to print strings... printf checking whether make supports the include directive... yes (GNU style) checking for gcc... aarch64-linux-gnu-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether aarch64-linux-gnu-gcc accepts -g... yes checking for aarch64-linux-gnu-gcc option to enable C11 features... none needed checking whether aarch64-linux-gnu-gcc understands -c and -o together... yes checking dependency style of aarch64-linux-gnu-gcc... none checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by aarch64-linux-gnu-gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking how to convert aarch64-unknown-linux-gnu file names to aarch64-unknown-linux-gnu format... func_convert_file_noop checking how to convert aarch64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for file... file checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from aarch64-linux-gnu-gcc object... ok checking for sysroot... no checking for a working dd... /usr/bin/dd checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 checking for mt... mt checking if mt is a manifest tool... no checking for stdio.h... yes checking for stdlib.h... yes checking for string.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for strings.h... yes checking for sys/stat.h... yes checking for sys/types.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if aarch64-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no checking for aarch64-linux-gnu-gcc option to produce PIC... -fPIC -DPIC checking if aarch64-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes checking if aarch64-linux-gnu-gcc static flag -static works... yes checking if aarch64-linux-gnu-gcc supports -c -o file.o... yes checking if aarch64-linux-gnu-gcc supports -c -o file.o... (cached) yes checking whether the aarch64-linux-gnu-gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for gcc... (cached) aarch64-linux-gnu-gcc checking whether the compiler supports GNU C... (cached) yes checking whether aarch64-linux-gnu-gcc accepts -g... (cached) yes checking for aarch64-linux-gnu-gcc option to enable C11 features... (cached) none needed checking whether aarch64-linux-gnu-gcc understands -c and -o together... (cached) yes checking dependency style of aarch64-linux-gnu-gcc... (cached) none checking whether ln -s works... yes checking for pkg-config... no checking dependency style of aarch64-linux-gnu-gcc... none checking whether to build with code coverage support... no checking how to create a pax tar archive... gnutar checking zfs author... OpenZFS checking zfs license... CDDL checking whether NLS is requested... yes checking for msgfmt... no checking for gmsgfmt... : checking for xgettext... no checking for msgmerge... no checking for ld... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking 32-bit host C ABI... no checking for the common suffixes of directories in the library search path... lib,lib checking zfs config... kernel checking the number of available CPUs... 8 checking whether aarch64-linux-gnu-gcc supports -Wno-clobbered... yes checking whether aarch64-linux-gnu-gcc supports -Winfinite-recursion... yes checking whether supports -Winfinite-recursion... yes checking whether aarch64-linux-gnu-gcc supports -Wimplicit-fallthrough... yes checking whether aarch64-linux-gnu-gcc supports -Wframe-larger-than=<size>... yes checking whether aarch64-linux-gnu-gcc supports -Wno-format-truncation... yes checking whether aarch64-linux-gnu-gcc supports -Wno-format-zero-length... yes checking whether aarch64-linux-gnu-gcc supports -Wformat-overflow... yes checking whether aarch64-linux-gnu-gcc supports -fno-omit-frame-pointer... yes checking whether aarch64-linux-gnu-gcc supports -fno-ipa-sra... yes checking whether supports -fno-ipa-sra... yes checking whether to build with -fsanitize=address support... no checking whether to build with -fsanitize=undefined support... no checking for system type (linux-gnu)... Linux checking for python3... python3 checking for python version... 3.11 checking for python platform... linux checking for GNU default python prefix... ${prefix} checking for GNU default python exec_prefix... ${exec_prefix} checking for python script directory (pythondir)... ${PYTHON_PREFIX}/lib/python3.11/site-packages checking for python extension module directory (pyexecdir)... ${PYTHON_EXEC_PREFIX}/lib/python3.11/site-packages configure: Disabling pyzfs for kernel/srpm config checking whether to enable pyzfs: ... no checking for sed --in-place... --in-place checking for cppcheck... no checking for shellcheck... no checking for checkbashisms... no checking for parallel... no checking kernel source and build directories... done checking kernel source directory... /lib/modules/6.14.0-edge-rockchip64/build checking kernel build directory... /lib/modules/6.14.0-edge-rockchip64/build checking kernel source version... 6.14.0-edge-rockchip64 configure: error: *** Cannot build against kernel version 6.14.0-edge-rockchip64. *** The maximum supported kernel version is 6.13. Building module: Cleaning build area...(bad exit status: 2) make -j8 KERNELRELEASE=6.14.0-edge-rockchip64...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.14.0-edge-rockchip64 (aarch64) Consult /var/lib/dkms/zfs/2.3.1/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.14.0-edge-rockchip64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 update-initramfs: Generating /boot/initrd.img-6.14.0-edge-rockchip64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8126a-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8126a-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125bp-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125d-1.fw for module r8169 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.14.0-edge-rockchip64 Image Name: uInitrd Created: Sat Apr 5 12:15:14 2025 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17825090 Bytes = 17407.31 KiB = 17.00 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.14.0-edge-rockchip64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.14.0-edge-rockchip64' update-initramfs: Armbian: done. Free space after deleting the package linux-image-edge-rockchip64 in /boot: 1.5G dpkg: error processing package linux-image-edge-rockchip64 (--configure): installed linux-image-edge-rockchip64 package post-installation script subprocess returned error exit status 1 Setting up linux-headers-edge-rockchip64 (25.2.3) ... Armbian 'linux-headers-edge-rockchip64' for '6.14.0-edge-rockchip64': 'postinst' starting. Configuring kernel-headers (6.14.0-edge-rockchip64) - please wait ... HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/confdata.o HOSTCC scripts/kconfig/expr.o LEX scripts/kconfig/lexer.lex.c YACC scripts/kconfig/parser.tab.[ch] HOSTCC scripts/kconfig/lexer.lex.o HOSTCC scripts/kconfig/menu.o HOSTCC scripts/kconfig/parser.tab.o HOSTCC scripts/kconfig/preprocess.o HOSTCC scripts/kconfig/symbol.o HOSTCC scripts/kconfig/util.o HOSTLD scripts/kconfig/conf # # configuration written to .config # Compiling kernel-headers scripts (6.14.0-edge-rockchip64) using 8 CPUs - please wait ... SYNC include/config/auto.conf.cmd HOSTCC scripts/dtc/dtc.o HOSTCC scripts/dtc/flattree.o HOSTCC scripts/dtc/fstree.o HOSTCC scripts/dtc/data.o HOSTCC scripts/dtc/livetree.o HOSTCC scripts/dtc/treesource.o HOSTCC scripts/dtc/srcpos.o HOSTCC scripts/dtc/checks.o HOSTCC scripts/dtc/util.o LEX scripts/dtc/dtc-lexer.lex.c YACC scripts/dtc/dtc-parser.tab.[ch] HOSTCC scripts/dtc/libfdt/fdt.o HOSTCC scripts/dtc/libfdt/fdt_ro.o HOSTCC scripts/dtc/libfdt/fdt_wip.o HOSTCC scripts/dtc/libfdt/fdt_sw.o HOSTCC scripts/dtc/libfdt/fdt_rw.o HOSTCC scripts/dtc/libfdt/fdt_strerror.o HOSTCC scripts/dtc/libfdt/fdt_empty_tree.o HOSTCC scripts/dtc/libfdt/fdt_addresses.o HOSTCC scripts/dtc/libfdt/fdt_overlay.o HOSTCC scripts/dtc/fdtoverlay.o HOSTCC scripts/dtc/dtc-lexer.lex.o HOSTCC scripts/dtc/dtc-parser.tab.o HOSTLD scripts/dtc/fdtoverlay HOSTLD scripts/dtc/dtc HOSTCC scripts/kallsyms HOSTCC scripts/sorttable HOSTCC scripts/insert-sys-cert HOSTCC scripts/asn1_compiler HOSTCC scripts/selinux/mdp/mdp Compiling kernel-headers scripts/mod (6.14.0-edge-rockchip64) using 8 CPUs - please wait ... make[1]: Entering directory '/usr/src/linux-headers-6.14.0-edge-rockchip64/scripts/mod' CC empty.o HOSTCC mk_elfconfig CC devicetable-offsets.s MKELF elfconfig.h HOSTCC modpost.o HOSTCC sumversion.o HOSTCC symsearch.o UPD devicetable-offsets.h HOSTCC file2alias.o HOSTLD modpost MODPOST Module.symvers make[1]: Leaving directory '/usr/src/linux-headers-6.14.0-edge-rockchip64/scripts/mod' Done compiling kernel-headers (6.14.0-edge-rockchip64). Done compiling kernel-headers tools (6.14.0-edge-rockchip64). Armbian 'linux-headers-edge-rockchip64' for '6.14.0-edge-rockchip64': 'postinst' finishing. Setting up linux-u-boot-nanopct6-edge (25.2.3) ... Armbian 'uboot-nanopct6-edge' for '2025.04-rc1-Sa517-P5a21-Hda62-V7687-Bb703-R448a': 'postinst' starting. Armbian 'uboot-nanopct6-edge' for '2025.04-rc1-Sa517-P5a21-Hda62-V7687-Bb703-R448a': 'postinst' finishing. Errors were encountered while processing: linux-image-edge-rockchip64 E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up linux-image-edge-rockchip64 (25.2.3) ... Armbian 'linux-image-edge-rockchip64' for '6.14.0-edge-rockchip64': 'postinst' starting. dkms: running auto installation service for kernel 6.14.0-edge-rockchip64. /usr/sbin/dkms: line 2497: echo: write error: Broken pipe Sign command: /lib/modules/6.14.0-edge-rockchip64/build/scripts/sign-file Binary /lib/modules/6.14.0-edge-rockchip64/build/scripts/sign-file not found, modules won't be signed Running the pre_build script: checking for gawk... gawk checking metadata... META file checking build system type... aarch64-unknown-linux-gnu checking host system type... aarch64-unknown-linux-gnu checking target system type... aarch64-unknown-linux-gnu checking whether to enable maintainer-specific portions of Makefiles... no checking whether make supports nested variables... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a race-free mkdir -p... /usr/bin/mkdir -p checking whether make sets $(MAKE)... yes checking how to print strings... printf checking whether make supports the include directive... yes (GNU style) checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether gcc accepts -g... yes checking for gcc option to enable C11 features... none needed checking whether gcc understands -c and -o together... yes checking dependency style of gcc... none checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking how to convert aarch64-unknown-linux-gnu file names to aarch64-unknown-linux-gnu format... func_convert_file_noop checking how to convert aarch64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for file... file checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for a working dd... /usr/bin/dd checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 checking for mt... mt checking if mt is a manifest tool... no checking for stdio.h... yes checking for stdlib.h... yes checking for string.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for strings.h... yes checking for sys/stat.h... yes checking for sys/types.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for gcc... (cached) gcc checking whether the compiler supports GNU C... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to enable C11 features... (cached) none needed checking whether gcc understands -c and -o together... (cached) yes checking dependency style of gcc... (cached) none checking whether ln -s works... yes checking for pkg-config... no checking dependency style of gcc... none checking whether to build with code coverage support... no checking how to create a pax tar archive... gnutar checking zfs author... OpenZFS checking zfs license... CDDL checking whether NLS is requested... yes checking for msgfmt... no checking for gmsgfmt... : checking for xgettext... no checking for msgmerge... no checking for ld... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking 32-bit host C ABI... no checking for the common suffixes of directories in the library search path... lib,lib checking zfs config... kernel checking the number of available CPUs... 8 checking whether gcc supports -Wno-clobbered... yes checking whether gcc supports -Winfinite-recursion... yes checking whether supports -Winfinite-recursion... yes checking whether gcc supports -Wimplicit-fallthrough... yes checking whether gcc supports -Wframe-larger-than=<size>... yes checking whether gcc supports -Wno-format-truncation... yes checking whether gcc supports -Wno-format-zero-length... yes checking whether gcc supports -Wformat-overflow... yes checking whether gcc supports -fno-omit-frame-pointer... yes checking whether gcc supports -fno-ipa-sra... yes checking whether supports -fno-ipa-sra... yes checking whether to build with -fsanitize=address support... no checking whether to build with -fsanitize=undefined support... no checking for system type (linux-gnu)... Linux checking for python3... python3 checking for python version... 3.11 checking for python platform... linux checking for GNU default python prefix... ${prefix} checking for GNU default python exec_prefix... ${exec_prefix} checking for python script directory (pythondir)... ${PYTHON_PREFIX}/lib/python3.11/site-packages checking for python extension module directory (pyexecdir)... ${PYTHON_EXEC_PREFIX}/lib/python3.11/site-packages configure: Disabling pyzfs for kernel/srpm config checking whether to enable pyzfs: ... no checking for sed --in-place... --in-place checking for cppcheck... no checking for shellcheck... no checking for checkbashisms... no checking for parallel... no checking kernel source and build directories... done checking kernel source directory... /lib/modules/6.14.0-edge-rockchip64/build checking kernel build directory... /lib/modules/6.14.0-edge-rockchip64/build checking kernel source version... 6.14.0-edge-rockchip64 configure: error: *** Cannot build against kernel version 6.14.0-edge-rockchip64. *** The maximum supported kernel version is 6.13. Building module: Cleaning build area...(bad exit status: 2) make -j8 KERNELRELEASE=6.14.0-edge-rockchip64...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.14.0-edge-rockchip64 (aarch64) Consult /var/lib/dkms/zfs/2.3.1/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.14.0-edge-rockchip64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 update-initramfs: Generating /boot/initrd.img-6.14.0-edge-rockchip64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8126a-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8126a-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125bp-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125d-1.fw for module r8169 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.14.0-edge-rockchip64 Image Name: uInitrd Created: Sat Apr 5 12:16:03 2025 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17825351 Bytes = 17407.57 KiB = 17.00 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.14.0-edge-rockchip64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.14.0-edge-rockchip64' update-initramfs: Armbian: done. Free space after deleting the package linux-image-edge-rockchip64 in /boot: 1.5G dpkg: error processing package linux-image-edge-rockchip64 (--configure): installed linux-image-edge-rockchip64 package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-edge-rockchip64 I guess it's in the ZFS version, but I can't remember which armbian repository I can install zfs from.

If there was a way to bring back an old version of kernel , I would test. But I don't know how. A crisis option is boot from another flash, chroot and fix the problem, but that takes a long time with me. My configuration is: the flash card is only /boot/, the OS is in raid1 /dev/nvme1n1p1 /dev/nvme2n1p1, separately I use zfs, again raid1 /dev/nvme1n1p2 u /dev/nvme2n1p2. I avoid using the test repo for this.

No problem. Super, I'll wait for it to show up and test it.

Здравейте, извинете за късния отговор, ето информацията от armbianmonitor -u https://paste.next.armbian.com/yajehilude I hope this is useful, if you need any further information I will share. After writing my post I think there are 2 or 3 new versions of kernel. So far everything else is working normally, at least apparently no problems. Greetings,

Hello, This is more informative. I saw the following news: https://www.armbian.com/newsflash/armbian-v25-2/ After seeing that you fixed USB3, I decided to update. For me, USB3 is not working. Stopped working and rngd If any additional information is needed, I will share.

After chrooting, uninstalling everything that is vendor and installing current, things were fine.

@eselarm Thanks for the idea. I'll test tonight. Kernel 6.12 works apparently very well and that's why I want to put it in. ZFS also works well. Apart from that, it made a positive impression on me that when booting the OS, the fan doesn't stop as it did with 6.1 and older versions and I had to manually adjust the dtb file.

Hello, Yesterday I was doing an upgrade on my NanoPi T6, and then I got a kernel panic and no boot. I am currently running kernel 6.1.84 To recover my information through a new mmc card I put armbian with kernel 6.12. And I logged in by doing a chroot. There used to be an option to install a newer kernel via armbian-config, but I can't find that option now. Is there any way how i can put on my current server a newer kernel or through cli which packages should i install. Greetings, A.H.

Hello, I apologize in advance if I haven't put the topic in the right section. I want to share my experience with NanoPC-T6 and two NVMe m.2 disk. I use my NanoPC-T6 for a small server. In the beginning I had 2 SSDs and an M.2 to 2 SATA adapter. But I never found the right solution to power both the NanoPC-T6 and the SSDs from 1 place. After some internet searching I was able to find a solution on how to put 2 NVMe drives on my NanoPC-T6 As you know NanoPC-T6 has 1 M.2 M-Key connector with PCIe 3.0 x4 There is also one PCIe which is M.2 E-key connector with PCIe 2.1 x1 With this adapter: https://www.aliexpress.com/item/1005004762924052.html I am using M.2 E-key to M.2 M-Key. The version of the kernel I use is 6.1.43-vendor-rk35xx. The speed that the NVMe disk on the adapter board can reach is about 400MB per second, which is quite good for my needs. I am attaching some pictures. I hope this is useful for you. If there are any questions, I'm at the meeting to answer them. Regards,

Due to my oversight, I have not posted the topic in the correct section. I'll help move it to "Software, Applications, Userspace".

I have no complaints about the kernel that comes with the board. And with the fact that the ZFS packages supplied by armbian are not for debian 12 (bookworm). This has nothing to do with my board. I imagine there will be other boards that will have problems with the zfs package that comes from armbian and are using debian 12. As you can see, I have also shared the workaround.

Hello, I found a temporary solution to the problem: Here are the steps: aptitude remove zfs-dkms aptitude install zfs-zed=2.2.3-1~bpo12+1 zfsutils-linux=2.2.3-1~bpo12+1 zfs-dkms=2.2.3-1~bpo12+1 aptitude install libnvpair3linux=2.2.3-1~bpo12+1 libzfs4linux=2.2.3-1~bpo12+1 libuutil3linux=2.2.3-1~bpo12+1 libzfs4linux=2.2.3-1~bpo12+1 libzpool5linux=2.2. 3-1~bpo12+1 aptitude install zfs-zed=2.2.3-1~bpo12+1 zfsutils-linux=2.2.3-1~bpo12+1 aptitude hold libnvpair3linux libuutil3linux libzfs4linux libzpool5linux zfs-dkms zfs-zed zfsutils-linux After "locking" the packages, you should see this: root@msrv 48.07℃ :~# apt-mark showhold libnvpair3linux libuutil3linux libzfs4linux libzpool5linux zfs-dkms zfs-zed zfsutils-linux systemctl enable --now zfs-scrub-weekly@ZPOOL.timer systemctl enable --now zfs-trim-weekly@ZPOOL.timer - if the array is on SSD It would be nice from the armbian team to fix things Actually, the new versions of zfs-dkms and zfsutils-linux come from the armbian repo, and these packages look for the libssl3t64 package, which is not present in Debian Bookworm, but is present in Debian Sid. I assume the Debian packages are compiled on top of Ubuntu, which is based on the Debian Sid. Regards,

Hello. I also had such a problem some time ago. I don't know how much experience you have with linux. Probably missing the /boot stuff. You can try the following, but it's a bit risky. You make an mmc card with arbian and kernel 6.1.XX. and you start nanopc from it. After it loads. You put in a USB to SD card adapter. In the new memory card, after loading the OS, create an OMV folder, in it /OMV/boot and /OMV/os/ in it you create /OMV/boot and /OMV/os/ rsync -va /boot/ /OMV/boot/ mv /OMV/os/lib/modules/6.1.43-vendor-rk35xx /OMV/os/lib/modules/6.1.43-vendor-rk35xx_old rsync -va /lib/modules/6.1.43-vendor-rk35xx /OMV/os/lib/modules/ After that, umount /OMV/boot and /OMV/os/, put the OMV card in the nanopc and if you're lucky, it might start. I hope I was helpful and good luck

Hello, I have ZFS installed, today there was an update, in which I no longer have ZFS. root@msrv 49.00℃ :~# apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: libnvpair3linux libuutil3linux libzfs4linux libzpool5linux Use 'apt autoremove' to remove them. The following packages will be REMOVED: zfs-zed zfsutils-linux The following packages have been kept back: libnvpair3linux libzfs4linux The following packages will be upgraded: libuutil3linux libzpool5linux zfs-dkms 3 upgraded, 0 newly installed, 2 to remove and 2 not upgraded. Need to get 0 B/3,598 kB of archives. After this operation, 2,533 kB disk space will be freed. Do you want to continue? [Y/n] Y Preconfiguring packages ... (Reading database ... 71907 files and directories currently installed.) Removing zfs-zed (2.1.11-1) ... Removing zfsutils-linux (2.2.3-1) ... (Reading database ... 71592 files and directories currently installed.) Preparing to unpack .../libuutil3linux_2.2.3-2_arm64.deb ... Unpacking libuutil3linux (2.2.3-2) over (2.2.3-1) ... Preparing to unpack .../libzpool5linux_2.2.3-2_arm64.deb ... Unpacking libzpool5linux (2.2.3-2) over (2.2.3-1) ... Preparing to unpack .../zfs-dkms_2.2.3-2_all.deb ... Module zfs-2.2.3 for kernel 6.1.43-vendor-rk35xx (aarch64). Before uninstall, this module version was ACTIVE on this kernel. zfs.ko: - Uninstallation - Deleting from: /lib/modules/6.1.43-vendor-rk35xx/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. spl.ko: - Uninstallation - Deleting from: /lib/modules/6.1.43-vendor-rk35xx/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... Deleting module zfs-2.2.3 completely from the DKMS tree. Unpacking zfs-dkms (2.2.3-2) over (2.2.3-1) ... Setting up zfs-dkms (2.2.3-2) ... Loading new zfs-2.2.3 DKMS files... Building for 6.1.43-vendor-rk35xx Building initial module for 6.1.43-vendor-rk35xx Done. zfs.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.1.43-vendor-rk35xx/updates/dkms/ spl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.1.43-vendor-rk35xx/updates/dkms/ depmod... Setting up libuutil3linux (2.2.3-2) ... Setting up libzpool5linux (2.2.3-2) ... Processing triggers for libc-bin (2.36-9+deb12u7) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for initramfs-tools (0.142) ... ln: failed to create hard link '/boot/initrd.img-6.1.43-vendor-rk35xx.dpkg-bak' => '/boot/initrd.img-6.1.43-vendor-rk35xx': Operation not permitted update-initramfs: Generating /boot/initrd.img-6.1.43-vendor-rk35xx W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 W: Possible missing firmware /lib/firmware/regulatory.db for built-in driver cfg80211 W: Possible missing firmware /lib/firmware/regulatory.db.p7s for built-in driver cfg80211 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.43-vendor-rk35xx Image Name: uInitrd Created: Sat May 11 11:42:20 2024 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 9305942 Bytes = 9087.83 KiB = 8.87 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.43-vendor-rk35xx to /boot/uInitrd ln: failed to create symbolic link '/boot/uInitrd': Operation not permitted update-initramfs: Symlink failed, moving /boot/uInitrd-6.1.43-vendor-rk35xx to /boot/uInitrd renamed '/boot/uInitrd-6.1.43-vendor-rk35xx' -> '/boot/uInitrd' update-initramfs: Armbian: done. root@msrv 48.07℃ :~# Fortunately, the module is on and everything is working now. ZFS is from the armbian repo. When I try to install I get this: root@msrv 47.15℃ :~# aptitude install zfs-zed zfsutils-linux The following NEW packages will be installed: libuutil3linux{a} zfs-zed{b} zfsutils-linux{b} 0 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 541 kB/666 kB of archives. After unpacking 2,696 kB will be used. The following packages have unmet dependencies: zfs-zed : Depends: libnvpair3linux (>= 0.8.2) but it is not installable Depends: libzfs4linux (>= 2.1.11-1) but it is not installable zfsutils-linux : Depends: libnvpair3linux (= 2.2.3-2) but it is not installable Depends: libzfs4linux (= 2.2.3-2) but it is not installable Depends: libzpool5linux (= 2.2.3-2) but it is not installable Depends: libssl3t64 (>= 3.0.0) which is a virtual package and is not provided by any available package The following actions will resolve these dependencies: Keep the following packages at their current version: 1) zfs-zed [Not Installed] 2) zfsutils-linux [Not Installed] Accept this solution? [Y/n/q/?] Y No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. Any ideas on how to fix it and/or what to provide as additional information

Hello, Today I upgraded from 24.5.0-trunk.231 to 24.5.0-trunk.318, for now everything is working normally. But I had to recompile the zfs module again. It has zfs-dkms installed, shouldn't it just recompile the module? If there is a need to upload a log or provide other information, I am available. Regards,

Hello, I don't have any issues with the CPU, I'm saying if I had to choose I'd go with the CPU, not the internal drive. Otherwise, I'm currently with kernel linux-image-vendor-rk35xx:arm64 24.5.0-trunk.231 and everything works fine. This kernel was installed via apt dist-upgrade. lscpu says everything normal but cpu-info keeps seeing things wrong. I'm not sure where the problem is. Regards,

Hello, My mistake. The image I use was published on 13.03.2024. Up until this point I was working with a personal kernel build based on armbian. From personal memory, I think it is 24.5.0-trunk.211 This is bad news for me. Apparently I won't touch the kernel. I already had a case, in a personal build, I used armbian-config to see a 5.10 kernel version, then I also put 6.1.43. Then the script removed kernel 5.10 and did not install 6.1.43. And everything started anew. That's how I found out that it was posted on 13.03.2024 image For me, it's more important to have a working CPU than an internal drive. Otherwise, I use the built-in disk to backup boot and the OS. In the source of the Edge version, at least until recently, most of the governors were missing. Now I've run and see that's fixed. I can't use Edge because of ZFS.

Hello, I will use the NanoPC-T6 for a micro server. The main thing it will run on is LibreNMS (currently my LibreNMS is on a NanoPi R6S) I will also use ZFS, tftp, bond, vlan and others. The reason I use the NanoPC-T6 is the 16GB ram as well as the PCIe slot. I am attaching 2 pictures if anyone is curious about what I have created. It's not very pretty, but it's functional. What I have further configured in /boot/armbianEnv.txt verbosity=7 - I prefer to see the OS loading extraargs=net.ifnames=0 biosdevname=0 consoleblanl=0 brd.rd_nr=0 mitigations=off brd.rd_nr=0 stops all Ram Block Devices mitigations=off - this is on an internal network and since I don't know if I'll lose performance I just stop everything console=serial - console output only serial port docker_optimizations=off - I don't use docker I only use the memory card for /boot The OS is on the SSD in raid1 (about 16GB), the rest is raid1 in a zfs array, for 3 pools (mysql, librenms, storage) I have installed ZFS like this: apt install linux-headers-vendor-rk35xx zfsutils-linux zfs-dkms zfs-zed From the kernels offered by Armbian 5.10, 6.1 and 6.8, I use 6.1 I removed the network-manager wpasupplicant packages, instead of network-manager I use ifupdown2 The control of the fan is through the dts file. The steering has 5 levels. 1st degree is at 50 degrees, then 2nd degree - 60 and so on With installed fan and stress-ng more than 55 degrees I can not lift. At linux-image-vendor-rk35xx_24.5.0-trunk.226_arm64 ZFS - compiles normally. governor - on CPU works, has all modes of operation governor for dmc, gpu and npu - only ondeman. Network cards work normally. FAN - management through the dts file works normally. At linux-image-vendor-rk35xx_24.5.0-trunk.231_arm64 Installed from apt dist-upgrade, ZFS doesn't compile, had to do aptitude reinstall zfsutils-linux zfs-dkms zfs-zed governor - on CPU works, has all modes of operation governor at dmc, gpu and npu - , has all modes of operation Network cards work normally. FAN - management through the dts file works normally. On this build, one core is constantly at 100% (probably ZFS, but not sure about top and htop doesn't show which one is causing the IO) I am using the 13.03 image, in this version in install linux-headers does not work, I installed it by hand. While writing this I saw in armbian-config that there is already a version linux-image-vendor-rk35xx_24.5.0-trunk.244_arm64 but I can't find what is fixed and will wait for it to appear with apt. I have further increased the size of /boot to 2GB like this: aptitude install fatresize umount /boot/ fatresize -v -p -s 2G /dev/mmcblk1p1 mount -a Before using armbian kernel I had compiled 6.1 with these optimizations. General setup ---> Preemption Model (Voluntary Kernel Preemption (Desktop)) ---> No Forced Preemption (Server) General setup ---> Compiler optimization level (Optimize for performance (-O2)) ---> Optimize for performance (-O2) Kernel Features ---> Timer frequency (300 HZ) ---> (X) 100 HZ As a positive effect, the system is a little more "agile". Negative effect, slightly warmer is the housing of the box. What I would like fixed. My version of NanoPC-T6 is 16GB ram and 256GB internal disk. In this case I don't see the internal disk. The other thing I want is to keep the old versions of the kernel. Currently, when I install a new version of the kernel, the old version of the kernel is uninstalled, and if the OS does not start, I have to do everything from the beginning. It could be a setting, but I can't find where it is. Regarding what I used like FAN, PCIe to Sata and SSD cage, I don't know if it is allowed to post links, not to be considered as advertising. I hope this is useful to someone. Regards,

Hello, Thanks to @ALIGMSTEN and @SteeMan, these days I will write what I have tested. Regards,

Hello, At the moment I am working with an image that is from the site. Many of the things work OK, but there are some that have reservations. I don't know if it's appropriate to comment in the tickets or address someone specifically or write elsewhere. That's what the last comment was about. I am happy with what has been done, but I would like to share impressions if anyone is interested. I know we are all busy with work, family, etc. And in order not to waste the time of many people, I asked like this. Regards,

Hello, I saw that on March 13 you released an image with kernel 6.1.XX. using the image, I would like to share feedback. Should I write here or can I address someone specifically? Regards,

Hello, I downloaded the source from the git repository. The configurator and compiler are very intuitive. They are easy to work with. Saved a lot of time and nerves Thanks for what has been done as a configurator and the documentation. Because I don't know if my problem is in the dtb file or in the kernel. I compiled three versions edge 6.8.0-rc7 - this does not work correctly. legacy 5.10.160 - everything works here. vendor 6.1.43 - everything works here. And I was pleasantly surprised to find out that the fan control is also active. CPU frequency scaling - works correctly on "legacy" and "vendor". CPUs are successfully overclocked to factory frequencies. For now, I'm still experimenting with compiling the kernel. I'm open to suggestions and tests. I hope this information was helpful. Regards,

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,