Werner

That's what you get with bleeding edge. Use vendor if you need stuff working. Here is great overview of what is working in mainline: https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md

I guess the patch has not been carried over to 6.12 since the folder is empty: https://github.com/armbian/build/tree/main/patch/kernel/archive/imx6-6.12

Yes. Tools like etcher or USBimager can decompress images on-the-fly. dd cannot do that. Latter since the image may already contain partitions, depending on board. Not really. If it is big enough to fit the image it is good enough. However microSD cards with bigger size are usually a lot faster as well. I personally use and can recommend sandisk extreme (the golden ones) with either 32G or 64G capacity. Too large is also possible since the SoCs may have a limit. So if your SD card is 2TB or something...try something a little smaller it never occurred to me that I had to install any kind of dependency to use it. Strange. Maybe there is another option available: https://gitlab.com/bztsrc/usbimager

known issue. its being worked on. Retry in a few days.

Of course, dd works too. The major issue with using this though is the lack of verification. While rare either dd or the target device can cause issues which are not detected while writing but when trying to read from the written device. USBimager and others like etcher verify all written data to make sure there is no issue. So if you run into weird hard to explain troubles, this could be a reason. arm64 download: https://gitlab.com/bztsrc/usbimager/-/blob/binaries/usbimager_1.0.10-aarch64-linux-x11.zip

I think this is part of the ramlog service. To reduce wear on microsd cards stuff is logged into memory and periodically written to sd. Since you are using a nvme this can be disabled. Check /etc/default/armbian-... files.

Wireguard is shipped by default with almost all Armbian images. Simply do code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } sudo modprobe wireguard All you need is wireguard-tools which can be installed with --no-install-recommends to avoid unnecessary bloat/dependencies.

Ah. I guess nobody ported the overlays from old bsp over yet. Well also nobody was asking for them yet either lol Anyway this may work with "modern" bsp too: /dts-v1/; /plugin/; / { fragment@0 { target = <&spi3>; __overlay__ { status = "okay"; spidev@0 { compatible = "rockchip,spidev"; status = "okay"; reg = <0>; spi-max-frequency = <50000000>; }; }; }; };

How do you connect a NVMe to this board? Never mind. Wrong prefix. Anyway you need boot loader present on either spi, emmc or sd. Direct boot from nvme isnt possible.

No clue, sorry. I never actually used i2c

Hm vendor seem lacking all rk356x overlays except rk3566-roc-pc-sata2.dtbo. Need to check current. Edit: current and edge only have a few more but also none spi related for rk3566. Odd...

rockchip bsp kernel has recently been bumped to 6.1.99. Maybe things run smoother using it. You can use the build framework to create a set of kernel package to install via dpkg. Or use armbian-config to switch to beta repo which should also have it.

Can you provide me with the output of code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ls /boot/dtb/rockchip/overlay ?

Check /boot/armbianEnv.txt overlays=i2c1 i2c2 rockchip-rk3399-i2c7 Try this instead: overlays=i2c1 i2c2 rk3399-i2c7

Armbian is evolving rapidly, now supporting an ever-growing list of single-board computers (SBCs) - each with unique hardware, kernels, and configurations. As the variety of supported boards expands, so does the complexity of troubleshooting and providing effective user assistance. To keep up with this demand, we’re raising 5,000 EUR to hire part-time support agents who can help manage this increasing workload and ensure high-quality support for the community. Read more: https://forum.armbian.com/crowdfunding/project/16-help-armbian-grow-support-join-our-team/

moved

My guess is that there is no npu driver upstreamed yet. Try vendor kernel

moved

moved

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

If you run from sdcard, put it into an existing system and make necessary adjustments. Easiest would be to use another arm64 based computer since you can simply chroot into your sdcard and use armbian-config to switch back to stable.

moved to userspace

Try these: https://fi.mirror.armbian.de/.testing/Armbian-unofficial_25.02.0-trunk_Orangepizero_bookworm_legacy_6.1.104_minimal.img.xz https://fi.mirror.armbian.de/.testing/Armbian-unofficial_25.02.0-trunk_Orangepizero_bookworm_edge_6.12.9_minimal.img.xz

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Not for mainline. HDMI implementation is incomplete and still WIP. If you need other resolutions vendor kernel is the way to go for now.