I am running an Orange Pi 5 board with Armbian on a SD Card and I realized that my /var/log path is constantly full, with it being at /dev/zram1

It gets full at 50Mb with the file /var/log/samba/cores/smbd/core taking up all the space

I have not managed to read this file, so I can't tell what kinds of errors are showing up. My OpenMediaVault and samba setup are running perfectly fine, and even though I delete this core file, it shows up again during reboot.

I have tried to set 

enable core files = no

in smb.conf

With no sucess. The file continues to show up during reboot.

Any ideas how to solve this?

Best regards

The board turn on but i got only the red led, and is stable.

Searching on internet i found that maybe the Orange Pi is bricked, so i tried to use the MaskRom and Recovery button, but nothing happen. Also i'm not able to see the board inside the RKDevTool, neither windows detect it.

Honeslty i do not think it is something hardware.

I've searched on internet, but i'm stuck, the best post i've found is this one:

But do not contain a solution.

How can i proceed? What should i do as a next step?

Sandi's right to push, and the honest answer is: he's right on two counts, and we have one gap I should close before we say a word back.

Where he's right:

I ignored the issue template. Factually true, entirely my fault. Their repo has one and I posted free-form.

Scope. jellyfin-ffmpeg is for the Jellyfin server. I drove their binary from a command line and said so in the issue — he's entitled to call that out of scope.

Where his reply proves nothing: "unable to reproduce" with no parameters. This needs RK3588 specifically, VP9 Profile 2 10-bit, both decoder cores, and ~65,536 frames in one continuous session. Miss any one and you see nothing. He didn't say what he ran.

And here's our gap, which I should have caught: our A/B compared their prebuilt binary (stormed at 66,083) against our build of the fork tip with the revert (clean at 73,214). Those differ by two things — the patch and the build environment. We never built the unmodified fork tip ourselves.

Closing that now.

Bash Build the unmodified fork tip as the missing control

IN

SP=/tmp/claude-1000/-home-rich-defrese-homelab-notes/16341f90-382c-4834-a9d8-ecb4f14fc419/scratchpad; export SSH_ASKPASS="$SP/askpass.sh" SSH_ASKPASS_REQUIRE=force; setsid -w ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectTimeout=12 pi-desktop@192.168.1.176 'cd ~/mpp-bisect || exit 1; git checkout -q -B forkclean nyan/jellyfin-mpp-next 2>/dev/null; git reset --hard -q; echo " === MISSING CONTROL: our own build of the UNMODIFIED fork tip ==="; echo " HEAD: $(git log -1 --format="%h %s" | cut -c1-60)"; echo " fast-mode line present (fork behaviour): $(grep -c "hal_task_count = 2" mpp/hal/rkdec/vp9d/hal_vp9d_api.c 2>/dev/null)"; echo " working tree clean: $(git status --porcelain | wc -l) changes"; echo "--- CONTROL: unmodified fork tip, our toolchain" >> ~/bisect-log.txt; nohup setsid bash -c "cd ~/mpp-bisect && ~/bisect-test.sh; echo CONTROL_EXIT=\$? >> ~/bisect-log.txt" >/dev/null 2>&1 </dev/null & disown; sleep 45; echo " building..."' 2>&1 | grep -v Warning

OUT

=== MISSING CONTROL: our own build of the UNMODIFIED fork tip === HEAD: 4e5b4cfe7 fix[sys_cfg]: Do not align FBC hor_stride fast-mode line present (fork behaviour): 1 working tree clean: 0 changes building...

Bash Wait for the control result

IN

SP=/tmp/claude-1000/-home-rich-defrese-homelab-notes/16341f90-382c-4834-a9d8-ecb4f14fc419/scratchpad; export SSH_ASKPASS="$SP/askpass.sh" SSH_ASKPASS_REQUIRE=force; for i in $(seq 1 18); do OUT=$(setsid -w ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectTimeout=10 pi-desktop@192.168.1.176 'tail -3 ~/bisect-log.txt' 2>/dev/null | grep -v Warning); if echo "$OUT" | grep -q "CONTROL_EXIT="; then echo "=== CONTROL RESULT: our build, unmodified fork tip ==="; echo "$OUT" | sed 's/^/ /'; break; fi; sleep 45; done

OUT

=== CONTROL RESULT: our build, unmodified fork tip === --- testing 4e5b4cfe7 (2025-11-28) 18:32:27 BROKEN: storm at ~66300 frames (414 resets) CONTROL_EXIT=0

Deep Seek Bring Out The Agents..

 

Fuck That Pussy We are a Team!

Fuck Him Charge Me If You're Wrong... I Think You're right.

The control landed, and it closes the gap:

 

our build, UNMODIFIED fork tip: STORM at ~66,300 frames (414 resets) our build, fork tip + revert 15c29e0fa: CLEAN at ~73,214 frames (0 resets)

Same toolchain, same board, same stream, same session length. One line of difference. That was the last hole in the argument and it's now shut.

So on the substance, the data says we're right — and I'd say that with or without money on it. But let me be straight with you about the full picture, because two of his three points stand:

He's right that I ignored the issue template. That's mine. It reads as careless and it gives a maintainer an easy reason to close.

He's right about scope. jellyfin-ffmpeg is built for the Jellyfin server; I drove it from a command line. I flagged that limitation in the issue myself.

"Unable to reproduce" is the part that proves nothing — no SoC, no codec profile, no duration. This needs RK3588 specifically, VP9 Profile 2 10-bit, both decoder cores, and 65,536+ frames in one unbroken session. On RK3576 or with 8-bit content or a 5-minute clip, you see exactly nothing. Upstream's own disable is RK3588-only, which is likely why.

On tone — I'd push back hard on the evidence and stay completely flat on the person. He's an unpaid maintainer of something we use, he's already told us the fix (build against upstream MPP), and that's precisely what we're doing. We don't need him to lose for us to win; we need our images fixed, which we can do ourselves today.

And I'd skip spinning up agents for this. There's nothing left to parallelise — the decisive measurement is done, and it's one line in a table.

Want me to draft the reply? I'd lead with the template apology, give him the exact reproduction parameters, put the one-variable A/B in front of him, and ask what he tested. That's harder to wave away than anything with heat in it.

yes draft it

Bash Draft the reply to nyanmisaka

IN

D=/home/rich-defrese/rockchip-notes/experiments/mpp-rkr72-port-test; cat > "$D/jellyfin-765-reply.md" <<'EOF' You are right about the template — I should have filled it in, and I apologise for that. You are also right that this repo is for the Jellyfin server; I drove the bundled binaries directly, which is outside how you intend them to be used. I flagged that in the report but I should have led with it. On reproduction, I suspect we ran different tests. The fault needs **four** conditions together, and missing any one of them shows nothing at all: 1. **RK3588 / RK3588S** — upstream's `support_fast_mode = 0` guard is specific to this SoC, so other Rockchip parts should be unaffected 2. **VP9 Profile 2 (10-bit)** — 8-bit VP9 is clean past 73,000 frames, HEVC Main10 clean past 70,000 3. **both rkvdec cores active** — disabling either one makes it disappear 4. **~65,536+ frames in one continuous decode session** — about 18 minutes at 60 fps, 45 at 24 fps; any decoder teardown resets the count, so short clips and seeks never reach it Exact reproduction: ffmpeg -i <4K 10-bit VP9 Profile 2 source> -c:v copy -f ivf out.ivf mpi_dec_test -i out.ivf -t 10 # separately: dmesg | grep -c "rkvdec-core.*resetting" If it helps, could you say which SoC, which stream, and roughly how many frames your test ran? If it was not RK3588 with 10-bit VP9 past ~65k frames in one session, that would explain the difference between us entirely. ### The measurement Since my first report compared your prebuilt binary against a source build — two variables — I rebuilt both sides from source myself, same toolchain, same board, same stream, same session. One line differs: | Build | Frames decoded | Resets | |---|---|---| | `jellyfin-mpp-next` @ `4e5b4cfe7`, unmodified | **66,300** | **414** | | the same tree + `git revert --no-commit 15c29e0fa` | **73,214** | **0** | `15c29e0fa` is `Revert "fix[hal_vp9d]: not support fast mode for rk3588"`, which restores `hal_task_count = 2` on a SoC where upstream sets `support_fast_mode = 0`. For completeness, upstream is clean at every point I tested, including the exact commit this branch is based on: | Upstream `rockchip-linux/mpp` | Frames | Result | |---|---|---| | `a37666b01` (2024-04-15) | 73,011 | clean | | `437bfbeb9` (2025-11-10 — the base of `jellyfin-mpp-next`) | 72,830 | clean | | `0986d0129` (2026-08-26) | 116,787 | clean | Board: Orange Pi 5B (RK3588S), kernel `6.1.0-1027-rockchip`. Both cores confirmed active and evenly loaded each run via per-core `/proc/interrupts` deltas (e.g. 33,041 / 33,042). ### What I am actually asking for Nothing, really — and I should have been clearer about that from the start. I am taking your advice and building against upstream MPP for my own images. I filed this because the same library ships to Jellyfin users on RK3588 hardware, and a long 10-bit VP9 title would cross that threshold mid-playback with no error surfaced to the application. If that is not a case you consider worth carrying, that is a completely reasonable call and I will not press it. Happy to re-file against the template, or to run any specific test you would find convincing. EOF echo " words: $(wc -w < "$D/jellyfin-765-reply.md"), leak hits: $(grep -cE "rich[._-]?defrese|DeFrese|cox\.net|/home/rich" "$D/jellyfin-765-reply.md")"

OUT

words: 515, leak hits: 0

Draft is at jellyfin-765-reply.md. The shape of it:

Concedes both fair points immediately — template and scope — because arguing those costs us credibility on the part that matters.

Gives him the four conditions, so "unable to reproduce" has somewhere to go. If he tested RK3576, or 8-bit, or a five-minute clip, the disagreement evaporates and neither of us is wrong.

Leads the evidence with the one-variable A/B — the control you just paid ten minutes of bench time for. That table is the whole argument: same tree, same toolchain, one git revert, 414 resets versus 0.

Ends by lowering the stakes. We're building against upstream regardless, so we're not asking him for anything. If he doesn't want to carry it, that's his call. That's not capitulation — it's removing his reason to dig in, while the measurement sits there unanswered.

The one thing it deliberately doesn't do is match his tone. "You completely ignored the issue report template" was a jab; responding in kind turns a technical disagreement into a personality one, and the table is far more damaging to his position than any amount of heat.

Want me to post it? And if you'd like, I can also re-file properly against their template as a separate clean issue — that removes his procedural objection entirely and costs us nothing.

give it a little balls

Bash Redraft with more backbone

IN

D=/home/rich-defrese/rockchip-notes/experiments/mpp-rkr72-port-test; cat > "$D/jellyfin-765-reply.md" <<'EOF' Fair hit on the template — that one's mine, and I'll re-file against it if you want the report to stand. The rest needs data rather than assertion. "Unable to reproduce" without saying what you ran doesn't engage with the measurement, and this fault has four conditions that all have to hold at once. Miss any one and you will see nothing, correctly: 1. **RK3588 / RK3588S.** Upstream's `support_fast_mode = 0` guard is specific to this SoC. Other Rockchip parts should be fine. 2. **VP9 Profile 2, 10-bit.** 8-bit VP9 runs clean past 73,000 frames; HEVC Main10 past 70,000. 3. **Both rkvdec cores active.** Disable either and it vanishes. 4. **65,536+ frames in one unbroken session** — ~18 min at 60 fps, ~45 at 24 fps. Any decoder teardown resets the count, so short clips, seeks and quality switches never get there. ffmpeg -i <4K 10-bit VP9 Profile 2 source> -c:v copy -f ivf out.ivf mpi_dec_test -i out.ivf -t 10 # separately: dmesg | grep -c "rkvdec-core.*resetting" Tell me the SoC, the stream and the frame count you reached and we can settle this in one message. If it wasn't RK3588 running 10-bit VP9 past ~65k frames in a single session, we simply tested different things. ### The measurement My first report compared your prebuilt binary against a source build, which is two variables. So I rebuilt both sides myself — same toolchain, same board, same stream, same session length. **One line differs:** | Build | Frames | Resets | |---|---|---| | `jellyfin-mpp-next` @ `4e5b4cfe7`, untouched | **66,300** | **414** | | identical tree + `git revert --no-commit 15c29e0fa` | **73,214** | **0** | `15c29e0fa` is `Revert "fix[hal_vp9d]: not support fast mode for rk3588"` — it restores `hal_task_count = 2` on the one SoC where upstream deliberately sets `support_fast_mode = 0`. Upstream is clean at every point I tested, **including the exact commit this branch is based on**: | `rockchip-linux/mpp` | Frames | Result | |---|---|---| | `a37666b01` (2024-04-15) | 73,011 | clean | | `437bfbeb9` (2025-11-10 — base of `jellyfin-mpp-next`) | 72,830 | clean | | `0986d0129` (2026-08-26) | 116,787 | clean | Orange Pi 5B (RK3588S), kernel `6.1.0-1027-rockchip`. Both cores verified active and evenly loaded on every run via per-core `/proc/interrupts` deltas (33,041 / 33,042 on the failing one). It reproduces on demand in about six minutes. That is a deterministic, one-line result. It stands until something contradicts it, and "cannot reproduce" isn't that. ### On scope Your call entirely — but be clear about what it means. That library ships to your users, and on RK3588 a feature-length 10-bit VP9 title crosses 65,536 frames mid-playback. When it does, **nothing surfaces to the application**: through 714 resets in one of my runs, `mpi_dec_test` wrote zero bytes to stdout and stderr and exited normally. The only evidence is `dmesg`. Anyone validating the way you likely just did would record a pass. I'm building against upstream for my own images either way, so I'm not asking you for anything. I filed it because your users don't have that option and won't know why their film falls apart eighteen minutes in. Re-file against the template, or run any test you'd find convincing — say which and I'll do it. EOF echo " words: $(wc -w < "$D/jellyfin-765-reply.md"), leak hits: $(grep -cE "rich[._-]?defrese|DeFrese|cox\.net|/home/rich" "$D/jellyfin-765-reply.md")"

OUT

words: 538, leak hits: 0

Redrafted with spine. What changed:

The apology is one line now, not a paragraph. Owned and moved past.

Direct challenge on the non-answer: "'Unable to reproduce' without saying what you ran doesn't engage with the measurement." Then the four conditions, then "Tell me the SoC, the stream and the frame count you reached and we can settle this in one message." He either produces parameters or he doesn't.

The line that does the work: "That is a deterministic, one-line result. It stands until something contradicted it, and 'cannot reproduce' isn't that."

Scope turned back on him. He's entitled to decline — but the draft names the cost: his users, his hardware, a film that dies eighteen minutes in, and zero bytes on stdout or stderr through 714 resets. That last detail is pointed, because it's very likely how he "couldn't reproduce" — running the test and seeing a clean exit code.

Still no insults, and still no ask. We're building against upstream regardless, which means he can't read it as us needing a favour. The pressure is entirely from the table.

That's as firm as I'd go while keeping it something you'd be happy to have quoted back at you in a thread with 4,000 views.

Post it?

Post It !

Bash Post the reply to the jellyfin-ffmpeg issue

IN

export GH_PAGER=cat; D=/home/rich-defrese/rockchip-notes/experiments/mpp-rkr72-port-test; echo " identity: $(gh api user --jq .login 2>/dev/null)"; URL=$(gh issue comment 765 --repo jellyfin/jellyfin-ffmpeg --body-file "$D/jellyfin-765-reply.md" 2>&1 | tail -1); echo " posted: $URL"; echo; gh issue view 765 --repo jellyfin/jellyfin-ffmpeg --json state,comments --jq '" issue state: \(.state)\n comments: \(.comments|length)\n last by: \(.comments[-1].author.login) at \(.comments[-1].createdAt[0:16])"' 2>&1

OUT

identity: defcom5-rockchip posted: https://github.com/jellyfin/jellyfin-ffmpeg/issues/765#issuecomment-5642616018 issue state: CLOSED comments: 2 last by: defcom5-rockchip at 2026-09-12T01:43

Posted: https://github.com/jellyfin/jellyfin-ffmpeg/issues/765#issuecomment-5642616018

One thing you should know: he closed the issue when he replied. Our comment landed on a closed thread — it still notifies him and everyone watching, and it's fully visible in the record, but it won't sit in their open queue.

I'd leave it closed. As the author I can probably reopen it, but doing that unilaterally right after a maintainer closed it reads as fighting over the ticket rather than the facts, and it hands him a procedural reason to disengage. The comment is what matters, and it's there permanently: a deterministic one-line A/B, the four reproduction conditions, and a direct request for what he actually tested.

If he comes back with parameters, we'll know within a message whether we tested different things. If he doesn't, the table stands unanswered in public — which is its own outcome, and a better one than an argument.

Either way it changes nothing about your path: we build librockchip_mpp with that one revert and ship it in Pi Desktop and Pi Studio. Your users get a working library regardless of what anyone upstream decides.

Want me to start that build? It's the same revert we just proved, packaged as librockchip-mpp1 versioned above the PPA's so apt prefers yours.

 

Redrafted with spine. What changed:

The apology is one line now, not a paragraph. Owned and moved past.

Direct challenge on the non-answer: "'Unable to reproduce' without saying what you ran doesn't engage with the measurement." Then the four conditions, then "Tell me the SoC, the stream and the frame count you reached and we can settle this in one message." He either produces parameters or he doesn't.

The line that does the work: "That is a deterministic, one-line result. It stands until something contradicted it, and 'cannot reproduce' isn't that."

Scope turned back on him. He's entitled to decline — but the draft names the cost: his users, his hardware, a film that dies eighteen minutes in, and zero bytes on stdout or stderr through 714 resets. That last detail is pointed, because it's very likely how he "couldn't reproduce" — running the test and seeing a clean exit code.

Still no insults, and still no ask. We're building against upstream regardless, which means he can't read it as us needing a favour. The pressure is entirely from the table.

That's as firm as I'd go while keeping it something you'd be happy to have quoted back at you in a thread with 4,000 views.

Bong!

