Search the Community

Unfortunately apt install --no-install-recommends wireguard doesn't help. I started by installing headers first which seemed to skip a kernel install (at least I got a – autoinstall for kernel 6.1.0-23-rt-arm64 was skipped since the kernel headers for this kernel do not seem to be installed – message) but still no boot on restart. I even tried installing edge kernel and headers which worked for me last time but as soon as Wireguard's installed it refuses to boot.

Hi Werner, thanks for your reply. I tried again several times today, including with the latest server image and am still unable to boot following installation (though no errors are reported). It occurred to me I should've tried installing headers first but I've spent another day trying to nut it out so I'll have to leave it for another day. Really frustrating not knowing what I'm doing wrong. I'll give this a try next time, thanks.

Bumps oras from 0.1.30 to 0.2.2. Release notes Sourced from oras's releases. Oras Python Release v0.2.2 What's Changed Token Auth Backend: Token request function didn`t set Authorization Header by @mariusbertram in oras-project/oras-py#153 Full Changelog: https://github.com/oras-project/oras-py/compare/0.2.1...0.2.2 Oras Python Release v0.2.1 What's Changed wip: separate auth into backends by @vsoch in oras-project/oras-py#134 docs: use valid media_type format in examples by @tarilabs in oras-project/oras-py#139 [tributors] contributors/update-2024-06-06 by @github-actions in oras-project/oras-py#140 chore: fix typing for manifest_config param of push fn by @tarilabs in oras-project/oras-py#141 core: make push response the one pertaining to Manifest (not config by @tarilabs in oras-project/oras-py#146 fix(core): provider do_request to maintain verify in all request, basic headers by @tarilabs in oras-project/oras-py#145 Enable chunked uploads by @isinyaaa in oras-project/oras-py#150 [tributors] contributors/update-2024-09-04 by @github-actions in oras-project/oras-py#151 New Contributors @tarilabs made their first contribution in oras-project/oras-py#139 @isinyaaa made their first contribution in oras-project/oras-py#150 Full Changelog: https://github.com/oras-project/oras-py/compare/0.1.30...0.2.1 Changelog Sourced from oras's changelog. CHANGELOG This is a manually generated log to track changes to the repository for each release. Each section should include general headers such as Implemented enhancements and Merged pull requests. Critical items to know are: renamed commands deprecated / removed commands changed defaults backward incompatible changes (recipe file format? image file format?) migration guidance (how to convert images?) changed behaviour (recipe sections work differently) The versions coincide with releases on pip. Only major versions will be released as tags on Github. 0.0.x (0.0.x) add missing basic auth data for request token function in token auth backend (0.2.2) re-enable chunked upload (0.2.1) refactor of auth to be provided by backend modules (0.2.0) bugfix maintain requests's verify valorization for all invocations, augment basic auth header to existing headers Allow generating a Subject from a pre-existing Manifest (0.1.30) add option to not refresh headers during the pushing flow, useful for push with basic auth (0.1.29) enable additionalProperties in schema validation (0.1.28) Introduce the option to not refresh headers when fetching manifests when pulling artifacts (0.1.27) To make it available for more OCI registries, the value of config used when manifest_config is not specified in client.push() has been changed from a pure empty string to {} (0.1.26) refactor tests using fixtures and rework pre-commit configuration (0.1.25) eliminate the additional subdirectory creation while pulling an image to a custom output directory (0.1.24) updating the exclude string in the pyproject.toml file to match the data type black expects patch fix for pulling artifacts by digest (0.1.23) patch fix to reject cookies as this could trigger registries into handling the lib as a web client patch fix for proper validation and specification of the subject element add tls_verify to provider class for optional disable tls verification (0.1.22) Allow to pull exactly to PWD (0.1.21) Ensure insecure is passed to provider class (0.1.20) patch fix for blob upload Windows, closes issue 93 (0.1.19) patch fix for empty manifest config on Windows, closes issue 90 (0.1.18) patch fix to correct session url pattern, closes issue 78 (0.1.17) add support for tag deletion and retry decorators (0.1.16) bugfix that pagination sets upper limit of 10K (0.1.15) pagination for tags (and general function for pagination) (0.1.14) expose upload_blob function to be consistent (0.1.13) ensure we always strip path separators before pull/push (0.1.12) exposing download_blob to the user since it uses streaming (0.1.11) adding developer examples for pull. start deprecation for _download_blob, _put_upload, _chunked_upload, _upload_manifest in favor of equivalent public functions. moving of docs to fully be here with extended examples (0.1.1) addition of oras.utils.workdir to provide local context clients are removed from Python SDK in favor of examples (0.1.0) login refactored to be part of the basic client ... (truncated) Commits 5d7b80d Token Auth Backend: Token request function didn`t set Authorization Header (#... 5763015 Automated deployment to update contributors 2024-09-04 (#151) dfc2415 Enable chunked uploads (#150) caf8db5 fix(core): provider do_request to maintain verify in all request, basic heade... b8c4885 core: make push response the one pertaining to Manifest (not config (#146) fd8a83c Merge pull request #141 from tarilabs/tarilabs-20240606-manifest_config 3a571e3 chore: fix typing for manifest_config param of push fn 9527aa1 Merge pull request #140 from oras-project/contributors/update-2024-06-06 19c1cb5 Automated deployment to update contributors 2024-06-06 571a23f Merge pull request #139 from tarilabs/tarilabs-20240605-docMediaType Additional commits viewable in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

Here you go: rob@orangepi5:~$ apt list --installed| grep armbian WARNING: apt does not have a stable CLI interface. Use with caution in scripts. armbian-bsp-cli-orangepi5-legacy/bookworm,now 24.5.1 arm64 [installed] armbian-bsp-cli-orangepi5/bookworm,now 24.8.2 arm64 [installed] armbian-config/bookworm,bookworm,bookworm,now 24.8.2 all [installed] armbian-firmware/bookworm,bookworm,bookworm,now 24.8.2 all [installed] armbian-plymouth-theme/bookworm,bookworm,bookworm,now 24.8.2 all [installed] armbian-zsh/bookworm,bookworm,bookworm,now 24.8.2 all [installed] hostapd/now 3:2.10-6~armbian22.02.3+1 arm64 [installed,local] rob@orangepi5:~$ apt list --installed| grep linux WARNING: apt does not have a stable CLI interface. Use with caution in scripts. binutils-aarch64-linux-gnu/stable,now 2.40-2 arm64 [installed,automatic] console-setup-linux/stable,stable,now 1.221 all [installed] libselinux1/stable,now 3.4-1+b6 arm64 [installed] linux-base/stable,stable,now 4.9 all [installed] linux-dtb-legacy-rk35xx/bookworm,now 24.5.1 arm64 [installed] linux-dtb-vendor-rk35xx/bookworm,now 24.8.2 arm64 [installed] linux-headers-legacy-rk35xx/bookworm,now 24.5.1 arm64 [installed] linux-image-legacy-rk35xx/bookworm,now 24.5.1 arm64 [installed] linux-image-vendor-rk35xx/bookworm,now 24.8.2 arm64 [installed] linux-libc-dev/now 23.02.2 arm64 [installed,local] linux-u-boot-orangepi5-legacy/bookworm,now 24.5.1 arm64 [installed] util-linux-extra/stable,stable-security,now 2.38.1-5+deb12u1 arm64 [installed,automatic] util-linux/stable,stable-security,now 2.38.1-5+deb12u1 arm64 [installed]

All I've done is apt update and somehow it got in this state. Any suggestions on how to fix? I tried the following but didn't work: rob@orangepi5:~$ sudo apt remove armbian-bsp-cli-orangepi5-legacy Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: armbian-bsp-cli-orangepi5 : Depends: armbian-bsp-cli-orangepi5-current (= 24.8.2) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). rob@orangepi5:~$ rob@orangepi5:~$ rob@orangepi5:~$ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: armbian-bsp-cli-orangepi5-current The following NEW packages will be installed: armbian-bsp-cli-orangepi5-current 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/430 kB of archives. After this operation, 1,435 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 104089 files and directories currently installed.) Preparing to unpack .../armbian-bsp-cli-orangepi5-current_24.8.2_arm64.deb ... Armbian 'armbian-bsp-cli-orangepi5-current' for '1-PC868b-V1187-H21c6-B199a-R7697': 'preinst' starting. Armbian 'armbian-bsp-cli-orangepi5-current' for '1-PC868b-V1187-H21c6-B199a-R7697': 'preinst' finishing. Unpacking armbian-bsp-cli-orangepi5-current (24.8.2) ... dpkg: error processing archive /var/cache/apt/archives/armbian-bsp-cli-orangepi5-current_24.8.2_arm64.deb (--unpack): trying to overwrite '/etc/X11/xorg.conf.d/01-armbian-defaults.conf', which is also in package armbian-bsp-cli-orangepi5-legacy 24.5.1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Armbian 'armbian-bsp-cli-orangepi5-current' for '1-PC868b-V1187-H21c6-B199a-R7697': 'postrm' starting. Armbian 'armbian-bsp-cli-orangepi5-current' for '1-PC868b-V1187-H21c6-B199a-R7697': 'postrm' finishing. Errors were encountered while processing: /var/cache/apt/archives/armbian-bsp-cli-orangepi5-current_24.8.2_arm64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Here's the legacy packages that are installed: rob@orangepi5:~$ apt list --installed| grep legacy WARNING: apt does not have a stable CLI interface. Use with caution in scripts. armbian-bsp-cli-orangepi5-legacy/bookworm,now 24.5.1 arm64 [installed] linux-dtb-legacy-rk35xx/bookworm,now 24.5.1 arm64 [installed] linux-headers-legacy-rk35xx/bookworm,now 24.5.1 arm64 [installed] linux-image-legacy-rk35xx/bookworm,now 24.5.1 arm64 [installed] linux-u-boot-orangepi5-legacy/bookworm,now 24.5.1 arm64 [installed]

