Endian

Just for the reference of others who are currently running the legacy 5.10.160 kernel and wanting to switch to kernel 6.7 (As this is not currently selectable in armbian-config >> System >> Other "Switch to other kernels"
 
Note that I tested this on a clean sd card install of Armbian Bookworm CLI with kernel 5.10
 
Here is what I did:
sudo apt install linux-image-edge-rockchip-rk3588 linux-dtb-edge-rockchip-rk3588 linux-u-boot-orangepi5-edge sudo reboot  
After reboot, uname -a now reports: 
Linux orangepi5 6.7.0-rc1-edge-rockchip-rk3588 #1 SMP PREEMPT Mon Nov 13 00:19:07 UTC 2023 aarch64 GNU/Linux  
Thanks very much armbian team for an excellent distribution.

I can assure you ZFS from Arbmian repo works perfectly fine. We are using it on two production grade servers.
 
odroidhc4:~:# modinfo zfs filename: /lib/modules/6.0.12-meson64/updates/dkms/zfs.ko.xz version: 2.1.6-0york1~22.04  

I just found a very interesting talk by Sebastian Reichel who works with hardware enablement of the RK3588 at Collabora in this video between 06:52:09 to 07:27:07 which I can recommend for those interested in the Collabora project for Rockchip.  Now also available here https://kernel-recipes.org/en/2023/schedule/getting-the-rk3588-soc-supported-upstream/ 
 

Without knowing what you did exactly, the following creates a bootable image.
 
./compile.sh BOARD=rock-5b BRANCH=collabora RELEASE=bookworm KERNEL_CONFIGURE=no BUILD_MINIMAL=no BUILD_DESKTOP=no COMPRESS_OUTPUTIMAGE=img BOOTSIZE=512  
You may also need to clear whatever is in your SPI flash. 

@SteeMan Thanks. no I did not.
 
I was just compiling one with that now. Using this post as a reference point.
 
I also made a mistake above (which I will delete and re-post if this all works) as I accidently put the dts files in arch/arm/boot/dts instead of arch/arm64/boot/dts/rockchip/.

Nothing. Everything you need is in the image. Just write to the SD card and run. Important - if a bootloader is installed in SPI\MTD, it must maintain the correct startup order, or it has been removed.
 
For reference, RK has three levels of startup order control
1. Hardware, you cannot change it (SPI\NOR\MTD, SD, eMMC).
2. The primary boot loader level (can be set when building u-boot).
3. The level of the "secondary" loader in the u-boot itself (can be set when building u-boot).
 
 

Are you sure about that? IIRC it was SPI, eMMC and microSD last.
See page 30 at https://www.t-firefly.com/download/Firefly-RK3399/docs/TRM/Rockchip RK3399TRM V1.3 Part1.pdf
I know this is for RK3399 but I assume Rockchip did not reconsider their boot order in the mean time?

Not necessarily. It depends on what is on the eMMC. The order you described would work only if there is a boot loader on eMMC that checks for microSD presence and points there if found.
 
If however the boot loader on eMMC is dumb and doesn't care about other bootable devices it just runs through, which can be a big issue if the eMMC module cannot disabled or removed from the board.
 
I faced a similar issue long time ago when I had a pinebook pro in my collection.
The fixed boot order of rk3399 is SPI, eMMC, SD. RK3588 might be similar. This default behavior cannot be altered, only worked around by telling the boot loader, that is going to be flashed to SPI or eMMC, to look for microSD first.

Problem solved. It was a DNS issue.

But my point is that this bleeding edge version works better than the main build based on the 5.10.110 kernel. 
 
With this kernel the hdmi/DVI screen works when connected to the HDMI-2 port.
With any 5.10.110 based build it does not work on either of the ports.
On older 5.10.66 and 5.10.72 based builds it worked on both ports.
 
There are a couple of forum threads about this, but no solution.