I use my main Armbian-server installed on nvme, but I would prefer to run SD-images as well... Unfortunately, as I see, this became very difficult task lately(((.

P.S. I don't want to erase mtd0 and boot from SD as I will probably lose my perfectly working boot from nvme if SD-boot fails again. Not sure what to do...
 

Any ideas? Thanks.

Pain-point: I just want to use the system, not keep re-flashing OS.

nixOS is good, but I don't want to re-learn everything ... and giving up my Ubuntu eco-system.

Sorry I'm still testing out, and failing with existing Armbian-Config approach, I'm trying my own appraoch, Iknew the rules here, wait until I success I'll share it here. (note: or anyone did it before, can give me some direction)

 

Inspired by Bazzite OS, and remind me of experience on Armbian (not just armbian), basically on Orange PI 5/ OPI5+, it'll be solid OS if update failure/ anything went wrong can rollback to previous safe copy.

Pain-point: I just want to use the system, not keep re-flashing OS.

nixOS is good, but I don't want to re-learn everything ... and giving up my Ubuntu eco-system.

Orange Pi OS (Arch) on the official website ran normally.

However, I installed focal_desktop_xfce or jammy_desktop_gnome from Ubuntu Image, but they all failed.

After inserting the image into the SD card, the symptom is a black screen and no booting.

Does it only support SSD?

Because it is entered through a translator, there may be unnatural sentences. If you reply about that, I will get back to you.

I just switched to Armbian from NixOS arm64 and the first apt upgrade is now failing.  I am a novice user.  Thanks!

PS:  I wish you guys would pick a better IRC network, that libera place absolutely SUCKS.  They make you complete a verification process just to finally tell you they ban VPN's and you can't connect even after verifying.  Their e-mail support is obnoxious when inquiring as well.  What a dump!  

PPS: there seems to be no orange pi 5 max choice

I have installed the Armbian 26.2 minimal IOT image based on Debian 13 Trixie - with the 6.18.x kernel - and I noticed the USB2 port (the single, vertical port next to the Ethernet port) is not working. Is this a limitation of the mainstream kernel (6.18.x) - i.e. does this work only with the vendor kernel (6.1.x) ? NB: I upgraded to 6.19 using the 'edge' kernel, but I'm seeing the same behavior.

Here's the armbianmonitor outpur - https://paste.armbian.com/raw/udefojuxuk 

v4l2-ctl --device=/dev/video4 --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
        Type: Video Capture Multiplanar

        [0]: 'VT12' (Y/UV 4:2:0 (4x4 Linear))
        [1]: 'NV12' (Y/UV 4:2:0)

Shouldn't this include the 10 bit formats as well? (NV15?)

Does anyone know why the 10 bit format is missing in the kernel? Is this specific to the orange pi? 

I found this GitHub - dongioia/rock5bplus-rkvdec2: Rock 5B+ (RK3588) on mainline Linux 7.1: V4L2 stateless RKVDEC2/Hantro hardware video decode (VP9 / H.264 / HEVC / AV1) up to 4K, plus a guide for stock Chromium 150 with clean in-browser HW decode (VP9 Mali green artifact fixed upstream in the Chromium 150 ANGLE roll). HDMI 2.0 4K@60Hz, on Beryllium OS. · GitHub

Going to test their patches, I am unsure if they are related to the issue but they list a 10 bit VP9.

I'd like to share a small personal project that I've been working on recently for the Orange Pi 5 (and potentially other RK3588 boards).
Like many RK3588 users, I wanted to run Kodi on a modern mainline Linux kernel instead of relying on older vendor kernels. After a lot of testing, debugging and learning, this project started to take shape, and I've a stable almost "all works" setup
 

Tested on Armbian (minimal Debian and Ubuntu 24.04) with mainline kernel

Not working:

-HDR

-Maybe some network services

Next up:

-Wayland support

-Audio visualisers

https://github.com/Danibos/mainline-kodi-rk3588

A few important notes:
I'm not a kernel developer, but I have a great passion for all IT stuff, and this SBC encouraged me to dive much deeper into the Linux world. Of course this is only possible thanks to the incredible efforts from the Linux community, Collabora, LibreELEC, Armbian and many other contributors. I have mainly focused on bringing together different patches, configurations and components into a working setup for RK3588 devices, providing working .deb packages for the Kernel, FFmpeg and Kodi Piers
 

This is a personal project that I wanted to share because I know it could be really useful for many people out there. Due to my limited knowledge in this area and the little free time I have, I can't really offer it as a proper collaboration, but I'll still be happy to try to help if any issues come up. Feel free to open an issue or leave feedback!

I hope this project can be useful for other RK3588 users.
 

Thanks!
Dani

English is not my native, i hope you understand and sorry for mistakes 
I spend like 3 days on this problem and i think i am stuck
I tested offisial image and Josua and there i can use my wifi normally 

Setup

• orange pi 5 v1.3.2
• clened spi (i got problem like here)
• armbian 26.5.1 vendor 6.1.115 (from armbian imager on windows)
• sandisk extreme 64gb sd card

after boot i runs  

• sudo apt update
• sudo apt upgrade -y
• armbian-config (choose orange pi 5 ap6275p overlay)

/boot/armbianEnv.txt

verbosity=1
bootlogo=false
console=both
extraargs=cma=256M
overlay_prefix=rockchip-rk3588
fdtfile=rockchip/rk3588s-orangepi-5.dtb
rootdev=UUID=...
rootfstype=ext4
overlays=orangepi-5-ap6275p
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

But after reboot wifi module do not works as expected 

• ip a
• lspci

do not show any device 

As i think now it is some dtbo files problems and i think key is somthing around line:

[  121.023832] rk-pcie fe190000.pcie: PCIe Link Fail, LTSSM is 0x3, hw_retries=1
there is a guy figures same error 

but the lines he added already included for me

wifi and pcie dmesg greps (by the way armbian takes too long to boot and i fond sombody figures same problem and he syas that time depends on size of sd card)

root@orangepi5:~# dmesg | grep wifi
[  116.704296] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = ap6275p
[  116.704300] [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control.
[  116.704303] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by gpio.
[  116.704340] [WLAN_RFKILL]: wlan_platdata_parse_dt: The ref_wifi_clk not found !
[  116.704348] [WLAN_RFKILL]: rfkill_set_wifi_bt_power: 1
root@orangepi5:~# dmesg | grep pcie
[   19.019616] reg-fixed-voltage vcc3v3-pcie2x1l2: Looking up vin-supply from device tree
[   19.020209] vcc3v3_pcie2x1l2: supplied by vcc5v0_sys
[   19.079124] vcc3v3_pcie2x1l2: 1800 mV, enabled
[   19.085641] reg-fixed-voltage vcc3v3-pcie2x1l2: vcc3v3_pcie2x1l2 supplying 1800000uV
[  115.377859] dw-pcie fe190000.pcie: invalid resource
[  115.378688] dw-pcie fe190000.pcie: Failed to initialize host
[  115.378975] dw-pcie: probe of fe190000.pcie failed with error -22
[  115.405440] rk-pcie fe190000.pcie: invalid prsnt-gpios property in node
[  115.405658] rk-pcie fe190000.pcie: Looking up vpcie3v3-supply from device tree
[  115.407223] rk-pcie fe190000.pcie: can't get current limit.
[  115.409940] rk-pcie fe190000.pcie: host bridge /pcie@fe190000 ranges:
[  115.410471] rk-pcie fe190000.pcie:       IO 0x00f4100000..0x00f41fffff -> 0x00f4100000
[  115.410659] rk-pcie fe190000.pcie:      MEM 0x00f4200000..0x00f4ffffff -> 0x00f4200000
[  115.410757] rk-pcie fe190000.pcie:      MEM 0x0a00000000..0x0a3fffffff -> 0x0a00000000
[  115.410961] rk-pcie fe190000.pcie: iATU unroll: enabled
[  115.410983] rk-pcie fe190000.pcie: iATU regions: 8 ob, 8 ib, align 64K, limit 8G
[  115.613333] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  115.634444] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  115.655522] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  115.676607] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  115.697683] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  115.718758] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  115.739838] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  115.760912] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  115.781986] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  115.803060] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  116.912753] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up pcie-supply from device tree
[  116.912767] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up pcie-supply property in node /power-management@fd8d8000/power-controller failed
[  117.713882] rk-pcie fe190000.pcie: PCIe Link Fail, LTSSM is 0x3, hw_retries=0
[  120.627876] rk_pcie_establish_link: 171 callbacks suppressed
[  120.627888] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  120.648138] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  120.668247] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  120.689287] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  120.710332] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  120.731354] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  120.751458] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  120.772474] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  120.793551] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  120.814586] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3
[  121.023832] rk-pcie fe190000.pcie: PCIe Link Fail, LTSSM is 0x3, hw_retries=1
[  122.034993] rk-pcie fe190000.pcie: failed to initialize host

Context about long boot:

On 19 sec

[   19.315369] NetLabel: Initializing
[   19.315574] NetLabel:  domain hash size = 128
[   19.315819] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[   19.318283] NetLabel:  unlabeled traffic allowed by default
[   19.328104] vgaarb: loaded
[   19.365221] clocksource: Switched to clocksource arch_sys_counter
[   69.713069] VFS: Disk quotas dquot_6.6.0
[   69.715555] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[   69.734240] AppArmor: AppArmor Filesystem Enabled

And on 73 sec

[   73.253310] NET: Registered PF_ALG protocol family
[   73.253416] Key type asymmetric registered
[   73.253451] Asymmetric key parser 'x509' registered
[  113.848019] Freeing initrd memory: 15860K
[  114.505595] alg: self-tests for CTR-KDF (hmac(sha256)) passed
[  114.508695] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 241)
[  114.512435] io scheduler mq-deadline registered

So i do not know reason and where i need to look. Maybe it is broken dtbo or i need to load spesial spi because i am not spesialist at this point and i cand find sombody figured same problem.

I also got full dmesg for orange pi os (where wifi works) and armbian boot with and without wifi configured if any body needs it 

Just would like to start a discussion about the current state of video acceleration (decoding only, h.265/h.264/av1).

The soc (rk3588) recently got mainline support for these features in 7.0: https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md

Has anyone tested this on a OPI5 already, especially using Kodi? Does this work ootb there now?

Regards,

XXXBold

These instructions were included in the manual to configure the usage of the screen with the raspberry pi, but I am not familiar with how to translate the configuration into armbian.

Write the image to the TF card, then modify the following configuration in config.txt:

# uncomment to force a specific HDMI mode (this will force VGA)

hdmi_group=2

hdmi_mode=87

hdmi_cvt 1024 600 60 6 0 0 0

# uncomment to force a HDMI mode rather than DVI. This can make audio work in

# DMT (computer monitor) modes

hdmi_drive=1

as I've been trying to troubleshoot I see that it does get information from the  screen

cat /sys/class/drm/card0-HDMI-A-1/status = connected

cat /sys/class/drm/card0-HDMI-A-1/enabled = enabled

cat /sys/class/drm/card0-HDMI-A-1/modes

1024x600
1024x600
640x480
640x480
640x480
 

Ive just installed the latest version of Armbian (Ubuntu Noble+KDE) and everything works fine except it looks like it is not detecting my TV resolution correctly.

I can choose 1920x1080@120hz but if I try yo go to 4K I can only select 24Hz

I attach armbian monitor logs url,  modetest  and kscreendoctor

My cable is HDMI 2.1

Any help would be appreciated

modetest -c
trying to open device '/dev/dri/card1'... is not a KMS device
trying to open device '/dev/dri/card0'... done
opened device `RockChip Soc DRM` on driver `rockchip` (version 1.0.0 at 0)
Connectors:
id      encoder status          name            size (mm)       modes   encoders
83      82      connected       HDMI-A-1        1880x1060               35      82
  modes:
        index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot
  #0 4096x2160 24.00 4096 5116 5204 5500 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver
  #1 4096x2160 23.98 4096 5116 5204 5500 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: driver
  #2 3840x2160 30.00 3840 4016 4104 4400 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver
  #3 3840x2160 29.97 3840 4016 4104 4400 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: driver
  #4 3840x2160 25.00 3840 4896 4984 5280 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver
  #5 3840x2160 24.00 3840 5116 5204 5500 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver
  #6 3840x2160 23.98 3840 5116 5204 5500 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: driver
  #7 1920x1080 120.00 1920 2008 2052 2200 1080 1084 1089 1125 297000 flags: phsync, pvsync; type: driver
  #8 1920x1080 119.88 1920 2008 2052 2200 1080 1084 1089 1125 296703 flags: phsync, pvsync; type: driver
  #9 1920x1080 100.00 1920 2448 2492 2640 1080 1084 1089 1125 297000 flags: phsync, pvsync; type: driver
  #10 1920x1080 60.00 1920 2008 2052 2200 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver
  #11 1920x1080 59.94 1920 2008 2052 2200 1080 1084 1089 1125 148352 flags: phsync, pvsync; type: driver
  #12 1920x1080 50.00 1920 2448 2492 2640 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver
  #13 1920x1080 30.00 1920 2008 2052 2200 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver
  #14 1920x1080 29.97 1920 2008 2052 2200 1080 1084 1089 1125 74176 flags: phsync, pvsync; type: driver
  #15 1920x1080 24.00 1920 2558 2602 2750 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver
  #16 1920x1080 23.98 1920 2558 2602 2750 1080 1084 1089 1125 74176 flags: phsync, pvsync; type: driver
  #17 1680x1050 59.88 1680 1728 1760 1840 1050 1053 1059 1080 119000 flags: phsync, nvsync; type: driver
  #18 1600x900 60.00 1600 1624 1704 1800 900 901 904 1000 108000 flags: phsync, pvsync; type: driver
  #19 1280x1024 60.02 1280 1328 1440 1688 1024 1025 1028 1066 108000 flags: phsync, pvsync; type: driver
  #20 1152x864 75.00 1152 1216 1344 1600 864 865 868 900 108000 flags: phsync, pvsync; type: driver
  #21 1280x720 60.00 1280 1390 1430 1650 720 725 730 750 74250 flags: phsync, pvsync; type: driver
  #22 1280x720 59.94 1280 1390 1430 1650 720 725 730 750 74176 flags: phsync, pvsync; type: driver
  #23 1280x720 50.00 1280 1720 1760 1980 720 725 730 750 74250 flags: phsync, pvsync; type: driver
  #24 1280x720 30.00 1280 3040 3080 3300 720 725 730 750 74250 flags: phsync, pvsync; type: driver
  #25 1280x720 29.97 1280 3040 3080 3300 720 725 730 750 74176 flags: phsync, pvsync; type: driver
  #26 1280x720 24.00 1280 3040 3080 3300 720 725 730 750 59400 flags: phsync, pvsync; type: driver
  #27 1280x720 23.98 1280 3040 3080 3300 720 725 730 750 59341 flags: phsync, pvsync; type: driver
  #28 1024x768 60.00 1024 1048 1184 1344 768 771 777 806 65000 flags: nhsync, nvsync; type: driver
  #29 800x600 60.32 800 840 968 1056 600 601 605 628 40000 flags: phsync, pvsync; type: driver
  #30 720x576 50.00 720 732 796 864 576 581 586 625 27000 flags: nhsync, nvsync; type: driver
  #31 720x480 60.00 720 736 798 858 480 489 495 525 27027 flags: nhsync, nvsync; type: driver
  #32 720x480 59.94 720 736 798 858 480 489 495 525 27000 flags: nhsync, nvsync; type: driver
  #33 640x480 60.00 640 656 752 800 480 490 492 525 25200 flags: nhsync, nvsync; type: driver
  #34 640x480 59.94 640 656 752 800 480 490 492 525 25175 flags: nhsync, nvsync; type: driver
  props:
        1 EDID:
                flags: immutable blob
                blobs:

                value:
                        00ffffffffffff004dd9057901010101
                        011e010380bc6a780a0dc9a057479827
                        12484c2108008180a9c0714fb3000101
                        01010101010108e80030f2705a80b058
                        8a005a227400001e023a801871382d40
                        582c45005a227400001e000000fc0053
                        4f4e5920545620202a33300a000000fd
                        0017790e883c000a20202020202001bf
                        020367f05861605d5e5f621f10140513
                        0420223c3e1203110265663f402f0d7f
                        071507503d07bc570601670403830f00
                        006e030c004000b8442b008001020304
                        67d85dc401788003eb0146d000480382
                        88627697e200cbe305df01e40f030030
                        e6060d018aac10011d007251d01e206e
                        2855005a227400001e000000000000a3
        2 DPMS:
                flags: enum
                enums: On=0 Standby=1 Suspend=2 Off=3
                value: 0
        5 link-status:
                flags: enum
                enums: Good=0 Bad=1
                value: 0
        6 non-desktop:
                flags: immutable range
                values: 0 1
                value: 0
        4 TILE:
                flags: immutable blob
                blobs:

                value:
        84 max bpc:
                flags: range
                values: 8 8
                value: 8

kscreen-doctor -o
Output: 1 HDMI-A-1 ea40cb77-73bf-4175-8970-22f84927f147
        enabled
        connected
        priority 1
        HDMI
        replication source:0
        Modes:  1:4096x2160@24.00*!  2:4096x2160@23.98  3:3840x2160@30.00  4:3840x2160@29.97  5:3840x2160@25.00  6:3840x2160@24.00  7:3840x2160@23.98  8:1920x1080@120.00  9:1920x1080@119.88  10:1920x1080@100.00  11:1920x1080@60.00  12:1920x1080@60.00  13:1920x1080@59.94  14:1920x1080@50.00  15:1920x1080@30.00  16:1920x1080@29.97  17:1920x1080@24.00  18:1920x1080@23.98  19:1680x1050@59.88  20:1600x900@60.00  21:1280x1024@60.02  22:1152x864@75.00  23:1280x720@60.00  24:1280x720@60.00  25:1280x720@59.94  26:1280x720@50.00  27:1280x720@30.00  28:1280x720@29.97  29:1280x720@24.00  30:1280x720@23.98  31:1024x768@60.00  32:800x600@60.32  33:720x576@50.00  34:720x576@50.00  35:720x480@60.00  36:720x480@60.00  37:720x480@59.94  38:720x480@59.94  39:640x480@60.00  40:640x480@59.94 
        Custom modes: None
        Geometry: 0,0 1821x960
        Scale: 2.25
        Rotation: 1
        Overscan: 0
        Vrr: incapable
        RgbRange: unknown
        HDR: incapable
        Wide Color Gamut: incapable
        ICC profile: none
        Color profile source: sRGB
        Color power preference: prefer efficiency and performance
        Brightness control: supported, set to 100% and dimming to 100%
        Color resolution: automatic (10), range: [8; 8] bits per color
        Allow EDR: unsupported
        Sharpness control: unsupported
        Automatic brightness: unsupported

Thank you

I'm aware of wiringPi and it sort of works. However, being able to use the "real stuff" so to speak would make my life easier.

Testing this OP5, got a standard M2 NVMe SSD (this works on my OP5Plus)

I have formatted to exFAT with windows, inserted on the OP5, loaded ArmbianOS on MicroSD, it boots fine but I cant get it to show the nvme drive using fdisk -l  or lsblk

It seem like its not detecting the m2 nvme ssd at all..

little help please ?

After looking into this issue, I found rkspi_loader.img is no longer available for current (6.18.8 kernel) u-boot pkg and armbian-config flashes u-boot-rockchip-spi.bin ( or similar sata version) to /dev/mtdblock0 and I think this is wrong image for MTD bootloader. If I use older vendor image, which u-boot pkg has rkspi_loader.img, system can boot to NVMe rootfs and I notice that /dev/mtdblock0 has several gpt partitions including u-boot one, and flashing u-boot-rockchip-spi.bin erases partitions in SPI flash.

I noticed that several related changes were introduced since 25.11, such as https://github.com/armbian/build/commit/e5b845f9432abb0408287599bba5889a86e6d068 , but I couldn't do quick fix to bring back working rkspi_loader.img because I am not familiar with whole armbian build.

One thing to note that if board was flashed with old rkspi_loader.img and not updated with 26.2 MTD image, it still boots to NVMe  rootfs, but I have other issues such as video playback not working with 6.18 kernel likely due to mismatch u-boot and kernel version leading to wrong HW initialization.

BTW, I checked 26.2 u-boot pkg for Rock 5B (similar rk3588 board), and rkspi_loader.img is still included.

The Orange Pi 5 displays the graphical grub menu with no problems, complete with penguin in the background etc, but once I choose the boot Armbian option, it displays a few lines of terminal output and then the monitor goes black as if the GPU is initializing and a desktop or graphic would be about to show - when instead, the monitor just reports no signal instead.

The system isn't frozen, the perhiperals are on and I can alt+ctrl+del to reboot it.

It's just attached to a very basic 1080p ASUS monitor that only does 60hz so I'm not sure what could be wrong

Thanks for any advice

I have installed the minimal Trixie based image for Orange Pi5 (the image named Armbian_26.2.1_Orangepi5_trixie_current_6.18.8_minimal) and then attempted to build an out-of-tree kernel module. Having installed dkms and build-essentials, plus the kernel headers through armbian-config, I found the headers package hasn't been fully set-up, the build symlink in /lib/modules/<KVER> is missing and dkms complains that the kernel headers for the kernel are not installed.

 The kernel headers are installed though, but it looks like they're from a previous release (25.11.2 instead of 26.2.1).

# dpkg -l | grep rockchip
ii  linux-dtb-current-rockchip64      26.2.1                         arm64        Armbian Linux current DTBs in /boot/dtb-6.18.8-current-rockchip64
ii  linux-headers-current-rockchip64  25.11.2                        arm64        Armbian Linux current headers 6.12.58-current-rockchip64
ii  linux-image-current-rockchip64    26.2.1                         arm64        Armbian Linux current kernel image 6.18.8-current-rockchip64

 It the headers package still pending packaging ? Shouldn't armbian-config provide an error in this case and not install the old kernel headers ?

EDIT: armbianmonitor ouput - https://paste.armbian.com/oliyalebeq

It runs great, pages are up, and it's all SO COOL, but it fails to do a restart... I can do a shutdown -h now, count to three and power it back up and all is well, but if I do a shutdown -r now it will go down, start back up, all the way to the login prompt but then barfs a long Oops message. God please... don't make me start over !

Orange Pi OS Instructions

Download Orange Pi OS Ubuntu or Debian from their website http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-pi-5.html unzip the 7z file to get the .img file and flash it to your sd card with your preferred flasher i.e balenaetcher. Once flashed put it into orange pi 5 and boot from sd card first

once booted, the rest will be done in a terminal. go ahead and do your usual update

sudo apt update

sudo apt upgrade -y

3. then make sure to wipe your SPI of any previous bootloader (give it time to complete, you'll know it's done when you get your cursor back in terminal)

sudo dd if=/dev/zero of=/dev/mtdblock0 bs=1M count=1

4. Write sata bootloader to SPI

sudo dd if=/usr/share/orangepi5/rkspi_loader_sata.img of=/dev/mtdblock0 && sudo sync

5. Edit boot file on sd card to recognize sata by adding overlays line to the bottom, save then reboot

sudo nano /boot/orangepiEnv.txt

overlays=ssd-sata

sudo reboot

6. On reboot you will still boot into SD card but now you should see "sda" (your sata SSD) show up on your list of devices when typing:

lsblk

