Active threads

Thank you. How can i add an external directory? Any config file or something?

This is an orange Pi zero with an H3 chip. I can't make sense out of the part numbers. But it's a zero, it is square, it has an ethernet and wifi, and has an H3 chip right on the top of the thing. The device tree says model = "Xunlong Orange Pi PC Plus"; compatible = "xunlong,orangepi-pc-plus\0allwinner,sun8i-h3"; The build I was running is the latest I could find [ 0.000000] Linux version 6.12.35-current-sunxi (build@armbian) (arm-linux-gnueabihf-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Fri Jun 27 10:11:46 UTC 2025 So whatever it says in the boot log and in the armbian monitor (which I included as a link in my original post) is what this is. And there is no ethernet or wifi on it, nor has there ever been since I bought it maybe 4 or 5 years ago. Every few years I try the latest build and check to see if that fixes it, and it never seems to happen. arbmianmonitor.log bootmaybeowkring.log

bananaoi-m5, Armbian 25.8.1 bookworm installed I can login via ssh as first user, gene, and sudo -i just fine. Buuuttttttt, at reboot the local screen ask's for the pw for amandabackup, a user lock down tightly which has never had a pw assigned. as its intended to be pw--less for the amanda backup system. What miss-configure can cause this????? Also I ordered 2 more of the keyboard/mouse combo''s which are the same as I'm using with a similar install for klipper running a 3d printer, but the dongle doesn't init when plugged in ack dmesg output, refusing its on discovery assigned address. So no keyboard/mouse is locally possible. I'll unpack the 2nd identical copy and see if its also broken. Switching back to an ultra- micro sized keyboard with a touchpad mouse works fine. And the second keyboard/mouse works as expected. The pw gizmo ask's for amandabackup's pw, I gave it my first user pw which it accepted logging me in normally. So I typed whoami and it responded gene. So wth is confusing the login requester????????? Many Thanks for any assistance. And why do I have to say solved in order to post when its not solved?? Counter productive to other readers.

What a PR is ? Could you be more specific about your suggestion ? In fact, could this module be included into the next 6.15 EDGE build ? CONFIG_RTW88_8821AU=m I don't know if this module is indeed functional (I want to test it). As it is concurrent with Armbian supplied 88XXau for the same hardware, one of them needs to be disabled in /etc/modprobe.d/ either: # cat blacklist-88XXau.conf blacklist 88XXau or # cat blacklist-RTW88_8821AU.conf blacklist rtw88_8821au

That is basically what I have been doing. I reconstructed image/partitions to have bootfs and rootfs separated. Typically format bootfs as simple FAT where you can fix things even on Windows computers maybe when SD-cards. For new fast SBCs I just have many partitions on NVMe where various Linux distros rootfs are and just copy or rename armbianEnv.txt which is then essentially only a UUID of a rootfs. When I know the SBC well enough, it is more the kernel only that matters, so i made a extlinux.conf generator so I can select a kernel via U-Boot serial console. I don't see what A+B brings me as I use Btrfs for rootfs and use snapper to make 'last-known-good' snapshots and also transfer those to NAS or so. If you want totally unattended, then A+B is an option, look at Android as well I would say. But more towards PC like systems, one can put efi bootloader (efi-grub) on the bootFAT, that allows you to select last-known-good more or less if you deploy snapshots. I usually do update in-place, so more like rolling release, but you can also do updates on a new read-write snapshot and fallback if it would fail to boot, see https://kubic.opensuse.org/documentation/man-pages/transactional-update.8.html for example how that works. U-Boot also has options I think to get to last-known-good automatically, but I don't know how that would work. For my stuff at home, it is good enough that I can quickly go back to older snapshot and that works for more than a decade on my PCs, so I do the same on SBCs/embedded, as long as they have a serial console cable (or HDMI,keyboard). For the NanoPi-NEO I also had Btrfs capable U-Boot, so then U-Boot can directly boot a certain rootfs partition, but it is not really default, so I keep an extra bootFAT.

Fresh Orangepi 5 image, this one: https://netcup-01.armbian.com/incoming/efectn/orangepi5/archive/Armbian_25.8.1_Orangepi5_noble_vendor_6.1.115_gnome_desktop.img.xz Your setup could be broken to some degree, but hard to tell what is missing.

Yes, I did read that. I was also thinking maybe the decompression on-the-fly could be a point of failure. Just now, I installed USBImager and wrote the image to a uSD. No presets applied (.not_looged_in_yet) First boot went smoothly. I updated with armbian-upgrade and rebooted and all looked OK. 🤷🏻‍♂️ Since I changed 2 things (using USBImager and no presets) I can't say what helped.

You need an overlay for that camera and 6.1.115-vendor-rk35xx does not have that AFAIR, older legacy 5.10 has it AFAIR. Look for something called RPi camera v1 or that sensor name.

It would be interesting to compare corrupt and non corrupt cards, including partition tables, etc. Windows might be playing bad with partition tables - if one only inserts ESXi boot disk into windows machine, such disk becomes non bootable. AFAIR this is because ESXi relies on records order in the gpt table of the disk, while windows strips away blank records so that if eg second and third records are blank then windows will move the fourth record to the second place, while ESXi relies on the fourth record in a table. I personally met this issue a few years ago and it took a while to find the solution of reordering gpt table records back to restore ESXi boot.

armbian-config : System > Storage > "STO001 - Install" or directly nand-sata-install You will get │ │ 1 Boot from SD - system on SATA, USB or NVMe │ │ │ │ 2 Boot from eMMC - system on eMMC │ │ │ │ 3 Boot from eMMC - system on SATA, USB or NVMe │ │ │ │ 4 Boot from MTD Flash - system on SATA, USB or NVMe │ │ │ │ 5 Install/Update the bootloader on SD card (/dev/mmcblk1) │ │ if you select boot from eMMC I think the installer will replace RoobiOS u-boot (and I guess Roobi Boot Menu) with Armbian U-Boot. I still need to experiment with Roobi OS (i.e. if there is a bootloader in SPI flash like on PC instead of only on eMMC). But you might want to try "boot from SD - system on NVME" and keep the Armbian bootloader on SD with the SD card kept plugged. If you install the bootloader on the eMMC likely you won't get the Roobi Boot menu anymore. About the boot priority, I guess it is written in the Radxa doc. It depends on how they configured their U-Boot.

Ok, that draft was way more complicated than it should and there's an easier way, also we need to logout and login again for the extension to show. Is it a problem if we restart GNOME shell during install? Here's a better script: 1 #!/bin/bash 2 git clone --depth=1 https://github.com/fthx/no-overview.git 3 NO_OVERVIEW=$(jq -r .uuid no-overview/metadata.json) 4 gnome-extensions pack no-overview 5 gnome-extensions install $NO_OVERVIEW.shell-extension.zip 6 # Restart GNOME shell 7 gnome-extensions enable $NO_OVERVIEW in line 6, I found the following: https://github.com/brunelli/gnome-shell-extension-installer/blob/4357903be8646d940902852bf3e150f625e350e6/gnome-shell-extension-installer#L288 This is not doable in Wayland from what I read around... so this will install, and the user will have to enable it manually.

Hello, I've recently bought a rock 5B plus. I have a brand new crucial P310 nvme 1TB with the goal to boot from it. As the title says, sometimes the nvme drive is properly detected, sometimes not. (Everytime the controller is visible in lspci, but only sometimes shows in lsblk). When the drive is properly detected, I can write to it and it works fine, without issues. I've noticed that it is more likely to be detected on a cold boot (ie. if I turn off the power and come back the next day, the first time it will probably show up). I have the official radxa 65w PD power adapter (although I've also tried a lot more during the process with the same results). I tried with the official radxa debian image, and with armbian, and the results are exactly the same on both. Btw, I would like to mention that armbian noble gnome doesn't boot even from the sd card (blue led but no display output, I let it for over 10 minutes), only the minimal/iot works. I don't know what else to try at this point, I can post any info / logs you may want. Thanks!

Any luck? my tx1 is in the mail.

@Nick AI tried to extract the dts from the working image, cloud you help me find any clues. Thank you. I was able to gain access to the os that works, this is the dmesg: dmesg | grep eth [ 8.550757] libphy: 5020000.eth: probed [ 8.568109] sunxi-gmac 5020000.eth eth0: eth0: Type(8) PHY ID 001cc916 at 0 IRQ poll (5020000.eth-0:00) [ 12.765916] sunxi-gmac 5020000.eth eth0: Link is Up - 1Gbps/Full - flow control off [ 12.775526] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready I also upload the pic of ethernet chip. dts.zip

That part of the instructions is clear. It's the steps involving the "wipe_part" file that supposedly erases partitions on the eMMC and the flashing of the second loader file that I can't make out. It looks like the instructions were edited to make them unusable. Nicolas has had the same issue in the H96 subforum with bad instructions and people asking for help due to the lack of clarity. I was able to make the board boot from SD card after flashing it with the YYT provided Debian 11 image, but only to Armbian Noble. No Debian distros work. When a Debian SD is inserted, the board boots then enters a systemd-devd shell with error messages about a UUID not being found. All Debian images do the same, I think it has to do with the eMMC memory not being seen because it is still formatted and not cleared. I have never seen a shell like this. Armbian Noble still boots properly, but only Noble. I need a Debian minimal distro in order to install OpenMediaVault and save my friend's files.

Greetings; I have downloaded this https://dl.armbian.com/cubox-i/Noble_current_server and verified that I got what I was supposed to (ASC, SHA). I have used a brand new usbimager to install it on various freshly formatted (brand new SD Formatter) and verified working Samsung Evo 32GB, SanDisk Extreme Plus 16GB, Extreme Plus 32GB. All the formatting, imaging and installation done on an Ubuntu 25.04 laptop. After usbimager is done, if I use the Ubuntu Disks application to look at the drive, the first partion shows as free space, which seems suspicious. When I insert the newly-set up SD cards in the Cubox-i4, I see the bootloader start and then do its handoff to the operating system... and then nothing. No more signal on the HDMI cable, nothing out on ssh, nothing. The Cubox-i4 tries to reboot every few minutes with no more successful outcome. This same Cubox-i4 runs fine with the last SD card system disk I built for it using the previous Debian server image. Does anyone have any ideas? Thanks in advance!

Try with one additional parameter: EXTRAWIFI="no"

@Piotr syou can try this build it’s based on the 6.14 kernel. Only issue I know of is audio using the a/v port. https://github.com/NickAlilovic/build/tree/v20250407

@ARx8if need help fixing the sd card. Login to IRC and ask the sunxi guys. https://oftc.catirclogs.org/linux-sunxi/2025-08-20

@Trung Nguyễn git clone https://github.com/NickAlilovic/build.git --branch v20250306 cd build ./compile.sh choose "Do not change kernel configuration" choose "Show CSC/WIP/EOS/TVB" choose "I understand and agree" choose "x98h" choose "edge" rest is up to you. Your image should be in output/images directory.

Outdated kernel. overlays were probably added later https://github.com/armbian/linux-rockchip/tree/rk-6.1-rkr5.1/arch/arm64/boot/dts/rockchip/overlay

@darcyg @ Hqnicolas rk3576-h96-m9s.dts rk3576 -h96-m9s-linux.dtsi armsom-sige5-rk3576_defconfig 1.Reset button in UBOOT OK 2. video acceleration OK work.。kodi video acceleration Armbian-unofficial_25.11.0-trunk_H96-m9_bookworm_vendor_6.1.115-backported-mesa.img https://drive.google.com/drive/folders/1lzLwm9NhxZ_0_mghKG4A0XQ6NNsU9sn-?usp=drive_link kodi https://github.com/armsurvivors/kodi-rockchip-deb 3. When turning off the box, the lights are still on. Probably - it is not really turned off. 4. No wifi No Bluetooth

Never too late to express gratitude and say "Thank you for sharing your findings"

Help! I used your overlay, but nothing works for me. overlay: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target = <&spi1>; __overlay__ { status = "okay"; cs-gpios = <&pio 7 5 0>,<&pio 2 15 0>; /*PH5=CS0 for lcd, PC15=CS1 for touch*/ display: display@0 { compatible = "ilitek,ili9341"; reg = <0>; pinctrl-names = "default"; spi-max-frequency = <20000000>; rotate = <270>; bgr = <0>; fps = <30>; buswidth = <8>; regwidth = <16>; height = <480>; width = <320>; reset-gpios = <&pio 2 14 1>; /* PC14 */ dc-gpios = <&pio 2 6 0>; /* PC6 */ debug = <3>; init = <0x10000b0 0x00 // Interface Mode Control 0x1000011 // Sleep Out 0x20000ff // Delay (255ms) 0x10000C0 0x0D 0x0D // Power Control 1 0x10000C1 0x43 // Power Control 2 0x10000C5 0x00 0x48 0x80 // VCOM Control 1 0x10000C7 0x00 // VCOM Control 2 0x1000036 0x28 // Memory Access Control (Rotacao) 0x100003A 0x55 // Pixel Format Set (16bit) 0x10000B1 0xB0 0x11 // Frame Rate Control 0x10000F0 0x01 // Enable Extended Comand Set 0x10000F6 0x00 0x01 0x32 // SPI ilInterface Control 0x1000026 0x01 // Gamma Set 0x10000E0 0x0F 0x31 0x2B 0x0C 0x0E 0x08 0x4E 0xF1 0x37 0x07 0x10 0x03 0x0E 0x09 0x00 // Positive Gamma Correction 0x10000E1 0x00 0x0E 0x14 0x03 0x11 0x07 0x31 0xC1 0x48 0x08 0x0F 0x0C 0x31 0x36 0x0F // Negative Gamma Correction 0x10000B6 0x02 0x02 0x3B // Display Function Control 0x1000011 // Sleep Out 0x20000ff // Delay (255ms) 0x1000029>; // Display ON }; ads7846: ads7846@1 { compatible = "ti,ads7846"; reg = <1>; pinctrl-names = "default"; spi-max-frequency = <1000000>; interrupt-parent = <&pio>; interrupts = <2 10 2>; /* PC10 - IRQ */ pendown-gpio = <&pio 2 10 1>; /* PC10 */ /* OPTIONS */ ti,x-min = /bits/ 16 <0>; ti,y-min = /bits/ 16 <0>; ti,x-max = /bits/ 16 <0xFFF>; ti,y-max = /bits/ 16 <0xFFF>; ti,pressure-min = /bits/ 16 <0>; ti,pressure-max = /bits/ 16 <0xFFF>; ti,x-plate-ohms = /bits/ 16 <400>; ti,swap-xy = <1>; }; }; }; }; Here's what I got in the console: root@orangepizero3:~# dmesg | grep -i "spi\|ili9486\|fb_" [ 1.496981] sun6i-spi 5010000.spi: Error applying setting, reverse things back [ 1.497500] sun6i-spi 5011000.spi: cannot register SPI host [ 1.504082] sun6i-spi 5010000.spi: Error applying setting, reverse things back [ 1.504504] sun6i-spi 5011000.spi: cannot register SPI host [ 1.512160] spi-nor spi0.0: supply vdd not found, using dummy regulator [ 6.677433] fb_ili9341: module is from the staging directory, the quality is unknown, you have been warned. [ 6.677997] fb_ili9341 spi1.0: fbtft_property_value: width = 320 [ 6.678010] fb_ili9341 spi1.0: fbtft_property_value: height = 480 [ 6.678018] fb_ili9341 spi1.0: fbtft_property_value: regwidth = 16 [ 6.678025] fb_ili9341 spi1.0: fbtft_property_value: buswidth = 8 [ 6.678033] fb_ili9341 spi1.0: fbtft_property_value: debug = 3 [ 6.678041] fb_ili9341 spi1.0: fbtft_property_value: rotate = 270 [ 6.678049] fb_ili9341 spi1.0: fbtft_property_value: fps = 30 [ 6.678234] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'reset' GPIO [ 6.678260] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'dc' GPIO [ 6.678279] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'rd' GPIO [ 6.678294] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'wr' GPIO [ 6.678310] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'cs' GPIO [ 6.678325] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'latch' GPIO [ 6.678340] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678354] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678369] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.678383] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678398] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678412] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.678426] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678441] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678456] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.678470] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678485] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678499] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.678514] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678528] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678543] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.678557] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678572] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678587] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.678604] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678621] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678638] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.678655] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678672] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678689] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.678706] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678723] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678740] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.678757] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678774] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678791] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.678808] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678825] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678842] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.678859] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678876] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678893] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.678910] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678927] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678944] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.678961] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.678978] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.678995] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.679012] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.679029] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.679046] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.679063] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.679080] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.679098] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.701957] ads7846 spi1.1: supply vcc not found, using dummy regulator [ 6.703555] ads7846 spi1.1: touchscreen, irq 77 [ 6.704030] input: ADS7846 Touchscreen as /devices/platform/soc/5011000.spi/spi_master/spi1/spi1.1/input/input0 [ 6.801201] fb_ili9341 spi1.0: init: write_register: [ 6.801229] fb_ili9341 spi1.0: buf[0] = B0 [ 6.801238] fb_ili9341 spi1.0: buf[1] = 00 [ 6.801397] fb_ili9341 spi1.0: init: write_register: [ 6.801406] fb_ili9341 spi1.0: buf[0] = 11 [ 6.801441] fb_ili9341 spi1.0: init: msleep(255) [ 7.073196] fb_ili9341 spi1.0: init: write_register: [ 7.073241] fb_ili9341 spi1.0: buf[0] = C0 [ 7.073265] fb_ili9341 spi1.0: buf[1] = 0D [ 7.073284] fb_ili9341 spi1.0: buf[2] = 0D [ 7.073489] fb_ili9341 spi1.0: init: write_register: [ 7.073510] fb_ili9341 spi1.0: buf[0] = C1 [ 7.073530] fb_ili9341 spi1.0: buf[1] = 43 [ 7.073701] fb_ili9341 spi1.0: init: write_register: [ 7.073721] fb_ili9341 spi1.0: buf[0] = C5 [ 7.073743] fb_ili9341 spi1.0: buf[1] = 00 [ 7.073762] fb_ili9341 spi1.0: buf[2] = 48 [ 7.073781] fb_ili9341 spi1.0: buf[3] = 80 [ 7.073952] fb_ili9341 spi1.0: init: write_register: [ 7.073973] fb_ili9341 spi1.0: buf[0] = C7 [ 7.073994] fb_ili9341 spi1.0: buf[1] = 00 [ 7.074163] fb_ili9341 spi1.0: init: write_register: [ 7.074183] fb_ili9341 spi1.0: buf[0] = 36 [ 7.074203] fb_ili9341 spi1.0: buf[1] = 28 [ 7.074372] fb_ili9341 spi1.0: init: write_register: [ 7.074392] fb_ili9341 spi1.0: buf[0] = 3A [ 7.074414] fb_ili9341 spi1.0: buf[1] = 55 [ 7.074581] fb_ili9341 spi1.0: init: write_register: [ 7.074601] fb_ili9341 spi1.0: buf[0] = B1 [ 7.074622] fb_ili9341 spi1.0: buf[1] = B0 [ 7.074641] fb_ili9341 spi1.0: buf[2] = 11 [ 7.074809] fb_ili9341 spi1.0: init: write_register: [ 7.074829] fb_ili9341 spi1.0: buf[0] = F0 [ 7.074850] fb_ili9341 spi1.0: buf[1] = 01 [ 7.075018] fb_ili9341 spi1.0: init: write_register: [ 7.075038] fb_ili9341 spi1.0: buf[0] = F6 [ 7.075058] fb_ili9341 spi1.0: buf[1] = 00 [ 7.075077] fb_ili9341 spi1.0: buf[2] = 01 [ 7.075096] fb_ili9341 spi1.0: buf[3] = 32 [ 7.075264] fb_ili9341 spi1.0: init: write_register: [ 7.075285] fb_ili9341 spi1.0: buf[0] = 26 [ 7.075306] fb_ili9341 spi1.0: buf[1] = 01 [ 7.075474] fb_ili9341 spi1.0: init: write_register: [ 7.075494] fb_ili9341 spi1.0: buf[0] = E0 [ 7.075515] fb_ili9341 spi1.0: buf[1] = 0F [ 7.075534] fb_ili9341 spi1.0: buf[2] = 31 [ 7.075553] fb_ili9341 spi1.0: buf[3] = 2B [ 7.075571] fb_ili9341 spi1.0: buf[4] = 0C [ 7.075590] fb_ili9341 spi1.0: buf[5] = 0E [ 7.075609] fb_ili9341 spi1.0: buf[6] = 08 [ 7.075628] fb_ili9341 spi1.0: buf[7] = 4E [ 7.075647] fb_ili9341 spi1.0: buf[8] = F1 [ 7.075665] fb_ili9341 spi1.0: buf[9] = 37 [ 7.075684] fb_ili9341 spi1.0: buf[10] = 07 [ 7.075703] fb_ili9341 spi1.0: buf[11] = 10 [ 7.075722] fb_ili9341 spi1.0: buf[12] = 03 [ 7.075742] fb_ili9341 spi1.0: buf[13] = 0E [ 7.075761] fb_ili9341 spi1.0: buf[14] = 09 [ 7.075780] fb_ili9341 spi1.0: buf[15] = 00 [ 7.075954] fb_ili9341 spi1.0: init: write_register: [ 7.075974] fb_ili9341 spi1.0: buf[0] = E1 [ 7.075995] fb_ili9341 spi1.0: buf[1] = 00 [ 7.076014] fb_ili9341 spi1.0: buf[2] = 0E [ 7.076034] fb_ili9341 spi1.0: buf[3] = 14 [ 7.076053] fb_ili9341 spi1.0: buf[4] = 03 [ 7.076071] fb_ili9341 spi1.0: buf[5] = 11 [ 7.076090] fb_ili9341 spi1.0: buf[6] = 07 [ 7.076109] fb_ili9341 spi1.0: buf[7] = 31 [ 7.076128] fb_ili9341 spi1.0: buf[8] = C1 [ 7.076147] fb_ili9341 spi1.0: buf[9] = 48 [ 7.076165] fb_ili9341 spi1.0: buf[10] = 08 [ 7.076184] fb_ili9341 spi1.0: buf[11] = 0F [ 7.076203] fb_ili9341 spi1.0: buf[12] = 0C [ 7.076222] fb_ili9341 spi1.0: buf[13] = 31 [ 7.076241] fb_ili9341 spi1.0: buf[14] = 36 [ 7.076260] fb_ili9341 spi1.0: buf[15] = 0F [ 7.076432] fb_ili9341 spi1.0: init: write_register: [ 7.076452] fb_ili9341 spi1.0: buf[0] = B6 [ 7.076473] fb_ili9341 spi1.0: buf[1] = 02 [ 7.076493] fb_ili9341 spi1.0: buf[2] = 02 [ 7.076511] fb_ili9341 spi1.0: buf[3] = 3B [ 7.076679] fb_ili9341 spi1.0: init: write_register: [ 7.076699] fb_ili9341 spi1.0: buf[0] = 11 [ 7.076797] fb_ili9341 spi1.0: init: msleep(255) [ 7.361180] fb_ili9341 spi1.0: init: write_register: [ 7.361202] fb_ili9341 spi1.0: buf[0] = 29 [ 7.490659] fb_ili9341 spi1.0: Display update: 2321 kB/s, fps=0 [ 7.491267] graphics fb0: fb_ili9341 frame buffer, 480x320, 300 KiB video memory, 16 KiB buffer memory, fps=31, spi1.0 at 20 MHz I'm connecting exactly according to this picture:

Apologies for the late reply. That error sounds like running out of space on the filesystem (maybe the tmpfs portions?), not running out of RAM, that would give you a different error.