04:47 <DC-IRC> [Discord] <Github> ✅ **Merged** into [armbian/documentation](<https://github.com/armbian/documentation>) by [EvilOlaf](<https://github.com/EvilOlaf>) - [Link](<https://github.com/armbian/documentation/commit/b045a72d2b4e9a72c54cb047c89e2f659616cee6>): *Remove a couple of question marks (#555)*

06:40 <DC-IRC> [Discord] <Github> ✅ **Merged** into [armbian/documentation](<https://github.com/armbian/documentation>) by [igorpecovnik](<https://github.com/igorpecovnik>) - [Link](<https://github.com/armbian/documentation/commit/d94e507bc9e1c2a6d0b39dd2dff2951c43aeeb0a>): *Fix wrongly named release months*

09:32 <DC-IRC> [Discord] <Github> ✅ **Merged** into [armbian/build](<https://github.com/armbian/build>) by [igorpecovnik](<https://github.com/igorpecovnik>) - [Link](<https://github.com/armbian/build/commit/08e7bba4f61c250a2ef6111ce72a7623896f9cea>): *extensions: image-output-abl: set rootfs image larger for kde*

12:16 <DC-IRC> [Discord] <evgeniyzh> I'm trying to run kernel 6 on MangoPi (allwinner d1) but the kernel is unable to register memory:

12:16 <DC-IRC> [Discord] <evgeniyzh> ```

12:16 <DC-IRC> [Discord] <evgeniyzh> [ 0.000000][ T0] memblock_cap_memory_range: No memory registered yet

12:16 <DC-IRC> [Discord] <evgeniyzh> [ 0.000000][ T0] INITRD: 0x5f2fe000+0x00d02000 is not a memory region - disabling initrd

12:16 <DC-IRC> [Discord] <evgeniyzh> [ 0.000000][ T0] OF: reserved mem: 0x0000000040000000..0x000000004003ffff (256 KiB) map non-reusable mmode_resv0@40000000

12:16 <DC-IRC> [Discord] <evgeniyzh> [ 0.000000][ C0] ------------[ cut here ]------------

12:16 <DC-IRC> [Discord] <evgeniyzh> [ 0.000000][ C0] kernel BUG at arch/riscv/mm/init.c:1283!

12:16 <DC-IRC> [Discord] <evgeniyzh> [ 0.000000][ C0] Kernel BUG [#1]

12:16 <DC-IRC> [Discord] <evgeniyzh> ```

12:16 <DC-IRC> [Discord] <evgeniyzh> (full log -- https://pastebin.com/8NwMYGHA). I've tried mainline 6.11 and 6.7 and also 6.1 from the current config. Any ideas on how I can debug this one?

13:34 <DC-IRC> [Discord] <igorpec> Try uefi risv64 builds. They might work

16:29 <DC-IRC> [Discord] <prahal> how do you edit a patch file? I want to add one line in the middle of patch/kernel/archive/rockchip64-6.12/add-board-helios64.patch, how should I proceed to update all the "initial patch" diff line references after my change "@@ -296,6 +502,11 @@ &gmac {" to cope with the newly added or removed line? Edit by hand one by one (adds a lot of noise)? Or test if the patch still apply <clipped message>

16:29 <DC-IRC> [Discord] <prahal> with the wrong line numbers and only change them if it don't apply anymore?

16:31 <DC-IRC> [Discord] <prahal> or make a separate patch for my fix and one for the line changes?

16:45 <DC-IRC> [Discord] <Werner> I think its safer to create a separate patch, like using `kernel-patch` method.

17:05 <DC-IRC> [Discord] <superkali> Correct

17:51 <DC-IRC> [Discord] <prahal> thanks. I am a bit surprised by this option though, because all the commit in patch/kernel/archive/rockchip64-6.12/ edit existing patch files instead of creating new ones

18:01 <DC-IRC> [Discord] <prahal> but I admit I found it pretty hackish to edit the patch files by hand. But I only saw two armbian patch file that were patching another armbian patch file, both from the same author 4 years ago, and I only kept them so because I was not convinced they were good patches so preferred to keep them out of the main patch (board-helios64-dts-fix-stability-issues.patch and board-helios6 <clipped message>

18:01 <DC-IRC> [Discord] <prahal> 4-remove-pcie-ep-gpios.patch: ie the stability fix does the opposite of what it is documented as ie it speed up transitions and the pcie-ep-gpios one I do not understand and no rationale for it was provided).

18:05 <DC-IRC> [Discord] <prahal> ie I already use kernel-patch to cook patch and test them. But I am about to submit a PR and none of the PR I know of provides kernel-patch cooked code. It always puzzled me. Can you confirm kernel-patch patches are indeed the way to go for PR against Armbian main?

18:54 <DC-IRC> [Discord] <superkali> Yes, but after it you've to do rewrite-kernel-patches for optimize the patch

18:54 <DC-IRC> [Discord] <superkali> and after it make a PR