I have installed the recently released `Desktop images with Armbian Linux v6.10` image (24.8.1, Debian Bookworm, with the Cinnamon desktop) on an OrangePi5 and I'm happy the HDMI support included has finaly enabled the video to my 1080p display. However, my previously supported WiFi adapter is not recognized in this version - it worked with the vendor (5.10) kernel which I used with last year's OrangePi5 image, but how it seems the driver is not installed with 6.10. The WiFi adapter is connected via USB and it's listed as Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter. Now, there are a few DKMS/out-of-tree drivers that I could install, but the problem is that there are no kernel headers for the current Linux image kernel - trying to install them via armbian-config returns me to the previous screen almost immediately. Is the kernel headers package missing or is maybe named differently ? FWIW, the Linux image package is linux-image-current-rockchip-rk3588.

Hello @Igor, thank you for the update. I understand the predicament for lacking enough resources given the scope of the project and I don't expect things to work OOB without testing. I've updated the package list via apt and now I can see the headers package now for the current-rockchip-rk3588 Linux kernel (along with a the new linux-image .deb package). I have installed it and can confirm that dkms works fine to complile the WiFi dongle's driver - though it's not fully working yet, though this is purely a driver issue, not related to Armbian/Debian. Thanks for the updated kernel packages.

Bumps oras from 0.1.30 to 0.2.2. Release notes Sourced from oras's releases. Oras Python Release v0.2.2 What's Changed Token Auth Backend: Token request function didn`t set Authorization Header by @mariusbertram in oras-project/oras-py#153 Full Changelog: https://github.com/oras-project/oras-py/compare/0.2.1...0.2.2 Oras Python Release v0.2.1 What's Changed wip: separate auth into backends by @vsoch in oras-project/oras-py#134 docs: use valid media_type format in examples by @tarilabs in oras-project/oras-py#139 [tributors] contributors/update-2024-06-06 by @github-actions in oras-project/oras-py#140 chore: fix typing for manifest_config param of push fn by @tarilabs in oras-project/oras-py#141 core: make push response the one pertaining to Manifest (not config by @tarilabs in oras-project/oras-py#146 fix(core): provider do_request to maintain verify in all request, basic headers by @tarilabs in oras-project/oras-py#145 Enable chunked uploads by @isinyaaa in oras-project/oras-py#150 [tributors] contributors/update-2024-09-04 by @github-actions in oras-project/oras-py#151 New Contributors @tarilabs made their first contribution in oras-project/oras-py#139 @isinyaaa made their first contribution in oras-project/oras-py#150 Full Changelog: https://github.com/oras-project/oras-py/compare/0.1.30...0.2.1 Changelog Sourced from oras's changelog. CHANGELOG This is a manually generated log to track changes to the repository for each release. Each section should include general headers such as Implemented enhancements and Merged pull requests. Critical items to know are: renamed commands deprecated / removed commands changed defaults backward incompatible changes (recipe file format? image file format?) migration guidance (how to convert images?) changed behaviour (recipe sections work differently) The versions coincide with releases on pip. Only major versions will be released as tags on Github. 0.0.x (0.0.x) add missing basic auth data for request token function in token auth backend (0.2.2) re-enable chunked upload (0.2.1) refactor of auth to be provided by backend modules (0.2.0) bugfix maintain requests's verify valorization for all invocations, augment basic auth header to existing headers Allow generating a Subject from a pre-existing Manifest (0.1.30) add option to not refresh headers during the pushing flow, useful for push with basic auth (0.1.29) enable additionalProperties in schema validation (0.1.28) Introduce the option to not refresh headers when fetching manifests when pulling artifacts (0.1.27) To make it available for more OCI registries, the value of config used when manifest_config is not specified in client.push() has been changed from a pure empty string to {} (0.1.26) refactor tests using fixtures and rework pre-commit configuration (0.1.25) eliminate the additional subdirectory creation while pulling an image to a custom output directory (0.1.24) updating the exclude string in the pyproject.toml file to match the data type black expects patch fix for pulling artifacts by digest (0.1.23) patch fix to reject cookies as this could trigger registries into handling the lib as a web client patch fix for proper validation and specification of the subject element add tls_verify to provider class for optional disable tls verification (0.1.22) Allow to pull exactly to PWD (0.1.21) Ensure insecure is passed to provider class (0.1.20) patch fix for blob upload Windows, closes issue 93 (0.1.19) patch fix for empty manifest config on Windows, closes issue 90 (0.1.18) patch fix to correct session url pattern, closes issue 78 (0.1.17) add support for tag deletion and retry decorators (0.1.16) bugfix that pagination sets upper limit of 10K (0.1.15) pagination for tags (and general function for pagination) (0.1.14) expose upload_blob function to be consistent (0.1.13) ensure we always strip path separators before pull/push (0.1.12) exposing download_blob to the user since it uses streaming (0.1.11) adding developer examples for pull. start deprecation for _download_blob, _put_upload, _chunked_upload, _upload_manifest in favor of equivalent public functions. moving of docs to fully be here with extended examples (0.1.1) addition of oras.utils.workdir to provide local context clients are removed from Python SDK in favor of examples (0.1.0) login refactored to be part of the basic client ... (truncated) Commits 5d7b80d Token Auth Backend: Token request function didn`t set Authorization Header (#... 5763015 Automated deployment to update contributors 2024-09-04 (#151) dfc2415 Enable chunked uploads (#150) caf8db5 fix(core): provider do_request to maintain verify in all request, basic heade... b8c4885 core: make push response the one pertaining to Manifest (not config (#146) fd8a83c Merge pull request #141 from tarilabs/tarilabs-20240606-manifest_config 3a571e3 chore: fix typing for manifest_config param of push fn 9527aa1 Merge pull request #140 from oras-project/contributors/update-2024-06-06 19c1cb5 Automated deployment to update contributors 2024-06-06 571a23f Merge pull request #139 from tarilabs/tarilabs-20240605-docMediaType Additional commits viewable in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

@Werner thank you for the reply. I'm familiar with the Wiki page, I'm aware some functionality will be missing using the 'edge/current' kernels. In fact, my intention when using the current/upstream kernel was to test how HDMI output was working, since it wasn't working a few months back. However, the functionality I'm missing is not related to the specific SBC/Vendor - as you said also, I was expecting the driver for the 8812au to be included/work. I haven't found a related 'kernel headers' package through apt also, hence my question/topic is mostly about the package. Having the headers package would help with any external kernel module that would be installed through dkms.

https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one mixed up. 5.10.y is legacy, 6.1.y is vendor. While it is great to have mainline for this board it is far from feature-complete. If you need more hw features to work you have to use vendor kernel branch. Have you tried to lookup headers via apt? If no success, try building your own kernel packages, or an image with matching headers pre-installed, with the build framework: https://github.com/armbian/build Sometimes it can happen that headers are not available for various reasons. Uncaught packaging failure, mirror unsync, .... Still interesting though since IIRC driver for 8812au should be included by default. However it might have been disabled due to build errors or whatever...

Hello, I have a problem, when I enter "sudo apt install zfs-dkms" on my Helios64, I get this error message: "Module build for kernel 6.6.36-current-rockchip64 was skipped because the kernel headers for this kernel do not appear to be installed." I also made sure to install the kernel header in armbian-config and also rebooted. When I type "apt list --installed | grep linux-headers", I get this listing: WARNING: apt does not have a stable CLI interface. Use it with caution in scripts. linux-headers-current-rockchip64/bookworm,now 24.5.1 arm64 [installed] omv7 itself is installed and running. The image "Armbian_24.5.3_Helios64_bookworm_current_6.6.36_minimal.img.xz" has been installed. apt update and apt upgrade were run after installing the image The plan is to get OMV7 running with zfs on my Helios64 I hope someone can help me with this Regards Saam27

Struggle continues... Because the hdmi is not working (error logs mentioned above) I tried uninstalling armbian kernels & installed official vendor .deb files, These I compiled using OPi official build procedure for OPi 3b v2.1 You can get x3 .debs from .7z archive here https://github.com/defencedog/orangepi3b_v2.1/tree/b0d58e10589c567025774da07ea300e48631740f/Orangepi-3B%20rk3566-5.10.160-panfrost/cross-built then apt list --installed |grep -e ^linux-image -e ^linux-dtb -e ^linux-headers sudo apt purge linux-image-xxx linux-dtb-xxx linux-headers-xxx sudo apt install libssl-dev python-is-python3 sudo dpkg -i linux-dtb-legacy-rockchip-rk356x_1.0.6_arm64.deb linux-headers-legacy-rockchip-rk356x_1.0.6_arm64.deb linux-image-legacy-rockchip-rk356x_1.0.6_arm64.deb sudo sync because of changed dtb & overlays modify /boot/armbianEnv.txt Following x2 lines must be same. This reflect changes in /boot/dtb/rockchip/ & /boot/dtb/rockchip/overlays overlay_prefix=rk356x fdtfile=rockchip/rk3566-orangepi-3b-v2.dtb Save edits & reboot Success HDMI now works. BT doesn't work (no module found). WIFI also works however Broadcom now uses wl driver instead of brcmfmac I installed ubuntu-desktop & the cursor is invisible, however cursor works OK while logged in as X-session of Ubuntu meaning wayland is to blame. If you logged in KODI wayland session cursor works OK?? GDM3 has no cursor as well When I move cursor while in wayland session, these errors keep repeating journalctl -f Aug 26 20:41:02 orangepi3b gnome-shell[2921]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Aug 26 20:41:02 orangepi3b kernel: [drm:vop2_plane_atomic_check] *ERROR* Unsupported linear format at Cluster0-win0 Aug 26 20:41:02 orangepi3b gnome-shell[2921]: Page flip discarded: drmModeAtomicCommit: Invalid argument Aug 26 20:41:02 orangepi3b gnome-shell[2921]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Aug 26 20:41:02 orangepi3b kernel: [drm:vop2_plane_atomic_check] *ERROR* Unsupported linear format at Cluster0-win0 Aug 26 20:41:02 orangepi3b gnome-shell[2921]: Page flip discarded: drmModeAtomicCommit: Invalid argument Aug 26 20:41:02 orangepi3b gnome-shell[2921]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Aug 26 20:41:02 orangepi3b kernel: [drm:vop2_plane_atomic_check] *ERROR* Unsupported linear format at Cluster0-win0 Aug 26 20:41:02 orangepi3b gnome-shell[2921]: Page flip discarded: drmModeAtomicCommit: Invalid argument I strongly believe its some GNOME related error. Internet is full of this bug when people are using eGPUs. If anyone has any idea, please help

Long story short, I accidentally removed all the contents of the /boot folder 😢. I'm running minimal Armbian 24.5.1 Bookworm with Linux 6.1.43-vendor-rk35xx on Orange pi 5 plus. It all started with a failed apt update indicating there wasn't enough space in the boot partition. The update was trying to install 6.1.75-vendor-rk35xx kernel, so I decided to remove the old one from the boot to free up some space. Instead, I accidentally applied 'rm -r' to the entire /boot folder. My SBC is working fine now, but I'm afraid it won't boot on next restart, so I'm looking for a way to recover the files. So far, I performed apt upgrade, which put the new 6.1.75-vendor-rk35xx kernel in the boot, but I'm not sure if it installed correctly - there was a warning that it couldn't be done automatically since there were no headers. I also copied armbianEnv.txt and boot.cmd from Armbian_24.5.3_Orangepi5-plus_bookworm_vendor_6.1.43_minimal.img so now armbianEnv.txt looks like below: verbosity=1 bootlogo=false console=both overlay_prefix=rockchip-rk3588 fdtfile=rockchip/rk3588-orangepi-5-plus.dtb rootdev=UUID=0af659d6-5b18-4106-9904-3ec2a1445b8a rootfstype=ext4 Finally I used u-boot-tools to make boot.scr: mkimage -C none -A arm -T script -d boot.cmd boot.scr Did I miss anything, or am I good to try restarting the SBC and see how it goes 😅? The original contents: total 74660 4 -rw-r--r-- 1 1003 1003 254 Jul 23 23:40 armbianEnv.txt 4 -rw-r--r-- 1 root root 1536 Sep 10 2023 armbian_first_run.txt.template 40 -rw-r--r-- 1 root root 38518 Sep 10 2023 boot.bmp 4 -rw-r--r-- 1 1003 1003 3820 Sep 10 2023 boot cmd 4 -rw-rw-r-- 1 root root 3892 Sep 10 2023 boot.scr 240 -rw-r--r-- 1 root root 243278 May 20 15:52 config-6.1.43-vendor-rk35xx 0 lrwxrwxrwx 1 root root 24 Jul 24 00:44 dtb -> dtb-6.1.43-vendor-rk35xx 4 drwxr-xr-x 3 root root 4096 Jun 12 12:21 dtb-5.10.160-legacy-rk35xx 4 drwxr-xr-x 3 root root 4096 Jun 17 20:40 dtb-6.1.43-vendor-rk35xx 0 lrwxrwxrwx 1 root root 28 Jul 24 00:44 Image -> vmlinuz-6.1.43-vendor-rk35xx 15452 -rw-r--r-- 1 root root 15816813 Jul 24 00:30 initrd.img-6.1.43-vendor-rk35xx 16 drwx------ 2 root root 16384 Sep 10 2023 lost+found 4 drwxr-xr-x 2 root root 4096 Feb 23 21:28 overlay-user 6836 -rw-r--r-- 1 root root 6998291 May 20 15:52 System.map-6.1.43-vendor-rk35xx 0 lrwxrwxrwx 1 root root 28 Jul 24 00:30 uInitrd -> uInitrd-6.1.43-vendor-rk35xx 15452 -rw-r--r-- 1 root root 15816877 Jul 24 00:30 uInitrd-6.1.43-vendor-rk35xx 36596 -rw-r--r-- 1 root root 37468672 May 20 15:52 vmlinuz-6.1.43-vendor-rk35xx After recover: total 74296 4 -rw-r--r-- 1 root root 181 Jul 25 01:14 armbianEnv.txt 0 -rw-r--r-- 1 root root 0 Jul 24 02:03 armbianEnv.txt.out 40 -rw-r--r-- 1 root root 38518 Jul 25 00:41 boot.bmp 8 -rw-r--r-- 1 root root 4159 Jul 25 00:13 boot.cmd 8 -rw-r--r-- 1 root root 4231 Jul 25 00:35 boot.scr 240 -rw-r--r-- 1 root root 243875 Jul 21 11:42 config-6.1.75-vendor-rk35xx 0 lrwxrwxrwx 1 root root 24 Jul 24 01:11 dtb -> dtb-6.1.75-vendor-rk35xx 4 drwxr-xr-x 3 root root 4096 Jul 24 01:11 dtb-6.1.75-vendor-rk35xx 0 lrwxrwxrwx 1 root root 28 Jul 24 01:12 Image -> vmlinuz-6.1.75-vendor-rk35xx 15460 -rw-r--r-- 1 root root 15827858 Jul 24 01:12 initrd.img-6.1.75-vendor-rk35xx 6756 -rw-r--r-- 1 root root 6917422 Jul 21 11:42 System.map-6.1.75-vendor-rk35xx 0 lrwxrwxrwx 1 root root 28 Jul 24 01:12 uInitrd -> uInitrd-6.1.75-vendor-rk35xx 15460 -rw-r--r-- 1 root root 15827922 Jul 24 01:12 uInitrd-6.1.75-vendor-rk35xx 36316 -rw-r--r-- 1 root root 37186048 Jul 21 11:42 vmlinuz-6.1.75-vendor-rk35xx

Good evening, Armbian noob here (Debian veteran) working with an RPi 5. I've just installed `Armbian_24.2.5_Rpi5b_bookworm_current_6.6.23.img.xz` and would like to build the ZFS modules. I've installed the kernel modules using `armbian-config` but when I try to build I get root@meson:~# dpkg-reconfigure zfs-dkms Deleting module zfs-2.2.3 completely from the DKMS tree. Loading new zfs-2.2.3 DKMS files... Building for 6.6.23-current-bcm2712 Module build for kernel 6.6.23-current-bcm2712 was skipped since the kernel headers for this kernel do not seem to be installed. root@meson:~# Edit: Current situation: root@meson:~# dpkg -l linux-headers-current-bcm2712 linux-image-current-bcm2712 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=============================-============-============-========================================================= ii linux-headers-current-bcm2712 24.2.1 arm64 Armbian Linux current headers 6.6.18-current-bcm2712 ii linux-image-current-bcm2712 24.2.5 arm64 Armbian Linux current kernel image 6.6.23-current-bcm2712 root@meson:~# It seems that the headers for this kernel are not available. `armbian-config` lists only a newer kernel as an option (6.7) `apt search` lists older kernels, probably from the Debian repos. Can I switch to these or is there something else I can do? Thanks! (First post here.)

My system has `linux-image-current-bcm2712` package installed with version 24.2.5 which I believe is the current Arbian release. I installed `linux-headers-current-bcm2712`, but this package has version 24.2.1. So I end up with system running `6.6.23-current-bcm2712` with headers for `6.6.18-current-bcm2712` and I can't build extra drivers in result. Any hints? I love technical forums that don't understand markdown, it makes life so much easier...

Im running Armbian 24.2.1 jammy on odroidm1 with additional zfs volumes. On update, sometimes I had to reinstall the zfs kernel module, but now I have the problem, that the system does not recognize the kernel headers: sudo apt-get --reinstall install zfs-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 2,397 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://mirrors.dotsrc.org/armbian-apt jammy/jammy-utils arm64 zfs-dkms all 2.2.3-1 [2,397 kB] Fetched 2,397 kB in 1s (3,567 kB/s) Preconfiguring packages ... (Reading database ... 72929 files and directories currently installed.) Preparing to unpack .../zfs-dkms_2.2.3-1_all.deb ... Deleting module zfs-2.2.3 completely from the DKMS tree. Unpacking zfs-dkms (2.2.3-1) over (2.2.3-1) ... Setting up zfs-dkms (2.2.3-1) ... Loading new zfs-2.2.3 DKMS files... Building for 6.1.12-rk3568-odroid Module build for kernel 6.1.12-rk3568-odroid was skipped since the kernel headers for this kernel does not seem to be installed. Processing triggers for initramfs-tools (0.140ubuntu13.4) ... update-initramfs: Generating /boot/initrd.img-6.1.12-rk3568-odroid W: Possible missing firmware /lib/firmware/nvidia/tegra194/xusb.bin for built-in driver xhci_tegra W: Possible missing firmware /lib/firmware/nvidia/tegra186/xusb.bin for built-in driver xhci_tegra W: Possible missing firmware /lib/firmware/nvidia/tegra210/xusb.bin for built-in driver xhci_tegra W: Possible missing firmware /lib/firmware/nvidia/tegra124/xusb.bin for built-in driver xhci_tegra update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.12-rk3568-odroid Image Name: uInitrd Created: Thu Apr 25 11:27:48 2024 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 27753116 Bytes = 27102.65 KiB = 26.47 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.12-rk3568-odroid to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.1.12-rk3568-odroid' update-initramfs: Armbian: done. I already removed and reinstalled the headers via armbian-config > Headers_remove, Headers_install but without change. apt-get list --installed |grep header linux-headers-edge-rockchip64/jammy,now 24.2.1 arm64 [installed] do I need to create some magic symlinks or parameters for apt-get to get the headers resolved since the kernel version is missing in the package?

No. You need more recent ZFS, which comes with supported Armbian OS, which is Bookworm. Bullseye generally works, but we don't support it anymore as upstream is also deserting it. We ship ZFS v2.2.4, soon upgrading to 2.2.5, but only on: All those headers are useless, remove them, also generic kernel 5.10 as it probably won't even boot. You need: apt install linux-headers-current-rockchip64 Fresh Bookworm image, same (sub)arch:

Attempting to install ZFS. But it seems that the latest linux headers are linux-headers-5.10.0-31-arm64. I am not able to install ZFS. Pretty sure I need to lower the kernel to match. sudo modprobe zfs modprobe: FATAL: Module zfs not found in directory /lib/modules/6.6.39-current-rockchip64 Installed linux-image-5.10.0.31-arm64. I also sudo apt-mark hold linux-image-5.10.0.31-arm64. But I do not know how to set the kernel to boot. Search tells me to use armbian-config. Had to install it and after running it the "Other" option is missing. There isn't any options to change the kernel.

Did some more searching and came across a post of yours. After sudo apt update && apt upgrade -y && linux-headers-current-rockchip64 Followed by some cleaning up and undoing of the other kernel. Reinstalled zfsutils-linux zfs-dkms zfs-zed packages and ran into errors. Setting up zfs-dkms (2.0.3-9+deb11u1) ... Removing old zfs-2.0.3 DKMS files... ------------------------------ Deleting module version: 2.0.3 completely from the DKMS tree. ------------------------------ Done. Loading new zfs-2.0.3 DKMS files... Building for 6.6.39-current-rockchip64 Building initial module for 6.6.39-current-rockchip64 configure: error: *** None of the expected "PDE_DATA" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.0.3-9+deb11u1 *** Compatible Kernels: 3.10 - 5.10 Error! Bad return status for module build on kernel: 6.6.39-current-rockchip64 (aarch64) Consult /var/lib/dkms/zfs/2.0.3/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 dpkg: dependency problems prevent configuration of zfs-zed: zfs-zed depends on zfs-modules | zfs-dkms; however: Package zfs-modules is not installed. Package zfs-dkms which provides zfs-modules is not configured yet. Package zfs-dkms is not configured yet. dpkg: error processing package zfs-zed (--configure): dependency problems - leaving unconfigured Processing triggers for initramfs-tools (0.140) ... update-initramfs: Generating /boot/initrd.img-6.6.39-current-rockchip64 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.39-current-rockchip64 Image Name: uInitrd Created: Mon Aug 5 02:43:51 2024..............................................................................] Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 20403257 Bytes = 19925.06 KiB = 19.46 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.39-current-rockchip64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.6.39-current-rockchip64' update-initramfs: Armbian: done. Errors were encountered while processing: zfs-dkms zfs-zed E: Sub-process /usr/bin/dpkg returned an error code (1) /var/lib/dkms/zfs/2.0.3/build/make.log: DKMS make.log for zfs-2.0.3 for kernel 6.6.39-current-rockchip64 (aarch64) Mon 05 Aug 2024 02:42:54 AM EDT make: *** No targets specified and no makefile found. Stop. Seems as though I have to use kernel 5.10...?

### lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M ### Group membership of *REDACTED* : *REDACTED* tty disk dialout sudo audio video plugdev games users systemd-journal input netdev ssh docker ### Userland: PRETTY_NAME="Armbian 23.8.1 bullseye" ARMBIAN_PRETTY_NAME="Armbian 23.8.1 bullseye" ### Installed packages: rc armbian-bsp-cli-rockpi-4c 23.8.1 arm64 Armbian CLI BSP for board 'rockpi-4c' - transitional package ii armbian-bsp-cli-rockpi-4c-current 23.8.1 arm64 Armbian CLI BSP for board 'rockpi-4c' branch 'current' ii armbian-config 24.5.5 all Armbian configuration utility ii armbian-firmware 24.5.6 all Armbian - Linux firmware ii armbian-plymouth-theme 24.5.5 all boot animation, logger and I/O multiplexer - Armbian theme ii hostapd 3:2.10-6~armbian22.02.3+1 arm64 IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator ii htop 3.1.0-0~armbian20.08.2+1 arm64 interactive processes viewer ii linux-base 4.6 all Linux image base package ii linux-dtb-current-rockchip64 24.5.3 arm64 Armbian Linux current DTBs in /boot/dtb-6.6.39-current-rockchip64 ii linux-headers-5.10.0-31-arm64 5.10.221-1 arm64 Header files for Linux 5.10.0-31-arm64 ii linux-headers-5.10.0-31-common 5.10.221-1 all Common header files for Linux 5.10.0-31 ii linux-headers-arm64 5.10.221-1 arm64 Header files for Linux arm64 configuration (meta-package) hi linux-image-5.10.0-31-arm64 5.10.221-1 arm64 Linux 5.10 for 64-bit ARMv8 machines (signed) ii linux-image-current-rockchip64 24.5.3 arm64 Armbian Linux current kernel image 6.6.39-current-rockchip64 ii linux-kbuild-5.10 5.10.221-1 arm64 Kbuild infrastructure for Linux 5.10 ii linux-libc-dev:arm64 23.02.2 arm64 Armbian Linux support headers for userspace development ii linux-u-boot-rockpi-4c-current 24.5.1 arm64 Das U-Boot for rockpi-4c ### Loaded modules: Module Size Used by dm_crypt 49152 1 trusted 12288 1 dm_crypt dm_mod 126976 3 dm_crypt xt_conntrack 12288 1 nft_chain_nat 12288 3 xt_MASQUERADE 16384 1 nf_nat 45056 2 nft_chain_nat,xt_MASQUERADE nf_conntrack_netlink 45056 0 nf_conntrack 118784 4 xt_conntrack,nf_nat,nf_conntrack_netlink,xt_MASQUERADE nf_defrag_ipv6 20480 1 nf_conntrack nf_defrag_ipv4 12288 1 nf_conntrack xfrm_user 40960 1 xfrm_algo 12288 1 xfrm_user xt_addrtype 12288 2 nft_compat 16384 4 nf_tables 225280 75 nft_compat,nft_chain_nat nfnetlink 16384 4 nft_compat,nf_conntrack_netlink,nf_tables br_netfilter 28672 0 bridge 241664 1 br_netfilter lz4hc 12288 0 lz4 12288 0 zram 32768 3 raid1 45056 1 snd_soc_hdmi_codec 20480 1 snd_soc_simple_card 20480 0 brcmfmac_wcc 12288 0 md_mod 151552 2 raid1 snd_soc_audio_graph_card 16384 0 snd_soc_simple_card_utils 24576 2 snd_soc_audio_graph_card,snd_soc_simple_card snd_soc_spdif_tx 12288 0 dw_hdmi_i2s_audio 12288 0 hci_uart 135168 0 panfrost 69632 0 dw_hdmi_cec 12288 0 gpu_sched 36864 1 panfrost drm_shmem_helper 16384 1 panfrost rk_crypto 28672 0 btqca 20480 1 hci_uart rng_core 16384 1 rk_crypto snd_soc_rockchip_i2s 24576 4 btsdio 16384 0 btrtl 28672 1 hci_uart btintel 40960 1 hci_uart hantro_vpu 249856 0 rockchip_vdec 77824 0 snd_soc_es8316 36864 1 brcmfmac 368640 1 brcmfmac_wcc btbcm 20480 1 hci_uart snd_soc_core 208896 7 snd_soc_spdif_tx,snd_soc_hdmi_codec,snd_soc_audio_graph_card,snd_soc_simple_card_utils,snd_soc_rockchip_i2s,snd_soc_simple_card,snd_soc_es8316 v4l2_vp9 20480 2 rockchip_vdec,hantro_vpu rockchip_rga 20480 0 brcmutil 16384 1 brcmfmac bluetooth 663552 7 btrtl,btqca,btsdio,btintel,hci_uart,btbcm videobuf2_dma_contig 20480 2 rockchip_vdec,hantro_vpu snd_compress 24576 1 snd_soc_core v4l2_h264 16384 2 rockchip_vdec,hantro_vpu snd_pcm_dmaengine 12288 1 snd_soc_core v4l2_mem2mem 24576 3 rockchip_vdec,hantro_vpu,rockchip_rga videobuf2_dma_sg 16384 1 rockchip_rga cfg80211 802816 1 brcmfmac realtek 32768 1 snd_pcm 106496 6 snd_soc_hdmi_codec,snd_compress,snd_soc_simple_card_utils,snd_soc_core,snd_soc_es8316,snd_pcm_dmaengine videobuf2_memops 16384 2 videobuf2_dma_contig,videobuf2_dma_sg videobuf2_v4l2 20480 4 rockchip_vdec,hantro_vpu,rockchip_rga,v4l2_mem2mem sg 28672 0 snd_timer 36864 1 snd_pcm videodev 229376 5 rockchip_vdec,videobuf2_v4l2,hantro_vpu,rockchip_rga,v4l2_mem2mem rfkill 24576 5 bluetooth,cfg80211 snd 77824 5 snd_soc_hdmi_codec,snd_timer,snd_compress,snd_soc_core,snd_pcm videobuf2_common 49152 8 rockchip_vdec,videobuf2_dma_contig,videobuf2_v4l2,hantro_vpu,rockchip_rga,videobuf2_dma_sg,v4l2_mem2mem,videobuf2_memops mc 53248 6 rockchip_vdec,videodev,videobuf2_v4l2,hantro_vpu,videobuf2_common,v4l2_mem2mem soundcore 12288 1 snd dwmac_rk 28672 0 stmmac_platform 20480 1 dwmac_rk stmmac 233472 3 stmmac_platform,dwmac_rk pcs_xpcs 20480 1 stmmac cpufreq_dt 16384 0 ip_tables 28672 0 x_tables 36864 5 xt_conntrack,nft_compat,xt_addrtype,ip_tables,xt_MASQUERADE autofs4 40960 2 ### nand-sata-install.log: ### Current system health: Time CPU n/a load %cpu %sys %usr %nice %io %irq Tcpu 23:45:28 --- 1.36 3% 1% 1% 0% 0% 0% 38.1 °C 23:45:29 --- 1.36 13% 5% 0% 0% 6% 0% 38.8 °C 23:45:29 --- 1.36 5% 4% 0% 0% 0% 0% 38.8 °C 23:45:29 --- 1.36 7% 5% 0% 0% 0% 0% 38.8 °C 23:45:30 --- 1.36 6% 5% 0% 0% 0% 0% 38.8 °C 23:45:30 --- 1.36 3% 1% 1% 0% 0% 0% 38.1 °C 23:45:31 --- 1.36 15% 14% 0% 0% 0% 0% 38.8 °C 23:45:31 --- 1.36 18% 12% 3% 0% 0% 1% 38.8 °C 23:45:31 --- 1.36 10% 2% 0% 0% 6% 0% 38.1 °C 23:45:32 --- 1.36 12% 6% 0% 0% 5% 0% 38.8 °C ### resolv.conf -rw-r--r-- 1 root root 82 Aug 4 22:13 /etc/resolv.conf # Generated by NetworkManager search mynetworksettings.com nameserver XXX.XXX.1.1 ### Current sysinfo: Linux 6.6.39-current-rockchip64 (*REDACTED*) 08/04/2024 _aarch64_ (6 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 1.08 0.00 1.74 0.47 0.00 96.70 Device tps kB_read/s kB_wrtn/s kB_dscd/s kB_read kB_wrtn kB_dscd mmcblk0 5.36 98.19 124.17 0.00 556727 704048 0 mmcblk0p1 5.33 97.59 124.17 0.00 553295 704048 0 mmcblk0boot0 0.03 0.13 0.00 0.00 760 0 0 mmcblk0boot1 0.03 0.13 0.00 0.00 760 0 0 sda 51.97 25080.47 364.52 0.00 142201730 2066762 0 sda1 51.94 25079.83 364.52 0.00 142198110 2066762 0 sdb 51.81 1.29 25441.61 0.00 7333 144249354 0 sdb1 51.79 0.87 25441.61 0.00 4929 144249354 0 md127 1.38 3.09 363.63 0.00 17520 2061704 0 zram0 0.03 0.63 0.00 0.00 3552 4 0 zram1 1.84 0.49 9.49 0.00 2768 53804 0 zram2 0.00 0.00 0.00 0.00 0 0 0 dm-0 1.31 1.31 362.87 0.00 7401 2057404 0 --procs-- -----------------------memory---------------------- ---swap-- -----io---- -system-- --------cpu-------- r b swpd free buff cache si so bi bo in cs us sy id wa st 1 0 0 2852696 87652 758476 0 0 17 84 72 79 1 2 97 0 0 total used free shared buff/cache available Mem: 3.8Gi 249Mi 2.7Gi 6.0Mi 826Mi 3.4Gi Swap: 1.9Gi 0B 1.9Gi NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 lzo-rle 1.9G 4K 74B 12K 6 [SWAP] /dev/zram1 zstd 50M 1.6M 169.1K 748K 6 /var/log 23:45:32 up 1:34, 2 users, load average: 1.41, 1.34, 1.13 [ 11.029453] systemd[1]: Mounting Kernel Trace File System... [ 11.036976] systemd[1]: Starting Restore / save the current clock... [ 11.043059] systemd[1]: Starting Set the console keyboard layout... [ 11.049490] systemd[1]: Starting Create list of static device nodes for the current kernel... [ 11.055273] systemd[1]: Starting Load Kernel Module configfs... [ 11.061097] systemd[1]: Starting Load Kernel Module drm... [ 11.067007] systemd[1]: Starting Load Kernel Module fuse... [ 11.074905] systemd[1]: Started Nameserver information manager. [ 11.076390] systemd[1]: Reached target Network (Pre). [ 11.078239] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. [ 11.078532] systemd[1]: Condition check resulted in File System Check on Root Device being skipped. [ 11.085766] systemd[1]: Starting Load Kernel Modules... [ 11.092078] systemd[1]: Starting Remount Root and Kernel File Systems... [ 11.098340] systemd[1]: Starting Coldplug All udev Devices... [ 11.109477] systemd[1]: Mounted Huge Pages File System. [ 11.110442] systemd[1]: Mounted POSIX Message Queue File System. [ 11.111668] systemd[1]: Mounted Kernel Debug File System. [ 11.112610] systemd[1]: Mounted Kernel Trace File System. [ 11.115214] systemd[1]: Finished Restore / save the current clock. [ 11.118234] systemd[1]: Finished Create list of static device nodes for the current kernel. [ 11.120119] systemd[1]: modprobe@configfs.service: Succeeded. [ 11.121741] systemd[1]: Finished Load Kernel Module configfs. [ 11.123734] systemd[1]: modprobe@drm.service: Succeeded. [ 11.125235] systemd[1]: Finished Load Kernel Module drm. [ 11.127108] systemd[1]: modprobe@fuse.service: Succeeded. [ 11.128707] systemd[1]: Finished Load Kernel Module fuse. [ 11.133332] systemd[1]: Finished Load Kernel Modules. [ 11.176850] systemd[1]: Mounting FUSE Control File System... [ 11.185205] systemd[1]: Mounting Kernel Configuration File System... [ 11.192924] EXT4-fs (mmcblk0p1): re-mounted 58156628-a1ec-48f7-971d-8c646a89e424 r/w. Quota mode: none. [ 11.193739] systemd[1]: Starting Apply Kernel Variables... [ 11.206913] systemd[1]: Finished Remount Root and Kernel File Systems. [ 11.208080] systemd[1]: Mounted FUSE Control File System. [ 11.208832] systemd[1]: Mounted Kernel Configuration File System. [ 11.211070] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. [ 11.211572] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. [ 11.219188] systemd[1]: Starting Load/Save Random Seed... [ 11.228196] systemd[1]: Starting Create System Users... [ 11.252755] systemd[1]: Finished Apply Kernel Variables. [ 11.299605] systemd[1]: Finished Load/Save Random Seed. [ 11.302490] systemd[1]: Finished Create System Users. [ 11.303527] systemd[1]: Condition check resulted in First Boot Complete being skipped. [ 11.308998] systemd[1]: Starting Create Static Device Nodes in /dev... [ 11.377873] systemd[1]: Finished Set the console keyboard layout. [ 11.380851] systemd[1]: Finished Create Static Device Nodes in /dev. [ 11.381677] systemd[1]: Reached target Local File Systems (Pre). [ 11.412109] systemd[1]: Mounting /tmp... [ 11.421698] systemd[1]: Starting Rule-based Manager for Device Events and Files... [ 11.430419] systemd[1]: Mounted /tmp. [ 11.539254] systemd[1]: Started Rule-based Manager for Device Events and Files. [ 11.688082] systemd[1]: Finished Coldplug All udev Devices. [ 11.732929] systemd[1]: Starting Helper to synchronize boot up for ifupdown... [ 11.744740] systemd[1]: Starting Show Plymouth Boot Screen... [ 11.754511] systemd[1]: Starting Wait for udev To Complete Device Initialization... [ 11.767593] systemd[1]: Finished Helper to synchronize boot up for ifupdown. [ 11.818605] cpu cpu0: OPP table can't be empty [ 11.819767] systemd[1]: Started Show Plymouth Boot Screen. [ 11.820700] systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch when bootsplash is active being skipped. [ 11.821404] systemd[1]: Started Forward Password Requests to Plymouth Directory Watch. [ 11.821630] systemd[1]: Reached target Paths. [ 11.913384] systemd[1]: Found device /dev/ttyS2. [ 11.930685] rk_gmac-dwmac fe300000.ethernet: IRQ eth_wake_irq not found [ 11.930708] rk_gmac-dwmac fe300000.ethernet: IRQ eth_lpi not found [ 11.930861] rk_gmac-dwmac fe300000.ethernet: PTP uses main clock [ 11.931113] rk_gmac-dwmac fe300000.ethernet: clock input or output? (input). [ 11.931128] rk_gmac-dwmac fe300000.ethernet: TX delay(0x28). [ 11.931141] rk_gmac-dwmac fe300000.ethernet: RX delay(0x11). [ 11.931159] rk_gmac-dwmac fe300000.ethernet: integrated PHY? (no). [ 11.931216] rk_gmac-dwmac fe300000.ethernet: clock input from PHY [ 11.947395] rk_gmac-dwmac fe300000.ethernet: init for RGMII [ 11.947901] rk_gmac-dwmac fe300000.ethernet: User ID: 0x10, Synopsys ID: 0x35 [ 11.947926] rk_gmac-dwmac fe300000.ethernet: DWMAC1000 [ 11.947938] rk_gmac-dwmac fe300000.ethernet: DMA HW capability register supported [ 11.947948] rk_gmac-dwmac fe300000.ethernet: RX Checksum Offload Engine supported [ 11.947957] rk_gmac-dwmac fe300000.ethernet: COE Type 2 [ 11.947967] rk_gmac-dwmac fe300000.ethernet: TX Checksum insertion supported [ 11.947976] rk_gmac-dwmac fe300000.ethernet: Wake-Up On Lan supported [ 11.948112] rk_gmac-dwmac fe300000.ethernet: Normal descriptors [ 11.948124] rk_gmac-dwmac fe300000.ethernet: Ring mode enabled [ 11.948133] rk_gmac-dwmac fe300000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 11.956858] mc: Linux media interface: v0.10 [ 12.006164] videodev: Linux video capture interface: v2.00 [ 12.024337] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 12.037495] sd 3:0:0:0: Attached scsi generic sg1 type 0 [ 12.086013] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 12.088325] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 12.089990] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600' [ 12.106142] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid [ 12.113244] rockchip-rga ff680000.rga: HW Version: 0x03.02 [ 12.116359] Bluetooth: Core ver 2.22 [ 12.119692] rockchip-rga ff680000.rga: Registered rockchip-rga as /dev/video0 [ 12.124169] NET: Registered PF_BLUETOOTH protocol family [ 12.124200] Bluetooth: HCI device and connection manager initialized [ 12.124230] Bluetooth: HCI socket layer initialized [ 12.124246] Bluetooth: L2CAP socket layer initialized [ 12.124312] Bluetooth: SCO socket layer initialized [ 12.152862] RTL8211E Gigabit Ethernet stmmac-0:00: attached PHY driver (mii_bus:phy_addr=stmmac-0:00, irq=POLL) [ 12.152889] RTL8211E Gigabit Ethernet stmmac-0:01: attached PHY driver (mii_bus:phy_addr=stmmac-0:01, irq=POLL) [ 12.155279] rockchip_vdec: module is from the staging directory, the quality is unknown, you have been warned. [ 12.163118] brcmfmac: F1 signature read @0x18000000=0x15294345 [ 12.165874] hantro-vpu ff650000.video-codec: Adding to iommu group 0 [ 12.167496] hantro-vpu ff650000.video-codec: registered rockchip,rk3399-vpu-enc as /dev/video1 [ 12.167575] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 [ 12.169043] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.radxa,rockpi4c.bin failed with error -2 [ 12.179711] hantro-vpu ff650000.video-codec: registered rockchip,rk3399-vpu-dec as /dev/video2 [ 12.187906] usbcore: registered new interface driver brcmfmac [ 12.189377] rkvdec ff660000.video-codec: Adding to iommu group 1 [ 12.326236] rk3288-crypto ff8b0000.crypto: will run requests pump with realtime priority [ 12.326355] rk3288-crypto ff8b0000.crypto: Register ecb(aes) as ecb-aes-rk [ 12.326471] rk3288-crypto ff8b0000.crypto: Register cbc(aes) as cbc-aes-rk [ 12.326515] rk3288-crypto ff8b0000.crypto: Register ecb(des) as ecb-des-rk [ 12.326556] rk3288-crypto ff8b0000.crypto: Register cbc(des) as cbc-des-rk [ 12.326597] rk3288-crypto ff8b0000.crypto: Register ecb(des3_ede) as ecb-des3-ede-rk [ 12.326638] rk3288-crypto ff8b0000.crypto: Register cbc(des3_ede) as cbc-des3-ede-rk [ 12.326679] rk3288-crypto ff8b0000.crypto: Register sha1 as rk-sha1 [ 12.326722] rk3288-crypto ff8b0000.crypto: Register sha256 as rk-sha256 [ 12.326765] rk3288-crypto ff8b0000.crypto: Register md5 as rk-md5 [ 12.326806] rk3288-crypto ff8b0000.crypto: Register TRNG with sample=1200 [ 12.372159] panfrost ff9a0000.gpu: clock rate = 500000000 [ 12.375101] rk3288-crypto ff8b8000.crypto: will run requests pump with realtime priority [ 12.401373] Bluetooth: HCI UART driver ver 2.3 [ 12.401406] Bluetooth: HCI UART protocol H4 registered [ 12.401417] Bluetooth: HCI UART protocol BCSP registered [ 12.404734] Bluetooth: HCI UART protocol LL registered [ 12.404763] Bluetooth: HCI UART protocol ATH3K registered [ 12.404867] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 12.405167] Bluetooth: HCI UART protocol Intel registered [ 12.405545] panfrost ff9a0000.gpu: mali-t860 id 0x860 major 0x2 minor 0x0 status 0x0 [ 12.405571] panfrost ff9a0000.gpu: features: 00000000,00000407, issues: 00000000,24040400 [ 12.405590] panfrost ff9a0000.gpu: Features: L2:0x07120206 Shader:0x00000000 Tiler:0x00000809 Mem:0x1 MMU:0x00002830 AS:0xff JS:0x7 [ 12.405612] panfrost ff9a0000.gpu: shader_present=0xf l2_present=0x1 [ 12.406923] Bluetooth: HCI UART protocol Broadcom registered [ 12.407046] Bluetooth: HCI UART protocol QCA registered [ 12.407059] Bluetooth: HCI UART protocol AG6XX registered [ 12.407149] Bluetooth: HCI UART protocol Marvell registered [ 12.412904] [drm] Initialized panfrost 1.2.0 20180908 for ff9a0000.gpu on minor 1 [ 12.523684] dw-apb-uart ff180000.serial: failed to request DMA [ 12.536248] asoc-audio-graph-card sound: ASoC: DAPM unknown pin Headphones [ 12.691413] asoc-audio-graph-card sound: ASoC: DAPM unknown pin Headphones [ 12.700558] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [ 12.701713] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Jun 16 2017 12:38:26 version XXX.XXX.96.2 (66c4e21@sh-git) (r) FWID 01-1813af84 [ 12.724993] input: Analog Headphones as /devices/platform/sound/sound/card0/input0 [ 12.775738] block device autoloading is deprecated and will be removed. [ 12.800391] systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. [ 12.801321] Bluetooth: hci0: BCM: chip id 130 [ 12.802223] Bluetooth: hci0: BCM: features 0x0f [ 12.805097] Bluetooth: hci0: BCM4345C5 [ 12.805136] Bluetooth: hci0: BCM4345C5 (003.006.006) build 0000 [ 12.807564] Bluetooth: hci0: BCM4345C5 'brcm/BCM4345C5.hcd' Patch [ 12.864598] systemd[1]: Starting Load/Save RF Kill Switch Status... [ 13.008216] md/raid1:md127: not clean -- starting background reconstruction [ 13.008246] md/raid1:md127: active with 2 out of 2 mirrors [ 13.042626] systemd[1]: Started Load/Save RF Kill Switch Status. [ 13.086290] systemd[1]: Started Timer to wait for more drives before activating degraded array md127.. [ 13.086513] systemd[1]: Reached target Bluetooth. [ 13.086647] systemd[1]: Reached target Sound Card. [ 13.186104] md127: detected capacity change from 0 to 1953257472 [ 13.334598] systemd[1]: mdadm-last-resort@md127.timer: Succeeded. [ 13.334645] systemd[1]: Stopped Timer to wait for more drives before activating degraded array md127.. [ 13.364253] systemd[1]: Started MD array monitor. [ 13.404853] systemd[1]: Finished Wait for udev To Complete Device Initialization. [ 13.718326] Bluetooth: hci0: BCM: features 0x0f [ 13.722257] Bluetooth: hci0: BCM4345C5 Ampak_CL1 UART 37.4 MHz BT 5.0 [Version: Version: 0039.0089] [ 13.722297] Bluetooth: hci0: BCM4345C5 (003.006.006) build 0089 [ 18.015740] systemd[1]: systemd-rfkill.service: Succeeded. [ 23.008896] platform sound-dit: deferred probe pending [ 101.050295] systemd[1]: dev-disk-by-uuid-1efe5ff5-c91e-4181-beb3-67d382095a5e.device: Job dev-disk-by-uuid-1efe5ff5-c91e-4181-beb3-67d382095a5e.device/start timed out. [ 101.050338] systemd[1]: Timed out waiting for device /dev/disk/by-uuid/1efe5ff5-c91e-4181-beb3-67d382095a5e. [ 101.050538] systemd[1]: Dependency failed for Cryptography Setup for luks-1efe5ff5-c91e-4181-beb3-67d382095a5e. [ 101.050651] systemd[1]: Dependency failed for Local Encrypted Volumes. [ 101.050756] systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'. [ 101.050823] systemd[1]: systemd-cryptsetup@luks-1efe5ff5-c91e-4181-beb3-67d382095a5e.service: Job systemd-cryptsetup@luks-1efe5ff5-c91e-4181-beb3-67d382095a5e.service/start failed with result 'dependency'. [ 101.050869] systemd[1]: dev-disk-by-uuid-1efe5ff5-c91e-4181-beb3-67d382095a5e.device: Job dev-disk-by-uuid-1efe5ff5-c91e-4181-beb3-67d382095a5e.device/start failed with result 'timeout'. [ 101.050954] systemd[1]: dev-disk-by-uuid-30e48ec2-bb9f-49e0-afd1-71f5dccd2435.device: Job dev-disk-by-uuid-30e48ec2-bb9f-49e0-afd1-71f5dccd2435.device/start timed out. [ 101.050974] systemd[1]: Timed out waiting for device /dev/disk/by-uuid/30e48ec2-bb9f-49e0-afd1-71f5dccd2435. [ 101.051138] systemd[1]: Dependency failed for Cryptography Setup for luks-30e48ec2-bb9f-49e0-afd1-71f5dccd2435. [ 101.051284] systemd[1]: systemd-cryptsetup@luks-30e48ec2-bb9f-49e0-afd1-71f5dccd2435.service: Job systemd-cryptsetup@luks-30e48ec2-bb9f-49e0-afd1-71f5dccd2435.service/start failed with result 'dependency'. [ 101.051396] systemd[1]: dev-disk-by-uuid-30e48ec2-bb9f-49e0-afd1-71f5dccd2435.device: Job dev-disk-by-uuid-30e48ec2-bb9f-49e0-afd1-71f5dccd2435.device/start failed with result 'timeout'. [ 101.051548] systemd[1]: Reached target Block Device Preparation for /dev/mapper/luks-1efe5ff5-c91e-4181-beb3-67d382095a5e. [ 101.052379] systemd[1]: Reached target Block Device Preparation for /dev/mapper/luks-30e48ec2-bb9f-49e0-afd1-71f5dccd2435. [ 101.088408] systemd[1]: Starting Install ZFS kernel module... [ 101.089415] systemd[1]: Stopped target Block Device Preparation for /dev/mapper/luks-1efe5ff5-c91e-4181-beb3-67d382095a5e. [ 101.089623] systemd[1]: Stopped target Block Device Preparation for /dev/mapper/luks-30e48ec2-bb9f-49e0-afd1-71f5dccd2435. [ 101.100061] systemd[1]: zfs-load-module.service: Main process exited, code=exited, status=1/FAILURE [ 101.100924] systemd[1]: zfs-load-module.service: Failed with result 'exit-code'. [ 101.102723] systemd[1]: Failed to start Install ZFS kernel module. [ 101.102944] systemd[1]: Dependency failed for Import ZFS pools by cache file. [ 101.103070] systemd[1]: zfs-import-cache.service: Job zfs-import-cache.service/start failed with result 'dependency'. [ 101.103618] systemd[1]: Reached target ZFS pool import target. [ 101.103825] systemd[1]: Condition check resulted in Mount ZFS filesystems being skipped. [ 101.103918] systemd[1]: Reached target Local File Systems. [ 101.109267] systemd[1]: Starting Armbian leds state... [ 101.115048] systemd[1]: Starting Armbian ZRAM config... [ 101.121155] systemd[1]: Starting Set console font and keymap... [ 101.127712] systemd[1]: Starting Raise network interfaces... [ 101.134102] systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... [ 101.134557] systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped. [ 101.134809] systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped. [ 101.134956] systemd[1]: Condition check resulted in Wait for ZFS Volume (zvol) links in /dev being skipped. [ 101.135105] systemd[1]: Reached target ZFS volumes are ready. [ 101.150780] systemd[1]: Finished Set console font and keymap. [ 101.152479] systemd[1]: Received SIGRTMIN+20 from PID 270 (plymouthd). [ 101.158406] systemd[1]: Finished Tell Plymouth To Write Out Runtime Data. [ 101.218457] systemd[1]: Finished Armbian leds state. [ 101.322310] zram: Added device: zram0 [ 101.323687] zram: Added device: zram1 [ 101.324852] zram: Added device: zram2 [ 101.421341] zram0: detected capacity change from 0 to 3952888 [ 101.461798] Adding 1976440k swap on /dev/zram0. Priority:5 extents:1 across:1976440k SS [ 101.484675] systemd[1]: Finished Raise network interfaces. [ 101.696246] zram1: detected capacity change from 0 to 102400 [ 101.755534] systemd[1]: Finished Armbian ZRAM config. [ 101.797108] systemd[1]: Starting Armbian memory supported logging... [ 101.897210] EXT4-fs (zram1): mounted filesystem 24de4176-fb3a-49d5-bf49-baf1c2b1b99b r/w without journal. Quota mode: none. [ 101.897287] ext4 filesystem being mounted at /var/log supports timestamps until 2038-01-19 (0x7fffffff) [ 117.158724] systemd[1]: Finished Armbian memory supported logging. [ 117.188825] systemd[1]: Starting Journal Service... [ 117.595993] systemd[1]: Started Journal Service. [ 117.680099] systemd-journald[657]: Received client request to flush runtime journal. [ 118.809081] systemd-journald[657]: Received client request to relinquish /var/log/journal/515cf686f9604730835651798a8c6e08 access. [ 120.219836] rk_gmac-dwmac fe300000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 120.229515] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211E Gigabit Ethernet] (irq=POLL) [ 120.229571] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found [ 120.229595] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW [ 120.231528] rk_gmac-dwmac fe300000.ethernet eth0: configuring for phy/rgmii link mode [ 124.295179] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 124.301982] Bridge firewalling registered [ 124.328027] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 125.022086] Initializing XFRM netlink socket [ 128.462731] systemd-journald[657]: Received client request to flush runtime journal. [ 129.138946] systemd-journald[657]: Received client request to relinquish /var/log/journal/515cf686f9604730835651798a8c6e08 access. [ 198.475560] systemd[2453]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set [ 246.674030] systemd-journald[657]: Received client request to flush runtime journal. [ 246.750322] systemd-journald[657]: Received client request to relinquish /var/log/journal/515cf686f9604730835651798a8c6e08 access. [ 1146.740058] systemd-journald[657]: Received client request to flush runtime journal. [ 1146.808901] systemd-journald[657]: Received client request to relinquish /var/log/journal/515cf686f9604730835651798a8c6e08 access. [ 2046.709361] systemd-journald[657]: Received client request to flush runtime journal. [ 2046.789845] systemd-journald[657]: Received client request to relinquish /var/log/journal/515cf686f9604730835651798a8c6e08 access. [ 2946.702604] systemd-journald[657]: Received client request to flush runtime journal. [ 2946.775122] systemd-journald[657]: Received client request to relinquish /var/log/journal/515cf686f9604730835651798a8c6e08 access. [ 3846.684206] systemd-journald[657]: Received client request to flush runtime journal. [ 3846.776059] systemd-journald[657]: Received client request to relinquish /var/log/journal/515cf686f9604730835651798a8c6e08 access. [ 4184.598033] md: resync of RAID array md127 [ 4189.064476] device-mapper: uevent: version 1.0.3 [ 4189.065162] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com [ 4212.546008] EXT4-fs (dm-0): mounted filesystem 5602eb7e-12b3-42fb-9798-1556b2a90df5 r/w with ordered data mode. Quota mode: none. [ 4746.765355] systemd-journald[657]: Received client request to flush runtime journal. [ 4746.826781] systemd-journald[657]: Received client request to relinquish /var/log/journal/515cf686f9604730835651798a8c6e08 access. [ 5462.651092] systemd-journald[657]: Received client request to flush runtime journal. [ 5462.716166] systemd-journald[657]: Received client request to relinquish /var/log/journal/515cf686f9604730835651798a8c6e08 access. vm.admin_reserve_kbytes = 8192 vm.compaction_proactiveness = 20 vm.compact_unevictable_allowed = 1 vm.dirty_background_bytes = 0 vm.dirty_background_ratio = 10 vm.dirty_bytes = 0 vm.dirty_expire_centisecs = 3000 vm.dirty_ratio = 20 vm.dirtytime_expire_seconds = 43200 vm.dirty_writeback_centisecs = 500 vm.extfrag_threshold = 500 vm.hugetlb_shm_group = 0 vm.laptop_mode = 0 vm.legacy_va_layout = 0 vm.lowmem_reserve_ratio = 256 256 32 0 vm.max_map_count = 65530 vm.memfd_noexec = 0 vm.min_free_kbytes = 22528 vm.min_slab_ratio = 5 vm.min_unmapped_ratio = 1 vm.mmap_min_addr = 4096 vm.mmap_rnd_bits = 18 vm.mmap_rnd_compat_bits = 11 vm.nr_hugepages = 0 vm.nr_hugepages_mempolicy = 0 vm.nr_overcommit_hugepages = 0 vm.numa_stat = 1 vm.numa_zonelist_order = Node vm.oom_dump_tasks = 1 vm.oom_kill_allocating_task = 0 vm.overcommit_kbytes = 0 vm.overcommit_memory = 0 vm.overcommit_ratio = 50 vm.page-cluster = 0 vm.page_lock_unfairness = 5 vm.panic_on_oom = 0 vm.percpu_pagelist_high_fraction = 0 vm.stat_interval = 1 vm.swappiness = 100 vm.user_reserve_kbytes = 121725 vm.vfs_cache_pressure = 100 vm.watermark_boost_factor = 15000 vm.watermark_scale_factor = 10 vm.zone_reclaim_mode = 0 ### interrupts: CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 18: 0 0 0 0 0 0 GICv3 25 Level vgic 20: 0 0 0 0 0 0 GICv3 27 Level kvm guest vtimer 23: 54633 65433 62030 49947 115779 61484 GICv3 30 Level arch_timer 25: 83504 64289 75597 60595 90417 72349 GICv3 113 Level rk_timer 31: 0 0 0 0 0 0 GICv3 37 Level ff6d0000.dma-controller 32: 0 0 0 0 0 0 GICv3 38 Level ff6d0000.dma-controller 33: 0 0 0 0 0 0 GICv3 39 Level ff6e0000.dma-controller 34: 0 0 0 0 0 0 GICv3 40 Level ff6e0000.dma-controller 35: 1236 0 0 0 0 0 GICv3 131 Level ttyS0 36: 693 0 0 0 0 0 GICv3 132 Level ttyS2 37: 0 0 0 0 0 0 GICv3 147 Level ff650800.iommu 38: 0 0 0 0 0 0 GICv3 149 Level ff660480.iommu 39: 0 0 0 0 0 0 GICv3 151 Level ff8f3f00.iommu, ff8f0000.vop 40: 0 0 0 0 0 0 GICv3 150 Level ff903f00.iommu, ff900000.vop 41: 0 0 0 0 0 0 GICv3 75 Level ff914000.iommu 42: 0 0 0 0 0 0 GICv3 76 Level ff924000.iommu 43: 66 0 0 0 0 0 GICv3 91 Level ff110000.i2c 44: 0 0 0 0 0 0 GICv3 66 Level ff130000.i2c 45: 61977 0 0 0 0 0 GICv3 68 Level ff160000.i2c 46: 429 0 0 0 0 0 GICv3 89 Level ff3c0000.i2c 47: 0 0 0 0 0 0 GICv3 88 Level ff3d0000.i2c 48: 0 0 0 0 0 0 GICv3 129 Level rockchip_thermal 49: 0 0 0 0 0 0 GICv3 152 Edge ff848000.watchdog 50: 9719 0 0 0 0 0 GICv3 96 Level dw-mci 51: 0 0 0 0 0 0 GICv3 97 Level dw-mci 52: 36031 0 0 0 0 0 GICv3 43 Level mmc0 53: 3 0 0 0 0 0 GICv3 94 Level ff100000.saradc 54: 0 0 0 0 0 0 GICv3-23 0 Level arm-pmu 55: 0 0 0 0 0 0 GICv3-23 1 Level arm-pmu 56: 0 0 0 0 0 0 rockchip_gpio_irq 7 Edge fe320000.mmc cd 57: 0 0 0 0 0 0 GICv3 59 Level rockchip_usb2phy 58: 0 0 0 0 0 0 GICv3 63 Level rockchip_usb2phy 59: 0 0 0 0 0 0 GICv3 137 Level xhci-hcd:usb1 60: 0 0 0 0 0 0 GICv3 142 Level xhci-hcd:usb3 61: 0 0 0 0 0 0 GICv3 58 Level ehci_hcd:usb5 62: 0 0 0 0 0 0 GICv3 62 Level ehci_hcd:usb7 63: 0 0 0 0 0 0 GICv3 60 Level ohci_hcd:usb6 64: 0 0 0 0 0 0 rockchip_gpio_irq 21 Level rk808 70: 0 0 0 0 0 0 rk808 5 Edge RTC alarm 74: 0 0 0 0 0 0 GICv3 64 Level ohci_hcd:usb8 75: 0 0 0 0 0 0 GICv3 81 Level pcie-sys 77: 154 0 0 0 0 0 GICv3 83 Level pcie-client 79: 0 0 0 0 0 0 ITS-MSI 0 Edge PCIe PME, aerdrv 80: 0 300801 0 0 0 0 ITS-MSI 524288 Edge ahci0 81: 0 0 0 0 0 0 ITS-MSI 524289 Edge ahci1 82: 0 0 0 0 0 0 ITS-MSI 524290 Edge ahci2 83: 0 0 0 0 166292 0 ITS-MSI 524291 Edge ahci3 84: 0 0 0 0 0 0 ITS-MSI 524292 Edge ahci4 88: 0 0 0 0 0 0 GICv3 55 Level ff940000.hdmi, dw-hdmi-cec 89: 25429 0 0 0 0 0 GICv3 44 Level eth0 90: 0 0 0 0 0 0 GICv3 87 Level ff680000.rga 91: 0 0 0 0 0 0 rockchip_gpio_irq 1 Level es8316 92: 0 0 0 0 0 0 GICv3 146 Level ff650000.video-codec 93: 0 0 0 0 0 0 GICv3 145 Level ff650000.video-codec 94: 335 0 0 0 0 0 rockchip_gpio_irq 3 Level brcmf_oob_intr 95: 0 0 0 0 0 0 GICv3 148 Level ff660000.video-codec 96: 0 0 0 0 0 0 GICv3 32 Level rk-crypto 97: 0 0 0 0 0 0 GICv3 167 Level rk-crypto 98: 0 0 0 0 0 0 GICv3 51 Level panfrost-gpu 99: 0 0 0 0 0 0 GICv3 53 Level panfrost-mmu 100: 6 0 0 0 0 0 rockchip_gpio_irq 4 Edge host_wake 101: 0 0 0 0 0 0 GICv3 52 Level panfrost-job 102: 0 0 0 0 0 0 rockchip_gpio_irq 0 Edge Headphone detection IPI0: 7051 6118 5124 6091 4565 4011 Rescheduling interrupts IPI1: 142253 90762 189514 163483 115662 95731 Function call interrupts IPI2: 0 0 0 0 0 0 CPU stop interrupts IPI3: 0 0 0 0 0 0 CPU stop (for crash dump) interrupts IPI4: 22657 24662 28699 29222 29184 28897 Timer broadcast interrupts IPI5: 0 0 0 0 0 0 IRQ work interrupts IPI6: 0 0 0 0 0 0 CPU wake-up interrupts Err: 0

