Active threads

Well, since it is already installed and working as expected, besides this issue of the my post above, what are my options? What could I do to fix this?

Accidentally included a duplicate in the previous post's image. Here is the missing SBC...I note this one has 32gb of ram vs the other's 16gb.

Hello there! I'm trying to build .iso image for orangepi5-plus, I've tried various options and other boards (including one board from Platinum support section), but always getting the same error stands for: Applying 153 patches from 135 files of which 1 driver patches, 134 patches in regular, sorted files... -> 001/153: /mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719(:1) Patch ->/mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719(:1) <- needs fixing: can't find file to patch. Problem with ->/mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719(:1) <-: Failed to apply patch Same section with DEBUG=yes: Applying 153 patches from 135 files of which 1 driver patches, 134 patches in regular, sorted files... - Root Makefile '/mnt/c/Users/mevep/armbian-build/cache/sources/linux-kernel-worktree/6.16__rockchip64__arm64/Makefile' date: '1753010333.0974233' -> 001/153: /mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719(:1) Rejects file /tmp/tmphi6p97nf exists. Patch ->/mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719(:1) <- needs fixing: can't find file to patch. Root Makefile is newer than patch '/mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719.patch', using Makefile date Problem with ->/mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719(:1) <-: Failed to apply patch /mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719.patch However, this file exists in folder tree and created above in this lines: --> (1684) INFO: Drivers have modifications [ exporting patch into /mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719.patch ] --> (1684) COMMAND: git add . --> (2225) COMMAND: env -i 'HOME=/home/me' 'PATH=/mnt/c/Users/mevep/armbian-build/.tmp/work-1421a594-9d88-4a93-8ce4-e89dd9820201/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin' 'GIT_COMMITTER_NAME=John Doe' 'GIT_COMMITTER_EMAIL=john.doe@somewhere.on.planet' git '-c' 'commit.gpgsign=false' commit '--quiet' '-m' 'drivers for rockchip64-edge version 6.16 git sha1 86731a2a651e58953fc949573895f2fa6d456841' '--author=John Doe <john.doe@somewhere.on.planet>' --> (2324) COMMAND: env -i 'HOME=/home/me' 'PATH=/mnt/c/Users/mevep/armbian-build/.tmp/work-1421a594-9d88-4a93-8ce4-e89dd9820201/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin' git format-patch '-1' '--stdout' '--unified=3' '--keep-subject' '--signature' 'Armbian generated patch from drivers for kernel 6.16 and family rockchip64' '--stat=120' '--stat-graph-width=10' '--zero-commit' > /mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719.patch.tmp --> (2408) COMMAND: mv -v /mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719.patch.tmp /mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719.patch renamed '/mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719.patch.tmp' -> '/mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_86731a2a651e58953fc949573895f2fa6d456841_rockchip64_edge_bddabb7e_6fc916f5-01ba4719.patch' Things that I've tried: switch between mainline arm-build and stable versions (v25.5.1) building various combinations of kernel (current, edge) and OS (debian, ubuntu) build for board BIGTREETECH CB1 from Platinum support section completely remove armbian-build folder from PC and retry from fresh start build with PREFER_DOCKER=yes and no My setup is: Windows 11 Ubuntu 24.04.2 LTS under WSL2 (fully updated & upgraded) Docker Desktop 4.43.1 (198352) Log files are too large for https://paste.next.armbian.com/log, so I've uploaded them as achieve build-export-debug.7z build-export.7z

works great for me in productive environment for 2+ years

I am Running Armbian 24.5.1 Jammy with Linux 6.1.115-vendor-rk35xx on Radxa Rock5b (and it works great!!) when running sudo apt dist-upgrade or sudo apt upgrade I get Die folgenden Pakete sind zurückgehalten worden: armbian-bsp-cli-rock-5b " Packages retained" apt list --installed | grep armbian-bsp-cli-rock-5b gives: armbian-bsp-cli-rock-5b-legacy/jammy,now 24.5.1 arm64 [installiert] armbian-bsp-cli-rock-5b/jammy,now 24.5.1 arm64 [Installiert,aktualisierbar auf: 25.5.1] ## installed, can be updated can/shall I force the the use of "armbian-bsp-cli-rock-5b/jammy,now 24.5.1 arm64 [Installiert,aktualisierbar auf: 25.5.1]" ? how? what is the correct procedure to update to 25.5.x? thanks

