Thanks, @WINEDS. I see you guy's are all over it, have at least the Ethernet sorted, and hints on the path to WiFi. I found an AllWinner CPU board from Radxa, that uses the same network peripherals as the newer H96 Max V56. The Radxa Cubie A5E is reported to feature WiFi6 and Bluetooth 5.4 using it's BLink BL-M8800DS2, which would be a step-up for me. https://docs.radxa.com/en/cubie/a5e/other-system/tina-os/build-system <- bsp, etc. Wish me luck. GBEM 👽

In the meantime, I spotted the pending MR from https://github.com/tmshlvck for this in the Pull Request Backlog. There are a number of issues with that, besides that it's very similar. Adding *.deb from xunlong without review is (mmm), better stay away from this. I'm not sure if the camera *.json is required. Not anything from the xunlong tree needs to be copied probably. I cleaned out my version (see https://github.com/sven-ola/armbian-build/tree/orangepi-rv2), but while this is open since October, I postpone to trigger another MR on that issue. My goal is: boot from upper 2230 SSD and use lower M.2 for Wifi (there are cheap Mediatek 3-band Wifi cards with 2280 adapter). If anyone wants similar setup, just checkout my branch from the link above and: ./compile.sh BOARD=orangepirv2 BRANCH=current RELEASE=trixie KERNEL_CONFIGURE=no BUILD_MINIMAL=yes KERNEL_GIT=shallow Write output/images/*.img to SD and boot with that. Use armbian-install to copy boot cfg on MTD. Again copy that *.img to /dev/nvme0n1. Remove SD card, reboot board. While investigating, there are a number of hints that the Ky X1 is in fact a SpacemiT K1 variant. Maybe stripped down, since the RCPU firmware (esos.elf) is much smaller. I have noticed, that Xunlong is not exactly welcome here. Chinese difficulties with the words upstream and donation probably. I think the hard work is to maintain / port the kernel and u-boot code drops with future versions. On the other hand: this board is cheap, offers a way to practice with a new CPU arch, and has the expected minimum number of M.2 slots. I'm currently compiling a kernel on that board. ETA 3 hours or so, board is not very fast. Anyhow, temp stays below 80°C if operated upright (above foto). No unusual hotspots, board and RAM seems stable, wifi and ethernet works. HTH and LG // Sven-Ola

What is booted also depends on boot scripts (and what is in armbianEnv.txt). This might have changed. And also the U-Boot code on the SD-card (sits invisible between partition table and 1st partition, usually sector 34-32767) might be newer and assume other defaults, I don't know. You need serial console cable and loglevel set to 7 so you can see what is happening after power-on. But maybe something else is wrong, at least make sure you post relevant info here on the forum. You can look in /usr/lib/u-boot/platform_install.sh to see where U-Boot is written. Also if you look there you can find some version string, likely in your mtd0/SPI is older than on the SD-card.

Hm... I never had such problems before. As far as I know, U-boot always overrides SPI as soon as bootable SD-card is inserted. How can I reach U-boot on SD-card if Armbian installation has been interrupted and not finished? When I insert such raw SD-card I do not see there any partitions applicable for mounting... My apologies for silly questions)))

I failed to run DaveTheDiver using these settings: PanVk-mesa 26.0 + wine-Proton-10.0.3 + Dxvk 2.7.1(stripped) the log shows: Unsupported ioctl 74080 Faking StorageDeviceProperty data Is FEX or DXVK 1.7.1 is a must ?