Werner

If desktop version supports HDMI then CLI and minimal do as well.

1. Not using CP2102 as it cannot handle 1.5mbaud. CP2104 for example does. 2. not using random UART you find on the GPIO but using the actual debug UART connectors: https://wiki.friendlyelec.com/wiki/images/7/7c/NanoPi_NEO3-layout.jpg 3. @lpirl can be right too. I used to own a Neo3 just like yours but it died on me.

Oddly there are no bcm2712 packages whatsoever in stable repo. At least not on my mirror. However there are current and edge packages in beta including headers. 13236 ./pool/main/l/linux-headers-current-bcm2712/linux-headers-current-bcm2712_24.2.0-trunk.480_arm64__6.6.13-S374f-D719f-P0000-Cb2aaH4168-HK01ba-Vc222-B4d80-R448a.deb 25531 ./pool/main/l/linux-6.6.13/linux-image-current-bcm2712_24.2.0-trunk.480_arm64__6.6.13-S374f-D719f-P0000-Cb2aaH4168-HK01ba-Vc222-B4d80-R448a.deb 120 ./pool/main/l/linux-dtb-current-bcm2712/linux-dtb-current-bcm2712_24.2.0-trunk.480_arm64__6.6.13-S374f-D719f-P0000-Cb2aaH4168-HK01ba-Vc222-B4d80-R448a.deb

moved

Yes, it is relevant. Without an sdcard with operating instructions (boot loader and OS to say) the board simply does absolutely nothing since there is no other storage on.

Use legacy if you need those. Do not run bleeding edge stuff if you don't know how to deal with such issues.

I don't know. However using the serial console you get an idea if the board is the issue or your usb-ethernet adapter.

Your baudrate is wrong. Try 115200 instead of 15200 as suggested in the video.

serial console is best way to debug boot and connectivity issues: https://debug.armbian.de

https://debug.armbian.de

SSH is always enabled by default. However I remember there is a rare case where sshd cannot start properly for some reason. serial console is the best way to debug this (and restart sshd) Buy a few extra. They are dirt cheap

Usually the filesystem expands itself across the whole sdcard on first boot...odd.

no

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

As long as you do not redistribute an image with built-in ZFS no. https://docs.kernel.org/admin-guide/tainted-kernels.html

Whole documentation is needs updates. Like all the build switches (kernel, kernel-config, uboot,...) are missing...

RK3588 support in mainline is still very basic/experimental.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. Try installing armbian-firmware-full via apt

Player left the game. Case closed.

for legacy: https://forum.armbian.com/topic/25590-problems-installing-zfs-dkms-config_modules-not-enabled/?do=findComment&comment=179556

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

https://openzfs.github.io/openzfs-docs/Developer Resources/Building ZFS.html [ 424.596656] zfs: module license taints kernel. [ 425.491531] ZFS: Loaded module v2.2.99-311_gd9cb42da9, ZFS pool version 5000, ZFS filesystem version 5 tested on OPi5 with kernel 6.7.1 Getting it working on legacy 5.10.y rk Android-hackedtogether kernel is a bot tougher. https://github.com/radxa/kernel/issues/54 Spoiler: patching method does not work anymore, at least not for me . Tested with 5.10.160...

Try installing from scratch: https://openzfs.github.io/openzfs-docs/Getting Started/index.html

So this is more or less a feature request. Therefore moved.