all those things are wow give kodi a try? https://kodi.tv/

It is documented there: So when booted from SD you need to copy over the u-boot image to SD card and do from there: dd if=cubie_a5e_spi_nor_raw_050624.img of=/dev/mtdblock0 But that won't you get NVMe support on Armbian as Cubie A5E NVMe support just isn't in the kernel, not even the dev version.

I assume you didn't change your power supply or add more things to USB? This could trigger crash. It would help if you could catch the crash. Enable more verbosity (loglevel) might give some clues, otherwise this can represent more serious debug / not easy to catch and resolve.

How long did you wait for this? if you for example use a quite large microsd card that however has a slow pace this may take a few minutes.

I don't have time to work on this right away, so to make sure this does not fall off the radar, I opened a ticket in the tracker.

OK That would be called regression and should be analysed for a fix moving forward. Specifically looking for an older release as a "solution" still seems misguided and should only be done to bisect not as a kind of permanent solution.

The Gnome desktop Power off menu selection and `sudo shutdown now` both reboot rather than powering down.

yeah, frustration is quite clear, but probably it is manufacturer who should be most/only interested in that. that also cost quite a lot, so it is probably better to demand where money were paid to, i guess.

That is the expected behavior. You always need to "install" u-boot after a new version from apt. The apt package just provides the binaries that you can install.

Tried rk3318 debian 12 with linux kernel 6.1.63 or up to 6.12.39 and no hdmi output, I installed on SD card. Though debian 11 with kernel 5.15.35 works Interesting thing that debian 12 with linux kernel 6.16.0-rc3 worked Is there anything I can do to provide useful information to debug?

At the same time as mmcblk1 disappeared someone had changed the ethernet port over to the secondary port as I could not get into the machine and tried the second port which had been configured to the same static IP address as the primary port was on.

You are right. I just downloaded something from youtube and assumed it was H264. When I checked it in VLC in my PC, the codec is: AOMedia's AV1 video (av01) I picked another mp4, which I verified in VLC as H264-MPEG4, 720p, and it played with 10% CPU This test below is with Bookworm XFCE, compositor ON, Linux 6.15.4 with default configuration Then I repeat the test with a 1080p H264 mp4. mpv tries to use hardware acceleration, but the mpv is black and there's continuous DRM_IOCTL errors: Then I tried this inside /etc/mpv/mpv.conf hwdec=drm-prime drm-drmprime-video-plane=primary drm-draw-plane=overlay and the 1080p H264 starts playing fluidly with just 40% CPU (compositor off) With compositor on, I get same 40% CPU Same video glitches, with or without compositor, but I am getting hardware acceleration (although there's the hwdec unsupported message) Update: Thank you to all who helped me. I have hardware acceleration again with my opiz3 hwdec=drm is more efficient extraargs=cma=256 is needed to avoid memory allocation problems and video glitches. https://forum.armbian.com/topic/29202-orange-pi-zero-3/page/26/#findComment-222596

And it turns out that nothing can be done? For some reason, it works for everyone, but something happened to me and it doesn't work anymore.

use my works: h616.tar.xz

follow the official instructions, change these dts to user overlay, simplicifed deployment just use `sudo make install` h616.tar.xz

Currently I am running HA supervised on Debian 12 bookworm. Debian boots from USB drive without any issue. So your suggestion should work I believe. Thanks for the suggestion. You are quick as always to reply.

This should have been addressed: https://github.com/armbian/linux-rockchip/pull/373 May take a while until an updated kernel is available via apt. You can always build a up-to-date package by yourself using the build framework.

Thank you for your generous offer, @coroner21. I am interested and would love to use this unit to keep it supported in Armbian Core. My goal would be to help keep it at standard supported status. I was already able to lift the BPi M2+ from community to standard support status. I have sent you a PM.

Thank you for sharing your success story for the benefit of everybody.

I cannot verify your claim that Ubuntu "reverted" to Gnome v44. Noble has v44 indeed. v46 is not anywhere in a Ubuntu release so my guess is you shot yourself in the foot with some random PPA or whatever repo out there. https://launchpad.net/ubuntu/+source/meta-gnome3 There is no shortage of boards out in the wild, nobody would think that. What there is, is a shortage of people willing to fund development, be it users or companies. Big shout out to those who do and to our volunteer devs, thank you!