Yes. Or update, install headers and try to build this driver via DKMS. But it might be challenging ...

Hello, after some troubleshooting, this boot issue occur only if I have my two ssd drive plugged. If I unplug this one, the kernel is booting, this issue is not occuring with older kernel 6.6.32 By the way, since the system is booted, if I plug the drives, the system panic so I will revert to 6.6.32 kernel. but I have loose my 6.6.32 headers, and I can't compil again the zfs module, anyone know how i can download the last 6.6.32 headers for rockpi ? Rgds

I've taken peeks at threads related to hardware decoding (of H.264 and HEVC, mainly) on Allwinner and Rockchip platforms on and off, sometimes dabbled in trying and failing to implement solutions recommended there. Being a complete amateur, I find the topic very opaque and confusing, with various different components that need to interface with each other, be patched in sync, and sometimes change drastically between kernel versions, etc. Today I sat down and read up on these subjects, scouring wikis, documentation, this forum, and assorted other sources to try and understand how this works. In this post I will attempt to compile what I've learned on the different software components involved, their relationships, their current status, and solutions to the problem. I hope people more knowledgeable will correct me when I get something wrong or cite outdated information. Stuff which I am highly uncertain of I will print in italics. (This post is going to focus on mainline implementations of Cedrus/Allwinner, I haven't looked into Hantro/Rkvdec/Rockchip specifics yet. I will speak only of H.264 and H.265/HEVC; I don't understand the high/low stuff and didn't pay attention to other codecs.) Components: Basics: Video codecs like H.264, H.265/HEVC, MPEG-2, etc. are standardised methods which serve to more efficiently encode and decode videos, reducing their filesize. Software en-/decoding is very CPU-intensive. Modern GPUS and ARM SoCs therefore contain specialised hardware (VPUs) to delegate these tasks to. Working hardware decoding is particularly important for underpowered ARM CPUs. Drivers: Topmost in the stack are the VPU drivers. These are Sunxi-Cedrus/Cedrus V4L2 M2M and Cedar [Is this the legacy one?] on Allwinner; Hantro and Rkvdec on Rockchip. These are all still in development, but Cedrus already fully supports H.264, and partially supports HEVC, and is already usable in the mainline kernel. APIs: In order for anything (userspace APIs, libraries) to make use of the VPU drivers, you need backends/APIs. For Cedrus, there is the unmaintained libva-v4l2-request backend which implements VA-API, the legacy VDPAU implementation libvdpau-sunxi, and as of kernel version 5.11, H.264 has been merged into the uAPI headers. Different applications may make recourse to one or another of these APIs. Libraries: FFmpeg and GStreamer. provide libraries and APIs of their own to other applications but can (importantly!) also output directly to the framebuffer. FFmpeg must be patched to access either libva-v4l2-request or the Cedrus driver headers. GStreamer directly accesses kernel headers since 1.18 (works on 5.9, not on 5.10; 1.20 will support 5.11.) Media players: mpv and depends on FFmpeg for hardware acceleration (and must be patched together with it). VLC can be set to access libva-v4l2-request directly. Kodi 19.0+ supports hardware acceleration out of the box without any out-of-tree patches. Display server: An additional complication is drawing the output of any of the above on screen. Most successful implementations I've seen bypass X11 and either output directly to the framebuffer or force a plane/display layer on top of any X windows. Wayland apparently makes this easier by allowing applications to use their own DRM planes, but this hasn't been explored much yet. Kodi 19.0 works with all three windowing systems (X, Wayland, and gbm). Codec status: Taken from the LibreElec thread (which reflects LibreElec's status and is ahead of what works elsewhere, but outlines hardware limitations): Approaches: Many people have managed to make it work on their machines using different approaches. Note that some of these solutions are one or two years old, and kernel developments since may have changed the situation. Ordered from newer to older: LibreElec – kernel + ffmpeg + Kodi: LibreElec is a Just-Enough-OS with the sole purpose of running Kodi, a media player. It's at the bleeding edge and usually implements codecs and features well before mainline or other distros. It achieves this by heavily patching everything up and down the stack, from the Linux kernel over FFmpeg to Kodi itself. These patches could all be applied to an Armbian build, but there are a lot of them, they're poorly documented, and you'd need to dig into their github to understand what they all do. LibreElec runs Kodi directly without a desktop. kodi-gbm is a package that can be installed on Armbian and functions similarly. Key contributors to the project are @jernej and @Kwiboo, who sometimes post about their work here (and have been very helpful with questions, thank you). @balbes150 includes some of LibreElec's patches in his Armbian-TV builds, but I don't know which. Kodi 19.0: LibreElec patches + mpv: @megous – Kernel 5.11 + GStreamer: This implementation, done here on a PinePhone (A64), patches the 5.9 kernel and uses a recent version of GStreamer (1.18 and up), whose output is rendered directly to a DRM plane via kmssink. (No X or Wayland.) GStreamer 1.18 works with the 5.9 kernel. It does not work with 5.10, because of numerous changes to the kernel headers in this version. In 5.11 the H.264 headers were moved into the uAPI; the master branch of GStreamer reflects this, but there haven't been any releases with these patches yet. It'll probably be in repositories with GStreamer 1.20; until then you can build it from source. @Sash0k – patched libva-v4l2-request + VLC: This updates bootlin's libva-v4l2-request and follows the Sunxi wiki's instructions for enabling VLC to make use of it. It works on the desktop. This only works for H.264 and breaks HEVC. When I tried to replicate this approach on a recent Armbian build, I discovered that the h264.c files in the kernel (that libva-v4l2-request draws on) have changed considerably between 5.8 and 5.10, and I lack the understanding to reconcile libva-v4l2-request with them. @ubobrov – old kernel + libcedrus + libvdpau-sunxi + ffmpeg + mpv: This approach, which supports encoding decoding of H.264 uses the libvdpau-sunxi API and ports the legacy driver to mainline as a loadable kernel module and if I understand it correctly, ubobrov ported a legacy feature to mainline. In the post quoted below the kernel is 4.20, but the same method has been successfully applied to 5.7.8 by another user. It requires that the board's device tree be patched, as documented in ubobrov's github repository. The summary seems to be that none of the current implementations on Allwinner boards really play nice with X or desktop sessions, and it's best to output directly to the framebuffer. Kwiboo has forked FFmpeg and mpv to make good use of new and unstable kernel features/hardware acceleration which will take a while to make their way upstream. The recent 5.11 move of stateless H.264 out of staging and into the uAPI should facilitate further developments. I intend to try some of these things in the nearer future. Thanks to everyone who works on mainlining all of this VPU stuff, and to users here who contribute solutions and readily & patiently answer questions (Jernej especially). I hope I didn't post any falsehoods out of ignorance, and welcome any corrections. Other related threads here: https://forum.armbian.com/topic/11551-4kp30-video-on-orange-pi-lite-and-mainline-hardware-acceleration/ https://forum.armbian.com/topic/16804-orange-pi-pc-h3-armbian-focal-5104-sunxi-av-tv-out-cvbs-enable/page/2/ https://forum.armbian.com/topic/11184-hardware-graphicvideo-acceleration-in-h3-mainline/ https://forum.armbian.com/topic/13622-mainline-vpu/