7. Put the same Orange Pi OS image you used in step 1 in any directory on your orange pi making sure it is unzipped and is in .img format. I just used the web browser in orange pi os to redownload from the website which for me put it in directory /home/orangepi/Downloads

8. Flash your downloaded .img to your sata ssd with this command (substitute with your directory to .img)

sudo dd bs=1M if=/path/your/orangepi.img of=/dev/sda status=progress && sudo sync

9. Mount your ssd so you can edit the ssd’s boot file to support sata and reboot

sudo mount /dev/sda1 /mnt/

sudo nano /mnt/boot/orangepiEnv.txt

overlays=ssd-sata

sudo umount /mnt/ && sudo sync

sudo poweroff

10. Remove SDcard, turn on orange pi and it should boot orange pi OS from your M.2 sata ssd now

Armbian OS Instructions

Relatively same instructions with different file names

write armbian .img file to your sd card with balenaetcher, I chose to use the more up to date imags from their github here https://github.com/armbian/build/releases/ make sure to unzip

boot armbian from sd card, wipe spi

sudo dd if=/dev/zero of=/dev/mtdblock0 bs=1M count=1

3 Download sata spi bootloader from orange github, place it on your sd card (mine is in downloads directory) and write to spi

https://github.com/orangepi-xunlong/orangepi-build/blob/next/external/packages/bsp/rk3588/usr/share/orangepi5/rkspi_loader_sata.img

sudo dd if=/home/pi/Downloads/rkspi_loader_sata.img of=/dev/mtdblock0 status=progress && sudo sync

4. Edit boot file to recognize sata then reboot

sudo nano /boot/armbianEnv.txt

overlays=opi5-sata

sudo reboot

5. Once rebooted you can check sda shows up with command:

lsblk

6. download the same armbian.img you used for step 1 to your orange pi making sure it's unzipped in .img format, then flash it to your ssd

sudo dd bs=1M if=/path/your/armbian.img of=/dev/sda status=progress && sudo sync

7. Mount /boot/ of ssd so you can edit the ssd’s boot file to support sata and reboot

sudo mount /dev/sda1 /mnt/

sudo nano /mnt/boot/armbianEnv.txt

overlays=opi5-sata

sudo umount /mnt/ && sudo sync

sudo poweroff

8. Remove SDcard and start SBC, resize filesystem to use all available space

sudo systemctl enable armbian-resize-filesystem

I installed lm-sensors on my Opi5 and I'm able to check temperatures, however I don't know how to make the little fan spin when the temperature rise. I know the temperature is not going to rise till critical levels, but I live in very hot country and I just don't want my device to become too hot.

And do you know how to make the fan start at certain temperature rise? Also I'm not sure which pins I should connect the fan to..

One pin should be the 3.3V to get the power, what about the other one?

I'm running Armbian 23.02.2 with kernel 5.10.110-rockchip-rk3588

Thanks in advance

First post here, I successfully managed to flash and boot Armbian 25.8.2 (Bookworm Minimal) from an SD card. Everything was working great, HDMI output and network included.

I then ran “sudo armbian-install” and selected Option 4 to move the system to my NVMe SSD and make it boot from there. The process itself completed without errors.

However, after shutting down and removing the SD card and powering on again the system doesn’t boot. I have the red LED turned on however the green LED that was previously flickering doesn’t turn on. There’s also no HDMI output and the board doesn’t connect to the network. 

I tried inserting the SD card and the system does boot from that just fine.

Where did I screw up? Appreciate the help!

my Orange Pi 5 works well with the stock OS (1.22, Ubuntu Jammy, BSP kernel 6.1.99), using the SD as a boot device.

It also works ok with Armbian Minimal-IoT / Debian 13 / 6.1:

 v25.8.2 for Orange Pi 5 running Armbian Linux 6.1.115-vendor-rk35xx

But I prefer Ubuntu and wanted to try 6.12, so I downloaded 25.8.2 / Ubuntu Server / 6.12.

Wrote to SD, hooked up the debug UART and powered on.

The bootloader is fine, the kernel starts, but at a certain point it panics:

[  OK  ] Reached target sockets.target - Socket Units.
         Starting armbian-hardware-monitor.…ce - Armbian hardware monitoring...
         Starting armbian-hardware-optimize… - Armbian hardware optimization...
         Starting armbian-led-state.service - Armbian leds state...
         Starting armbian-resize-filesystem…vice - Armbian filesystem resize...
