1) Language. Either I expressed myself incorrectly or I was misunderstood, but my communication on this forum will most likely proceed as follows: My message in Russian -> Translator -> My message in English And the same in reverse order. 2) A little information about me. I'm a school student, so I'm unlikely to understand any of the high-tech terms. 3) AI If it helps, here's the most productive thread of conversation with Deepseek: https://chat.deepseek.com/share/20dl6vpqy97gpu4et4 4) DTBO and DTS Thanks to AI, almost every new version of dts had a new name, but they all seemed to compile to dtbo with the same name. I'm thinking of finding one that can produce a gradient, but I haven't succeeded yet, and I haven't tried everything. I don't know what color it should be, but mine was a white-to-black gradient. I'll also attach a Python script for it. I didn't create it separately, but wrote it directly into the SSH console (as far as I understand). 5) Raspberry Pi I have a primary 32 GB SD card, which I've been using since installing Klipper on my 3D printer. I also have a spare 64 GB SD card, which I installed MainsailOS, KlipperScreen, and added printer.cfg to. Initially, when I tried using ready-made libraries, I used the primary card, and even used it for a few attempts with AI. But then I switched to a second (spare) card, so that if I messed up the firmware or made any irreparable changes, I could reinstall the OS, reset it to its original state (as mentioned at the beginning), and then repeat all the necessary operations from the beginning. It's probably best to record all your steps somewhere so that after successfully setting up the screen on the spare card, you can repeat the necessary steps on the main card. Just in case, I'll save the current config.txt and all created dts files on my PC. 6) Display I'm attaching a photo of my display and another from the product page on AliExpress. I already have it soldered into the Raspberry Pi. During my attempts, I soldered from spi1 to spi0 and back maybe five times. But I'm tired of this and want to stick with the current pinout with spi1, since I have two more accelerometers on spi0, which I desoldered while setting up the display. 7) Display nuance During the first connection, I slightly damaged the solder mask of the ground plane near the positive contact of the display with a soldering iron and shorted it out with solder. I thought something on the display was broken, so I desoldered and checked some components (the microcircuit, capacitors, and resistor), but they were intact. It was only later that I discovered the real problem. After solving the problem, I connected the 5-volt power supply, but after a couple of hours, I decided to switch it to 3.3 volts just in case. I can switch it back to 5 volts if necessary. I hope this short-circuit situation didn't affect the operation in any way. If this is helpful, I've attached all the DTS versions I currently have; they can be opened in Notepad++. When I find the one that produces the gradient, I'll edit this post or write a new one. test_display.txt ili9488-debug.dts ili9488-fixed.dtbo ili9488-fixed.dts ili9488-fixed-gpio.dts ili9488-full-init.dts ili9488-priority.dts ili9488-test.dts ili9488-test-18bit.dts ili9488-test-bgr.dts ili9488-test-reg36.dts ili9488-test-rotate.dts ili9488-working.dts ili9488-xpt2046.dts ili9488-64bit.dts ili9488-correct-horizontal.dts

A long time ago, I made an armbian guide, which included adding a kernel patch. Can you try this method? "Move them* to ~/armbian-2023.05/build/userpatches/kernel/archives/sunxi-6.1 (using the scp command or sshfs)" * would mean the cpio file (use diff3 to convert to patch file**) and any linux configuration patches needed to make your initramfs. ** diff3 linux_orig_source_folder linux_source_folder_with_cpio_file https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md#73-add-the-tv-encoder-driver-to-the-linux-kernel-source

This unit on Armbian has bigger problems than the Ethernet not coming up. such as: I believe that stems from the current U-Boot being used. If I flash mine and use my DTS that comes up correctly and the ethernet. Sorry but bringing this unit up to snuff would take more time than I'm currently willing to put in right now. If a window opens up in the future, I'll look into it.

So far I only have working ethernet, which is good enough probably. So, hdmi, wifi, audio, gpu are not working. Is there anything I can do to fix any of these? Install some firmware, edit the dtb or something?

Hello @brunorro, I have uploaded two images to https://privat-in.de/ (navigate to downloads, grab Armbian*.img). Simply post findings here. The "edge" image is rather unstable, e.g. my NVME gives a read-error while working fine with "current", while a Mediatek Wifi card seems to work. Probably no easy task, could be anywhere in the IOMMU - DMA - PCIe triangle. The images are compiled from https://github.com/sven-ola/armbian-build/tree/orangepi-rv2 kernel with defaults plus switched on every Mediatek Wifi driver module. Here's my Todo for ref (+ marks ok): To be merged + Boot from SSD (upper+lower) + SPI NOR flash boot / install + SD/TF speed too slow (15mb/s) - Check SD UHS in uboot speed limit + Brcm SDIO wifi not working - Armbian edge: Brcm SDIO Wifi - Armbian edge: PCIe NVME IOErr + Bluetooth not working - RTL ethernet (2.5gbit R2V board?) - Ky overlay dtbo's missing - Focaltech touch driver from Ky? - Ky MIPI/CSI cam modules - What is that realtime r_uart? - GPU? USB2-OTG? USB3? Sound? Personal wishlist: - Device-mapper / dm_era missing + Mediatek PCIe wifi modules - PCIe adapter: Radeon GPU test Ah, yes. OpenWrt is on the Ky list of supported systems. I have a personal history on that too. While getting rid of systemd may be not that difficult (see Devuan) exchanging libc is another beast probably. LG // Sven-Ola