Description Little fixes to uwe5622 missing headers. This will make the driver compile on kernel 6.8 How Has This Been Tested? [x] Module compiles on edge kernel 6.8 [x] Module compiles on current kernel 6.6 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Hello, I'm identifying myself has a newbie concerning linux. After some time I reboot my rock5c and it is not booting anymore. Here is what I've done initially: I bought a rock 5c and a penta sata hat. -I installed Armbian_24.5.1_Rock-5c_bookworm_edge_6.8.10_minimal. -I installed OMV (configure some samba shared folder) -I installed ZFS (for that I needed linux headers that I found online because there were not included) -I create a ZFS pull with two SSD. -I installed immich and setup a cloudflare tunel to use it. -I installed plex media server. That's pretty much all I have setup on my SBC. I've done apt upgrade multiple time & update some immich / Plex. Every time I did update I rebooted the SBC. And then yesterday I did an immich & plex update, apt upgrade and lastly rebooted. And my SBC never did come back online. I try to install a fresh armbian install to see if it still boot and it did boot. I'm not sure where to start to get it boot again with keeping has much stuff has I can. I wanted to try this: https://docs.armbian.com/User-Guide_Recovery/#replacing-boot But I'm not sure what Root file system, Kernel, Firmware & Device Tree Binary (DTB) version I should take. Or maybe someone could point me to an other path to fix my install?