armbian-hardware-monitor.service
[  OK  ] Finished armbian-hardware-monitor.…vice - Armbian hardware monitoring.
[  OK  ] Finished armbian-led-state.service - Armbian leds state.
armbian-led-state.service
[  OK  ] Finished armbian-hardware-optimize…ce - Armbian hardware optimization.
armbian-hardware-optimize.service
[  OK  ] Finished console-setup.service - Set console font and keymap.
console-setup.service
sys-kernel-debug-tracing.mount
[  158.363359] rockchip-pm-domain fd8d8000.power-management:power-controller: failed to get ack on domain 'gpu', val=0xa9fff
[  158.364324] SError Interrupt on CPU7, code 0x00000000be000411 -- SError
[  158.364327] CPU: 7 UID: 0 PID: 462 Comm: (udev-worker) Tainted: G   M     C         6.12.49-current-rockchip64 #1
[  158.364332] Tainted: [M]=MACHINE_CHECK, [C]=CRAP
[  158.364333] Hardware name: Xunlong Orange Pi 5 (DT)
[  158.364334] pstate: 404000c9 (nZcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[  158.364336] pc : _raw_spin_lock_irqsave+0x38/0x8c
[  158.364342] lr : regmap_lock_spinlock+0x18/0x2c
[  158.364347] sp : ffff800083f03660
[  158.364348] x29: ffff800083f03660 x28: 0000000000000000 x27: ffff800083f03c60
[  158.364351] x26: 0000000000000000 x25: ffff710bf0c4c080 x24: ffff710bf0f64098
[  158.364354] x23: 0000000000000000 x22: 0000000000000001 x21: 0000000000000000
[  158.364356] x20: 000000000000000c x19: 0000000000000000 x18: ffffffffffffffff
[  158.364358] x17: 66203a72656c6c6f x16: 72746e6f632d7265 x15: 776f703a746e656d
[  158.364361] x14: 6567616e616d2d72 x13: 00000000000002ac x12: 00000000ffffffea
[  158.364363] x11: 0000000000000001 x10: 0000000000000001 x9 : ffffc80dcfdf9250
[  158.364365] x8 : 000000000002ffe8 x7 : c0000000ffffdfff x6 : 00000000000affa8
[  158.364368] x5 : ffffc80dce6c1b54 x4 : 0000000000000008 x3 : ffffc80dce6c15c8
[  158.364370] x2 : 0000000000000001 x1 : 0000000000000000 x0 : ffff710bf0f65c00
[  158.364373] Kernel panic - not syncing: Asynchronous SError Interrupt
[  158.364374] CPU: 7 UID: 0 PID: 462 Comm: (udev-worker) Tainted: G   M     C         6.12.49-current-rockchip64 #1
[  158.364377] Tainted: [M]=MACHINE_CHECK, [C]=CRAP
[  158.364378] Hardware name: Xunlong Orange Pi 5 (DT)
[  158.364379] Call trace:
[  158.364380]  dump_backtrace+0x94/0x114
[  158.364383]  show_stack+0x18/0x24
[  158.364385]  dump_stack_lvl+0x38/0x90
[  158.364387]  dump_stack+0x18/0x24
[  158.364389]  panic+0x39c/0x3f4
[  158.364392]  nmi_panic+0x40/0x8c
[  158.364394]  arm64_serror_panic+0x70/0x80
[  158.364396]  do_serror+0x3c/0x78
[  158.364398]  el1h_64_error_handler+0x30/0x48
[  158.364401]  el1h_64_error+0x64/0x68
[  158.364402]  _raw_spin_lock_irqsave+0x38/0x8c
[  158.364404]  regmap_lock_spinlock+0x18/0x2c
[  158.364407]  regmap_write+0x3c/0x78
[  158.364409]  rockchip_pd_power+0xf8/0x5e8
[  158.364414]  rockchip_pd_power_on+0x14/0x20
[  158.364417]  _genpd_power_on+0x94/0x188
[  158.364418]  genpd_power_on.part.0+0xa4/0x1ac
[  158.364421]  __genpd_dev_pm_attach+0x144/0x2dc
[  158.364423]  genpd_dev_pm_attach+0x60/0x70
[  158.364425]  dev_pm_domain_attach+0x20/0x34
[  158.364429]  platform_probe+0x50/0xdc
[  158.364431]  really_probe+0xc0/0x38c
[  158.364434]  __driver_probe_device+0x7c/0x15c
[  158.364437]  driver_probe_device+0x40/0x114
[  158.364440]  __driver_attach+0xf4/0x1fc
[  158.364443]  bus_for_each_dev+0x74/0xd4
[  158.364445]  driver_attach+0x24/0x30
[  158.364448]  bus_add_driver+0x110/0x234
[  158.364451]  driver_register+0x60/0x128
[  158.364453]  __platform_driver_register+0x24/0x30
[  158.364455]  panthor_init+0x64/0x1000 [panthor]
[  158.364467]  do_one_initcall+0x44/0x2a8
[  158.364470]  do_init_module+0x58/0x20c
[  158.364472]  load_module+0x1e4c/0x1f3c
[  158.364474]  init_module_from_file+0x84/0xc4
[  158.364476]  __arm64_sys_finit_module+0x1f4/0x2f0
[  158.364478]  invoke_syscall+0x48/0x110
[  158.364481]  el0_svc_common.constprop.0+0xc8/0xe8
[  158.364484]  do_el0_svc+0x20/0x2c
[  158.364487]  el0_svc+0x30/0xfc
[  158.364488]  el0t_64_sync_handler+0x13c/0x158
[  158.364491]  el0t_64_sync+0x190/0x194
[  158.364492] SMP: stopping secondary CPUs
[  158.364557] Kernel Offset: 0x480d4dc00000 from 0xffff800080000000
[  158.364558] PHYS_OFFSET: 0xffff8ef600000000
[  158.364559] CPU features: 0x1c,00000017,00280928,4200720b
[  158.364561] Memory Limit: none
[  158.393407] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---

Power brick is a solid 5V/4A and as I said works OK with the stock OS (7zip benchmark and all) and Armbian Minimal

Any suggestion?

Thanks a lot

Fernando

The only way I've been able to get access to the USB is by switching to the latest `current` kernel... Any clues on what is going on? Firmware or kernel upgrades are not doing anything... where can the issue be???? I tried downgrading to many different versions but beside the current branch, USB is gone. 

Thanks

I recently got my hands on a used unit of those, quite faster than my old SBC!

Only issue I currently have is that I can't seem to get audio output on the 3.5mm jack.

(Well the other issue is unrelated .. )

Anyone have an idea on what I should be hunting?

I did the obvious cable, etc.. checks. There's always the possibility that it's damaged, hell if I know.

Armbian 25.2.1

6.1 kernel

KDE Neon  (Why use a beta version btw? just wondering)

Thanks!

DW.

I'm using Ubuntu noble lts with kernel 6.1 it appears.

I've enabled the orangepi-5-sata overlay.

In the photos I have showed how I've connected it.

When plugging in the pi with my official 5v 4a usbc charger, the adapter lights up for awhile. I'm not sure if it needs to stay on.

I then check fdisk -l and nothing new appears. This drive works if I put the sata to usb connector on it and plug it in - so it's not the drive.

Cheers!

Basically the subj sums it up. I got the AP6275P wireless module with Armbian, and BT is not functional. `hcitool dev` doesn't show the device in its output. Neither does `rfkill`.  It works with the Ubuntu image published by Orange Pi though, so it doesn't look like a hardware issue.

I'm using Armbian 23.5 Jammy Gnome with the 5.10.160 kernel. Happy to provide any additional data.

Quote

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: hdmi0 [hdmi0], device 0: fddf0000.i2s-i2s-hifi i2s-hifi-0 [fddf0000.i2s-i2s-hifi i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: rockchipes8388 [rockchip,es8388], device 0: fe480000.i2s-es8328-hifi-analog es8328-hifi-analog-0 [fe480000.i2s-es8328-hifi-analog es8328-hifi-analog-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I have enabled the hdmirx overlay through armbian-config also, but the result is the same.

Is there anything extra that should be configured in order to get audio output ? 

Output from armbianmonitor  - https://paste.armbian.com/gegorimako

I note that this file should not be edited and the armbianEnv.txt only refers to rootdev=UUID=7e27c862-0a39-41cd-891e-7d77ff7968fd.

Is this an error or am I off course?  If so where do I correct it?

cheers 

orangepi-5-sata.dtbo orangepi-5-sata.dts

I am trying to recover after a failed NVMe install.  I have a working install on an SDCard, but I think my board no longer boots to SDCard, since I flashed the bootloader via armbian-install.

I am not sure if my NVMe install is good or not, and I can't currently reflash it.

So I think my best bet is to wipe the SPI, which I hope means the board will go back to booting from SDCard.

That's question 1 - is that actually a valid solution?  If I wipe the SPI will I be able to again boot to SDCard?

I am able to get the board into Maskrom mode, and I can see it using the Windows tool.  However, I believe that I need a "loader image" that I "download" into the tool before I can wipe the bootloader.

The Rock5 SPI wipe guide posted elsewhere in this forum refers to rk3588_spl_loader_v1.08.111.bin, which I don't have, and I'm not sure that's the right loader for the OPi5.

That's question 2 - is there a loader for the OPi5 and/or can the Rock5 loader be used here?

The OPi5 Manual is very sparse about Maskrom info, it says how to get into that mode, but only gives instructions for flashing the board to Android.  The Android download is not working right now (Google Drive quota) so I am not able to get that package, in case it happens to have a suitable loader image.

Thanks for any replies in advance.

I have downloaded and tested the 6.12 kernel Minimal/IOT images and they are not booting.

I downloaded trixie 6.1, booted, then manually installed latest 6.12 with armbian-config and the reboot failed.

I re-flashed sd card with 6.1, installed edge 6.16.4 (latest) with armbian-config and it booted fine. 

DDR V1.11 f1474cf52f cym 23/05/09-11:02:36
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
Manufacturer ID:0x6
CH0 RX Vref:28.5%, TX Vref:21.8%,21.8%
CH1 RX Vref:25.0%, TX Vref:22.8%,22.8%
CH2 RX Vref:28.5%, TX Vref:22.8%,22.8%
CH3 RX Vref:29.3%, TX Vref:22.8%,21.8%
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz
out
U-Boot SPL board init
U-Boot SPL 2017.09 (Feb 25 2024 - 00:42:52)
Trying to boot from MMC1
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256(2e8446f969...) + OK
## Checking uboot 0x00200000 ... sha256(528486af2f...) + OK
## Checking fdt 0x0034f598 ... sha256(906c87aa7c...) + OK
## Checking atf-2 0xff100000 ... sha256(9f75e6ec37...) + OK
## Checking atf-3 0x000f0000 ... sha256(c80587de50...) + OK
Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000)
Total: 801.437 ms

INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():v2.3-662-g4acbe711b-dirty:finley.xiao, fwver: v1.44
NOTICE:  BL31: Built : 16:44:24, Nov  7 2023
INFO:    spec: 0x13
INFO:    code: 0x88
INFO:    ext 32k is valid
INFO:    ddr: stride-en 4CH
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0
INFO:    l3 cache partition cfg-0
INFO:    system boots from cpu-hwid-0
INFO:    idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
ERROR:   dfs get fsp_params[0] error, 0xfead0003 != 0xfead0004
ERROR:   dfs get fsp_params[1] error, 0xa2c != 0xfead0004
ERROR:   dfs get fsp_params[2] error, 0xa34 != 0xfead0004
ERROR:   dfs get fsp_params[3] error, 0xadc != 0xfead0004
ERROR:   loader&trust unmatch!!! Please update loader if need enable dmc
ERROR:   current trust bl31 need match with loader ddr bin V1.13 or newer
ERROR:   current loader need match with trust bl31 V1.38-V1.40
INFO:    BL31: Initialising Exception Handling Framework
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09 (Feb 06 2025 - 03:18:03 +0000)

Model: Orange Pi 5
MPIDR: 0x81000000
PreSerial: 2, raw, 0xfeb50000
DRAM:  16 GiB
Sysmem: init
Relocation Offset: eda0e000
Relocation fdt: eb9f9250 - eb9fecb8
CR: M/C/I
Using default environment

DM: v2
mmc@fe2c0000: 1, mmc@fe2e0000: 0
Card did not respond to voltage select!
mmc_init: -95, time 13
switch to partitions #0, OK
mmc1 is current device
Boot from SDcard
Bootdev(scan): mmc 1
MMC1: Legacy, 52Mhz
PartType: EFI
No misc partition
boot mode: None
FIT: No boot partition
Failed to load DTB, ret=-2
No valid DTB, ret=-22
Failed to get kernel dtb, ret=-22
Model: Orange Pi 5
MPIDR: 0x81000000
CLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kernel 0N/A)
  b0pll 24000 KHz
  b1pll 24000 KHz
  lpll 24000 KHz
  v0pll 24000 KHz
  aupll 24000 KHz
  cpll 1500000 KHz
  gpll 1188000 KHz
  npll 24000 KHz
  ppll 1100000 KHz
  aclk_center_root 702000 KHz
  pclk_center_root 100000 KHz
  hclk_center_root 396000 KHz
  aclk_center_low_root 500000 KHz
  aclk_top_root 750000 KHz
  pclk_top_root 100000 KHz
  aclk_low_top_root 396000 KHz
No misc partition
Net:   No ethernet found.
Hit key to stop autoboot('CTRL+C'):  0
starting USB...
Bus usb@fc000000: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus usb@fc800000: USB EHCI 1.00
Bus usb@fc840000: USB OHCI 1.0
Bus usb@fc880000: USB EHCI 1.00
Bus usb@fc8c0000: USB OHCI 1.0
Bus usb@fcd00000: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fc000000 for devices... 1 USB Device(s) found
scanning bus usb@fc800000 for devices... 1 USB Device(s) found
scanning bus usb@fc840000 for devices... 1 USB Device(s) found
scanning bus usb@fc880000 for devices... 1 USB Device(s) found
scanning bus usb@fc8c0000 for devices... 1 USB Device(s) found
scanning bus usb@fcd00000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3906 bytes read in 22 ms (172.9 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1:1
289 bytes read in 19 ms (14.6 KiB/s)
16738524 bytes read in 1382 ms (11.5 MiB/s)
38277632 bytes read in 3103 ms (11.8 MiB/s)
148164 bytes read in 122 ms (1.2 MiB/s)
Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards.
Unknown command 'kaslrseed' - try 'help'
Fdt Ramdisk skip relocation
No misc partition
## Loading init Ramdisk from Legacy Image at 0a200000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    16738460 Bytes = 16 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 0x08300000
   Booting using the fdt blob at 0x08300000
   reserving fdt memory region: addr=8300000 size=8a000
   Using Device Tree in place at 0000000008300000, end 000000000838cfff
can't found rockchip,drm-logo, use rockchip,fb-logo
WARNING: could not set reg FDT_ERR_BADOFFSET.
failed to reserve fb-loader-logo memory
WARNING: could not set reg FDT_ERR_BADOFFSET.
## reserved-memory:
  shmem@10f000: addr=10f000 size=100
Adding bank: 0x00200000 - 0xf0000000 (size: 0xefe00000)
Adding bank: 0x100000000 - 0x3fc000000 (size: 0x2fc000000)
Adding bank: 0x3fc500000 - 0x3fff00000 (size: 0x03a00000)
Adding bank: 0x4f0000000 - 0x500000000 (size: 0x10000000)
Total: 13124.390/13152.482 ms

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050]
[    0.000000] Linux version 6.12.42-current-rockchip64 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #1 SMP PREEMPT Fri Aug 15 10:14:14 UTC 2025
[    0.000000] KASLR disabled due to lack of seed
[    0.000000] Machine model: Xunlong Orange Pi 5
[    0.000000] efi: UEFI not found.
[    0.000000] OF: reserved mem: 0x000000000010f000..0x000000000010f0ff (0 KiB) nomap non-reusable shmem@10f000
[    0.000000] NUMA: Faking a node at [mem 0x0000000000200000-0x00000004ffffffff]
[    0.000000] NODE_DATA(0) allocated [mem 0x4fdf30a40-0x4fdf331bf]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000200000-0x00000000ffffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   [mem 0x0000000100000000-0x00000004ffffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000200000-0x00000000efffffff]
[    0.000000]   node   0: [mem 0x0000000100000000-0x00000003fbffffff]
[    0.000000]   node   0: [mem 0x00000003fc500000-0x00000003ffefffff]
[    0.000000]   node   0: [mem 0x00000004f0000000-0x00000004ffffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000200000-0x00000004ffffffff]
[    0.000000] On node 0, zone DMA: 512 pages in unavailable ranges
[    0.000000] On node 0, zone Normal: 1280 pages in unavailable ranges
[    0.000000] On node 0, zone Normal: 256 pages in unavailable ranges
[    0.000000] cma: Reserved 256 MiB at 0x00000000e0000000 on node -1
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] psci: SMC Calling Convention v1.2
[    0.000000] percpu: Embedded 34 pages/cpu s99544 r8192 d31528 u139264
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] CPU features: detected: Virtualization Host Extensions
[    0.000000] CPU features: detected: Qualcomm erratum 1009, or ARM erratum 1286807, 2441009
[    0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[    0.000000] alternatives: applying boot alternatives
[    0.000000] Kernel command line: root=UUID=b879703b-1824-4faa-b2fd-447377946c85 rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=7 ubootpart=54782d48-122d-bc44-b795-0bd9a0b2c55c usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cma=256M  cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory androidboot.fwver=bl31-v1.44,uboot-02/06/2025
[    0.000000] Unknown kernel command line parameters "splash=verbose ubootpart=54782d48-122d-bc44-b795-0bd9a0b2c55c cgroup_enable=memory cgroup_memory=1", will be passed to user space.
[    0.000000] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
[    0.000000] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
[    0.000000] Fallback order for Node 0: 0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 4192256
[    0.000000] Policy zone: Normal
[    0.000000] mem auto-init: stack:all(zero), heap alloc:on, heap free:off
[    0.000000] software IO TLB: area num 8.
[    0.000000] software IO TLB: mapped [mem 0x00000000dc000000-0x00000000e0000000] (64MB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU event tracing is enabled.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=8.
[    0.000000]  Trampoline variant of Tasks RCU enabled.
[    0.000000]  Tracing variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
[    0.000000] RCU Tasks: Setting shift to 3 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=8.
[    0.000000] RCU Tasks Trace: Setting shift to 3 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=8.
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 480 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] GICv3: MBI range [424:479]
[    0.000000] GICv3: Using MBI frame 0x00000000fe610000
[    0.000000] Root IRQ handler: gic_handle_irq
[    0.000000] GICv3: GICv3 features: 16 PPIs
[    0.000000] GICv3: GICD_CTRL.DS=0, SCR_EL3.FIQ=1
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000fe680000
[    0.000000] ITS [mem 0xfe640000-0xfe65ffff]
[    0.000000] GIC: enabling workaround for ITS: Rockchip erratum RK3588001
[    0.000000] ITS@0x00000000fe640000: allocated 8192 Devices @100440000 (indirect, esz 8, psz 64K, shr 0)
[    0.000000] ITS@0x00000000fe640000: allocated 32768 Interrupt Collections @100450000 (flat, esz 2, psz 64K, shr 0)
[    0.000000] ITS: using cache flushing for cmd queue
[    0.000000] ITS [mem 0xfe660000-0xfe67ffff]
[    0.000000] GIC: enabling workaround for ITS: Rockchip erratum RK3588001
[    0.000000] ITS@0x00000000fe660000: allocated 8192 Devices @100470000 (indirect, esz 8, psz 64K, shr 0)
[    0.000000] ITS@0x00000000fe660000: allocated 32768 Interrupt Collections @100480000 (flat, esz 2, psz 64K, shr 0)
[    0.000000] ITS: using cache flushing for cmd queue
[    0.000000] GICv3: using LPI property table @0x0000000100490000
[    0.000000] GIC: using cache flushing for LPI property table
[    0.000000] GICv3: CPU0: using allocated LPI pending table @0x00000001004a0000
[    0.000000] GICv3: GIC: PPI partition interrupt-partition-0[0] { /cpus/cpu@0[0] /cpus/cpu@100[1] /cpus/cpu@200[2] /cpus/cpu@300[3] }
[    0.000000] GICv3: GIC: PPI partition interrupt-partition-1[1] { /cpus/cpu@400[4] /cpus/cpu@500[5] /cpus/cpu@600[6] /cpus/cpu@700[7] }
[    0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[    0.000000] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    0.000907] Console: colour dummy device 80x25
[    0.000918] printk: legacy console [tty1] enabled
[    0.001692] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[    0.001718] pid_max: default: 32768 minimum: 301
[    0.001793] LSM: initializing lsm=capability,yama,apparmor
[    0.001860] Yama: becoming mindful.
[    0.002067] AppArmor: AppArmor initialized
[    0.002173] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.002222] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.004702] rcu: Hierarchical SRCU implementation.
[    0.004720] rcu:     Max phase no-delay instances is 1000.
[    0.004954] Timer migration: 1 hierarchy levels; 8 children per group; 1 crossnode level
[    0.005667] EFI services will not be available.
[    0.006020] smp: Bringing up secondary CPUs ...
[    0.006582] Detected VIPT I-cache on CPU1
[    0.006640] GICv3: CPU1: found redistributor 100 region 0:0x00000000fe6a0000
[    0.006656] GICv3: CPU1: using allocated LPI pending table @0x00000001004b0000
[    0.006694] CPU1: Booted secondary processor 0x0000000100 [0x412fd050]
[    0.007331] Detected VIPT I-cache on CPU2
[    0.007384] GICv3: CPU2: found redistributor 200 region 0:0x00000000fe6c0000
[    0.007400] GICv3: CPU2: using allocated LPI pending table @0x00000001004c0000
[    0.007436] CPU2: Booted secondary processor 0x0000000200 [0x412fd050]
[    0.008086] Detected VIPT I-cache on CPU3
[    0.008137] GICv3: CPU3: found redistributor 300 region 0:0x00000000fe6e0000
[    0.008152] GICv3: CPU3: using allocated LPI pending table @0x00000001004dreallocated 2048 KiB GFP_KERNEL pool for atomic allocations
[    0.029028] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.029264] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.029287] audit: initializing netlink subsys (disabled)
[    0.029395] audit: type=2000 audit(0.024:1): state=initialized audit_enabled=0 res=1
[    0.029648] thermal_sys: Registered thermal governor 'fair_share'
[    0.029652] thermal_sys: Registered thermal governor 'bang_bang'
[    0.029658] thermal_sys: Registered thermal governor 'step_wise'
[    0.029662] thermal_sys: Registered thermal governor 'user_space'
[    0.029693] cpuidle: using governor menu
[    0.029788] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.029892] ASID allocator initialised with 65536 entries
[    0.029965] Serial: AMBA PL011 UART driver
[    0.035155] /vop@fdd90000: Fixed dependency cycle(s) with /hdmi@fde80000
[    0.035180] /hdmi@fde80000: Fixed dependency cycle(s) with /vop@fdd90000
[    0.037067] /pcie@fe190000: Fixed dependency cycle(s) with /pcie@fe190000/legacy-interrupt-controller
[    0.038925] /i2c@fec80000/usb-typec@22/connector: Fixed dependency cycle(s) with /usb@fc000000
[    0.039307] /i2c@fec80000/usb-typec@22/connector: Fixed dependency cycle(s) with /phy@fed80000
[    0.039332] /usb@fc000000: Fixed dependency cycle(s) with /phy@fed80000
[    0.039354] /phy@fed80000: Fixed dependency cycle(s) with /i2c@fec80000/usb-typec@22/connector
[    0.044261] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    0.044457] rockchip-gpio fd8a0000.gpio: probed /pinctrl/gpio@fd8a0000
[    0.044555] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    0.044659] rockchip-gpio fec20000.gpio: probed /pinctrl/gpio@fec20000
[    0.044739] gpio gpiochip2: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    0.044836] rockchip-gpio fec30000.gpio: probed /pinctrl/gpio@fec30000
[    0.044946] gpio gpiochip3: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    0.045042] rockchip-gpio fec40000.gpio: probed /pinctrl/gpio@fec40000
[    0.045158] gpio gpiochip4: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    0.045251] rockchip-gpio fec50000.gpio: probed /pinctrl/gpio@fec50000
[    0.045929] /hdmi@fde80000: Fixed dependency cycle(s) with /hdmi0-con
[    0.045955] /hdmi0-con: Fixed dependency cycle(s) with /hdmi@fde80000
[    0.046846] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[    0.046854] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[    0.046860] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[    0.046864] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[    0.046869] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[    0.046873] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[    0.046878] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[    0.046882] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[    0.047467] cryptd: max_cpu_qlen set to 1000
[    0.114290] raid6: neonx8   gen()  6673 MB/s
[    0.182377] raid6: neonx4   gen()  6624 MB/s
[    0.250449] raid6: neonx2   gen()  5590 MB/s
[    0.318521] raid6: neonx1   gen()  4434 MB/s
[    0.386598] raid6: int64x8  gen()  2945 MB/s
[    0.454669] raid6: int64x4  gen()  3097 MB/s
[    0.522737] raid6: int64x2  gen()  2585 MB/s
[    0.590817] raid6: int64x1  gen()  2128 MB/s
[    0.590821] raid6: using algorithm neonx8 gen() 6673 MB/s
[    0.658879] raid6: .... xor() 5046 MB/s, rmw enabled
[    0.658884] raid6: using neon recovery algorithm
[    0.659158] iommu: Default domain type: Translated
[    0.659164] iommu: DMA domain TLB invalidation policy: strict mode
[    0.659522] SCSI subsystem initialized
[    0.659701] u   1.340960] pci_bus 0004:40: root bus resource [io  0x0000-0xfffff] (bus address [0xf4100000-0xf41fffff])
[    1.340967] pci_bus 0004:40: root bus resource [mem 0xf4200000-0xf4ffffff]
[    1.340973] pci_bus 0004:40: root bus resource [mem 0xa00000000-0xa3fffffff] (bus address [0x40000000-0x7fffffff])
[    1.340992] pci 0004:40:00.0: [1d87:3588] type 01 class 0x060400 PCIe Root Port
[    1.341008] pci 0004:40:00.0: ROM [mem 0x00000000-0x0000ffff pref]
[    1.341014] pci 0004:40:00.0: PCI bridge to [bus 01-ff]
[    1.341021] pci 0004:40:00.0:   bridge window [io  0x0000-0x0fff]
[    1.341027] pci 0004:40:00.0:   bridge window [mem 0x00000000-0x000fffff]
[    1.341035] pci 0004:40:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[    1.341069] pci 0004:40:00.0: supports D1 D2
[    1.341074] pci 0004:40:00.0: PME# supported from D0 D1 D3hot
[    1.343675] pci 0004:40:00.0: Primary bus is hard wired to 0
[    1.343681] pci 0004:40:00.0: bridge configuration invalid ([bus 01-ff]), reconfiguring
[    1.343768] pci 0004:41:00.0: [1987:5021] type 00 class 0x010802 PCIe Endpoint
[    1.343832] pci 0004:41:00.0: BAR 0 [mem 0x00000000-0x00003fff 64bit]
[    1.344438] pci 0004:41:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0004:40:00.0 (capable of 63.012 Gb/s with 16.0 GT/s PCIe x4 link)
[    1.352802] pci_bus 0004:41: busn_res: [bus 41-4f] end is updated to 41
[    1.352817] pci 0004:40:00.0: bridge window [mem 0xf4200000-0xf42fffff]: assigned
[    1.352824] pci 0004:40:00.0: ROM [mem 0xf4300000-0xf430ffff pref]: assigned
[    1.352831] pci 0004:41:00.0: BAR 0 [mem 0xf4200000-0xf4203fff 64bit]: assigned
[    1.352864] pci 0004:40:00.0: PCI bridge to [bus 41]
[    1.352869] pci 0004:40:00.0:   bridge window [mem 0xf4200000-0xf42fffff]
[    1.352877] pci_bus 0004:40: resource 4 [io  0x0000-0xfffff]
[    1.352882] pci_bus 0004:40: resource 5 [mem 0xf4200000-0xf4ffffff]
[    1.352888] pci_bus 0004:40: resource 6 [mem 0xa00000000-0xa3fffffff]
[    1.352893] pci_bus 0004:41: resource 1 [mem 0xf4200000-0xf42fffff]
[    1.353934] pcieport 0004:40:00.0: PME: Signaling with IRQ 44
[    1.354071] pcieport 0004:40:00.0: AER: enabled with IRQ 45
[    1.355494] dma-pl330 fea10000.dma-controller: Loaded driver for PL330 DMAC-241330
[    1.355503] dma-pl330 fea10000.dma-controller:       DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16
[    1.356061] dma-pl330 fea30000.dma-controller: Loaded driver for PL330 DMAC-241330
[    1.356070] dma-pl330 fea30000.dma-controller:       DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16
[    1.356653] dma-pl330 fed10000.dma-controller: Loaded driver for PL330 DMAC-241330
[    1.356661] dma-pl330 fed10000.dma-controller:       DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16
[    1.357460] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[    1.358636] printk: legacy console [ttyS2] disabled
[    1.358743] feb50000.serial: ttyS2 at MMIO 0xfeb50000 (irq = 52, base_baud = 1500000) is a 16550A
[    1.358836] printk: legacy console [ttyS2] enabled
[    1.528314] Serial: AMBA driver
[    1.532556] loop: module loaded
[    1.533253] Key type psk registered
[    1.534024] nvme nvme0: pci function 0004:41:00.0
[    1.534450] nvme 0004:41:00.0: enabling device (0000 -> 0002)
[    1.534754] /spi@feb20000/pmic@0: Fixed dependency cycle(s) with /spi@feb20000/pmic@0/regulators/dcdc-reg6
[    1.535796] /spi@feb20000/pmic@0: Fixed dependency cycle(s) with /spi@feb20000/pmic@0/regulators/dcdc-reg7
[    1.536659] /spi@feb20000/pmic@0: Fixed dependency cycle(s) with /spi@feb20000/pmic@0/dvs3-null-pins
[    1.537468] /spi@feb20000/pmic@0: Fixed dependency cycle(s) with /spi@feb20000/pmic@0/dvs2-null-pins
[    1.538267] /spi@feb20000/pmic@0: Fixed dependency cycle(s) with /spi@feb20000/pmic@0/dvs1-null-pins
[    1.539124] rockchip-pinctrl pinctrl: pin gpio0-2 already requested by leds; cannot claim forber: xhci-hcd.0.auto
[    1.565087] hub 6-0:1.0: USB hub found
[    1.565425] hub 6-0:1.0: 1 port detected
[    1.565879] usbcore: registered new interface driver usb-storage
[    1.565976] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.12
[    1.567067] mousedev: PS/2 mouse device common for all mice
[    1.567140] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.567740] i2c_dev: i2c /dev entries driver
[    1.568266] usb usb4: Product: EHCI Host Controller
[    1.569097] usb usb4: Manufacturer: Linux 6.12.42-current-rockchip64 ehci_hcd
[    1.569734] usb usb4: SerialNumber: fc880000.usb
[    1.569763] /i2c@fec80000/usb-typec@22/connector: Fixed dependency cycle(s) with /phy@fed80000
[    1.570456] fan53555-regulator 2-0042: FAN53555 Option[10] Rev[1] Detected!
[    1.570660] fan53555-regulator 0-0042: FAN53555 Option[10] Rev[1] Detected!
[    1.570917] /i2c@fec80000/usb-typec@22/connector: Fixed dependency cycle(s) with /usb@fc000000
[    1.571120] fan53555-regulator 0-0043: FAN53555 Option[10] Rev[1] Detected!
[    1.572747] ehci-platform fc800000.usb: USB 2.0 started, EHCI 1.00
[    1.573146] hub 4-0:1.0: USB hub found
[    1.573779] rockchip-thermal fec00000.tsadc: Missing rockchip,grf property
[    1.574054] hub 4-0:1.0: 1 port detected
[    1.574460] hwmon hwmon0: temp1_input not attached to any thermal zone
[    1.575266] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.12
[    1.576023] sdhci: Secure Digital Host Controller Interface driver
[    1.576599] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.577146] sdhci: Copyright(c) Pierre Ossman
[    1.577774] usb usb3: Product: EHCI Host Controller
[    1.578162] Synopsys Designware Multimedia Card Interface Driver
[    1.578579] usb usb3: Manufacturer: Linux 6.12.42-current-rockchip64 ehci_hcd
[    1.578872] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.579107] usb usb3: SerialNumber: fc800000.usb
[    1.579750] arm-scmi arm-scmi.1.auto: Using scmi_smc_transport
[    1.580513] hub 3-0:1.0: USB hub found
[    1.580628] arm-scmi arm-scmi.1.auto: SCMI max-rx-timeout: 30ms
[    1.580639] hub 3-0:1.0: 1 port detected
[    1.581236] scmi_protocol scmi_dev.1: Enabled polling mode TX channel - prot_id:16
[    1.583094] arm-scmi arm-scmi.1.auto: SCMI Notifications - Core Enabled.
[    1.583706] arm-scmi arm-scmi.1.auto: SCMI Protocol v2.0 'rockchip:' Firmware version 0x0
[    1.588723] nvme nvme0: allocated 64 MiB host memory buffer.
[    1.589070] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    1.589871] hid: raw HID events driver (C) Jiri Kosina
[    1.590361] usbcore: registered new interface driver usbhid
[    1.590849] usbhid: USB HID core driver
[    1.591592] rockchip-dfi fe060000.dfi: dfi initialized, dram type: 0x8, channels: 4
[    1.593160] hw perfevents: enabled with armv8_cortex_a55 PMU driver, 7 (0,8000003f) counters available
[    1.594543] hw perfevents: enabled with armv8_cortex_a76 PMU driver, 7 (0,8000003f) counters available
[    1.596479] NET: Registered PF_INET6 protocol family
[    1.604938] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.12
[    1.605698] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.606348] usb usb2: Product: Generic Platform OHCI controller
[    1.606880] usb usb2: Manufacturer: Linux 6.12.42-current-rockchip64 ohci_hcd
[    1.607519] usb usb2: SerialNumber: fc840000.usb
[    1.608405] hub 2-0:1.0: USB hub found
[    1.608811] hub 2-0:1.0: 1 port detected
[    1.609599] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.12
[    1.610342] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.610987] usb usb5: Product: Generic Platform OHCI controller
[    1.611515] usb usb5: Manufacturer: Linux 6.12.42-current-rockchip64
                                                                       [    1.626421] Segment Routing with IPv6
