All Activity

I should have mentioned, I tried fsck on loop device and it was fine. It's what I cannot understand. In my script after writing the image I read it back and compare with the source: dd status=progress if=Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img of=/dev/sdc bs=1M conv=fsync 2032140288 bytes (2.0 GB, 1.9 GiB) copied, 79 s, 25.7 MB/s2034237440 bytes (2.0 GB, 1.9 GiB) copied, 79.2902 s, 25.7 MB/s Reading image from disk ... dd status=progress if=/dev/sdc of=Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img.from-disk bs=1M count=1941 2032140288 bytes (2.0 GB, 1.9 GiB) copied, 127 s, 16.0 MB/s They are equal in size. Produce same SHA hash: $ sha256sum Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img* ab74fc6f34f4f235ca224bc8d282feb1acf94cfe56bdf0b93c21894838ea0c71 Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img ab74fc6f34f4f235ca224bc8d282feb1acf94cfe56bdf0b93c21894838ea0c71 Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img.from-disk Tried also simple cmp on image file and SD card: $ sudo cmp Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img /dev/sdc cmp: EOF on Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img after byte 2034237440, in line 14175730 See, after byte 2034237440, so the 2034237440 bytes are equal on disk and on the SD card, .img is 2034237440 bytes of size: $ stat Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img File: Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img Size: 2034237440 Blocks: 1643993 IO Block: 131072 regular file $ sudo -fn /dev/sdc1 gives FS errors, hundreds of "Unattached inode" and such. Pass 5: Checking group summary information armbi_root: ********** WARNING: Filesystem still has errors ********** armbi_root: 64131/123136 files (0.1% non-contiguous), 441689/492539 blocks Voodoo? 😉 A spare SD card anyone to try it: 🙂

My intention is not to put the whole desktop on the display. Just a user application. I am trying to build a thermostat and might use LVGL for it. I tried a similar project on 256MB and still had plenty of RAM left.

As of 2025-12-01, current 'Armbian 25.11.1 Trixie Minimal / IOT' lists as 'Kernel: 6.12.58, Size: 505 KB, Release date: Nov 22, 2025' and seems to have had problems on image generation. Please check when possible. Thanks in advance, pbg

See https://wiki.luckfox.com/Luckfox-Lyra/Pinout and connect USB serial console cable You should see then what is going on and post that here.

At this time, panel-mipi-dbi is the most universal way of using these SPI LCDs. Even the Raspberry community gets this recommendation (except for Waveshare LCDs). Bhupiister, does the MilkV Duo S really have 512MB RAM? How do you deal with that? I have used an orange pi zero LTS with 512MB of RAM with LXDE desktop in the past, but only with lightweight GUI applications. Does it really have a useful TPU?

Making it work with panel-mipi-dbi is completely new to me. I hope ill be able to make sense out of it.

There's a 4 inch RED ili9488 in aliexpress. VERY RECOMMENDED. It may be shown as ili9486, correctly or incorrectly, but it doesn't matter. I have seen both ili9486 and ili9486 work with the same panel-mipi-dbi driver, settings and init firmware. At least in orange pi zero 3, some pins worked fine for GPIO and others didn't. Also make sure to use the default chip selects in your MilkV Duo 5, and not try to change that. Also share what Armbian and Linux version you are using.

See my 'dry' test: # cat Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img.xz.sha 80ffb7486a9d9950c2613f42be520c4086d4a3b894da4fd46a07120ecd9ddb30 Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img.xz # sha256sum -c Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img.xz.sha Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img.xz: OK # xzcat Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img.xz > Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img # losetup --show -fP Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img /dev/loop0 # sudo fsck -f /dev/loop0p1 fsck from util-linux 2.41 e2fsck 1.47.2 (1-Jan-2025) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information armbi_root: 64131/123136 files (0.1% non-contiguous), 441689/492539 blocks # losetup -d loop0 So can't reproduce. I won't write it to real SD-card and then do the fsck. You can try this first, so via loop device. My computer is Armbian Trixie edge 6.18.0-rc7 NanoPi-R6C, .xz file downloaded on N100, so could also done it there, does not matter Ext4 is Ext4.

@robertoj My objective is MilkV Duo S with Waveshare ili9486 LCD, and it will be much better if I can use ST7796, as this is a 4-inch display. I need to make at least a 4-inch display work for my project. It can be any readily available display.

