hi-ko

I suspect that this disappeared earlier in the legacy boot and only became apparent when switching to u-boot from SPI. armbian-install will probably not adjust the partition if you select an existing one as target (I didn't check in the script). It would be a good lifesaver if the install/update of to bootloader also checks if the partition has the boot flag ... @Igor would be a valuable enhancement to check and at least warn if the partition has no boot flag set

@usual user you nailed it! For any reason that flag had been removed. I used parted, set 2 boot on and boot loader get's happy. Thank you all! One last thing/question: currently I use Armbian_24.5.2_Odroidm1_noble_current_6.6.35.img which couldn't find any header packackes in arbian-config similar thing choosing other kernels. I switched to 6.6.32-current-rockchip64 and now I also get the header packackes installed. I guess the packages are looked up in https://mirrors.dotsrc.org/armbian-apt/pool/main/l/ ? There is indeed no package for kernel 6.6.35, so it's a bit strange that the kernel from the image is newer but on the repo there are only older packages available.

but when I remove the sdcard, the bootloader doesn't find a boot device and falls back to network boot ... https://paste.armbian.com/xuniqokoyu.vbnet

mkfs.ext4 -L armbian /dev/nvme0n1p2 then run armbian-installer again, choosing Boot from MTD ... and fstype ext4 which also installed the bootloader: bootloader still boots into sdcard: terminal-log: https://paste.armbian.com/icusecahob.sql

Hey Igor, Thank you very much for your efforts. The patch only adjusts the partitioning itself. This works in my case / is already given. My problem is that the bootloader mechanism does not work as it should. It always boots from the sdcard, even if I have selected the menu entry "4 Boot from MTD Flash - system on SATA, USB or NVMe". Here is a terminal log after successfully writing to the second partition: https://paste.armbian.com/uvitekehup.sql Question is for me: how to install/Update the bootloader to boot from /dev/nvme0n1p2 instead of /dev/mmcblk1p1? How could I check, what is configured in the bootloader?

I got the SPI bootloader configured as expected by manually adding rootdev variable to /boot/armbianEnv.txt on the sdcard (!) and then run armbian-install again to update the bootloader. It seems, the installer is writing the armbianEnv.txt to the target device (nve partition) but reads from the booted device (sdcard) when installing the bootloader. Looks like a bug?

sure - but that's nothing I could influence since I just used the menu entries from the armbian-install. I did another try in the meantime using yet another fresh sdcard image. I used boot from from nve (choosing ext4) install bootloader on SPI system still boots from sdcard and if I remove the sdcard the system does not boot. How could I check / fix the config in the bootloader? I also chroot'ed into the mounted nve partition and run armbian-install again to install the bootloader into SPI. Same.

ok - that's what I did now. I booted a vanilla Armbian_24.5.2_Odroidm1_bookworm_current_6.6.35_minimal.img from sdcard used armbian-install: to boot from selected nve partition and install bootloader on SPI but this fails when I remove the sdcard: U-Boot 2024.04-rc3-armbian (Jun 17 2024 - 14:15:19 +0000) Model: Hardkernel ODROID-M1 DRAM: 8 GiB (effective 7.7 GiB) PMIC: RK8090 (on=0x80, off=0x08) Core: 326 devices, 34 uclasses, devicetree: separate MMC: mmc@fe2b0000: 1, mmc@fe310000: 0 Loading Environment from SPIFlash... SF: Detected mx25u12835f with page size 256 Bytes, erase size 4 KiB, total 16 MiB OK In: serial@fe660000 Out: serial@fe660000 Err: serial@fe660000 Model: Hardkernel ODROID-M1 Net: eth0: ethernet@fe2a0000 armbian leds armbian env already set once Hit any key to stop autoboot: 0 Bus usb@fd000000: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 Bus usb@fd800000: USB EHCI 1.00 Bus usb@fd840000: USB OHCI 1.0 Bus usb@fd880000: USB EHCI 1.00 Bus usb@fd8c0000: USB OHCI 1.0 scanning bus usb@fd000000 for devices... 1 USB Device(s) found scanning bus usb@fd800000 for devices... 1 USB Device(s) found scanning bus usb@fd840000 for devices... ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) unable to get device descriptor (error=-1) 1 USB Device(s) found scanning bus usb@fd880000 for devices... 1 USB Device(s) found scanning bus usb@fd8c0000 for devices... 1 USB Device(s) found Card did not respond to voltage select! : -110 Card did not respond to voltage select! : -110 scanning bus for devices... SATA link 0 timeout. AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp fbss pio slum part ccc apst ethernet@fe2a0000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! phy_startup() failed: -110FAILED: -110ethernet@fe2a0000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! second try: used recovery button to force boot from sdcard used armbian-install: to boot from selected nve partition (btrfs) and install bootloader on sdcard bootloader found the partition but faild to mount brfs partition: [/sbin/fsck.ext4 (1) -- /dev/nvme0n1p2] fsck.ext4 -a -C0 /dev/nvme0n1p2 done. mount: Invalid argument Failed to mount /dev/nvme0n1p2 as root file sytstem.

I'll play a bit with the booting process via SPI once I finished a backup. I thought rerunning armbian-install would not be supported since the tool gets uninstalled once run, but I guess that's the way to run it again? Here the console log from the failed boot after updating the kernel: Offset = 0x1946eaaa3bbc Image 7337: -14679873 Bytes = 4 GiB Offset = 0x1947e8aa9ebc Image 7338: -12582666 Bytes = 4 GiB Offset = 0x1948e7ca9f7c Image 7339: -115341057 Bytes = 3.9 GiB Offset = 0x1949e70aa074 Image 7340: -33545985 Bytes = 4 GiB Offset = 0x194ae02aa974 Image 7341: -16776969 Bytes = 4 GiB Offset = 0x194bde2aca74 Image 7342: -16768290 Bytes = 4 GiB Offset = 0x194cdd2acb6c Image 7343: -79691393 Bytes = 3.9 GiB Offset = 0x194ddc2aee4c Image 7344: -83787522 Bytes = 3.9 GiB Offset = 0x194ed76aefcc Image 7345: -8384321 Bytes = 4 GiB Offset = 0x194fd26c70cc Image 7346: -16776961 Bytes = 4 GiB Offset = 0x1950d1ec818c Image 7347: -148897537 Bytes = 3.9 GiB Offset = 0x1951d0ec828c Image 7348: 1862336925 Bytes = 1.7 GiB Offset = 0x1952c80c838c Image 7349: -16776705 Bytes = 4 GiB Offset = 0x1953370d852c Image 7350: -1627389857 Bytes = 2.5 GiB Offset = 0x1954360d872c Image 7351: -587202305 Bytes = 3.5 GiB Offset = 0x1954d50d878c Image 7352: -16776961 Bytes = 4 GiB Offset = 0x1955b20d888c Image 7353: -16777093 Bytes = 4 GiB Offset = 0x1956b10d898c Image 7354: -16252433 Bytes = 4 GiB Offset = 0x1957b00d8a08 Image 7355: -15658755 Bytes = 4 GiB Offset = 0x1958af158bf8 Image 7356: -1619001089 Bytes = 2.5 GiB Offset = 0x1959ae269cf8 Image 735 DDR Version V1.09 20210630 In ddrconfig:7 LPDDR4X, 324MHz BW=32 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=8192MB tdqss: cs0 dqs0: 48ps, dqs1: -96ps, dqs2: -72ps, dqs3: -144ps, tdqss: cs1 dqs0: 48ps, dqs1: -96ps, dqs2: -48ps, dqs3: -144ps, change to: 324MHz PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:41% dram drv:40,odt:0 clk skew:0x61 change to: 528MHz PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:41% dram drv:40,odt:0 clk skew:0x58 change to: 780MHz PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:41% dram drv:40,odt:0 clk skew:0x58 change to: 1560MHz(final freq) PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:22% dram drv:40,odt:80 vref_ca:00000071 clk skew:0x1c cs 0: the read training result: DQS0:0x32, DQS1:0x31, DQS2:0x32, DQS3:0x2a, min : 0xf 0xe 0x11 0xf 0x1 0x5 0x9 0x3 , 0xa 0xa 0x2 0x2 0x12 0x9 0xc 0x8 , 0x10 0xf 0xb 0xa 0x5 0x1 0x3 0x5 , 0xb 0x8 0x7 0x3 0xf 0xf 0xd 0x10 , mid :0x28 0x29 0x2c 0x2a 0x1d 0x21 0x24 0x1f ,0x24 0x23 0x1b 0x1c 0x28 0x24 0x25 0x22 , 0x2a 0x2a 0x25 0x22 0x1e 0x1b 0x1d 0x20 ,0x24 0x21 0x1f 0x1c 0x27 0x28 0x25 0x28 , max :0x42 0x45 0x48 0x45 0x3a 0x3d 0x3f 0x3c ,0x3f 0x3d 0x34 0x37 0x3f 0x3f 0x3f 0x3d , 0x45 0x46 0x3f 0x3b 0x37 0x35 0x37 0x3b ,0x3d 0x3a 0x38 0x36 0x40 0x42 0x3d 0x41 , range:0x33 0x37 0x37 0x36 0x39 0x38 0x36 0x39 ,0x35 0x33 0x32 0x35 0x2d 0x36 0x33 0x35 , 0x35 0x37 0x34 0x31 0x32 0x34 0x34 0x36 ,0x32 0x32 0x31 0x33 0x31 0x33 0x30 0x31 , the write training result: DQS0:0x25, DQS1:0x9, DQS2:0xe, DQS3:0x0, min :0x70 0x73 0x77 0x74 0x64 0x69 0x6d 0x6d 0x6b ,0x4f 0x4d 0x46 0x4a 0x52 0x4e 0x52 0x50 0x4a , 0x59 0x5c 0x54 0x53 0x4d 0x48 0x4d 0x52 0x53 ,0x4c 0x48 0x46 0x45 0x4d 0x4e 0x4a 0x51 0x45 , mid :0x8d 0x8f 0x92 0x8f 0x7c 0x81 0x87 0x86 0x83 ,0x6b 0x69 0x60 0x63 0x6d 0x69 0x6c 0x69 0x64 , 0x75 0x76 0x6e 0x6f 0x67 0x62 0x66 0x6a 0x6d ,0x67 0x62 0x5f 0x5e 0x67 0x6a 0x64 0x6c 0x5f , max :0xab 0xab 0xae 0xab 0x95 0x99 0xa2 0x9f 0x9b ,0x87 0x86 0x7b 0x7d 0x88 0x84 0x87 0x83 0x7e , 0x92 0x91 0x89 0x8b 0x81 0x7c 0x80 0x83 0x87 ,0x82 0x7d 0x79 0x77 0x82 0x87 0x7e 0x87 0x7a , range:0x3b 0x38 0x37 0x37 0x31 0x30 0x35 0x32 0x30 ,0x38 0x39 0x35 0x33 0x36 0x36 0x35 0x33 0x34 , 0x39 0x35 0x35 0x38 0x34 0x34 0x33 0x31 0x34 ,0x36 0x35 0x33 0x32 0x35 0x39 0x34 0x36 0x35 , cs 1: the read training result: DQS0:0x30, DQS1:0x32, DQS2:0x36, DQS3:0x2d, min : 0xf 0xe 0x12 0x10 0x2 0x5 0x8 0x4 , 0xa 0x9 0x2 0x1 0x11 0xa 0xc 0x7 , 0x14 0x14 0xd 0xd 0x8 0x1 0x4 0x8 , 0xc 0x7 0x8 0x2 0xf 0xe 0xc 0xe , mid :0x27 0x29 0x2b 0x2a 0x1c 0x20 0x22 0x1f ,0x24 0x23 0x1c 0x1c 0x29 0x25 0x26 0x23 , 0x2d 0x2e 0x26 0x26 0x20 0x1c 0x1e 0x21 ,0x25 0x21 0x21 0x1c 0x27 0x28 0x25 0x28 , max :0x3f 0x44 0x45 0x44 0x37 0x3b 0x3d 0x3a ,0x3f 0x3d 0x36 0x38 0x42 0x41 0x41 0x3f , 0x47 0x49 0x3f 0x40 0x38 0x38 0x39 0x3b ,0x3e 0x3b 0x3a 0x36 0x40 0x43 0x3f 0x42 , range:0x30 0x36 0x33 0x34 0x35 0x36 0x35 0x36 ,0x35 0x34 0x34 0x37 0x31 0x37 0x35 0x38 , 0x33 0x35 0x32 0x33 0x30 0x37 0x35 0x33 ,0x32 0x34 0x32 0x34 0x31 0x35 0x33 0x34 , the write training result: DQS0:0x25, DQS1:0x9, DQS2:0xe, DQS3:0x0, min :0x6d 0x72 0x74 0x71 0x61 0x66 0x6a 0x6a 0x69 ,0x4d 0x4c 0x45 0x48 0x51 0x4d 0x4f 0x4d 0x47 , 0x5e 0x5e 0x57 0x56 0x4f 0x4b 0x4f 0x53 0x56 ,0x48 0x47 0x44 0x3e 0x4b 0x4d 0x48 0x4e 0x43 , mid :0x8a 0x8e 0x90 0x8d 0x7a 0x80 0x84 0x83 0x82 ,0x69 0x68 0x5f 0x61 0x6c 0x68 0x69 0x67 0x62 , 0x7a 0x7a 0x72 0x73 0x6a 0x66 0x6a 0x6e 0x70 ,0x62 0x61 0x5e 0x59 0x65 0x68 0x62 0x69 0x5e , max :0xa8 0xaa 0xac 0xa9 0x93 0x9a 0x9f 0x9c 0x9b ,0x86 0x85 0x79 0x7b 0x87 0x84 0x84 0x82 0x7e , 0x97 0x96 0x8e 0x90 0x86 0x82 0x86 0x89 0x8b ,0x7c 0x7b 0x78 0x74 0x7f 0x84 0x7d 0x85 0x79 , range:0x3b 0x38 0x38 0x38 0x32 0x34 0x35 0x32 0x32 ,0x39 0x39 0x34 0x33 0x36 0x37 0x35 0x35 0x37 , 0x39 0x38 0x37 0x3a 0x37 0x37 0x37 0x36 0x35 ,0x34 0x34 0x34 0x36 0x34 0x37 0x35 0x37 0x36 , CA Training result: cs:0 min :0x52 0x57 0x49 0x48 0x4a 0x45 0x50 ,0x50 0x4f 0x46 0x45 0x48 0x46 0x4f , cs:0 mid :0x92 0x93 0x88 0x85 0x87 0x81 0x80 ,0x8f 0x8c 0x84 0x81 0x85 0x83 0x80 , cs:0 max :0xd2 0xcf 0xc7 0xc2 0xc5 0xbd 0xb0 ,0xcf 0xca 0xc2 0xbe 0xc3 0xc0 0xb2 , cs:0 range:0x80 0x78 0x7e 0x7a 0x7b 0x78 0x60 ,0x7f 0x7b 0x7c 0x79 0x7b 0x7a 0x63 , cs:1 min :0x4f 0x5b 0x45 0x4f 0x46 0x48 0x54 ,0x4d 0x52 0x43 0x48 0x43 0x48 0x4f , cs:1 mid :0x92 0x93 0x88 0x87 0x88 0x81 0x86 ,0x8f 0x8c 0x84 0x82 0x85 0x82 0x81 , cs:1 max :0xd6 0xcc 0xcc 0xbf 0xca 0xbb 0xb8 ,0xd1 0xc6 0xc6 0xbd 0xc7 0xbd 0xb3 , cs:1 range:0x87 0x71 0x87 0x70 0x84 0x73 0x64 ,0x84 0x74 0x83 0x75 0x84 0x75 0x64 , out U-Boot SPL board init U-Boot SPL 2017.09 (Apr 24 2022 - 07:36:50) Trying to boot from MMC1 MMC error: The cmd index is 0, ret is -110 mmc_init: -110, time 4 spl: mmc init failed with error: -110 Trying to boot from MMC2 No misc partition spl: partition error Trying to boot from MTD2 No misc partition ## Verified-boot: 0 ## Checking atf-1 0x00040000 ... sha256(2f01bd8955...) + OK ## Checking uboot 0x00a00000 ... sha256(59105c2b16...) + OK ## Checking fdt 0x00b1bca0 ... sha256(06b6d16a4d...) + OK ## Checking atf-2 0xfdcc9000 ... sha256(f1fecab971...) + OK ## Checking atf-3 0xfdcd0000 ... sha256(d7aa45eb18...) + OK ## Checking optee 0x08400000 ... sha256(b8cddafab0...) + OK Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000) Total: 321.590 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-152-g4e725b15f:cl NOTICE: BL31: Built : 10:51:13, Jul 15 2021 INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: pmu v1 is valid INFO: dfs DDR fsp_param[0].freq_mhz= 1560MHz INFO: dfs DDR fsp_param[1].freq_mhz= 324MHz INFO: dfs DDR fsp_param[2].freq_mhz= 528MHz INFO: dfs DDR fsp_param[3].freq_mhz= 780MHz INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: BL31: Initializing runtime services INFO: BL31: Initializing BL32 I/TC: I/TC: Start rockchip platform init I/TC: Rockchip release version: 1.0 I/TC: OP-TEE version: 3.6.0-307-g0b06ae94 #1 Fri May 7 01:52:27 UTC 2021 aarch64 I/TC: Initialized INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0xa00000 INFO: SPSR = 0x3c9 U-Boot 2017.09 (Apr 24 2022 - 07:36:50 +0000) Model: Hardkernel ODROID-M1 PreSerial: 2, raw, 0xfe660000 DRAM: 7.7 GiB Sysmem: init Relocation Offset: ecc5e000 Relocation fdt: eb3f8990 - eb3fecf0 CR: M/C/I SF: Detected sfc_nor with page size 256 Bytes, erase size 4 KiB, total 16 MiB Bootdev(atags): mtd 2 PartType: EFI MMC error: The cmd index is 0, ret is -110 mmc_init: -110, time 33 ** Bad device mmc 2 ** MMC error: The cmd index is 0, ret is -110 mmc_init: -110, time 33 ** Bad device mmc 2 ** MMC error: The cmd index is 0, ret is -110 mmc_init: -110, time 33 ** Bad device mmc 2 ** SF: Detected sfc_nor with page size 256 Bytes, erase size 4 KiB, total 16 MiB device 0 offset 0x400000, size 0xc00000 SF: 12582912 bytes @ 0x400000 Read: OK device 0 offset 0xe0000, size 0x20000 SF: 131072 bytes @ 0xe0000 Read: OK No misc partition boot mode: None FIT: No boot partition ### CRAMFS load complete: 127256 bytes loaded to 0xa100000 Error binding driver 'gpio_led': -22 Some drivers failed to bind I2c3 speed: 100000Hz PMIC: RK8090 (on=0x10, off=0x00) vdd_logic init 900000 uV vdd_gpu init 900000 uV vdd_npu init 900000 uV io-domain: OK SF: Detected mx25u12835f with page size 256 Bytes, erase size 4 KiB, total 16 MiB MMC: dwmmc@fe2b0000: 1, dwmmc@fe2c0000: 2, sdhci@fe310000: 0 Could not find baseparameter partition Rockchip UBOOT DRM driver version: v1.0.1 VOP have 1 active VP vp0 have layer nr:6[0 2 4 1 3 5 ], primary plane: 4 vp1 have layer nr:0[], primary plane: 0 vp2 have layer nr:0[], primary plane: 0 xfer: num: 2, addr: 0x50 xfer: num: 2, addr: 0x50 Monitor has basic audio support Could not find baseparameter partition mode:1920x1080 hdmi@fe0a0000: detailed mode clock 148500 kHz, flags[5] H: 1920 2008 2052 2200 V: 1080 1084 1089 1125 bus_format: 2025 VOP update mode to: 1920x1080p0, type: HDMI0 for VP0 VOP VP0 enable Smart0[1920x1080->1920x1080@0x0] fmt[0] addr[0xed800000] CEA mode used vic=16 final pixclk = 148500000 tmdsclk = 148500000 PHY powered down in 0 iterations PHY PLL locked 1 iterations PHY powered down in 0 iterations PHY PLL locked 1 iterations sink has audio support hdmi_set_clk_regenerator: fs=48000Hz ftdms=148.500MHz N=6144 cts=148500 Model: Hardkernel ODROID-M1 MMC error: The cmd index is 1, ret is -110 Card did not respond to voltage select! mmc_init: -95, time 19 ** Bad device mmc 0 ** MMC error: The cmd index is 1, ret is -110 Card did not respond to voltage select! mmc_init: -95, time 19 ** Bad device mmc 0 ** ** Invalid partition 2 ** device 0 offset 0x300000, size 0x100000 SF: 1048576 bytes @ 0x300000 Read: OK VOP VP0 enable Smart0[1280x720->1920x1080@0x0] fmt[1] addr[0xedfe907a] CLK: (sync kernel. arm: enter 816000 KHz, init 816000 KHz, kernel 0N/A) apll 816000 KHz dpll 780000 KHz gpll 1188000 KHz cpll 1000000 KHz npll 1200000 KHz vpll 24000 KHz hpll 148000 KHz ppll 200000 KHz armclk 816000 KHz aclk_bus 150000 KHz pclk_bus 100000 KHz aclk_top_high 500000 KHz aclk_top_low 400000 KHz hclk_top 150000 KHz pclk_top 100000 KHz aclk_perimid 300000 KHz hclk_perimid 150000 KHz pclk_pmu 100000 KHz No misc partition Net: No ethernet found. Hit key to stop autoboot('CTRL+C'): 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3920 bytes read in 24 ms (159.2 KiB/s) ## Executing script at 00c00000 Boot script loaded from mmc 1:1 "Error" handler, esr 0xbe000011 * Reason: Exception from SError interrupt * PC = 0000000000aad208 * LR = 0000000000a8ca30 * SP = 00000000eb3f6020 * ESR_EL2 = 00000000be000011 * Reloc Off = 00000000ecc5e000 x0 : 0000000009000000 x1 : 00000000eb3f6200 x2 : 00000000000000b2 x3 : 0000000000000040 x4 : 00000000000000b0 x5 : 0000000000000016 x6 : 682d383635336b72 x7 : 0000000080000010 x8 : 0000000080000014 x9 : 0000000000000008 x10: 00000000ffffffd8 x11: 0000000000000010 x12: 0000000000000002 x13: 0000000000000004 x14: 00000000eb3f887c x15: 0000000000000002 x16: 0000000000000001 x17: 0000000000000000 x18: 00000000eb3ffcf8 x19: 00000000000000b2 x20: 00000000eb6464e0 x21: 0000000000247008 x22: 0000000009000000 x23: 00000000eb3f6200 x24: 00000000eb3f6440 x25: 00000000ed7ca568 x26: 0000000000247008 x27: 0000000000000000 x28: 0000000000000009 x29: 00000000eb3f6680 Call trace: PC: [< 00aad208 >] LR: [< 00a8ca30 >] Stack: [< 00aad208 >] [< 00a88be0 >] [< 00a88d84 >] [< 00a878c0 >] [< 00a87cc4 >] [< 00a329a8 >] [< 00a1bb78 >] [< 00a1bd10 >] [< 00a1b478 >] [< 00a1b940 >] [< 00a1b7ec >] [< 00a1bd10 >] [< 00a1b430 >] [< 00a31ebc >] [< 00a079b0 >] [< 00a07ab8 >] [< 00a329a8 >] [< 00a1bb78 >] [< 00a1bd10 >] [< 00a1b478 >] [< 00a1b940 >] [< 00a1bd10 >] [< 00a1b430 >] [< 00a31f6c >] [< 00a329a8 >] [< 00a1bb78 >] [< 00a1b7ec >] [< 00a1b7ec >] [< 00a1bd10 >] [< 00a1b430 >] [< 00a31f6c >] [< 00a329a8 >] [< 00a1bb78 >] [< 00a1b7ec >] [< 00a1bd10 >] [< 00a1b430 >] [< 00a31f6c >] [< 00a329a8 >] [< 00a1bb78 >] [< 00a1b7ec >] [< 00a1b7ec >] [< 00a1bd10 >] [< 00a1b430 >] [< 00a31f6c >] [< 00a329a8 >] [< 00a1bb78 >] [< 00a1b7ec >] [< 00a1bd10 >] [< 00a1b430 >] [< 00a31f6c >] [< 00a329a8 >] [< 00a1bb78 >] [< 00a1bd10 >] [< 00a1b430 >] [< 00a31f6c >] [< 00a329a8 >] [< 00a1bb78 >] [< 00a1bd10 >] [< 00a1b478 >] [< 00a1b940 >] [< 00a1b7ec >] [< 00a1bd10 >] [< 00a1b430 >] [< 00a31f6c >] [< 00a329a8 >] [< 00a1bb78 >] [< 00a1bd10 >] [< 00a1b430 >] [< 00a31ebc >] [< 00a1c3b8 >] [< 00a19e98 >] [< 00a1ca4c >] [< 00a94214 >] [< 00a1ce44 >] [< 00a01df4 >] Copy info from "Call trace..." to a file(eg. dump.txt), and run command in your U-Boot project: ./scripts/stacktrace.sh dump.txt Resetting CPU ... ### ERROR ### Please RESET the board ###

Thanks @Igor, I did this and also modified BOARDFAMILY=rockchip64 LINUXFAMILY=rockchip64 then I used armbian-config to update the kernel and header files. This seemed to work. Unfortunately now the system has an boot issue (system is installed on /dev/nvme0n1p2) I inserted a new sdcard having current fresh image installed and tried to roll back using armbian-config mounting the partition from ssd using chroot without luck. Questions: should installing another kernel work from within chroot'ed mounted root device? how can I install the bootloader correctly - or at least how could I fix this? if starting with new image from scratch is the only/better option: is it save to run armbian-install from a new image keeping my separate data partition on the nvme? I'm willing to help document things like how to manually do the bootloader setup on the command line to also help others to help themselves, but then I need some assistence or pointers where to go. Just in case the issue is caused be the modified armbian-release: # PLEASE DO NOT EDIT THIS FILE BOARD=odroidm1 BOARD_NAME="Odroid M1" #BOARDFAMILY=rk3568-odroid BOARDFAMILY=rockchip64 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=014eb55b5 #LINUXFAMILY=rk3568-odroid LINUXFAMILY=rockchip64 ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=wip #BOARD_TYPE=conf BOOT_SOC=rk3568 INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image FORCE_BOOTSCRIPT_UPDATE= FORCE_UBOOT_UPDATE= VENDOR="Armbian" VENDORDOCS="https://docs.armbian.com" VENDORURL="https://www.armbian.com/" VENDORSUPPORT="https://forum.armbian.com" VENDORBUGS="https://www.armbian.com/bugs" BOOTSCRIPT_FORCE_UPDATE="no" BOOTSCRIPT_DST="boot.cmd" VERSION=23.11.1 REVISION=23.11.1 BRANCH=edge

@SteeMan, thanks for the prompt feedback. Very strange: something removed `/etc/armbian-release` from the system. Could this be regenerated? armbian-image-release is still there. I guess I understand now also the problems I had already previously with I initially installed jammy 24.2.1 having `LINUXFAMILY=rk3568-odroid` but since then Odroid M1 was merged into rockchip64 Having the `/etc/armbian-release` file removed is something else of course ... I'm trying to collect the variables in armbian-release by hand

I have a strange issue trying to update/switch kernel and installed header packages: when I open armbian-config > System > Other the tool loads 137 sources and then shows the warning by switching as expected but then returns to the "System Settings" menu without doing anything same issue when trying to install kernel headers - just doing nothing I worked around for now by manually install the required headers from https://mirrors.dotsrc.org/armbian-apt/pool/main/l/ but next time I do a apt upgrade this will byte me again. is there any log where I can see possible issues? Is there a way to check / fix the armbian-config setup? I'm running on Armbian 24.5.1 jammy (odroidm1 6.8.11-edge-rockchip64) Thanks for any hint

Thanks @Igor for your help, yes, I did, but now found out, that installed headers are: /usr/src/linux-headers-6.6.16-current-rockchip64 while kernel still was Linux odroidm1 6.1.12-rk3568-odroid #23.02.2 SMP PREEMPT Sat Feb 18 00:05:38 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux I got my Frozen kernel in armbian-config somehow solved by updating firmware and rebooting several times. Now kernel and headers are in sync again and zfs-module gets loaded! I will need to reanimate my odroidc2, which I use as a standby for the odroidm1, since that device doesn't boot any more after reinstall latest kernel, but that's another story ... Thanks!

additional info: in armbian-config I see, that the kernel is frozen (I can't remembere to have that configured) When I select "Defreeze", the dialog just returns and still offers "Defreeze". On a odroidc2 I have similar issue with headers not regognized: In armbian-config of the odroidc2 device the kernel was not frozen so I could update to the latest (6.7.4-edge-meson64) installed headers: linux-headers-current-meson64/jammy,now 24.2.1 arm64 [installed] but `apt-get --reinstall install zfs-dkms` also returns Loading new zfs-2.2.3 DKMS files... Building for 6.7.4-edge-meson64 Module build for kernel 6.7.4-edge-meson64 was skipped since the kernel headers for this kernel does not seem to be installed.

Im running Armbian 24.2.1 jammy on odroidm1 with additional zfs volumes. On update, sometimes I had to reinstall the zfs kernel module, but now I have the problem, that the system does not recognize the kernel headers: sudo apt-get --reinstall install zfs-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 2,397 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://mirrors.dotsrc.org/armbian-apt jammy/jammy-utils arm64 zfs-dkms all 2.2.3-1 [2,397 kB] Fetched 2,397 kB in 1s (3,567 kB/s) Preconfiguring packages ... (Reading database ... 72929 files and directories currently installed.) Preparing to unpack .../zfs-dkms_2.2.3-1_all.deb ... Deleting module zfs-2.2.3 completely from the DKMS tree. Unpacking zfs-dkms (2.2.3-1) over (2.2.3-1) ... Setting up zfs-dkms (2.2.3-1) ... Loading new zfs-2.2.3 DKMS files... Building for 6.1.12-rk3568-odroid Module build for kernel 6.1.12-rk3568-odroid was skipped since the kernel headers for this kernel does not seem to be installed. Processing triggers for initramfs-tools (0.140ubuntu13.4) ... update-initramfs: Generating /boot/initrd.img-6.1.12-rk3568-odroid W: Possible missing firmware /lib/firmware/nvidia/tegra194/xusb.bin for built-in driver xhci_tegra W: Possible missing firmware /lib/firmware/nvidia/tegra186/xusb.bin for built-in driver xhci_tegra W: Possible missing firmware /lib/firmware/nvidia/tegra210/xusb.bin for built-in driver xhci_tegra W: Possible missing firmware /lib/firmware/nvidia/tegra124/xusb.bin for built-in driver xhci_tegra update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.12-rk3568-odroid Image Name: uInitrd Created: Thu Apr 25 11:27:48 2024 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 27753116 Bytes = 27102.65 KiB = 26.47 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.12-rk3568-odroid to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.1.12-rk3568-odroid' update-initramfs: Armbian: done. I already removed and reinstalled the headers via armbian-config > Headers_remove, Headers_install but without change. apt-get list --installed |grep header linux-headers-edge-rockchip64/jammy,now 24.2.1 arm64 [installed] do I need to create some magic symlinks or parameters for apt-get to get the headers resolved since the kernel version is missing in the package?

I tried to update my odroidm1 to 23.11.2 (from 23.8.1) by fresh install using Armbian_23.11.2_Odroidm1_bookworm_current_6.1.68 flashed to sdcard but when booting the device (holding recovery button) I see "Gave up waiting for root file system device." The same issue when using the other CLI images flashed to sdcard. Any idea how to fix this? When mounting the sdcard from a ubuntu system the uuid seem to match and the sdcard is mountable.

unfortunately not - I suggested samsung support to upload the firmware there, but they suggested to send the ssd in. after a week it came back with new firmware ...

Thanks @Werner, I understand that this has no real "hard" effects and it's caused by using the ubuntu apt sources. I think the armbian version should better not be written into the distro specific release files, but into an independant armbian file (which needs to be introduced ...). Do you also have a hint for the upgrades? Since I installed the ubuntu (Jammy) variant I guess there will no upgrade somewhen later since ubuntu upgrade manager may not work. Is debian then the better decision since others had success with debian's `full-upgrade`? When I installed armbian, I didn't think about the possible upgrade consequences ... Feel free to move the subject to another hardware independant forum.

Sorry, if this is not odroid specific but I don't know if this issue is a armbian generic one: I guess also in armbian running apt update && apt upgrade is the correct way to install updates? When I run that from a Armbian 23.02.2 system I will get a Ubuntu 22.04 afterwards. before: cat /etc/issue Armbian 23.02.2 Jammy \l after: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy Similar question: What is the intended way to do an armbian upgrade? I did not find any hint in the documentation. In my current use case installing all from scratch would not be a big issue since I use the odroid to run lxd containers on a separate disk but if someone installs and configures a lot of software a fresh reinstall is maybe a big task. Thanks

Unfortunately there is no firmware update tool from samsung which runs on aarch64.

First, thanks to you guys for the great work you are doing for armbian! I am quite impressed and very happy to be able to run my odroid devices (c2, m1) on the latest kernel with zfs and lxd! What I'm wondering: since there is no such thing as do-release-upgrade in armbian: What are your best practices for upgrades to avoid being forced to always install and configure everything from scratch? Since I run most everything in lxd containers and use zfs on a separate disk, upgrading is as simple as installing/compiling zfs and lxd and restoring the lxd databases, but maybe there is a better approach besides reinstalling and compiling packages?

a big thumbs up! With the odroidm1 sid-build I managed for the first time to successfully test my use case with lxd and zfs! Only problem I had: After installing the zfsutils-linux the kernel module was missing: # /sbin/modprobe zfs modprobe: FATAL: Module zfs not found in directory /lib/modules/5.19.0-odroid-arm64 I got it working by manually installing/compiling the kernel module: apt install linux-headers-arm64 zfs-dkms Is this an issue in the debian upstream or in the armbian build? I am looking forward to a first release!