ValdikSS

Igor, the package itself doesn't seem to be present in the repository, I guess? I did run armbian-install to force-update u-boot after apt-upgrade, but it's still the old version. I had to extract the files from the newer image, as described in the message above, as they were not present after update in my filesystem. I had the older u-boot.

Only after I manually did the steps you've described, it started to boot. In other words, the apt-upgrade path is still broken. Was the fix for apt-upgrade not planned? P.S. kernel 6.12 power consumption is slightly higher than 6.6, both in idle and in suspend. Since Truenox mentioned working audio, does 6.12 come with always-enabled audio domain power?

This is still the issue. Download https://mirror.yandex.ru/mirrors/armbian/archive/rockpi-s/archive/Armbian_24.11.1_Rockpi-s_bookworm_current_6.6.62_minimal.img.xz apt update && apt -y upgrade armbian-install, update bootloader = yes Result: OS does not boot after reboot, with ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree It doesn't matter whether armbian-install is run. My device does not have emmc, only microsd. Fix in this post works fine. … Load uboot, ReadLba = 2000 Load OK, addr=0x600000, size=0x99518 RunBL31 0x40000 @ 122481 us INFO: Preloader serial: 0 NOTICE: BL31: v1.3(release):30f1405 NOTICE: BL31: Built : 17:08:28, Sep 23 2019 INFO: Lastlog: last=0x100000, realtime=0x102000, size=0x2000 INFO: ARM GICv2 driver initialized INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 1 INFO: plat_rockchip_pmu_init: pd status 0xe b INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x600000 INFO: SPSR = 0x3c9 U-Boot 2022.04-armbian-2022.04-Se4b6-P2db4-He13b-V7409-Bda0a-R448a (Nov 16 2024 - 02:33:20 +0000) Model: Radxa ROCK Pi S DRAM: 510 MiB Core: 276 devices, 20 uclasses, devicetree: separate MMC: dwmmc@ff480000: 1, dwmmc@ff490000: 0 Loading Environment from nowhere... OK In: serial Out: serial Err: serial Model: Radxa ROCK Pi S rockchip_dnl_key_pressed read board id failed Net: eth0: ethernet@ff4e0000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3633 bytes read in 5 ms (709 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1:1 257 bytes read in 4 ms (62.5 KiB/s) 17262801 bytes read in 735 ms (22.4 MiB/s) 36538880 bytes read in 1549 ms (22.5 MiB/s) 56214 bytes read in 17 ms (3.2 MiB/s) 688 bytes read in 16 ms (42 KiB/s) Applying kernel provided DT overlay rk3308-bs.dtbo 459 bytes read in 34 ms (12.7 KiB/s) Applying kernel provided DT overlay rk3308-bs@1.3ghz.dtbo Moving Image from 0x680000 to 0x800000, end=2bb0000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17262737 Bytes = 16.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... Card did not respond to voltage select! : -110 starting USB... No working controllers found USB is stopped. Please issue 'usb start' first. starting USB... No working controllers found ethernet@ff4e0000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! …

If your board in unstable, it hangs, kernel panics with Unable to handle kernel paging request at virtual address ffff7fffbef91008 Or MicroSD read errors, and you use Wi-Fi, Put Wi-Fi antenna outside of the board! Apparently EMI from the Wi-Fi module is so high it influence RAM and/or MicroSD if the antenna is in closest proximity. I've tested it on tens of Zero 3's, and could reliably reproduce the issue.

If your board in unstable, it hangs, kernel panics with Unable to handle kernel paging request at virtual address ffff7fffbef91008 Or MicroSD read errors, and you use Wi-Fi, Put Wi-Fi antenna outside of the board! Apparently EMI from the Wi-Fi module is so high it influence RAM and/or MicroSD if the antenna is in closest proximity. I've tested it on tens of Zero 3's, and could reliably reproduce the issue.

@zaibot.w did you manage to fix it? It's possible to use gpio-keys from the regular pinctrl, but you won't have pull-up/down. Could not fix it with pull up.

It's been several years since I started looking for a forum to discuss various general aspects of SBCs, such as "recommend me the board for X", SoC software support state, pricing, deals, etc. All not armbian-related per se. Neither of current categories are exactly suitable for such questions on this forum. Off-topic category doesn't receive much attention as I would guess. Proposal: create "general discussions" category.