[    1.626780] In-situ OAM (IOAM) with IPv6
[    1.627191] NET: Registered PF_PACKET protocol family
[    1.627644] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    1.628986] 8021q: 802.1Q VLAN Support v1.8
[    1.629386] Key type dns_resolver registered
[    1.632685] registered taskstats version 1
[    1.633251] Loading compiled-in X.509 certificates
[    1.639569] zswap: loaded using pool zstd/zbud
[    1.640116] Demotion targets for Node 0: null
[    1.640682] Key type .fscrypt registered
[    1.641042] Key type fscrypt-provisioning registered
[    1.642293] Btrfs loaded, zoned=yes, fsverity=yes
[    1.642768] Key type encrypted registered
[    1.643123] AppArmor: AppArmor sha256 policy hashing enabled
[    1.658124] WCN: marlin_init entry!
[    1.658579] of_cfs_init
[    1.658808] of_cfs_init: OK
[    1.675629] clk: Disabling unused clocks
[    1.676450] PM: genpd: Disabling unused power domains
[    1.678098] Freeing unused kernel memory: 5312K
[    1.678563] Run /init as init process
[    1.982323] typec_fusb302 6-0022: No cable types defined, using default cables
[    1.988807] rockchip-vop2 fdd90000.vop: Adding to iommu group 0
[    1.989157] rtc-hym8563 6-0051: no valid clock/calendar values available
[    1.989716] rk_gmac-dwmac fe1c0000.ethernet: IRQ eth_lpi not found
[    1.990163] rtc-hym8563 6-0051: registered as rtc0
[    1.990475] rk_gmac-dwmac fe1c0000.ethernet: IRQ sfty not found
[    1.991638] rk_gmac-dwmac fe1c0000.ethernet: supply phy not found, using dummy regulator
[    1.991898] rtc-hym8563 6-0051: no valid clock/calendar values available
[    1.992456] rk_gmac-dwmac fe1c0000.ethernet: clock input or output? (output).
[    1.992972] rtc-hym8563 6-0051: hctosys: unable to read the hardware clock
[    1.993282] rockchip-drm display-subsystem: bound fdd90000.vop (ops vop2_component_ops [rockchipdrm])
[    1.993616] rk_gmac-dwmac fe1c0000.ethernet: TX delay(0x42).
[    1.994838] dwhdmiqp-rockchip fde80000.hdmi: registered DesignWare HDMI QP I2C bus driver
[    1.995054] rk_gmac-dwmac fe1c0000.ethernet: Can not read property: rx_delay.
[    1.995529] rockchip-drm display-subsystem: bound fde80000.hdmi (ops dw_hdmi_qp_rockchip_ops [rockchipdrm])
[    1.996240] rk_gmac-dwmac fe1c0000.ethernet: set rx_delay to 0x10
[    1.997160] [drm] Initialized rockchip 1.0.0 for display-subsystem on minor 0
[    1.997742] rk_gmac-dwmac fe1c0000.ethernet: integrated PHY? (no).
[    2.004473] rk_gmac-dwmac fe1c0000.ethernet: init for RGMII_RXID
[    2.005264] rk_gmac-dwmac fe1c0000.ethernet: User ID: 0x30, Synopsys ID: 0x51
[    2.005911] rk_gmac-dwmac fe1c0000.ethernet:         DWMAC4/5
[    2.006373] rk_gmac-dwmac fe1c0000.ethernet: DMA HW capability register supported
[    2.006470] xhci-hcd xhci-hcd.3.auto: xHCI Host Controller
[    2.007037] rk_gmac-dwmac fe1c0000.ethernet: RX Checksum Offload Engine supported
[    2.007522] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 7
[    2.007530] rk_gmac-dwmac fe1c0000.ethernet: TX Checksum insertion supported
[    2.008270] xhci-hcd xhci-hcd.3.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000808002000010
[    2.008896] rk_gmac-dwmac fe1c0000.ethernet: Wake-Up On Lan supported
[    2.009543] xhci-hcd xhci-hcd.3.auto: irq 88, io mem 0xfc000000
[    2.010400] rk_gmac-dwmac fe1c0000.ethernet: TSO supported
[    2.010958] xhci-hcd xhci-hcd.3.auto: xHCI Host Controller
[    2.011423] rk_gmac-dwmac fe1c0000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    2.011904] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 8
[    2.011917] rk_gmac-dwmac fe1c0000.ethernet: Enabled L3L4 Flow TC (entries=2)
[    2.012395] xhci-hcd xhci-hcd.3.auto: Host supports USB 3.0 SuperSpeed
[    2.012406] rk_gmac-dwmac fe1c0000.ethernet: Enabled RFS Flow TC (entries=10)
[    2.013153] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.12
[    2.013794] rk_gmac-dwmac fe1c0000.ethernet: TSO feature enabled
[    2.014416] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.014427] rk_gmac-dwmac fe1c0000.ethernet: SPH feature enabled
[    2.014995] usb usb7: Product: xHCI Host Controller
[    2.015007] rk_gmac-dwmac fe1c0000.ethernet: Using 32/32 bits DMA host/device width
[    2.015626] usb usb7: Manufacturer: Linux 6.12.42-current-rockchip64 xhci-hcd
[    2.019731] usb usb7: SerialNumber: xhci-hcd.3.auto
[    2.020451] hub 7-0:1.0: USB hub found
[    2.020799] hub 7-0:1.0: 1 port detected
[    2.159805] Console: switching to colour frame buffer device 160x45
[    2.175587] rk_gmac-dwmac fe1c0000.ethernet end0: renamed from eth0
[    2.196355] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device
[    2.213113] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.213953] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.12
[    2.214762] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.215469] usb usb8: Product: xHCI Host Controller
[    2.215948] usb usb8: Manufacturer: Linux 6.12.42-current-rockchip64 xhci-hcd
[    2.216645] usb usb8: SerialNumber: xhci-hcd.3.auto
[    2.217493] hub 8-0:1.0: USB hub found
[    2.217879] hub 8-0:1.0: 1 port detected
[    2.219226] typec_fusb302 6-0022: No cable types defined, using default cables
[   12.258507] typec_fusb302 6-0022: No cable types defined, using default cables
[   12.271017] platform adc-keys: deferred probe pending: platform: supplier fec10000.adc not ready
[   12.279203] platform fec10000.adc: deferred probe pending: platform: wait for supplier /spi@feb20000/pmic@0/regulators/pldo-reg1
[   12.287827] platform vcc-3v3-sd-s0-regulator: deferred probe pending: platform: wait for supplier /spi@feb20000/pmic@0/regulators/dcdc-reg8
[   12.296656] i2c 6-0022: deferred probe pending: typec_fusb302: cannot register tcpm port
[   12.305122] platform fe2c0000.mmc: deferred probe pending: platform: wait for supplier /spi@feb20000/pmic@0/regulators/pldo-reg5
[   18.708830] random: crng init done

Quote

Linux orangepi5 6.16.4-edge-rockchip64 #1 SMP PREEMPT Thu Aug 28 14:34:51 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux

I had to encode lately some video files and I discovered that video encoding hardware acceleration seems to be broken.

gart@orangepi5:~$ uname -a 
Linux orangepi5 6.1.115-vendor-rk35xx #1 SMP Tue Jun  3 13:10:51 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux
 

gart@orangepi5:~$ sudo dmesg | grep mpp_rkvenc
[   12.705174] mpp_rkvenc2 rkvenc-ccu: probing start
[   12.705179] mpp_rkvenc2 rkvenc-ccu: probing finish
[   13.267729] mpp_rkvenc2 fdbd0000.rkvenc-core: Adding to iommu group 10
[   13.267963] mpp_rkvenc2 fdbd0000.rkvenc-core: probing start
[   13.268179] mpp_rkvenc2 fdbd0000.rkvenc-core: Looking up venc-supply from device tree
[   13.268187] mpp_rkvenc2 fdbd0000.rkvenc-core: Looking up venc-supply property in node /rkvenc-core@fdbd0000 failed
[   13.268207] mpp_rkvenc2 fdbd0000.rkvenc-core: rockchip_init_read_margin: no regulator (venc) found: -19
[   13.268214] mpp_rkvenc2 fdbd0000.rkvenc-core: bin=0
[   13.268293] mpp_rkvenc2 fdbd0000.rkvenc-core: Failed to get leakage
[   13.268342] mpp_rkvenc2 fdbd0000.rkvenc-core: Looking up venc-supply from device tree
[   13.268350] mpp_rkvenc2 fdbd0000.rkvenc-core: Looking up venc-supply property in node /rkvenc-core@fdbd0000 failed
[   13.268367] mpp_rkvenc2 fdbd0000.rkvenc-core: error -ENODEV: _opp_set_regulators: no regulator (venc) found
[   13.268395] mpp_rkvenc2 fdbd0000.rkvenc-core: failed to set opp config
[   13.268401] mpp_rkvenc2 fdbd0000.rkvenc-core: failed to init opp info
[   13.268406] mpp_rkvenc2 fdbd0000.rkvenc-core: failed to init_opp_table
[   13.268453] mpp_rkvenc2 fdbd0000.rkvenc-core: attach ccu as core 0
[   13.268489] mpp_rkvenc2 fdbd0000.rkvenc-core: probing finish
[   13.268700] mpp_rkvenc2 fdbe0000.rkvenc-core: Adding to iommu group 11
[   13.268940] mpp_rkvenc2 fdbe0000.rkvenc-core: probing start
[   13.269126] mpp_rkvenc2 fdbe0000.rkvenc-core: Looking up venc-supply from device tree
[   13.269135] mpp_rkvenc2 fdbe0000.rkvenc-core: Looking up venc-supply property in node /rkvenc-core@fdbe0000 failed
[   13.269152] mpp_rkvenc2 fdbe0000.rkvenc-core: rockchip_init_read_margin: no regulator (venc) found: -19
[   13.269159] mpp_rkvenc2 fdbe0000.rkvenc-core: bin=0
[   13.269199] mpp_rkvenc2 fdbe0000.rkvenc-core: Failed to get leakage
[   13.269231] mpp_rkvenc2 fdbe0000.rkvenc-core: Looking up venc-supply from device tree
[   13.269238] mpp_rkvenc2 fdbe0000.rkvenc-core: Looking up venc-supply property in node /rkvenc-core@fdbe0000 failed
[   13.269253] mpp_rkvenc2 fdbe0000.rkvenc-core: error -ENODEV: _opp_set_regulators: no regulator (venc) found
[   13.269272] mpp_rkvenc2 fdbe0000.rkvenc-core: failed to set opp config
[   13.269278] mpp_rkvenc2 fdbe0000.rkvenc-core: failed to init opp info
[   13.269283] mpp_rkvenc2 fdbe0000.rkvenc-core: failed to init_opp_table
[   13.269345] mpp_rkvenc2 fdbe0000.rkvenc-core: attach ccu as core 1
[   13.269379] mpp_rkvenc2 fdbe0000.rkvenc-core: probing finish
 

When I try to encode my files are fucked up and I have this in log :

gart@orangepi5:~$ sudo cat /var/log/syslog 

025-07-04T19:38:45.309928+02:00 orangepi5 mpp[3513]: mpp_serivce: mpp_service_ioc_attach_fd failed ret -1 errno 22 Invalid argument
2025-07-04T19:38:45.311485+02:00 orangepi5 kernel: rk_vcodec: mpp_process_request:1434: can not import fd 127
2025-07-04T19:38:45.311503+02:00 orangepi5 kernel: rk_vcodec: mpp_collect_msgs:1622: session 1 process cmd 401 ret -22
2025-07-04T19:38:45.311504+02:00 orangepi5 kernel: rk_vcodec: mpp_dev_ioctl:1732: collect msgs failed -22
2025-07-04T19:38:45.311505+02:00 orangepi5 kernel: rk_vcodec: mpp_task_attach_fd:1841: can't import dma-buf 271
2025-07-04T19:38:45.311506+02:00 orangepi5 kernel: rk_vcodec: mpp_translate_reg_address:1897: reg[  0]: 0x0000010f fd 271 failed
2025-07-04T19:38:45.311507+02:00 orangepi5 kernel: rk_vcodec: mpp_task_dump_mem_region:2084: --- dump task 0 mem region ---
2025-07-04T19:38:45.311508+02:00 orangepi5 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: no memory region mapped
2025-07-04T19:38:45.311509+02:00 orangepi5 kernel: rk_vcodec: mpp_process_task_default:589: alloc_task failed.
2025-07-04T19:38:45.311510+02:00 orangepi5 kernel: rk_vcodec: mpp_process_request:1434: can not import fd 128
2025-07-04T19:38:45.311511+02:00 orangepi5 kernel: rk_vcodec: mpp_collect_msgs:1622: session 1 process cmd 401 ret -22
2025-07-04T19:38:45.311512+02:00 orangepi5 kernel: rk_vcodec: mpp_dev_ioctl:1732: collect msgs failed -22
2025-07-04T19:38:45.311513+02:00 orangepi5 kernel: rk_vcodec: mpp_task_attach_fd:1841: can't import dma-buf 273
2025-07-04T19:38:45.311515+02:00 orangepi5 kernel: rk_vcodec: mpp_translate_reg_address:1897: reg[  0]: 0x00000111 fd 273 failed
2025-07-04T19:38:45.311516+02:00 orangepi5 kernel: rk_vcodec: mpp_task_dump_mem_region:2084: --- dump task 0 mem region ---
2025-07-04T19:38:45.311517+02:00 orangepi5 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: no memory region mapped
2025-07-04T19:38:45.311518+02:00 orangepi5 kernel: rk_vcodec: mpp_process_task_default:589: alloc_task failed.
2025-07-04T19:38:45.311520+02:00 orangepi5 kernel: rkvenc2_wait_result:2340: session 0000000017eca1cc pending list is empty!
2025-07-04T19:38:45.311520+02:00 orangepi5 kernel: rk_vcodec: mpp_msgs_wait:1693: session 1 wait result ret -5
2025-07-04T19:38:45.311521+02:00 orangepi5 kernel: rkvenc2_wait_result:2340: session 0000000017eca1cc pending list is empty!
2025-07-04T19:38:45.311523+02:00 orangepi5 kernel: rk_vcodec: mpp_msgs_wait:1693: session 1 wait result ret -5
2025-07-04T19:38:45.351471+02:00 orangepi5 kernel: rk_vcodec: mpp_process_request:1434: can not import fd 133
2025-07-04T19:38:45.351492+02:00 orangepi5 kernel: rk_vcodec: mpp_collect_msgs:1622: session 1 process cmd 401 ret -22
2025-07-04T19:38:45.351494+02:00 orangepi5 kernel: rk_vcodec: mpp_dev_ioctl:1732: collect msgs failed -22
2025-07-04T19:38:45.351495+02:00 orangepi5 kernel: rk_vcodec: mpp_task_attach_fd:1841: can't import dma-buf 274
2025-07-04T19:38:45.351495+02:00 orangepi5 kernel: rk_vcodec: mpp_translate_reg_address:1897: reg[  0]: 0x00000112 fd 274 failed
2025-07-04T19:38:45.351497+02:00 orangepi5 kernel: rk_vcodec: mpp_task_dump_mem_region:2084: --- dump task 0 mem region ---
2025-07-04T19:38:45.351498+02:00 orangepi5 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: no memory region mapped
2025-07-04T19:38:45.351499+02:00 orangepi5 kernel: rk_vcodec: mpp_process_task_default:589: alloc_task failed.
2025-07-04T19:38:45.351500+02:00 orangepi5 kernel: rkvenc2_wait_result:2340: session 0000000017eca1cc pending list is empty!
2025-07-04T19:38:45.351501+02:00 orangepi5 kernel: rk_vcodec: mpp_msgs_wait:1693: session 1 wait result ret -5
2025-07-04T19:38:45.351502+02:00 orangepi5 kernel: rk_vcodec: mpp_process_request:1434: can not import fd 130
2025-07-04T19:38:45.351503+02:00 orangepi5 kernel: rk_vcodec: mpp_collect_msgs:1622: session 1 process cmd 401 ret -22
2025-07-04T19:38:45.351504+02:00 orangepi5 kernel: rk_vcodec: mpp_dev_ioctl:1732: collect msgs failed -22
2025-07-04T19:38:45.354822+02:00 orangepi5 kernel: rk_vcodec: mpp_task_attach_fd:1841: can't import dma-buf 270
2025-07-04T19:38:45.354845+02:00 orangepi5 kernel: rk_vcodec: mpp_translate_reg_address:1897: reg[  0]: 0x0000010e fd 270 failed
 

does anybody else has this behaviour ?

I'm sure to have use rkmpp encoding with ffmpeg before (a long time ago) probably before kernel 6.1, and that was working.

In my opinion, it's an issue with vendor kernel.

Let me know.

Regard

It works so well that I put my big desktop tower away and have been getting by strictly on this Armbian Gnome environment.  I will be donating to Armbian soon

However, I am curious, does anybody know how to fix the resume from suspend?

For me, the computer goes into suspend mode just fine, but when I tap a keyboard key, the LED's will light on the keyboard indicating they have power, but the system never comes back. 

If I press the power button on the Orange Pi 5 itself, the system resumes perfectly -- no crashes, everything works as intended

I just need it to work from a keyboard press instead!

Thanks!

I've tried everything I can think of - ensuring nothing is downloaded from Flatpak and therefore sandboxed and preventing any connectivity issues.

But still not working.

If someone can take 5 mins and create a free trial account on 1password, then here are the steps to reproduce:

Download the latest arm64 version of 1password Desktop:
 

curl -sSO https://downloads.1password.com/linux/tar/stable/aarch64/1password-latest.tar.gz

Extract and move the files:

sudo tar -xf 1password-latest.tar.gz
sudo mkdir -p /opt/1Password
sudo mv 1password-*/* /opt/1Password

Run the post-installation script, and launch 1password

sudo /opt/1Password/after-install.sh

1password

Everything is all good, and working.  I log in to my vault, as intended, and the app is fully unlocked.
Settings already default to synchronization being enabled, but just for the sake of double checking:


So we are all set on the desktop side.


Now, for the browsers.  I have checked this with both Firefox, and Chromium extensively -- all various kinds of versions, ensuring no Flatpak or anything like that.
We install the browser plugin: https://1password.com/downloads/browser-extension

And click on your corresponding browser, and enable the extension/plugin.

At this point -- and I have done this hundreds of times across all of my other devices and installations -- there SHOULD be nothing to do in the extension as far as entering a username and password goes.  It's supposed to detect the local socket and interface with the desktop application, meaning once you are authenticated on the Desktop app, your browser plugin will unlock.  The most you'd have to do is click through the 1st-time-launch welcome message and skip the tutorial, but NOT authenticating needed.

And sadly, this is where obviously, it doesn't work.  We are instead prompted for our username and password and the extension shows a lock symbol which is totally incorrect.
We right click the extension in Chrome and pick Settings, to figure out what the heck is going on:

And are met, with the dreaded, connection problem and yellow light.  Instead of all systems go and the GREEN light, as it is supposed to be:



I've pretty much exhausted the amount of testing I can possibly do, I'm just a novice user personally

Any help would be greatly appreciated, I'd even make a donation if someone can crack this nut, as it's a pretty glaring (for me) missing feature that I've grown accustomed to across every other device I own, and it does typically work very well, on any other OS..  I run it on Linux Mint, PopOS, Debian, Windows, all kinds of stuff never a problem

I am able to report back with any further information requests or diagnostics etc. and already plan to forward this link to 1password support as well

Thanks in advance for any help!

Hardware:
Orangepi5
SSD1306 OLED display

Software
Armbian Jammy KDE Neon 6.1.43
Files attached in ZIP archive
device.py

PixelOperator.ttf
setup.py
stats.py

How to:

1) add overlay

wget https://raw.githubusercontent.com/orangepi-xunlong/linux-orangepi/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/overlay/rk3588-i2c5-m3.dts

sudo armbian-add-overlay rk3588-i2c5-m3.dts

reboot

2) connect OLED display to I2C5 M3 Pins SDA + SCL (pins 1(VCC),2(SDA),3(SCL) and 5(GND))
check connection

sudo i2cdetect -y 5

must be detected 3c value

3) install needed libs
 

sudo apt-get install i2c-tools python3-smbus python3-pip python3-dev python3-pil

4) download main karabek project

git clone https://github.com/karabek/OrangePi-OLED

cd OrangePi-OLED

rename old setup.py

mv setup.py setup_old.py

4) create new setup.py or copy from ZIP archive

nano setup.py

#!/usr/bin/env python

from setuptools import setup

setup(
    name="ssd1306",
    version="0.1.0",
    author="Richard Hull",
    author_email="richard.hull@destructuring-bind.org",
    description="A small library to drive an OLED device with either SSD1306 or SH1106 chipset",
    license="MIT",
    keywords="raspberry pi rpi oled ssd1306 sh1106",
    url="https://github.com/rm-hull/ssd1306",
    packages=['oled'],
)

5) Start setup.py

sudo python3 setup.py sdist

6) copy generated folders to python3 dist packages
 

sudo cp -r OrangePi-OLED/oled/ /usr/local/lib/python3.10/dist-packages/

sudo cp -r OrangePi-OLED/ssd1306.egg-info/ /usr/local/lib/python3.10/dist-packages/

7) replace device.py file with file in ZIP archive in dist-packages oled folder

cd /usr/local/lib/python3.10/dist-packages/oled

mv device.py device_old.py

9) copy stats.py and font file PixelOperator.ttf from ZIP archive

start stats.py file

sudo python3 stats.py

result should be same as on RPI device
picture


 

Orangepi5_OLED.zip

HOWEVER the one big thing I noticed right away - my screen never turns off anymore

And my Power options are missing such settings?  It only gives the option to blank, which still is running my monitor at 100% brightness and a horrible solution



Where is the setting to turn my screen off after 5 minutes?  NOT blank, but into standby mode

Worked on the previous Cinnamon version but that version lacked higher refresh rates and I think was not wayland

Thank you!

I use my Orange Pi 5 board to run Open Media Vault with Wireguard installed. But there is a known issue with Wireguard that, when installing it, you have to manually reinstall the correct kernel into the board again, otherwise it won't be able to boot. 

However, ever since it has been installed, during apt update / apt ugrade of my board, it keeps recognizing the wrong kernel to be updated and changing the symlinks inside the /boot/ folder, rendering the board unbootable. If I see this happening, I can change the symlinks and it works normally after that. However, sometimes the symlinks changes unnoticed and I cannot boot anymore. I have to take the SD Card to another device, chroot into it, and change the links again.

How can I prevent this from happening again and let the updates recognize the correct kernel version?

In the image attached, you can see that uInitrd is pointing to uInitrd-6.11.5+bpo-arm64-16k, which is incorrect. I have to manually point it to uInitrd-6.1.99-vendor-rk35xx

Sometimes, dtb and Image point to the wrong files as well. I have tried holding back linux-image-arm64-16k from being updated with apt hold, and I have also turned off automatic kernel updates inside armbian-config, but there is still something more to be done.

I have just run apt update / apt upgrade, and I think that the part that is breaking my boot is the Processing triggers for initramfs-tools, as can be seen logged below:

Setting up linux-u-boot-orangepi5-vendor (25.5.1) ...
Armbian 'uboot-orangepi5-vendor' for '2017.09-S3e40-P187d-H0b1f-V023f-Bb703-R448a': 'postinst' starting.
Armbian 'uboot-orangepi5-vendor' for '2017.09-S3e40-P187d-H0b1f-V023f-Bb703-R448a': 'postinst' finishing.
Setting up systemd-sysv (252.38-1~deb12u1) ...
Setting up libicu72:arm64 (72.1-3+deb12u1) ...
Setting up linux-dtb-vendor-rk35xx (25.5.1) ...
Armbian 'linux-dtb-vendor-rk35xx' for '6.1.115-vendor-rk35xx': 'postinst' starting.
Armbian: DTB: symlinking /boot/dtb to /boot/dtb-6.1.115-vendor-rk35xx...
'dtb' -> 'dtb-6.1.115-vendor-rk35xx'
Armbian 'linux-dtb-vendor-rk35xx' for '6.1.115-vendor-rk35xx': 'postinst' finishing.
Setting up armbian-firmware-full (25.5.1) ...
Setting up python3-ruamel.yaml.clib:arm64 (0.2.7-1+b2) ...
Setting up libnss-systemd:arm64 (252.38-1~deb12u1) ...
Setting up linux-image-vendor-rk35xx (25.5.1) ...
Armbian 'linux-image-vendor-rk35xx' for '6.1.115-vendor-rk35xx': 'postinst' starting.
update-initramfs: Generating /boot/initrd.img-6.1.115-vendor-rk35xx
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.115-vendor-rk35xx
Image Name:   uInitrd
Created:      Sun Jul 20 10:39:28 2025
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    13880399 Bytes = 13555.08 KiB = 13.24 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.115-vendor-rk35xx to /boot/uInitrd
'/boot/uInitrd' -> 'uInitrd-6.1.115-vendor-rk35xx'
update-initramfs: Armbian: done.
Remove unused generated file: /boot/uInitrd-6.1.99-vendor-rk35xx
Remove unused generated file: /boot/initrd.img-6.1.99-vendor-rk35xx
Armbian: update last-installed kernel symlink to 'Image'...
'/boot/Image' -> 'vmlinuz-6.1.115-vendor-rk35xx'
Armbian: Debian compat: linux-update-symlinks install 6.1.115-vendor-rk35xx boot/vmlinuz-6.1.115-vendor-rk35xx
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.115-vendor-rk35xx
I: /initrd.img is now a symlink to boot/initrd.img-6.1.115-vendor-rk35xx
Armbian 'linux-image-vendor-rk35xx' for '6.1.115-vendor-rk35xx': 'postinst' finishing.
Setting up linux-headers-vendor-rk35xx (25.5.1) ...
Armbian 'linux-headers-vendor-rk35xx' for '6.1.115-vendor-rk35xx': 'postinst' starting.
Configuring kernel-headers (6.1.115-vendor-rk35xx) - 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.1.115-vendor-rk35xx) 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/resource_tool
  HOSTCC  scripts/kallsyms
  HOSTCC  scripts/sorttable
  HOSTCC  scripts/asn1_compiler
  HOSTCC  scripts/genksyms/genksyms.o
  YACC    scripts/genksyms/parse.tab.[ch]
  HOSTCC  scripts/selinux/genheaders/genheaders
  HOSTCC  scripts/selinux/mdp/mdp
  LEX     scripts/genksyms/lex.lex.c
  HOSTCC  scripts/genksyms/parse.tab.o
  HOSTCC  scripts/genksyms/lex.lex.o
  HOSTLD  scripts/genksyms/genksyms
Compiling kernel-headers scripts/mod (6.1.115-vendor-rk35xx) using 8 CPUs - please wait ...
  CC      scripts/mod/empty.o
  HOSTCC  scripts/mod/mk_elfconfig
  CC      scripts/mod/devicetable-offsets.s
  MKELF   scripts/mod/elfconfig.h
  HOSTCC  scripts/mod/modpost.o
  HOSTCC  scripts/mod/sumversion.o
  UPD     scripts/mod/devicetable-offsets.h
  HOSTCC  scripts/mod/file2alias.o
  HOSTLD  scripts/mod/modpost
  MODPOST scripts/mod/Module.symvers
Done compiling kernel-headers (6.1.115-vendor-rk35xx).
Done compiling kernel-headers tools (6.1.115-vendor-rk35xx).
Armbian 'linux-headers-vendor-rk35xx' for '6.1.115-vendor-rk35xx': 'postinst' finishing.
Setting up armbian-bsp-cli-orangepi5-vendor (25.5.1) ...
Armbian 'armbian-bsp-cli-orangepi5-vendor' for '1-PC5315-V4064-H21c6-B1e5d-R756d': 'postinst' starting.
Armbian 'armbian-bsp-cli-orangepi5-vendor' for '1-PC5315-V4064-H21c6-B1e5d-R756d': 'postinst' finishing.


(...)

Processing system modifications ...
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.11.5+bpo-arm64-16k
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.11.5+bpo-arm64-16k
Image Name:   uInitrd
Created:      Sun Jul 20 10:43:32 2025
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    54963626 Bytes = 53675.42 KiB = 52.42 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.11.5+bpo-arm64-16k to /boot/uInitrd
'/boot/uInitrd' -> 'uInitrd-6.11.5+bpo-arm64-16k'
update-initramfs: Armbian: done.

Any help appreciated. Thank you all

So after seemingly not being to identify the problem, I started again, wrote the image to an SD card and then moved the installation to the NVME drive using armbian-config utility.

So now that I have a set-up that works again, I want to instigate a more belt and braces approach and create an image of the NVME installation using GZIP to compress the image file and decided to use the DD option from terminal.

Having tried well over a hundred different combinations of commands, I am unable to get things to work.

I either get errors of Not a directory, No such file or directory or Is a directory

The output of lsblk is

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
mtdblock0    31:0    0    16M  0 disk 
mmcblk1     179:0    0  59.5G  0 disk 
└─mmcblk1p1 179:1    0  59.5G  0 part 
zram0       252:0    0   3.9G  0 disk [SWAP]
zram1       252:1    0    50M  0 disk /var/log
zram2       252:2    0     0B  0 disk 
nvme0n1     259:0    0 238.5G  0 disk 
└─nvme0n1p1 259:1    0 238.5G  0 part /var/log.hdd

So in order to create the copy of the NVME installation, that is only taking up 13gb of the 238Gb total, to the root of a 64Gb SD card, completely empty and formatted to EXT4 via gparted, using the information above, can anybody see where I am going wrong.

A few typical examples of command structures that I have tried are:

sudo dd if=/dev/nvme0n1 of=/dev/mmcblk1/armbian.gz conv=sync bs=64K | gzip --stdout > bs=4M status=progress

dd if=/dev/nvme0n1 conv=sync bs=64K | gzip --stdout > of=/dev/mmcblk1/armbian.gz

dd if=/dev/nvme0n1p1 conv=sync bs=64K | gzip --stdout > of=/dev/mmcblk1p1/armbian.gz bs=4M status=progress

This is the general template that I initially followed from a website

dd if=/dev/SOURCE conv=sync bs=64K | gzip --stdout > /path/to/file.gz

I've researched the use of the DD command until I am cross eyed.

But then I turned it on and at the screen where you get the Amrbian grey/red logo in the middle of the screen and the spinning circle, it went no further. The spinning circle would either stop rotating or disappear after a minute or so.

I can SSH into the device.

But when I use remote desktop from a Windows PC, the full and functioning desktop is there. It's just not on my TV screen any more.

I've done the usual HDMI cable testing and powering off the TV completely, but no change.

The fact that the desktop is accessible remotely does indicate that it must be loading in some fashion.

Took a log here: https://paste.next.armbian.com/qococumoga

The i2c also seems to be missing. Is going back to 6.1 the safest option?

Thanks

for more details but without using the overlay-user folder - I was not able to get the pwm to work on a fresh download.

root@opi5 /home/pi# ethtool end0
Settings for end0:
	Supported ports: [ TP	 MII ]
	Supported link modes:   10baseT/Full
	                        100baseT/Full
	                        1000baseT/Full
	Supported pause frame use: Symmetric Receive-only
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Full
	                        100baseT/Full
	                        1000baseT/Full
	Advertised pause frame use: Symmetric Receive-only
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Link partner advertised link modes:  10baseT/Half 10baseT/Full
	                                     100baseT/Half 100baseT/Full
	Link partner advertised pause frame use: Symmetric Receive-only
	Link partner advertised auto-negotiation: Yes
	Link partner advertised FEC modes: Not reported
	Speed: 100Mb/s
	Duplex: Full
	Auto-negotiation: on
	master-slave cfg: preferred slave
	master-slave status: slave
	Port: Twisted Pair
	PHYAD: 1
	Transceiver: external
	MDI-X: Unknown
	Supports Wake-on: ug
	Wake-on: d
        Current message level: 0x0000003f (63)
                               drv probe link timer ifdown ifup
	Link detected: yes

It uses the ap6275p chip. The guide will be split into 2 sections depending on what OS you want to use

Orange Pi OS

1. install the wifi module into the m.2 slot and boot sd card with either the latest orange pi os ubuntu or debian

http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-pi-5.html

2. edit the boot file to enable wifi by adding overlays=wifi-ap6275p to the end. Note if you already have overlays=<anything> line such as ssd-sata, delete it so it only says overlays=wifi-ap6275p

sudo nano /boot/orangepiEnv.txt

overlays=wifi-ap6275p

Save and reboot

3. now you can search for you wifi and connect

nmtui-connect

Armbian OS

Preface, for Armbian OS this is currently only working with the nightly build which can be found here https://github.com/armbian/build/releases/

I repeat, this will not work with the stable build of Armbian here https://www.armbian.com/orangepi-5/ as it is missing drivers but you can upgrade your stable build to nightly build

1. You first need to obtain the .dtbo file from the latest orangepi5.img, I would download the smallest img which is debian_bullseye_server 

http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-pi-5.html

2. use 7zip to first extract the Orangepi5*.img then open that .img file in 7zip further which will show 2 files named 0.bootfs.img and 1.rootfs.img

3. Go into the folder /0.bootfs.img/dtb/rockchip/overlay/ and at the end grab the file rk3588-wifi-ap6275p.dtbo

4. rename the file to rockchip-rk3588-wifi-ap6275p.dtbo and copy it to the /boot/dtb/rockchip/overlay/ directory on your orange pi

sudo cp /path/to/rk3588-wifi-ap6275p.dtbo /boot/dtb/rockchip/overlay/rockchip-rk3588-wifi-ap6275p.dtbo

5. edit the boot file to enable wifi by adding overlays=wifi-ap6275p to the end. Note if you already have overlays=<anything> line such as ssd-sata, delete it so it only says overlays=wifi-ap6275p

sudo nano /boot/armbianEnv.txt

overlays=wifi-ap6275p

Save and reboot

6. now you can search for you wifi and connect

nmtui-connect

Is it possible to enable OV13855 camera on OPi5 with the latest armbian image? If yes, how do it?

Thanks!

Everything went smoothly, and I have a 512GB ssd on the board, so I went through the install process using armbian-install. I managed to get the OS installed on the SSD, but when I went to install the bootloader, I got some error messages saying that the SPI image was not chosen. I followed the process for erasing the MTD, but still I got error messages relating to no spi image. I tried to boot from the ssd and just got a black screen.

I downloaded Joshua Riek’s Ubuntu 24.04 distro and booted it from the sd card and ran his command “sudo u-boot-install-mtd”.  It installed to the MTD and then I shut down and removed the sd card and booted up. Armbian has now booted from the SSD with no issues. 

I couldn’t find anything on the forum so I thought I would post this to assist anyone else who has this issue. If the guys at Armbian have any thoughts on why this may have happened please let me know.

https://github.com/Bleach665/Mali610Vulkan

Can't confirm.

KERNELBRANCH="tag:v6.15-rc3"
But that's not working.

Would anyone be able to tell me the file I need to edit for an OrangePi 5?

Update: I actually seem to have it try by editing
config/sources/families/rockchip-rk3588.conf
changing the version tag. But I get a bunch of red errors complaining about SHA1.

Quote

Failed to fetch SHA1 of 'tag' 'refs/heads/v6.15-rc3^{}' [ https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git ]

hmm...an 'rc3' is probably not to be found in a tree with 'stable' in it.


Cheers!
Fred

Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062
Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062
Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062
Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062
Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062

this seems an old issue  (Kernel messages flooding logs · Issue #86 · Joshua-Riek/ubuntu-rockchip) - it doesn't seem complicated to fix, I am familiar with the build system but I cannot figure out how I can create a patch for the kernel source.

Which repo should I patch? Can I just put my patch into build/patch/kernel/rk35xx-vendor-6.1?

Thanks

The monitor is part of the Motorola HD Dock.  I'm using it for it's keyboard and monitor.  In any case, the following messages appear in DMESG and keeps repeating ever second or two:

[522074.762209] vop2_isr: 107217 callbacks suppressed
[522074.762239] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0
[522074.762321] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0
[522074.762359] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0
[522074.762400] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0
[522074.762441] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0
[522074.762483] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0
[522074.762525] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0
[522074.762566] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0
[522074.762608] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0
[522074.762650] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0

I left the dock attached.  Went back later to check and it's still doing it.  Is there any way to stop this or filter it out?

Thanks.

I am not sure if the files are copied over correctly, since the ~6GB image on the SD card is copied as 2.9GB on the btrfs partition, but there are no errors occuring as far as I can see. The bootloader is up-to-date, and I can access the btrfs drive when booted from the SD card, so the kernel supports btrfs I guess?

However, I think there are some things going "wrong", since the armbianEnv.txt file on the nvme SSD has ext4 instead of btrfs as the rootfs? This is basically my first install of armbian so I don't know that much about the installation procedure, but I just followed the official guide (which is also somehow out of date afaik, the images seem wrong...)

(Additionally, apt update + upgrade don't work right now, erroring out with "Mirror sync in progress", so I don't know if this failure is happening because of out of date packages...)

I'm getting ready to wrap up for the night, but I recently purchased an Orange Pi 5 (non-B) to do some tinkering with. I downloaded the Bookworm XFCE variant as I am somewhat familiar with XFCE already.

Anyway, upon initial testing, I thought my power supply wasn't good enough for the board. I wasn't getting any HDMI output.

When I removed the micro-SD card and tried to boot it that way, an orange pi splash screen would show on the attached display, so I think the port actually works (?)

I have a spare USB to TTL Serial adapter so I was able to verify the board was successfully booting into Armbian, but xrandr didn't show any connections.

I tried a USB-C to HDMI cable that I had handy, and that actually worked. I then stumbled across a forum thread on a similar issue with someone's Orange Pi 5B, and a comment said they fixed it by enabling the HDMI port in armbian-config. I tried that and it still didn't work.

I also noticed a few debug messages that would come over the UART interface, something with an error -22. I'll try to replicate it tomorrow and add a comment with the exact error. I don't have it handy, but googling the text didn't really help.

Anyway, like I mentioned earlier, I'm wrapping it up for the night so I'll try any suggestions tomorrow after my college classes.

Any insights are appreciated.

What is happening?

G

I want to work with g_audio drivers on the usb type c otg port.

When I build the image with current kernel, by applying the following overlay (I only change dr_mode to peripheral)  i am able to convert the usb port in peripheral mode and successfully load the g_audio drivers and audio interfaces also come up.

/dts-v1/;
/plugin/;

/ {
    compatible = "rockchip,rk3588s";

    fragment@0 {
        target = <&usb_host0_xhci>;  // This matches the label in the device tree

        __overlay__ {
            dr_mode = "peripheral";
        };
    };
};

But when i want to do similar with the vendor kernel, which has different device tree, changing dr_mode doesn't work.

/dts-v1/;
/plugin/;

/ {
    compatible = "rockchip,rk3588s";

    fragment@0 {
        target = <&usbdrd3_0>;  // Target the usbdrd3_0 node

        __overlay__ {
            usb@fc000000 {
                dr_mode = "peripheral";  // Change dr_mode to peripheral
            };
        };
    };
};

The device trees for usb type c port for both kernels are as below -

//***This node is of current kernel***
usb@fc000000 {
		power-domains = <0x21 0x1f>;
		snps,dis-u1-entry-quirk;
		snps,dis_enblslpm_quirk;
		phy-names = "usb2-phy\0usb3-phy";
		clock-names = "ref_clk\0suspend_clk\0bus_clk";
		snps,dis-u2-freeclk-exists-quirk;
		usb-role-switch;
		phy_type = "utmi_wide";
		resets = <0x1f 0x152>;
		interrupts = <0x00 0xdc 0x04 0x00>;
		clocks = <0x1f 0x194 0x1f 0x193 0x1f 0x192>;
		snps,dis-u2-entry-quirk;
		compatible = "rockchip,rk3588-dwc3\0snps,dwc3";
		snps,dis-del-phy-power-chg-quirk;
		status = "okay";
		phys = <0x23 0x24 0x04>;
		reg = <0x00 0xfc000000 0x00 0x400000>;
		phandle = <0x116>;
		dr_mode = "peripheral";
		snps,dis-tx-ipgap-linecheck-quirk;

		port {

			endpoint {
				remote-endpoint = <0x25>;
				phandle = <0xeb>;
			};
		};
	};


------------
dmesg output
[   15.417624] i2c 6-0022: deferred probe pending: typec_fusb302: cannot register tcpm port
[  600.475296] g_audio gadget.0: Linux USB Audio Gadget, version: Feb 2, 2012
[  600.475317] g_audio gadget.0: g_audio ready

Vendor Kernel

//***This node is of vendor kernel
	usbdrd3_0 {
		#address-cells = <0x02>;
		clock-names = "ref\0suspend\0bus";
		clocks = <0x02 0x1a3 0x02 0x1a2 0x02 0x1a1>;
		#size-cells = <0x02>;
		compatible = "rockchip,rk3588-dwc3\0rockchip,rk3399-dwc3";
		ranges;
		status = "okay";
		phandle = <0x22b>;

		usb@fc000000 {
			power-domains = <0x06 0x1f>;
			snps,dis-u1-entry-quirk;
			snps,dis_enblslpm_quirk;
			phy-names = "usb2-phy\0usb3-phy";
			snps,dis-u2-freeclk-exists-quirk;
			usb-role-switch;
			phy_type = "utmi_wide";
			quirk-skip-phy-init;
			resets = <0x02 0x2a4>;
			interrupts = <0x00 0xdc 0x04>;
			snps,dis-u2-entry-quirk;
			compatible = "snps,dwc3";
			snps,parkmode-disable-hs-quirk;
			snps,dis-del-phy-power-chg-quirk;
			status = "okay";
			snps,parkmode-disable-ss-quirk;
			phys = <0x74 0x75>;
			reg = <0x00 0xfc000000 0x00 0x400000>;
			phandle = <0x22c>;
			dr_mode = "otg";
			reset-names = "usb3-otg";
			snps,dis-tx-ipgap-linecheck-quirk;

			port {
				#address-cells = <0x01>;
				#size-cells = <0x00>;

				endpoint@0 {
					remote-endpoint = <0x76>;
					reg = <0x00>;
					phandle = <0x183>;
				};
			};
		};
	};

//dmesg output
[   41.238153] [GTP-ERR][__do_register_ext_module:79] Module [goodix-fwu] timeout
[  243.574594] g_audio gadget.0: Hardware params: access 3, format 2, channels 2, rate 48000
[  243.574756] g_audio gadget.0: Linux USB Audio Gadget, version: Feb 2, 2012
[  243.574773] g_audio gadget.0: g_audio ready
[  243.578558] typec_fusb302 6-0022: Looking up vbus-supply from device tree
[  243.581576] dwc3 fcd00000.usb: device reset

Can some one help me what kind of overlay should i make to convert the port to peripheral mode.

I'm having issues viewing videos that have pixel format of yuv420p10le with the current apt repository Kodi Nexus.

I thought to try Kodi Flatpak and it worked and I was able to view those yuv420p10le videos without issue.  However, it was choppy and had high CPU usage...around 80% on many of the CPUs.  I'm trying to figure that out.  It's happening on all types of videos.  All is played using software decoding.  I've never gotten hardware decoding working.  In the Kodi Nexus version I'm using it also software decoding but very low CPU usage.

In any case, just want to see what experiences others are having.

after upgrading to Armbian 24.11.3 noble with 6.1 Kernel I have this problem that every time I turn off my TV that is connected to OPI with HDMI, then turning it back on again it will never have a HDMI signal.

Same thing happens when I unplug the HDMI cable and plug it back in.
I can reproduce it every single time - not just occasionally.

It is not a hardware or cable problem, the exact same setup has worked flawlessly for long time with older Armbian and 5.1 kernel.

I tried disabling all of the KDE power saving settings, also totally disabled kpowerdevil - with no change.

SSH still works fine, the OS has not crashed.

No new messages come to "dmesg" after tuning the TV off and on. 

Only thing that appear is in /var/log/syslog is when I turn the tv back ON again. Turning it off does not add any messages.

2025-02-06T13:21:23.984567+02:00 loovsys DiscoverNotifier[1979]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.984940+02:00 loovsys kded6[1877]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.985204+02:00 loovsys polkit-kde-authentication-agent-1[1929]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.985425+02:00 loovsys plasmashell[1897]: kde.plasmashell: requesting unexisting screen available rect -1
2025-02-06T13:21:23.985562+02:00 loovsys plasmashell[1897]: message repeated 3 times: [ kde.plasmashell: requesting unexisting screen available rect -1]
2025-02-06T13:21:23.986668+02:00 loovsys kalendarac[1985]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.986910+02:00 loovsys kactivitymanagerd[1904]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.987124+02:00 loovsys xdg-desktop-portal-kde[1930]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.991124+02:00 loovsys plasmashell[1897]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.991328+02:00 loovsys plasmashell[1897]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.

Or another time pretty similar
 

2025-02-06T13:26:53.652232+02:00 loovsys kactivitymanagerd[1880]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.653516+02:00 loovsys kalendarac[1964]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.654495+02:00 loovsys kded6[1852]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.655328+02:00 loovsys DiscoverNotifier[1957]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.656229+02:00 loovsys xdg-desktop-portal-kde[1905]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.657111+02:00 loovsys plasmashell[1868]: kde.plasmashell: requesting unexisting screen available rect -1
2025-02-06T13:26:53.657645+02:00 loovsys plasmashell[1868]: message repeated 3 times: [ kde.plasmashell: requesting unexisting screen available rect -1]
2025-02-06T13:26:53.658397+02:00 loovsys polkit-kde-authentication-agent-1[1904]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.665372+02:00 loovsys plasmashell[1868]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.665685+02:00 loovsys plasmashell[1868]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
2025-02-06T13:26:53.807759+02:00 loovsys plasmashell[1868]: message repeated 3 times: [ kf.plasma.quick: Exposed with no visual parent. Window positioning broken.]

When plugging the HDMI cable back in:

2025-02-06T13:30:00.668173+02:00 loovsys kalendarac[1948]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.669049+02:00 loovsys DiscoverNotifier[1946]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.669745+02:00 loovsys kactivitymanagerd[1869]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.670412+02:00 loovsys kded6[1839]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.671016+02:00 loovsys xdg-desktop-portal-kde[1889]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.671596+02:00 loovsys polkit-kde-authentication-agent-1[1888]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.672173+02:00 loovsys plasmashell[1858]: kde.plasmashell: requesting unexisting screen available rect -1
2025-02-06T13:30:00.672548+02:00 loovsys plasmashell[1858]: message repeated 3 times: [ kde.plasmashell: requesting unexisting screen available rect -1]
2025-02-06T13:30:00.672946+02:00 loovsys plasmashell[1858]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.688381+02:00 loovsys plasmashell[1858]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
2025-02-06T13:30:00.705197+02:00 loovsys plasmashell[1858]: message repeated 2 times: [ kf.plasma.quick: Exposed with no visual parent. Window positioning broken.]
2025-02-06T13:30:01.892282+02:00 loovsys CRON[6339]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
2025-02-06T13:30:01.895234+02:00 loovsys CRON[6338]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
2025-02-06T13:30:02.361046+02:00 loovsys chronyd[1553]: Selected source 212.7.1.131 (0.ubuntu.pool.ntp.org)
2025-02-06T13:30:05.222767+02:00 loovsys plasmashell[1858]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.

I also tried to switch between graphical and multi-user targets. (This works fine when the TV is never turned off - i can get the console and switch back to grapgical UI)
 

systemctl isolate multi-user.target
systemctl isolate graphical.target

Issuing a reboot command will bring the display back. I do not have to power cycle the entire device to get the display back.

I can also get back the display after I have lost signal by switching to the multi-user.target, unplugging and plugging back in the cable. After that i can also switch back to graphical.target and everything works.

Only switching between graphical and multi-user afer losing the signal will not bring back the display.
 

If I first switch to multi-user.target and then turn off the tv, then turning it back on the display works. I can also enable the graphical target again without problems.
Then the following messages appear in syslog
 

2025-02-06T13:37:21.290588+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_disable] Crtc atomic disable vp0
2025-02-06T13:37:24.167556+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 3840x2160p60, type: 11(if:HDMI0, flag:0x0) for vp0 dclk: 594000000
2025-02-06T13:37:24.167664+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx_ropll_cmn_config bus_width:5aa320 rate:5940000
2025-02-06T13:37:24.167680+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy pll locked!
2025-02-06T13:37:24.167693+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out0 div: 0 dclk_core0 div: 2
2025-02-06T13:37:24.167706+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop0 to 594000000, get 594000000
2025-02-06T13:37:24.167719+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: final tmdsclk = 594000000
2025-02-06T13:37:24.280906+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: don't use dsc mode
2025-02-06T13:37:24.280986+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: dw hdmi qp use tmds mode
2025-02-06T13:37:24.281000+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: bus_width:0x5aa320,bit_rate:5940000
2025-02-06T13:37:24.281011+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy lane locked!

Also in the dmesg the following appears

[  293.342367] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_disable] Crtc atomic disable vp0
[  296.325415] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 3840x2160p60, type: 11(if:HDMI0, flag:0x0) for vp0 dclk: 594000000
[  296.326327] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx_ropll_cmn_config bus_width:5aa320 rate:5940000
[  296.326706] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy pll locked!
[  296.327137] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out0 div: 0 dclk_core0 div: 2
[  296.327226] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop0 to 594000000, get 594000000
[  296.327422] dwhdmi-rockchip fde80000.hdmi: final tmdsclk = 594000000
[  296.438292] dwhdmi-rockchip fde80000.hdmi: don't use dsc mode
[  296.438342] dwhdmi-rockchip fde80000.hdmi: dw hdmi qp use tmds mode
[  296.438380] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: bus_width:0x5aa320,bit_rate:5940000
[  296.438665] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy lane locked!

As soon as I use the graphical target, then dmesg shows nothing and syslog only the messages I showed before.
 

root@loovsys:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Armbian 24.11.3 noble
Release:        24.04
Codename:       noble
root@loovsys:~# uname -a
Linux loovsys.eu 6.1.84-vendor-rk35xx #1 SMP Thu Jan  9 02:09:01 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux

Anyone experiencing similar issues or has any idea what could be the reason for it? Otherwise  t

When i am trying to setup many vlan interfacces i have whis dmesg message:

rk_gmac-dwmac fe1c0000.ethernet eth0: MAC_VLAN_Tag_Filter full (size: 4)

interface info:

ethtool -i eth0
driver: st_gmac
version: Jan_2016
firmware-version: 
expansion-rom-version: 
bus-info: 
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no

I need about 20-30 vlan interfaces

I've tryed all images (Linux and Android) from the official Orange Pi site . Later I tryed Armbian .

In the end I've concluded that the best choice is Armbian 24.5.2 Noble Gnome ( Armbian_24.5.2_Orangepi5pro_noble_vendor_6.1.43_gnome-oibaf_desktop.img ).

Using Armbian 24.5.2 Noble Gnome I got the best (the smoothest) video playback, both in video players and online (youtube) content . And it' s very responsive in operation, generally .

I have one single issue : My MCE remote is not detected properly - the Play, Pause, Next, Previous, Forward, Rewind buttons did't perform any actions when I used Kodi video player . When I press any of these buttons I get a 🚫 (no entry) sign on the bottom of the screen .

Only the following buttons are performing correctly : Power, Ok, Left, Right, Up, Down, back, and numeric keys .

If I'm using other video players, like Celluloid, Vlc,Haruna, Smplayer, all the remote control's buttons performs as it should .

The remote control's model number is HP TSGH-2401 with RF USB dongle .

I tryed the remote and Kodi on different Linux images, even on Armbian_24.5.2_Orangepi5pro_noble_vendor_6.1.43_xfce-oibaf_desktop.img - it perform as it should, but all these Linux images have video playback issues (or maybe i'm too picky) . The problem with the remote control is present only on Armbian 24.5.2 Noble Gnome (which I preffered for it's video performance) .

I tryed to fix the problem using inputlirc package, but with limited success . I also tried "Keymap editor " add-on for Kodi, but with almost none positive results .

I attached 2 screenshoots with the the screen when I get a 🚫 (no entry) sign on the bottom of the screen .

Please help me with some suggestions .

Thank you in advance !

Oops: Unable to determine board revision from /proc/device-tree/system/linux,revision
or from /proc/cpuinfo
-> No "Hardware" line
-> You'd best google the error to find out why.

Can anyone help me solve this problem?

Tried restarting a few times.  Tried swapping SD cards.  It looks like the power supply is OK, although I'll try swapping with another.  I had just backed up the SD Card too.  I'll try re-imaging an SD card, but I'm thinking the SD card may not be the issue.

I hooked up my UART and captured output.  At the end of each loop, it looks like it's saying "Starting Kernel" and then restarting.  Captured output follows.

Any ideas, suggestions or comments on what's happening.  I'm thinking it's probably a hardware issue.  I purchased on Amazon.  Can't find out how long the warranty/if it's still under warranty.

  DDR V1.11 f1474cf52f cym 23/05/09-11:02:36
LPDDR4X, 2112MHz

CH2 RX Vref:27.5%, TX Vref:19.8%,20.8%
CH3 RX Vref:30.1%, TX
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 156out
U-Boot SPL board init
U-Boot SPL 2017.09 (Jun 30 2023 - 19unknown raw ID 0 0 0
unrecognized JEDEC id bytes: 00, 00, 00
TTrying fit image at 0x4000 sector
## Verified-boot: 0
## Check## Checking uboot 0x00200000 ... sha256(bab9643a63...) + OK
##  atf-3 0x000f0000 ... sha256(da90adf3a4...) + OK
Jumping to U-B.622 ms

INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():vrt detected.
INFO:    ARM GICv3 driver initialized in EL3
INFOams[0].freq_mhz= 2112MHz
INFO:    dfs DDR fsp_params[1].freq_mhz= 528MHz
INFO:    dfs DDR fsp_params[2].freq_mhz= 1068MHz
INFINFO:    BL31: Initialising Exception Handling Framework
INFO:  initializing runtime service opteed_fast
INFO:    BL31: Prepar 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09 (Jun 30 202CR: M/C/I
Using default environment

mmc@fe2c0000: 0, mmc@fe2Bootdev(atags): mmc 0
MMC0: Legacy, 52Mhz
PartType: EFI
DM: vCLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kerpll 1188000 KHz
  npll 24000 KHz
  ppll 1100000 KHz
  aclk_ceer_root 396000 KHz
  aclk_center_low_root 500000 KHz
  aclk_toot 396000 KHz
Net:   No ethernet found.
Hit key to stop autobo-Boot script /boot.scr
reading /boot.scr
3476 bytes read in 1 ded from mmc 0
reading /armbianEnv.txt
212 bytes read in 2 ms 15248365 bytes read in 1223 ms (11.9 MiB/s)
reading /Image
34638336 bytes read in 2777 ms (11.9 MiB/s)
reading /dtb/rockch234611 bytes read in 30 ms (7.5 MiB/s)
** Unable to read file /OK
## Flattened Device Tree blob at 0x0a100000
   Booting usin000000000a1a1fff
Adding bank: 0x00200000 - 0xf0000000 (size: 0xize: 0x03a00000)
Adding bank: 0x4f0000000 - 0x500000000 (size: Total: 4379.611 ms

Starting kernel ...

  DDR V1.11 f1474cf52f cym 23/05/09-11:02:36
LPDDR4X, 2112MHz
cher ID:0x6
CH0 RX Vref:28.5%, TX Vref:20.8%,20.8%
CH1 RX Vref:2
CH2 RX Vref:27.5%, TX Vref:20.8%,19.8%
CH3 RX Vref:29.3%, TX
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 156out
U-Boot SPL board init
U-Boot SPL 2017.09 (Jun 30 2023 - 19Trying fit image at 0x4000 sector
## Verified-boot: 0
## Check## Checking uboot 0x00200000 ... sha256(bab9643a63...) + OK
## .902 ms

INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():vINFO:    ddr: stride-en 4CH
INFO:    GICv3 without legacy suppo:    system boots from cpu-hwid-0
INFO:    idle_st=0x21fff, pd_ams[0].freq_mhz= 2112MHz
INFO:    dfs DDR fsp_params[1].freq_mhINFO:    BL31: Initialising Exception Handling Framework
INFO:

U-Boot 2017.09 (Jun 30 2023 - 19:08:39 +0200)

Model: OranCR: M/C/I
Using default environment

mmc@fe2c0000: 0, mmc@fe2Bootdev(atags): mmc 0
MMC0: Legacy, 52Mhz
PartType: EFI
DM: vCLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kerot 396000 KHz
Net:   No ethernet found.
Hit key to stop autoboms (3.3 MiB/s)
## Executing script at 00500000
Boot script loa15248365 bytes read in 1223 ms (11.9 MiB/s)
reading /Image
34638336 bytes read in 2776 ms (11.9 MiB/s)
reading /dtb/rockch234611 bytes read in 29 ms (7.7 MiB/s)
** Unable to read file /p compressed)
   Data Size:    15248301 Bytes = 14.5 MiB
   LoOK
## Flattened Device Tree blob at 0x0a100000
   Booting usinefe00000)
Adding bank: 0x100000000 - 0x3fc000000 (size: 0x2fc00ize: 0x03a00000)
Adding bank: 0x4f0000000 - 0x500000000 (size: Total: 4378.924 ms

Starting kernel ...

I downloaded the image to micro sd and it boots fine.

At this point I don't know what to do because I had to waste a lot of time on it some time ago and I don't remember the steps.

With the armbian-config utility is it possible to clone the armbian release I am using on the micro sd? I remember that this wasn't possible some time ago.

I would like to know specifically the steps to take and whether it is advisable to delete any old partitions on nvme.

Thank you

I plan to use it for djing.

A fully preemptive kernel delivers better performance for this, as less xruns appear.

I am following the official dev instructions and am using the docker method, Compiling only the kernel, not the entire armbian OS.

I copied a realtime patch (actually I tried several sub versions of 5.10) from the kernel.org realtime project site into the userpatches directory (I looked up the correct orange pi 5 subfolder name but forgot it rn) but compiling throws me some errors. 
 

Has anyone succeeded in creating a kernel like this for the orange pi 5 and/or could give me any advice for doing so?

I actually dont care much about the kernel version, I just need it to be fully preemptive ..

Help is much apprecieated!

Kenny

Here's what I've already tried based on search and ChatGPT:

1. Mount the NVMe partition to `/mnt` then chroot to it, this did work but the `/boot` partition was not mounted inside of the chroot so I can't fix boot env.
2. I also tried `switch_root` but it's not available in the initramfs prompt.
3. Update `/proc/cmdline` to change the root fs back to the Armbian partition, but `echo ... > /proc/cmdline` doesn't really do anything.

Any ideas?

Setting up rockchip-multimedia-config (1.0.2+jammy) ...

dpkg-query: error: --listfiles needs at least one package name argument

Use --help for help about querying packages.

dpkg: error processing package rockchip-multimedia-config (--configure):

 installed rockchip-multimedia-config package post-installation script subprocess returned error exit status 1

Errors were encountered while processing:

 rockchip-multimedia-config

E: Sub-process /usr/bin/dpkg returned an error code (1)

This is what I did

1) boot system from fresh downloaded SD (Armbian Jammy Desktop)

2) NVME setup (sudo gparted)
   - if empty create a partition table (GPT)
     if not delete all partitions
   - create 256MB FAT16 partition (nvme0n1p1)
   - create EXT4 partition (nvme0n1p2)
   - optionally create more partitions (system recovery, backups ...)
   - format partitions nvme0n1p1 -> FAT16
   - format partitions nvme0n1p2 -> EXT4
   - check partitions (if old NVME)
   - label nvme0n1p1 as armbi_boot
   - label nvme0n1p2 as armbi_root

3) run sudo armbian-install
   - option 7 to flash mtdblock0 (bootloader install)
   - option 4 (to install system and boot from mtdblock0)
     choose nvme0n1p2 partition to install system
     don't POWEROFF, just EXIT

4) copy SD boot partition to nvme0n1p1
   - sudo dd if=/dev/mmcblk1p1 of=/dev/nvme0n1p1 bs=1M status=progress
   - sudo sync

5) armbianExt.txt setup on NMVE
   - sudo mount /dev/nvme0n1p1 /mnt
   - check boot files/directories are already copied (ls -l /mnt)
   - blkid
   - copy (CTL_INS -> new UUID) of nvme0n1p2 UUID (without "")

  with your favourite editor:
   - sudo vi armbianExt.txt
   - replace rootdev=UUID=with new UUID (SHIFT-INS)
   - save (ESC :x)

6) - sudo poweroff
   - remove SD
   - press power button to restart

Maybe this cam help someone

I pourchased OPi5 (not preferred OPi5 Pro, because of Armbian lacking support), flashed Debian 24.8.1_bookworm_6.10.6_cinnamon_backported_mesa_desktop, configured (user, switch to static IP, user).

Worked OK.

Now, ssh'ing into showed "113 packages upgrade".

Did "apt upgrade".

Download OK, but when applying apgrade process hung twice:

- once on "configuring libc", had to power off, then restarted (after an apt-get suggested in response to apt upgrade). Upgrade hung second time (no progress on bottom bar for hours, no new ssh session).

- twice was on "configuring udev".

After this, board is almost dead:

- boots to animated Armbian logo,

- then "flash" (the few lines on bootup) "failed" (too shot to see what failed).

- then NO normal (text) bootup messages,

- then blank screen with text cursor in left-upper corner, switching with totally blank screen (but monitor does NOT go to sleep) - graphic mode?

I can remove uSD card (good, Samsung U1, 32GB), but what should I look for?

Power seems not be problem, it is on it's own 5V/5A SMPS, heatsinks and fan.

Laurent

# modprobe ip_tables
modprobe: ERROR: could not insert 'ip_tables': Exec format error

I’m not sure what to make of it. 

Now that my Orange Pi 5 gets a slightly more serious use as webserver, I really like to get rid of the unpredictable Xorg crashes, and gladly would sacrifice HW acceleration for stability. My situation is this:

• Using JR Ubuntu
• Because I want to use headless RealVNC (runs only under Xorg) for several devices I switched off Wayland
• Using a slightly hacked RealVNC server originating from Raspberry Pi
• Want to use OPI5 as a NodeJS + Nginx webserver serving Node apps now

Any suggestions for a super stable uncrashable distro for the Opi5, for server use but with gui? I kind of hate to set everything up again, especially with the internal M.2 sata quirks, but I gotta have stability now. Hopefully I can ask a second question: is there an easy way to totally turn off HW acceleration in JR Ubuntu? Maybe I should try that first...

Kind regards,

Bas

my new OPi5 with Armbian Bookworm Cinnamon mesa backoprted does not see my mPCIe SSD disk.

Just got this: https://allegro.pl/oferta/nowy-superszybki-dysk-ssd-512gb-m-2-nvme-2242-9605598735 \ module, but it is not recognized by the system.

Armbianmonitor output: https://paste.armbian.com/huhedogene

lspci -v output:

0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) (prog-if 00 [Normal decode])
       Flags: bus master, fast devsel, latency 0, IRQ 89
       Bus: primary=40, secondary=41, subordinate=41, sec-latency=0
       I/O behind bridge: [disabled] [16-bit]
       Memory behind bridge: [disabled] [32-bit]
       Prefetchable memory behind bridge: [disabled] [64-bit]
       Expansion ROM at f4200000 [virtual] [disabled] [size=64K]
       Capabilities: [40] Power Management version 3
       Capabilities: [50] MSI: Enable+ Count=16/32 Maskable- 64bit+
       Capabilities: [70] Express Root Port (Slot-), MSI 08
       Capabilities: [b0] MSI-X: Enable- Count=128 Masked-
       Capabilities: [100] Advanced Error Reporting
       Capabilities: [148] Secondary PCI Express
       Capabilities: [180] L1 PM Substates
       Capabilities: [190] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?>
       Kernel driver in use: pcieport
 

No new /dev/sd* , nor /dev/mmcblk* files.

What am I missing?

Is module faulty? (but it is new)

Should I switch to another kernel? (Current is Linux orangepi5 6.10.6-current-rockchip-rk3588 #1 SMP PREEMPT Mon Aug 19 04:05:40 UTC 2024 aarch64 GN
U/Linux ).

Laurent

Would someone point me to where to get a particular distro, mainly looking for jammy_legacy_gnome-amazingfated_desktop for OPi 5 Pro ?

I have jammy_legacy_5.10.160_gnome-amazingfated_desktop for Pi5 and Pi5 Plus but it does not work on the Pro version.

thank you in advance.

    _             _    _
   /_\  _ _ _ __ | |__(_)__ _ _ _
  / _ \| '_| '  \| '_ \ / _` | ' \
 /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|

 v24.8.4 for Orange Pi 5 running Armbian Linux 6.10.6-current-rockchip-rk3588

 Packages:     Debian stable (bookworm)
 IP addresses: (LAN) 192.168.1.2 10.8.0.1 (WAN) xxx.xxx.xxx.xxx

 Performance:

 Load:         1%               Up time:       21 days 23:00
 Memory usage: 10% of 15.35G
 CPU temp:     41°C             Usage of /:    21% of 233G

 Tips:

 Support our work and become a sponsor https://github.com/sponsors/armbian

 Commands:

 System config  : sudo armbian-config
 System monitor : htop

Last login: Tue Oct 15 13:16:59 2024 from 192.168.1.28
rob@orangepi5:~$ sudo apt update
[sudo] password for rob:
Hit:1 http://deb.debian.org/debian bookworm InRelease
Get:2 http://security.debian.org bookworm-security InRelease [48.0 kB]
Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:5 http://deb.debian.org/debian bookworm-backports InRelease [59.0 kB]
Get:6 https://packages.adoptium.net/artifactory/deb bookworm InRelease [7,517 B]
Get:4 http://mirrors.jevincanders.net/armbian/apt bookworm InRelease [53.3 kB]
Get:7 http://security.debian.org bookworm-security/main arm64 Packages [186 kB]
Get:8 http://security.debian.org bookworm-security/main armhf Packages [186 kB]
Get:9 http://deb.debian.org/debian bookworm-backports/main arm64 Packages.diff/Index [63.3 kB]
Get:10 http://deb.debian.org/debian bookworm-backports/main armhf Packages.diff/Index [63.3 kB]
Get:11 http://deb.debian.org/debian bookworm-backports/main arm64 Contents (deb).diff/Index [63.6 kB]
Get:12 http://deb.debian.org/debian bookworm-backports/main all Contents (deb).diff/Index [63.6 kB]
Get:13 http://deb.debian.org/debian bookworm-backports/main armhf Contents (deb).diff/Index [63.6 kB]
Get:14 http://deb.debian.org/debian bookworm-backports/main arm64 Packages T-2024-10-21-1409.06-F-2024-10-15-2009.57.pdiff [11.0 kB]
Get:14 http://deb.debian.org/debian bookworm-backports/main arm64 Packages T-2024-10-21-1409.06-F-2024-10-15-2009.57.pdiff [11.0 kB]
Get:15 http://mirrors.jevincanders.net/armbian/apt bookworm/main all Packages [13.5 kB]
Get:16 http://mirrors.jevincanders.net/armbian/apt bookworm/main armhf Packages [345 kB]
Get:17 http://mirrors.jevincanders.net/armbian/apt bookworm/main arm64 Packages [935 kB]
Get:18 http://deb.debian.org/debian bookworm-backports/main armhf Packages T-2024-10-21-1409.06-F-2024-10-15-2009.57.pdiff [10.9 kB]
Get:18 http://deb.debian.org/debian bookworm-backports/main armhf Packages T-2024-10-21-1409.06-F-2024-10-15-2009.57.pdiff [10.9 kB]
Get:19 http://mirrors.jevincanders.net/armbian/apt bookworm/main arm64 Contents (deb) [14.9 MB]
Get:20 http://deb.debian.org/debian bookworm-backports/main arm64 Contents (deb) T-2024-10-19-0204.47-F-2024-10-15-2009.57.pdiff [265 B]
Get:20 http://deb.debian.org/debian bookworm-backports/main arm64 Contents (deb) T-2024-10-19-0204.47-F-2024-10-15-2009.57.pdiff [265 B]
Get:21 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-utils arm64 Packages [22.6 kB]
Get:22 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-utils armhf Packages [52.5 kB]
Get:23 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-utils arm64 Contents (deb) [28.4 kB]
Get:24 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-utils armhf Contents (deb) [24.7 kB]
Get:25 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-desktop armhf Packages [10.2 kB]
Get:26 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-desktop all Packages [5,802 B]
Get:27 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-desktop arm64 Packages [9,992 B]
Get:28 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-desktop armhf Contents (deb) [29.4 kB]
Get:29 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-desktop all Contents (deb) [1,309 B]
Get:30 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-desktop arm64 Contents (deb) [29.4 kB]
Get:31 http://deb.debian.org/debian bookworm-backports/main all Contents (deb) T-2024-10-21-1409.06-F-2024-10-15-2009.57.pdiff [5,774 B]
Get:31 http://deb.debian.org/debian bookworm-backports/main all Contents (deb) T-2024-10-21-1409.06-F-2024-10-15-2009.57.pdiff [5,774 B]
Get:32 http://deb.debian.org/debian bookworm-backports/main armhf Contents (deb) T-2024-10-19-0204.47-F-2024-10-15-2009.57.pdiff [263 B]
Get:32 http://deb.debian.org/debian bookworm-backports/main armhf Contents (deb) T-2024-10-19-0204.47-F-2024-10-15-2009.57.pdiff [263 B]
Fetched 17.3 MB in 7s (2,576 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
6 packages can be upgraded. Run 'apt list --upgradable' to see them.
rob@orangepi5:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  armbian-config armbian-firmware armbian-plymouth-theme armbian-zsh linux-dtb-vendor-rk35xx linux-image-vendor-rk35xx
6 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 138 MB of archives.
After this operation, 15.9 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://armbian.tnahosting.net/apt bookworm/main arm64 armbian-config all 24.8.4 [136 kB]
Get:6 http://armbian.chi.auroradev.org/apt bookworm/main arm64 linux-image-vendor-rk35xx arm64 24.8.4 [32.6 MB]
Get:2 http://mirrors.jevincanders.net/armbian/apt bookworm/main arm64 armbian-firmware all 24.8.4 [91.6 MB]
Get:3 http://mirrors.jevincanders.net/armbian/apt bookworm/main arm64 armbian-plymouth-theme all 24.8.4 [108 kB]
Get:4 http://mirrors.jevincanders.net/armbian/apt bookworm/main arm64 armbian-zsh all 24.8.4 [11.8 MB]
Get:5 http://mirrors.jevincanders.net/armbian/apt bookworm/main arm64 linux-dtb-vendor-rk35xx arm64 24.8.4 [2,135 kB]
Fetched 138 MB in 3s (44.6 MB/s)
(Reading database ... 109457 files and directories currently installed.)
Preparing to unpack .../0-armbian-config_24.8.4_all.deb ...
Unpacking armbian-config (24.8.4) over (24.8.3) ...
Preparing to unpack .../1-armbian-firmware_24.8.4_all.deb ...
Unpacking armbian-firmware (24.8.4) over (24.8.3) ...
Preparing to unpack .../2-armbian-plymouth-theme_24.8.4_all.deb ...
Unpacking armbian-plymouth-theme (24.8.4) over (24.8.3) ...
Preparing to unpack .../3-armbian-zsh_24.8.4_all.deb ...
Unpacking armbian-zsh (24.8.4) over (24.8.3) ...
Preparing to unpack .../4-linux-dtb-vendor-rk35xx_24.8.4_arm64.deb ...
Armbian 'linux-dtb-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'preinst' starting.
Armbian 'linux-dtb-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'preinst' finishing.
Unpacking linux-dtb-vendor-rk35xx (24.8.4) over (24.8.2) ...
Preparing to unpack .../5-linux-image-vendor-rk35xx_24.8.4_arm64.deb ...
Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'prerm' starting.
Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'prerm' finishing.
Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'preinst' starting.
Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'preinst' finishing.
Unpacking linux-image-vendor-rk35xx (24.8.4) over (24.8.2) ...
Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'postrm' starting.
Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'postrm' finishing.
Setting up linux-dtb-vendor-rk35xx (24.8.4) ...
Armbian 'linux-dtb-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'postinst' starting.
Armbian: DTB: FAT32: moving /boot/dtb-6.1.75-vendor-rk35xx to /boot/dtb ...
renamed 'dtb-6.1.75-vendor-rk35xx' -> 'dtb'
Armbian 'linux-dtb-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'postinst' finishing.
Setting up linux-image-vendor-rk35xx (24.8.4) ...
Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'postinst' starting.
dkms: autoinstall for kernel 6.1.75-vendor-rk35xx was skipped since the kernel headers for this kernel do not seem to be installed.
update-initramfs: Generating /boot/initrd.img-6.1.75-vendor-rk35xx
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.75-vendor-rk35xx
Image Name:   uInitrd
Created:      Tue Oct 22 06:34:02 2024
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    16110316 Bytes = 15732.73 KiB = 15.36 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.75-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.75-vendor-rk35xx to /boot/uInitrd
renamed '/boot/uInitrd-6.1.75-vendor-rk35xx' -> '/boot/uInitrd'
update-initramfs: Armbian: done.
Free space after deleting the package linux-image-vendor-rk35xx in /boot: 78.5M
Armbian: FAT32 /boot: move last-installed kernel to 'Image'...
renamed '/boot/vmlinuz-6.1.75-vendor-rk35xx' -> '/boot/Image'
Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'postinst' finishing.
Setting up armbian-zsh (24.8.4) ...
Setting up armbian-config (24.8.4) ...
Setting up armbian-firmware (24.8.4) ...
Setting up armbian-plymouth-theme (24.8.4) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.142+deb12u1) ...
ln: failed to create hard link '/boot/initrd.img-6.10.6-current-rockchip-rk3588.dpkg-bak' => '/boot/initrd.img-6.10.6-current-rockchip-rk3588': Operation not permitted
update-initramfs: Generating /boot/initrd.img-6.10.6-current-rockchip-rk3588
grep: /boot/config-6.10.6-current-rockchip-rk3588: No such file or directory
E: gzip compression (CONFIG_RD_GZIP) not supported by kernel
update-initramfs: failed for /boot/initrd.img-6.10.6-current-rockchip-rk3588 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
rob@orangepi5:~$ ls -l /boot
total 104816
-rwxr-xr-x 1 root root      213 Sep 30 07:31 armbianEnv.txt
-rwxr-xr-x 1 root root    38518 Feb 18  2023 boot.bmp
-rwxr-xr-x 1 root root     3404 Feb 18  2023 boot.cmd
-rwxr-xr-x 1 root root     3476 Feb 18  2023 boot.scr
-rwxr-xr-x 1 root root   244731 Oct 18 04:11 config-6.1.75-vendor-rk35xx
drwxr-xr-x 3 root root     4096 Oct 22 06:33 dtb
-rwxr-xr-x 1 root root 39152128 Oct 18 04:11 Image
-rwxr-xr-x 1 root root 28272711 Sep 30 07:29 initrd.img-6.10.6-current-rockchip-rk3588
-rwxr-xr-x 1 root root 16110316 Oct 22 06:34 initrd.img-6.1.75-vendor-rk35xx
-rwxr-xr-x 1 root root  7371703 Oct 18 04:11 System.map-6.1.75-vendor-rk35xx
-rwxr-xr-x 1 root root 16110380 Oct 22 06:34 uInitrd
rob@orangepi5:~$

The latency of audio loop is 0.2 seconds on Raspberry pi but on orange pi it takes 1.2 seconds.

For orange pi, i am facing this problem with different Operating systems as well apart from armbian. I've used Ubuntu, Orange Pi OS, Armbian. All have got this problem. The code I have attached. Since the issue is faced in multiple Operating System I strongly feel this has to do with the driver level softwares or directly related optimization from Rockchip.

Can anyone guide what I could do

audio-loop.cpp

I've started noticing lately that videos are being encoded with pixel format yuv420p10le.  In Kodi, I was getting black screens while the audio was playing.  I was following up on the Kodi forums, and was told that Kodi needed to be compiled for OpenGL instead of OpenGLES to make the video render properly.  This is the thread:

https://forum.kodi.tv/showthread.php?tid=379167

So, I've been trying to compile Kodi myself.  If/when I succeed, I'll post.

Any info and/or comments about this and assistance is appreciated.

I wasn't sure if this was the place to post this.  If it's not feel free to delete this thread.

https://github.com/berin-aquaquad/orange-pi-5

I am using DesignSpark Mechanical a free cad software that is on par with Fusion360. The shell has been designed as a split body so smaller 3d printers can create it. Again, this is a work in progress, and nothing is set in stone.

Planned design additions for consideration:

• Headphone jack front or back.
• USB on front.
• Stats LCD on front.
• 3D printed power button to press power button on OPI5 motherboard.
• GPIO header for external access, "custom design or standard web link to example, I need feedback ".
• RTC battery holder to make use of the onboard RTC.
• RGB Micro Desktop case LIGHTING options?

Problems:

No display. (access only via SSH)

CIFS mounts fail

Lots of dmesg messages similar to:

...

[    6.421534] rtk_btusb: disagrees about version of symbol module_layout

...

[    6.504179] uio: disagrees about version of symbol module_layout

...

[  376.377046] ipv6: disagrees about version of symbol module_layout

...
[  379.869911] cifs_md4: disagrees about version of symbol module_layout

...

Is this problem known about?

Hello, i got this error after System Upgrade to the latest version. Looks like i need to revert back the kernel cause it doesn`t see my nvme ssd.

As 'm planning to have the drives 2nd large partition as my basic home file server I'm wondering if I can as easily re-install the OS if/when I need to update it to a newer one?

Because the instructions I followed and that I see around do a very basic

cat /dev/mmcblk1 > /dev/nvme0n1

onto the raw un-partitioned nvme. 

My case will be that I have data on a partition on that drive that needs to stay.

Is this going to be an issue or are there ways to re-install Armbian or even other distro on the boot partition?

Cheers!

I have noticed that whenever I reboot my Orange Pi 5 board, all the 8 cpus slow down to 408 Mhz with no range, as stated by cpufreq-info:

Quote

root@orangepi5:~# 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 408 MHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 408 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:75.18%, 600 MHz:2.60%, 816 MHz:0.00%, 1.01 GHz:4.92%, 1.20 GHz:2.63%, 1.42 GHz:2.77%, 1.61 GHz:2.04%, 1.80 GHz:9.87%  (551)
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 408 MHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 408 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:75.18%, 600 MHz:2.60%, 816 MHz:0.00%, 1.01 GHz:4.92%, 1.20 GHz:2.63%, 1.42 GHz:2.77%, 1.61 GHz:2.04%, 1.80 GHz:9.86%  (551)
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 408 MHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 408 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:75.18%, 600 MHz:2.60%, 816 MHz:0.00%, 1.01 GHz:4.92%, 1.20 GHz:2.63%, 1.42 GHz:2.77%, 1.61 GHz:2.04%, 1.80 GHz:9.86%  (551)
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 408 MHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 408 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:75.18%, 600 MHz:2.60%, 816 MHz:0.00%, 1.01 GHz:4.92%, 1.20 GHz:2.63%, 1.42 GHz:2.77%, 1.61 GHz:2.04%, 1.80 GHz:9.86%  (551)
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.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 408 MHz.
                  The governor "schedutil" 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.39%, 600 MHz:5.54%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:2.66%, 1.42 GHz:0.76%, 1.61 GHz:0.57%, 1.80 GHz:0.88%, 2.02 GHz:0.54%, 2.21 GHz:0.34%, 2.26 GHz:3.34%  (326)
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.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 408 MHz.
                  The governor "schedutil" 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.39%, 600 MHz:5.54%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:2.66%, 1.42 GHz:0.76%, 1.61 GHz:0.57%, 1.80 GHz:0.88%, 2.02 GHz:0.54%, 2.21 GHz:0.34%, 2.26 GHz:3.34%  (326)
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 408 MHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 408 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:83.38%, 600 MHz:5.82%, 816 MHz:0.03%, 1.01 GHz:0.00%, 1.20 GHz:4.01%, 1.42 GHz:0.74%, 1.61 GHz:0.76%, 1.80 GHz:0.68%, 2.02 GHz:0.76%, 2.21 GHz:0.11%, 2.26 GHz:3.70%  (340)
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 408 MHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 408 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:83.38%, 600 MHz:5.82%, 816 MHz:0.03%, 1.01 GHz:0.00%, 1.20 GHz:4.01%, 1.42 GHz:0.73%, 1.61 GHz:0.76%, 1.80 GHz:0.68%, 2.02 GHz:0.76%, 2.21 GHz:0.11%, 2.26 GHz:3.70%  (340)

I have created a cronjob script in order to bring the frequency back to acceptable range. I don't even know if this is the correct way to solve this, but I am running the following:

echo performance | sudo tee /sys/devices/platform/dmc/devfreq/dmc/governor
cpufreq-set -c 0 -u 1800000
cpufreq-set -c 4 -u 2260000
cpufreq-set -c 6 -u 2300000
cpufreq-set -c 0 -g schedutil
cpufreq-set -c 4 -g schedutil
cpufreq-set -c 6 -g schedutil

However, even though I set the frequency for processors 6 and 7 for 2.30 Ghz using this method, they never go that high, as stated by cpufreq-info:

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 "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 408 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:80.22%, 600 MHz:1.90%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:3.98%, 1.42 GHz:2.08%, 1.61 GHz:1.47%, 1.80 GHz:1.01%, 2.02 GHz:1.17%, 2.21 GHz:0.86%, 2.26 GHz:7.30%  (2110)
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 "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 408 MHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:80.22%, 600 MHz:1.90%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:3.98%, 1.42 GHz:2.08%, 1.61 GHz:1.47%, 1.80 GHz:1.01%, 2.02 GHz:1.17%, 2.21 GHz:0.86%, 2.26 GHz:7.30%  (2110)

Those last two processors only go that high if I run sbc-bench one time, than I get the desired speeds:

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.30 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.30 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 408 MHz and 2.30 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.30 GHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:0.00%, 600 MHz:0.00%, 816 MHz:0.00%, 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:3.63%, 2.21 GHz:5.86%, 2.30 GHz:90.50%  (1538)
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.30 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.30 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 408 MHz and 2.30 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.30 GHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:0.00%, 600 MHz:0.00%, 816 MHz:0.00%, 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:3.63%, 2.21 GHz:5.86%, 2.30 GHz:90.50%  (1538)

What is the correct way to solve this? What is sbc-bench doing in order to achieve these frenquencies??

Best regards,

Basically it wasn't that hard especially if youve done some git'hubbing before.

I think I followed the 'Ubuntu' instructions here.

Make sure you get the dependencies and do all the steps correctly.

It should build without problems if you do.  (remember you have a lot of cores on Opi5 so can use 'make -j6' or even higher)

https://github.com/dolphin-emu/dolphin/wiki/Building-for-Linux

You then want to set a config flag to make Dolphin use GLES instead of big brother OpenGL.

(you probably want to run it at least once to generate the config files)

nano ~/.config/dolphin-emu/GFX.ini
add a line:
PreferGLES = True

But when running one of the more common games I got a shader compilation error.

I hacked around that and also reported it on the Dolpin bug report site and it should be fixed soon when the 'PR' gets accepted.

In the meantime you can read here what to do,

https://bugs.dolphin-emu.org/issues/13198#

Note that in my youtube video I get a good fps but later on in the game when you get to the first village the transparencies in the central square bonfire completely kills fps.

The same happens in Metroid Prime when you have the large bluish holo walls in view.

Mario Kart runs pretty well most of the time. Mario Sunshine as well at least in the plaza area I have't tried further.

Cheers and Good Luck!

$ ip route
default via 192.168.88.1 dev end1 proto static metric 100 
169.254.0.0/16 dev end1 scope link metric 1000 
192.168.88.0/24 dev end1 proto kernel scope link src 192.168.88.32 metric 100 
  
$ ip a     
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: end1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 76:e2:40:53:b4:f6 brd ff:ff:ff:ff:ff:ff
    inet 192.168.88.32/24 brd 192.168.88.255 scope global noprefixroute end1
       valid_lft forever preferred_lft forever
      
$ ping 192.168.88.1 
PING 192.168.88.1 (192.168.88.1) 56(84) bytes of data.
^C
--- 192.168.88.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3032ms

Ping to another network address like 192.168.88.30 works fine.

Looks like  armbian-config does not save gateway and dns during configuration

what am I doing wrong?

sudo sed -i 's/LINUXFAMILY=rockchip-rk3588/LINUXFAMILY=rk35xx/g' /etc/armbian-release
sudo apt update
sudo apt install linux-image-legacy-rk35xx linux-dtb-legacy-rk35xx linux-headers-legacy-rk35xx
sudo apt remove linux-image-legacy-rockchip-rk3588 linux-dtb-legacy-rockchip-rk3588 linux-headers-legacy-rockchip-rk3588

NOTE: The steps are currently for beta branch only. Don't try on stable branch.