[Bug]: Failed to apply patch /mnt/c/Users/mevep/armbian-build/cache/patch/kernel-drivers/sha1_***_rockchip64_edge_***.patch

[mevepe]

What happened?

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 24H2
• Ubuntu 24.04.2 LTS under WSL2 (fully updated & upgraded)
• Docker Desktop 4.43.2 (199162)

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

How to reproduce?

Run Windows Terminal and do these steps:

1. wsl
2. git clone https://github.com/armbian/build
3. cd build
4. ./compile.sh BOARD=orangepi5-plus BRANCH=edge PREFER_DOCKER=no KERNEL_GIT=full DEBUG=yes kernel-patch

Branch

main (main development branch)

On which host OS are you running the build script and observing this problem?

Ubuntu 24.04 Noble

Are you building on Windows WSL2?

• Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Hey @mevepe! 👋

Thanks for opening your first issue with the Armbian project — we’re glad to have you here! 🧡
Your input doesn’t just help us improve the project — it benefits everyone who uses Armbian.

If you'd like to stay informed about project updates or collaborate more closely with the team,
you can optionally share some personal contact preferences at armbian.com/update-data.
This helps us keep in touch without relying solely on GitHub notifications.

Also, don’t forget to ⭐ star the repo to support the work — and welcome aboard! 🚀

[github-actions]

Jira ticket: AR-2714

[igorpecovnik]

Thanks!

@rpardini this related to special kernel or we see something new?