Hi, I just switched from an ancient ubuntu-rockchip install to armbian ubuntu 26.04 with the mainline kernel. I did a bit of an unorthodox installation, I wanted to install on an nvme drive, and instead of using a microSD and then copying the system with armbian-install, since I didn't have a working microsd available I did a "manual" installation, I flashed rkspi_loader.img into the SPI taken from the armbian image and then flashed the armbian img directly to the nvme drive with an usb adapter from my PC. All is good and working fine, but I'm wondering if I'm missing any settings that gets applied during the armbian-install process (are there any?) that are specific for nvme. And regarding Zram, ram2log and other optimizations that armbian uses for SDs, how should I configure them? My setup is a Radxa Rock 5B with 8GB of RAM with a Samsung 970 evo plus, should I disable zram and create a swapfile? Any other setting to look out for? I think my hdparm -t speed is a bit low, around 1300 MB/s. Thanks in advance

I was wrong, the dafault baudrate is 100 kHz - the sensor is not responding at first try, when it is in sleep mode.

Hi Dodeval, so I am having trouble accessing Gemini 3.1 pro chat about this but this sounds vaguely familiar. Things that could be the cause are the "mkfs.ext4 -b 4096" option and "debootstrap --arch=arm64". Try some of these top tier models https://artificialanalysis.ai/leaderboards/models they should be able to crack the code even though you might have to wrestle a bit to get them to produce the right solution. Most things seem to work like magic I guess it is about the device tree, battery management seems fine etc.. touch needs drivers, no audio from internal speakers which is no big deal anyway as bluetooth audio works everything there works as expected. I did get this aliexpress.com/item/1005009649297050.html at a discount but I not completely get the touchpad to work comfortably with a patched input driver, a lot of miss-clicks goosh nice keyboard but still need bluetooth mouse in reality. Rii i4 Mini Bluetooth would be fine but then again it is not quite the desktop experience I was looking for.

Hi, I need help identifying the Maskrom/eMMC short points for an RK3528 TV box. Device: - TV box sold as H20 Pro - SoC confirmed as Rockchip RK3528 - Board marking: M16-R6B-L3-V1.0-260121 - RAM detected in Linux: 963 MiB - eMMC detected in Linux: 7.83 GB / 7.30 GiB - eMMC name from Linux: P1J95K - eMMC CID: fe014e50314a39354b12739109744200 What happened: - The box originally booted Android from eMMC. - Armbian booted successfully from SD using a customized joilg/x88pro-based image. - Later I wrote U-Boot/idbloader to eMMC: - idbloader.img at sector 64 - u-boot.itb at sector 16384 - After reboot, the board no longer boots from SD or eMMC. - LED stays red. - No HDMI output. - No Ethernet link/activity. - RKDevTool on Windows shows "No Devices Found". Recovery attempts: - Tried the reset/recovery button behind the AV/P2 jack while connecting power and USB. - Tried both USB ports. - Tried RKDevTool v2.86 with Rockchip drivers installed. - No Loader or Maskrom device appears. - Tried UART pads marked GND/TX/RX using ESP32-C3 as bridge, but output is not readable. Question: Can anyone identify the eMMC Maskrom short point for this board? I need to force RK3528 into Maskrom mode so I can restore the first bootloader area of the eMMC. Attached photos: - Front of board - Back of board - Macro photo of the eMMC/storage chip area - Macro photo of test pads near the storage chip

I tried to downgrade to 6.18, unfortunately it froze during the process, which left the kernel and boot loader in an incomplete state. I have decided to re-image the whole thing with 6.18.x and for now it appears to be stable again.