Deactivate spi-dev in the armbian-config. That DTS is only used if you want to run a userspace program to talk to the LCD. In this case, we want the linux kernel to talk to the LCD, so we only need to use the LCD driver (ideally not a FBTFT. DRM is preferred)

@РобертсSorry, I didn't have time to read your reply. I tried Pancake's instructions, but I got stuck at the Armbian image build stage. Would his method work on the Armbian image that comes with the Orange Pi Zero3 board? I think I've figured out which pins I need to solder so I don't have to change the GPIOs in the file, as I'm not very good at deciphering pins for configuration. Thank you very much for the information and your efforts. I'll try to give it a try tomorrow and give you an answer.

I tried two methods with ili9341 and ili9488 with 9341, when checking SPI, it returned the log below. The second method showed that spi-dev0.0 is my FullHD HDMI display. After turning it on, SPI-dev detected the connection, but the screen was still white. True, I didn’t change the rotate line for 9488 I soldered the pins according to the DST file /* OrangePi Zero 3 -> ILI9341 LCD connections SPI CLOCK = PH6 SPI DO (LCD MISO) = PH8 (OPIZ MISO) SPI DI (LCD MOSI) = PH7 (OPIZ MOSI) LCD DATA/CONTROL = PC8 LCD RESET = PC10 CHIP SELECT = PH9 < NOT USED ANYMORE ;) VCC = 3.3V PIN GND = GND PIN */ /dts-v1/; /plugin/; /{ compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { target = <&pio>; __overlay__{ display_pins: display_pins { pins = "PC8", "PC10"; /* DC, reset pins*/ function = "gpio_out", "gpio_out"; }; }; }; fragment@1 { target = <&spi1>; __overlay__ { /* needed to avoid dtc warning */ #address-cells = <1>; #size-cells = <0>; status="okay"; pinctrl-names = "default"; pinctrl-0 = <&spi1_pins>; /* Mux the PI to make sure they are set in spi Mode */ /*cs-gpios = <&pio 0 13 0>; /* PA13 chip select NOT USED! */ num-chipselects = <0>; display: display@0 { compatible = "ilitek,ili9341"; /*compatible = "ilitek,ili9488";*/ reg = <0>; pinctrl-names = "default"; pinctrl-1 = <&display_pins>; spi-max-frequency = <40000000>; rotate = <270>; /* rotate for ili9341, rotation for yx240qv29 */ bgr=<0>; fps = <15>; buswidth = <8>; height = <320>; width = <240>; reset-gpios = <&pio 2 10 0>; /* PC10 reset pin*/ dc-gpios = <&pio 2 8 0>; /* PC8 Data control pin */ debug = <3>; init = <0x10000b0 0x00 0x1000011 0x20000ff 0x100003a 0x55 0x1000036 0x28 0x10000c2 0x44 0x10000c5 0x00 0x00 0x00 0x00 0x10000e0 0x0f 0x1f 0x1c 0x0c 0x0f 0x08 0x48 0x98 0x37 0x0a 0x13 0x04 0x11 0x0d 0x00 0x10000e1 0x0f 0x32 0x2e 0x0b 0x0d 0x05 0x47 0x75 0x37 0x06 0x10 0x03 0x24 0x20 0x00 0x10000e2 0x0f 0x32 0x2e 0x0b 0x0d 0x05 0x47 0x75 0x37 0x06 0x10 0x03 0x24 0x20 0x00 0x1000036 0x28 0x1000011 0x1000029>; }; }; }; __overrides__ { rotate = <&display>,"rotate:0"; fps = <&display>,"fps:0"; debug = <&display>,"debug:0"; }; }; user@orangepizero3:~$ dmesg|grep spi [ 1.899568] sun6i-spi 5011000.spi: chipselect 0 already in use [ 1.899578] spi_master spi1: spi_device register error /soc/spi@5011000/spidev@0 [ 1.899601] spi_master spi1: Failed to create SPI device for /soc/spi@5011000/spidev@0 [ 6.735454] SPI driver fb_ili9341 has no spi_device_id for ilitek,ili9341 [ 6.735562] fb_ili9341 spi1.0: fbtft_property_value: width = 240 [ 6.735571] fb_ili9341 spi1.0: fbtft_property_value: height = 320 [ 6.735577] fb_ili9341 spi1.0: fbtft_property_value: buswidth = 8 [ 6.735583] fb_ili9341 spi1.0: fbtft_property_value: debug = 3 [ 6.735589] fb_ili9341 spi1.0: fbtft_property_value: rotate = 270 [ 6.735595] fb_ili9341 spi1.0: fbtft_property_value: fps = 15 [ 6.735669] fb_ili9341 spi1.0: fbtft_gamma_parse_str() str= [ 6.735674] fb_ili9341 spi1.0: 1F 1A 18 0A 0F 06 45 87 32 0A 07 02 07 05 00 [ 6.735764] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'reset' GPIO [ 6.735785] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'dc' GPIO [ 6.735805] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'rd' GPIO [ 6.735820] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'wr' GPIO [ 6.735834] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'cs' GPIO [ 6.735849] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'latch' GPIO [ 6.735864] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.735879] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.735894] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.735909] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.735924] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.735938] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.735953] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.735968] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.735982] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.735997] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736013] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736049] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736064] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736078] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736101] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736116] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736131] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736146] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736161] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736176] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736212] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736227] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736242] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736256] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736271] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736286] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736301] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736315] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736330] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736345] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736360] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736375] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736389] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736404] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736419] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736434] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736449] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736463] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736478] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736493] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736507] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736522] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736537] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736552] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736567] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736581] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736596] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736610] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736616] fb_ili9341 spi1.0: fbtft_verify_gpios() [ 6.736627] fb_ili9341 spi1.0: fbtft_reset() [ 6.864274] fb_ili9341 spi1.0: init: write_register: [ 6.864300] fb_ili9341 spi1.0: buf[0] = B0 [ 6.864306] fb_ili9341 spi1.0: buf[1] = 00 [ 6.864541] fb_ili9341 spi1.0: init: write_register: [ 6.864546] fb_ili9341 spi1.0: buf[0] = 11 [ 6.864568] fb_ili9341 spi1.0: init: msleep(255) [ 7.144245] fb_ili9341 spi1.0: init: write_register: [ 7.144271] fb_ili9341 spi1.0: buf[0] = 3A [ 7.144281] fb_ili9341 spi1.0: buf[1] = 55 [ 7.144365] fb_ili9341 spi1.0: init: write_register: [ 7.144370] fb_ili9341 spi1.0: buf[0] = 36 [ 7.144375] fb_ili9341 spi1.0: buf[1] = 28 [ 7.144410] fb_ili9341 spi1.0: init: write_register: [ 7.144414] fb_ili9341 spi1.0: buf[0] = C2 [ 7.144419] fb_ili9341 spi1.0: buf[1] = 44 [ 7.144447] fb_ili9341 spi1.0: init: write_register: [ 7.144452] fb_ili9341 spi1.0: buf[0] = C5 [ 7.144456] fb_ili9341 spi1.0: buf[1] = 00 [ 7.144461] fb_ili9341 spi1.0: buf[2] = 00 [ 7.144466] fb_ili9341 spi1.0: buf[3] = 00 [ 7.144470] fb_ili9341 spi1.0: buf[4] = 00 [ 7.144519] fb_ili9341 spi1.0: init: write_register: [ 7.144524] fb_ili9341 spi1.0: buf[0] = E0 [ 7.144529] fb_ili9341 spi1.0: buf[1] = 0F [ 7.144533] fb_ili9341 spi1.0: buf[2] = 1F [ 7.144537] fb_ili9341 spi1.0: buf[3] = 1C [ 7.144542] fb_ili9341 spi1.0: buf[4] = 0C [ 7.144547] fb_ili9341 spi1.0: buf[5] = 0F [ 7.144551] fb_ili9341 spi1.0: buf[6] = 08 [ 7.144555] fb_ili9341 spi1.0: buf[7] = 48 [ 7.144560] fb_ili9341 spi1.0: buf[8] = 98 [ 7.144564] fb_ili9341 spi1.0: buf[9] = 37 [ 7.144569] fb_ili9341 spi1.0: buf[10] = 0A [ 7.144574] fb_ili9341 spi1.0: buf[11] = 13 [ 7.144579] fb_ili9341 spi1.0: buf[12] = 04 [ 7.144583] fb_ili9341 spi1.0: buf[13] = 11 [ 7.144588] fb_ili9341 spi1.0: buf[14] = 0D [ 7.144592] fb_ili9341 spi1.0: buf[15] = 00 [ 7.144627] fb_ili9341 spi1.0: init: write_register: [ 7.144632] fb_ili9341 spi1.0: buf[0] = E1 [ 7.144636] fb_ili9341 spi1.0: buf[1] = 0F [ 7.144641] fb_ili9341 spi1.0: buf[2] = 32 [ 7.144646] fb_ili9341 spi1.0: buf[3] = 2E [ 7.144650] fb_ili9341 spi1.0: buf[4] = 0B [ 7.144655] fb_ili9341 spi1.0: buf[5] = 0D [ 7.144659] fb_ili9341 spi1.0: buf[6] = 05 [ 7.144663] fb_ili9341 spi1.0: buf[7] = 47 [ 7.144668] fb_ili9341 spi1.0: buf[8] = 75 [ 7.144672] fb_ili9341 spi1.0: buf[9] = 37 [ 7.144677] fb_ili9341 spi1.0: buf[10] = 06 [ 7.144681] fb_ili9341 spi1.0: buf[11] = 10 [ 7.144686] fb_ili9341 spi1.0: buf[12] = 03 [ 7.144690] fb_ili9341 spi1.0: buf[13] = 24 [ 7.144695] fb_ili9341 spi1.0: buf[14] = 20 [ 7.144699] fb_ili9341 spi1.0: buf[15] = 00 [ 7.144732] fb_ili9341 spi1.0: init: write_register: [ 7.144736] fb_ili9341 spi1.0: buf[0] = E2 [ 7.144741] fb_ili9341 spi1.0: buf[1] = 0F [ 7.144746] fb_ili9341 spi1.0: buf[2] = 32 [ 7.144750] fb_ili9341 spi1.0: buf[3] = 2E [ 7.144755] fb_ili9341 spi1.0: buf[4] = 0B [ 7.144759] fb_ili9341 spi1.0: buf[5] = 0D [ 7.144763] fb_ili9341 spi1.0: buf[6] = 05 [ 7.144768] fb_ili9341 spi1.0: buf[7] = 47 [ 7.144772] fb_ili9341 spi1.0: buf[8] = 75 [ 7.144777] fb_ili9341 spi1.0: buf[9] = 37 [ 7.144781] fb_ili9341 spi1.0: buf[10] = 06 [ 7.144786] fb_ili9341 spi1.0: buf[11] = 10 [ 7.144790] fb_ili9341 spi1.0: buf[12] = 03 [ 7.144795] fb_ili9341 spi1.0: buf[13] = 24 [ 7.144799] fb_ili9341 spi1.0: buf[14] = 20 [ 7.144804] fb_ili9341 spi1.0: buf[15] = 00 [ 7.144836] fb_ili9341 spi1.0: init: write_register: [ 7.144841] fb_ili9341 spi1.0: buf[0] = 36 [ 7.144846] fb_ili9341 spi1.0: buf[1] = 28 [ 7.144873] fb_ili9341 spi1.0: init: write_register: [ 7.144878] fb_ili9341 spi1.0: buf[0] = 11 [ 7.144895] fb_ili9341 spi1.0: init: write_register: [ 7.144899] fb_ili9341 spi1.0: buf[0] = 29 [ 7.180777] fb_ili9341 spi1.0: Display update: 4186 kB/s, fps=0 [ 7.181166] graphics fb1: fb_ili9341 frame buffer, 320x240, 150 KiB video

I only have RED ili9341, ili9486 and ili9488 I don't have time to look right now, but search the Raspberry Pi forum and there's a nice thread with just the RED LCDs, st77** and iliteks working with panel-mipi-dbi driver Then, when you find a solution over there, post the link here. Your objective is MilkV Duo S with Waveshare ili9488 LCD, right?

The waveshare clones may not work with panel-mipi-dbi, because these LCDs are not purely SPI. They have a SPI-to-parallel chip which allows the LCD panel to work in parallel mode. Maybe they will work, but I don't own any waveshare LCD. There's a driver inside the kernel for waveshare SPI LCDs (ILI9486_DRM or something like that), but I still haven't seen any example of anyone using it.

@robertoj What about your experience with ST7796? I have one with red pcb. Even this one is not working for me. Tried different dtb and .c files. Did this work for you ever?

Hello everyone! I need help. I was very happy to learn that Armbian support is now available for the Luckfox Lyra Ultra W! https://blog.armbian.com/github-highlights-5/ This board has 8GB of EMCC memory and the firmware needs to be loaded onto this EMCC. I went to this page in this mini guide https://github.com/armbian/build/pull/8862?ref=blog.armbian.com where is the author @vidplace7 clearly indicates how to correctly compile and install the firmware ./compile.sh BOARD=luckfox-lyra-ultra-w BRANCH=vendor KERNEL_CONFIGURE=no DEB_COMPRESS=xz KERNEL_BTF=yes INSTALL_ARMBIAN_FIRMWARE=no BUILD_DESKTOP=no BUILD_MINIMAL=yes RELEASE=trixie Boot from emmc working (write to 0x0 with rkdevtool as the generated image includes the "loader") Shell works over UART0 AIC8800DC WiFi works Ethernet works I compiled the Armbian-unofficial_25.11.0-trunk_Luckfox-lyra-ultra-w_trixie_vendor_6.1.115_minimal.img firmware without any problems and ran the RKDevTool_Release_v2.96 program. I pressed the boot button on the device and the program RKDevTool displayed a message that the Loader device was found. I checked item 2, selected emcc, the address was 0X0000000, and selected the image to flash: Armbian-unofficial_25.11.0-trunk_Luckfox-lyra-ultra-w_trixie_vendor_6.1.115_minimal.img. I pressed RUN. The flashing completed successfully. The device rebooted, and the red LED lit up for 30 seconds, then went out—and that was it. The device no longer responded and wouldn't boot. If I pressed the BOOT button afterwards, the device didn't respond and didn't enter LOADER mode. The only way to restore the device is to short two points on the rear panel and apply power. The device will be detected in RKDevTool in Maskrom mode, and you can load the factory firmware. Unfortunately, I don't know how to contact the author @vidplace7 - https://github.com/armbian/linux-rockchip/pull/418 Please tell me what I did wrong? And why does the device become bricked after reflashing? I really want to install a normal system on it!

I don't own any waveshare LCD. I am not sure what to suggest, except that I believe it will only work with a "ili9486_DRM" (can't remember the exact name) driver ko. It is made explicitly for waveshare SPI LCDSs, and you must activate within the armbian build script process.

No, it wont work. I have made another thread just for the orange pi zero 3 and ili9488 https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#comment-208446 Change the GPIOs to match your wiring and connections.

@Michael Robinson I want to make a cyberdeck with this display and this single board computer The ports are supposed to be used for connecting peripherals. That's why I want to know if my project is viable, or if I should look for something else.

This is really a strange question, Werner. fsck for filesystems like ext2/3/4 is for a purpose, no? But here you go. Normally when I install a new system, configure it to my needs and liking I make a backup image of it. To let say quickly restore after breaking the system with some "experiments" or such. Is much easier then install from scratch. As first step in this procedure i shrink the filesystem on the 1st partition which requires a fsck -f on it. Theodore's telling us to do so, he must know why 🙂 So I discovered those two images I mentioned give me filesystem errors. As there is nobody in my neighborhood messing up with Armbian, I asked here for help. If somebody could try to see if he/she reproduced my problem. Instead I was instructed what tools are recommended (by whom?) and "scolded" for using fsck. 🙂 BTW, after fsck lost+found contains several hundreds of files, most of them .c/.h from kernel source/headers. Thanks.

Alright. Trust sacrificed. BTW, I am a 71yo real estate developer, which may explain my stupidity with coding, my not being able to ascertain streams of consciousness, nor plumb huge gaps in information. I would like to get some things done with the N2+, and the answer is Armbian is obviously not the way to do them. I have much bigger things to do than bit-twiddling. PS - NTPd doesn't fix time either.

Please STOP installing android Stock ROM's in this devices It's full of malware https://www.youtube.com/watch?v=1vpepaQ-VQQ There's no malware, but you need to review all the code before using it. We're talking about Linux, the code is there, review it, don't trust it.

May I ask why you do this fsck? Is there a problem with the image like not booting?

IMO the best choice is something with hdmi port.

I do verify what is written to the SD card. It's a homegrown script I have used for at least ten years. It's not the cause of my problem. And as for all those shiny clicky-clickity tools, no thanks! I prefer to know what is going on on my computer. Any comments on my question, anyone? If anybody could write one of the images using his his preferred/recommended imaging tool and run fsck on the resulting partition it would help me much. Thank you.