bananapinas

Ok, I repeated the update of bullseye to bookworm. But I did not apt upgrade (only apt update) from the bookworm armbian repository, which installed these packages last time armbian-bsp-cli-odroidn2 armbian-config armbian-zsh base-files linux-dtb-current-meson64 linux-image-current-meson64 linux-u-boot-odroidn2-current Instead I used armbian-config to switch kernels. This also updated the uboot, I think. U-Boot 2022.10-armbian (Feb 23 2024 - 10:32:33 +0000) odroid-n2/n2-plus And now it boots, monitor shows the startup and login does work: ___ _ _ _ _ _ ____ / _ \ __| |_ __ ___ (_) __| | | \ | |___ \ _ | | | |/ _` | '__/ _ \| |/ _` | | \| | __) || |_ | |_| | (_| | | | (_) | | (_| | | |\ |/ __/_ _| \___/ \__,_|_| \___/|_|\__,_| |_| \_|_____||_| Welcome to Armbian 24.2.1 Bookworm with Linux 6.6.16-current-meson64 # lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Armbian 24.2.1 bookworm Release: 12 Codename: bookworm # uname -mrs Linux 6.6.16-current-meson64 aarch64 # cat /etc/debian_version 12.5 Boot log now shows: U-Boot 2022.10-armbian (Feb 23 2024 - 10:32:33 +0000) odroid-n2/n2-plus Model: Hardkernel ODROID-N2 SoC: Amlogic Meson G12B (S922X) Revision 29:c (40:2) DRAM: 3.8 GiB Core: 388 devices, 27 uclasses, devicetree: separate MMC: sd@ffe05000: 0, mmc@ffe07000: 1 Loading Environment from nowhere... OK In: serial Out: serial Err: serial Board variant: n2-plus Net: dwmac_meson8b ethernet@ff3f0000: Can't get reset: -2 eth0: ethernet@ff3f0000 Hit any key to stop autoboot: 0 starting USB... Bus usb@ff500000: Register 3000140 NbrPorts 3 Starting the controller USB XHCI 1.10 scanning bus usb@ff500000 for devices... 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 8147 bytes read in 2 ms (3.9 MiB/s) ## Executing script at 08000000 U-boot default fdtfile: amlogic/meson-g12b-odroid-n2-plus.dtb Current variant: n2-plus For variant n2-plus (dash version, 2021.07 or up), set default fdtfile: amlogic/meson-g12b-odroid-n2-plus.dtb 161 bytes read in 2 ms (78.1 KiB/s) Current fdtfile after armbianEnv: amlogic/meson-g12b-odroid-n2-plus.dtb Mainline bootargs: root=UUID=efa55279-3372-4eee-9c23-7b26c477cfb0 rootwait rootfstype=ext4 splash=verbose console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=210296a2-01 libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=memory swapaccount=1 16364304 bytes read in 698 ms (22.4 MiB/s) 28346880 bytes read in 1208 ms (22.4 MiB/s) 80112 bytes read in 7 ms (10.9 MiB/s) 232 bytes read in 5 ms (44.9 KiB/s) Applying kernel provided DT fixup script (meson-fixup.scr) ## Executing script at 32000000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16364240 Bytes = 15.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Loading Ramdisk to 3f064000, end 3ffff2d0 ... OK Loading Device Tree to 000000003efe8000, end 000000003f063fff ... OK Starting kernel ... So everybody - thanks!

So, I got the boot log. It boots to an "emergency"? shell. Give root password for maintenance (or press Control-D to continue): after login I see: root@system:~# uname -a Linux system 5.10.60-meson64 #21.08.1 SMP PREEMPT Wed Aug 25 19:29:40 UTC 2021 aarch64 GNU/Linux I would expect 6.6.16 - no clue why it says 5.10.60, when in /boot/ anything sys 6.6.16. Full boot log follows. So what's wrong here? 😞 G12B:BL:6e7c85:2a3b91;FEAT:E0F83180:402000;POC:F;RCY:0;EMMC:0;READ:0;0. bl2_stage_init 0x01 bl2_stage_init 0x81 hw id: 0x0000 - pwm id 0x01 bl2_stage_init 0xc1 bl2_stage_init 0x02 L0:00000000 L1:00000703 L2:0000c067 L3:14000020 B2:00402000 B1:e0f83180 TE: 180255 BL2 Built : 06:17:13, Jun 28 2019. g12b gf0505d7-dirty - qi.duan@droid13 Board ID = 5 Set A53 clk to 24M Set A73 clk to 24M Set clk81 to 24M A53 clk: 1200 MHz A73 clk: 1200 MHz CLK81: 166.6M smccc: 00030852 eMMC boot @ 0 sw8 s DDR driver_vesion: LPDDR4_PHY_V_0_1_14 build time: Jun 28 2019 06:17:09 board id: 5 Load FIP HDR from eMMC, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0 fw parse done Load ddrfw from eMMC, src: 0x00030200, des: 0xfffd0000, size: 0x0000c000, part: 0 Load ddrfw from eMMC, src: 0x0002c200, des: 0xfffd0000, size: 0x00004000, part: 0 PIEI prepare done fastboot data load 00000000 emmc switch 1 ok 00000000 emmc switch 2 ok fastboot data verify verify result: 255 Cfg max: 2, cur: 1. Board id: 255. Force loop cfg DDR4 probe ddr clk to 1320MHz Load ddrfw from eMMC, src: 0x00014200, des: 0xfffd0000, size: 0x0000c000, part: 0 00000000 emmc switch 0 ok Check phy result INFO : End of initialization INFO : End of read enable training INFO : End of fine write leveling INFO : End of read dq deskew training INFO : End of MPR read delay center optimization INFO : End of Write leveling coarse delay INFO : End of write delay center optimization INFO : End of read delay center optimization INFO : End of max read latency training INFO : Training has run successfully! 1D training succeed Load ddrfw from eMMC, src: 0x00020200, des: 0xfffd0000, size: 0x0000c000, part: 0 Check phy result INFO : End of initialization INFO : End of 2D read delay Voltage center optimization INFO : End of 2D write delay Voltage center optimization INFO : Training has run successfully! R0_RxClkDly_Margin==70 ps 6 R0_TxDqDly_Margi==106 ps 9 R1_RxClkDly_Margin==0 ps 0 R1_TxDqDly_Margi==0 ps 0 dwc_ddrphy_apb_wr((0<<20)|(2<<16)|(0<<12)|(0xb0):0001 2D training succeed auto size-- 65535DDR cs0 size: 2048MB DDR cs1 size: 2048MB DMC_DDR_CTRL: 00600024DDR size: 3928MB cs0 DataBus test pass cs1 DataBus test pass cs0 AddrBus test pass cs1 AddrBus test pass pre test bdlr_100_average==407 bdlr_100_min==407 bdlr_100_max==407 bdlr_100_cur==407 aft test bdlr_100_average==407 bdlr_100_min==407 bdlr_100_max==407 bdlr_100_cur==407 non-sec scramble use zero key ddr scramble enabled 100bdlr_step_size ps== 398 result report boot times 0Enable ddr reg access 00000000 emmc switch 3 ok Authentication key not yet programmed get rpmb counter error 0x00000007 00000000 emmc switch 0 ok Load FIP HDR from eMMC, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 0 Load BL3X from eMMC, src: 0x0003c200, des: 0x0172c000, size: 0x00099400, part: 0 0.0;M3 CHK:0;cm4_sp_mode 0 E30HDR MVN_1=0x00000000 MVN_2=0x00000000 [Image: g12b_v1.1.3375-8f9c8a7 2019-01-24 10:44:46 guotai.shen@droid11-sz] OPS=0x40 ring efuse init chipver efuse init 29 0c 40 00 01 11 0c 00 00 07 31 33 32 58 33 50 [0.019858 Inits done] secure task start! high task start! low task start! run into bl31 NOTICE: BL31: v1.3(release):ab8811b NOTICE: BL31: Built : 15:03:31, Feb 12 2019 NOTICE: BL31: G12A normal boot! NOTICE: BL31: BL33 decompress pass ERROR: Error initializing runtime service opteed_fast U-Boot 2015.01 (Aug 08 2021 - 16:09:39) DRAM: 3.5 GiB Relocation Offset is: d6eeb000 spi_post_bind(spifc): req_seq = 0 register usb cfg[0][1] = 00000000d7f83db0 MMC: aml_priv->desc_buf = 0x00000000d3edb7c0 aml_priv->desc_buf = 0x00000000d3eddb00 SDIO Port C: 0, SDIO Port B: 1 co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x3, tx-dly 0, clock 400000 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x1, tx-dly 0, clock 40000000 aml_sd_retry_refix[983]:delay = 0x0,gadjust =0x2000 [mmc_startup] mmc refix success [mmc_init] mmc init success In: serial Out: serial Err: serial vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters vpu: driver version: v20190313 vpu: detect chip type: 9 vpu: clk_level default: 7(666667000Hz), max: 7(666667000Hz) vpu: clk_level = 7 vpu: vpu_power_on vpu: set_vpu_clk vpu: set clk: 666667000Hz, readback: 666666667Hz(0x100) vpu: set_vpu_clk finish vpu: vpu_module_init_config vpp: vpp_init vpp: g12a/b osd1 matrix rgb2yuv .............. vpp: g12a/b osd2 matrix rgb2yuv.............. vpp: g12a/b osd3 matrix rgb2yuv.............. cvbs: cpuid:0x29 cvbs_config_hdmipll_g12a cvbs_set_vid2_clk ** File not found boot-logo.bmp.gz ** ** File not found boot-logo.bmp ** movi: not registered partition name, logo movi - Read/write command from/to SD/MMC for ODROID board Usage: movi <read|write> <partition|sector> <offset> <address> [<length>] - <read|write> the command to access the storage - <offset> the offset from the start of given partiton in lba - <address> the memory address to load/store from/to the storage device - [<length>] the size of the block to read/write in bytes - all parameters must be hexa-decimal only [OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters [OSD]set initrd_high: 0x3d800000 [OSD]fb_addr for logo: 0x3d800000 [OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters [OSD]fb_addr for logo: 0x3d800000 [OSD]VPP_OFIFO_SIZE:0xfff01fff [CANVAS]canvas init [CANVAS]addr=0x3d800000 width=5760, height=2160 cvbs: outputmode[1080p60hz] is invalid vpp: vpp_matrix_update: 2 set hdmitx VIC = 16 config HPLL = 5940000 frac_rate = 1 HPLL: 0x3b3a04f7 HPLL: 0x1b3a04f7 HPLLv1: 0xdb3a04f7 config HPLL done j = 6 vid_clk_div = 1 hdmitx phy setting done hdmitx: set enc for VIC: 16 enc_vpu_bridge_reset[1319] rx version is 1.4 or below div=10 Net: dwmac.ff3f0000 syntax error Hit Enter or space or Ctrl+C key to stop autoboot -- : 0 ## Attempting fetch boot.ini in mmc:0... ** File not found boot.ini ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch boot.scr in mmc:0... ** File not found boot.scr ** ## Executing script at 04000000 Wrong image format for "source" command ## Attempting fetch /boot/boot.ini in mmc:0... 5579 bytes read in 4 ms (1.3 MiB/s) ## Executing script at 04000000 0 bytes read in 3 ms (0 Bytes/s) Found mainline kernel configuration edid extension block number : 2 Dump EDID Rawdata 000000000000000022f02033010000000a1b010380351e782ac020a656529c27 0f5054a10800d1c0b300a9c095008180810081c00101023a801871382d40582c 45000f282100001e000000fd00323c1e5011000a202020202020000000fc0048 5020323465730a2020202020000000ff0033434d37313031323246202020019f 020319b149901f0413031201021167030c0010000022e2002b023a801871382d 40582c45000f282100001e023a80d072382d40102c45800f282100001e011d00 7251d01e206e2855000f282100001e011d00bc52d01e20b82855400f28210000 1e8c0ad08a20e02d10103e96000f28210000180000000000000000000000000b No header found - count 0 hdmitx: read edid fails.. retry.. edid extension block number : 2 Dump EDID Rawdata 00ffffffffffff0022f02033010000000a1b010380351e782ac020a656529c27 0f5054a10800d1c0b300a9c095008180810081c00101023a801871382d40582c 45000f282100001e000000fd00323c1e5011000a202020202020000000fc0048 5020323465730a2020202020000000ff0033434d37313031323246202020019f 020319b149901f0413031201021167030c0010000022e2002b023a801871382d 40582c45000f282100001e023a80d072382d40102c45800f282100001e011d00 7251d01e206e2855000f282100001e011d00bc52d01e20b82855400f28210000 1e8c0ad08a20e02d10103e96000f28210000180000000000000000000000000b Manufacturer: HWP Model 3320 Serial Number 1 EDID version: 1.3 Established timings supported: 720x400@70Hz 640x480@60Hz 800x600@60Hz 1024x768@60Hz Standard timings supported: 1920x1080@60Hz 1680x1050@60Hz 1600x900@60Hz 1440x900@60Hz 1280x1024@60Hz 1280x800@60Hz 1280x720@60Hz Detailed mode (1) : Clock 148 MHz, 527 mm x 296 mm 1920 2008 2052 2200 hborder 0 1080 1084 1089 1125 vborder 0 +hsync +vsync Monitor ranges (GTF): 50-60Hz V, 30-80kHz H, max dotclock 170MHz Monitor name: HP 24es Serial number: 3CM710122F Has 1 extension blocks Checksum: 0x9f (valid) CEA extension block Extension version: 3 21 bytes of CEA data VIC 16 1920x1080@60Hz (native) VIC 31 1920x1080@50Hz VIC 4 1280x720@60Hz VIC 19 1280x720@50Hz VIC 3 720x480@60Hz VIC 18 720x576@50Hz VIC 1 640x480@60Hz VIC 2 720x480@60Hz VIC 17 720x576@50Hz Vendor-specific data block, OUI 000c03 (HDMI) Maximum TMDS clock: 170MHz YCbCr quantization: (0) RGB quantization: (0) PT scan behaviour: (2) IT scan behaviour: (2) CE scan behaviour: (3) Detailed mode (1) : Clock 148 MHz, 527 mm x 296 mm 1920 2008 2052 2200 hborder 0 1080 1084 1089 1125 vborder 0 +hsync +vsync Detailed mode (1) : Clock 148 MHz, 527 mm x 296 mm 1920 2448 2492 2640 hborder 0 1080 1084 1089 1125 vborder 0 +hsync +vsync Detailed mode (1) : Clock 74 MHz, 527 mm x 296 mm 1280 1390 1430 1650 hborder 0 720 725 730 750 vborder 0 +hsync +vsync Detailed mode (1) : Clock 74 MHz, 527 mm x 296 mm 1280 1720 1760 1980 hborder 0 720 725 730 750 vborder 0 +hsync +vsync Detailed mode (1) : Clock 27 MHz, 527 mm x 296 mm 720 736 798 858 hborder 0 480 489 495 525 vborder 0 -hsync -vsync Checksum: 0xb (valid) bestmode is custombuilt, IEEEOUI 0x000c03 HDMI Mode bestmode is custombuilt, IEEEOUI 0x000c03 HDMI Mode 161 bytes read in 3 ms (51.8 KiB/s) ** File not found uImage ** 25461312 bytes read in 713 ms (34.1 MiB/s) ** File not found dtb/amlogic/meson-g12b-odroid-n2-plus.dtb ** 80112 bytes read in 13 ms (5.9 MiB/s) ** File not found uInitrd ** 16366032 bytes read in 460 ms (33.9 MiB/s) ee_gate_off ... ## Booting kernel from Legacy Image at 01100000 ... Image Name: Linux Image Type: AArch64 Linux Kernel Image (uncompressed) Data Size: 25461248 Bytes = 24.3 MiB Load Address: 01080000 Entry Point: 01080000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 03700000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16365968 Bytes = 15.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK active_slot is <NULL> Unknown command 'store' - try 'help' No dtbo patitions found load dtb from 0x1000000 ...... ## Flattened Device Tree blob at 01000000 Booting using the fdt blob at 0x1000000 No valid dtbo image found Loading Kernel Image(COMP_NONE) ... OK kernel loaded at 0x01080000, end = 0x028c8200 libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND [rsvmem] fdt get prop fail. Loading Ramdisk to 3c864000, end 3d7ff990 ... OK Loading Device Tree to 000000001ffe9000, end 000000001ffff8ef ... OK Starting kernel ... uboot time: 8836498 us Give root password for maintenance (or press Control-D to continue): root@system:~# uname -a Linux system 5.10.60-meson64 #21.08.1 SMP PREEMPT Wed Aug 25 19:29:40 UTC 2021 aarch64 GNU/Linux root@system:~# cat /var/log/apt/history.log Start-Date: 2024-04-03 10:11:58 Commandline: apt upgrade --without-new-pkgs Upgrade: libnetfilter-conntrack3:arm64 (1.0.8-3, 1.0.9-3... End-Date: 2024-04-03 10:16:32 Start-Date: 2024-04-03 10:20:02 Commandline: apt full-upgrade Install: libperl5.36:arm64 (5.36.0-7+deb12u1, automatic), libnode108:arm64 (18.19.0+... End-Date: 2024-04-03 10:52:59 Start-Date: 2024-04-03 10:59:13 Commandline: apt full-upgrade Upgrade: php-redis:arm64 (6.0.2-1+0~20231128.56+debian11~1.gbp9f3071, 6.0.2-1+0~20231128.56+debian12~1.gbp9f3071), ... End-Date: 2024-04-03 11:00:44 Start-Date: 2024-04-03 11:53:03 Commandline: apt full-upgrade Install: armbian-bsp-cli-odroidn2-current:arm64 (24.2.1) Upgrade: armbian-config:arm64 (23.02.2, 24.2.1), linux-image-current-meson64:arm64 (21.08.1, 24.2.1), armbian-zsh:arm64 (23.02.2, 24.2.1), linux-u-boot-odroidn2-current:arm64 (21.08.1, 24.2.1), base-files:arm64 (12.4+deb12u5, 24.2.1-12.4+deb12u5-bookworm), linux-dtb-current-meson64:arm64 (21.08.1, 24.2.1), armbian-bsp-cli-odroidn2:arm64 (23.02.2, 24.2.1) End-Date: 2024-04-03 11:54:34 root@system:~# content of /boot drwxr-xr-x 3 root root 4096 3. Apr 11:58 . drwxrwxrwx 19 root root 4096 3. Apr 11:54 .. -rw-r--r-- 1 root root 161 3. Apr 11:58 armbianEnv.txt -rw-r--r-- 1 root root 161 2. Nov 2021 armbianEnv.txt.old -rw-r--r-- 1 root root 1531 30. Okt 2021 armbian_first_run.txt.template -rw-r--r-- 1 root root 38518 26. Aug 2021 boot.bmp -rw-r--r-- 1 root root 8075 3. Apr 11:54 boot.cmd -rw-r--r-- 1 root root 5579 16. Jun 2023 boot.ini -rw-r--r-- 1 root root 8147 3. Apr 11:54 boot.scr -rw-r--r-- 1 root root 258772 29. Feb 18:56 config-6.6.16-current-meson64 -rwxr-xr-x 1 root root 120 1. Jan 1970 display.bin lrwxrwxrwx 1 root root 26 3. Apr 11:54 dtb -> dtb-6.6.16-current-meson64 drwxr-xr-x 3 root root 4096 3. Apr 11:53 dtb-6.6.16-current-meson64 -rwxr-xr-x 1 root root 256 1. Jan 1970 edid.bin lrwxrwxrwx 1 root root 30 3. Apr 11:54 Image -> vmlinuz-6.6.16-current-meson64 -rw-r--r-- 1 root root 16365968 3. Apr 11:54 initrd.img-6.6.16-current-meson64 -rw-r--r-- 1 root root 0 3. Apr 11:54 .next -rw-r--r-- 1 root root 4424139 29. Feb 18:56 System.map-6.6.16-current-meson64 -rw-r--r-- 1 root root 25461312 9. Dez 2021 uImage lrwxrwxrwx 1 root root 30 3. Apr 11:54 uInitrd -> uInitrd-6.6.16-current-meson64 -rw-r--r-- 1 root root 16366032 3. Apr 11:54 uInitrd-6.6.16-current-meson64 -rw-r--r-- 1 root root 28346880 29. Feb 18:56 vmlinuz-6.6.16-current-meson64 content of /boot/dtb/amlogic: root@system:/boot# ls dtb/amlogic/ amlogic-c3-c302x-aw409.dtb meson-gxl-s805x-p241.dtb amlogic-t7-a311d2-an400.dtb meson-gxl-s905d-libretech-pc.dtb amlogic-t7-a311d2-khadas-vim4.dtb meson-gxl-s905d-mecool-kii-pro.dtb meson-a1-ad401.dtb meson-gxl-s905d-p230.dtb meson-axg-jethome-jethub-j100.dtb meson-gxl-s905d-p231.dtb meson-axg-jethome-jethub-j110-rev-2.dtb meson-gxl-s905d-phicomm-n1.dtb meson-axg-jethome-jethub-j110-rev-3.dtb meson-gxl-s905d-sml5442tw.dtb meson-axg-s400.dtb meson-gxl-s905d-vero4k-plus.dtb meson-g12a-radxa-zero.dtb meson-gxl-s905w-jethome-jethub-j80.dtb meson-g12a-radxa-zero-spidev.dtb meson-gxl-s905w-p281.dtb meson-g12a-sei510.dtb meson-gxl-s905w-tx3-mini.dtb meson-g12a-u200.dtb meson-gxl-s905x-hwacom-amazetv.dtb meson-g12a-x96-max.dtb meson-gxl-s905x-khadas-vim.dtb meson-g12b-a311d-bananapi-m2s.dtb meson-gxl-s905x-libretech-cc.dtb meson-g12b-a311d-khadas-vim3.dtb meson-gxl-s905x-libretech-cc-v2.dtb meson-g12b-a311d-khadas-vim3-spidev.dtb meson-gxl-s905x-nexbox-a95x.dtb meson-g12b-a311d-khadas-vim3-spinor.dtb meson-gxl-s905x-p212.dtb meson-g12b-bananapi-cm4-cm4io.dtb meson-gxm-gt1-ultimate.dtb meson-g12b-gsking-x.dtb meson-gxm-khadas-vim2.dtb meson-g12b-gtking.dtb meson-gxm-mecool-kiii-pro.dtb meson-g12b-gtking-pro.dtb meson-gxm-mini-m8s-pro.dtb meson-g12b-odroid-go-ultra.dtb meson-gxm-minix-neo-u9h.dtb meson-g12b-odroid-n2.dtb meson-gxm-nexbox-a1.dtb meson-g12b-odroid-n2l.dtb meson-gxm-q200.dtb meson-g12b-odroid-n2-plus.dtb meson-gxm-q201.dtb meson-g12b-odroid-n2-plus-spidev.dtb meson-gxm-rbox-pro.dtb meson-g12b-odroid-n2-plus-spinor.dtb meson-gxm-s912-libretech-pc.dtb meson-g12b-odroid-n2-spinor.dtb meson-gxm-t95z-plus.dtb meson-g12b-radxa-zero2.dtb meson-gxm-vega-s96.dtb meson-g12b-radxa-zero2-spidev.dtb meson-gxm-wetek-core2.dtb meson-g12b-s922x-bananapi-m2s.dtb meson-s4-s805x2-aq222.dtb meson-g12b-s922x-khadas-vim3.dtb meson-sm1-a95xf3-air.dtb meson-g12b-ugoos-am6.dtb meson-sm1-a95xf3-air-gbit.dtb meson-g12b-waveshare-cm4-io-base-b.dtb meson-sm1-bananapi-m2-pro.dtb meson-gxbb-kii-pro.dtb meson-sm1-bananapi-m5.dtb meson-gxbb-nanopi-k2.dtb meson-sm1-h96-max.dtb meson-gxbb-nexbox-a95x.dtb meson-sm1-khadas-vim3l.dtb meson-gxbb-odroidc2.dtb meson-sm1-khadas-vim3l-spidev.dtb meson-gxbb-p200.dtb meson-sm1-khadas-vim3l-spinor.dtb meson-gxbb-p201.dtb meson-sm1-odroid-c4.dtb meson-gxbb-vega-s95-meta.dtb meson-sm1-odroid-c4-spidev.dtb meson-gxbb-vega-s95-pro.dtb meson-sm1-odroid-hc4.dtb meson-gxbb-vega-s95-telos.dtb meson-sm1-sei610.dtb meson-gxbb-wetek-hub.dtb meson-sm1-x96-air.dtb meson-gxbb-wetek-play2.dtb meson-sm1-x96-air-gbit.dtb meson-gxl-s805x-libretech-ac.dtb overlay Before the last upgrade (with armbian bookworm repository), there was an directory rockchip in /boot/dtb (as link to dtb-5.10.60-meson64) root@system:/boot/dtb-5.10.60-meson64# ls -al insgesamt 16 drwxr-xr-x 4 root root 4096 9. Dez 2021 . drwxr-xr-x 3 root root 4096 3. Apr 16:48 .. drwxr-xr-x 3 root root 4096 9. Dez 2021 amlogic drwxr-xr-x 2 root root 4096 9. Dez 2021 rockchip

ok, many thanks so far. Will take some time to get the serial console output, the n2's UART port is not usable with normal jumper cables... so will need to get the official uart kit, I fear. But until then, one last question: as the to bookworm upgraded system was fine until the last updates from the armbian repository, would it be ok to use bookworm with the old kernel 5.10.60?

Ok thanks, will try to capture the boot log and see what I can find, if there is some output. But another question: would it be possible to replace the whole /boot/ directory of the not-working bookworm with the contents of the bullseye installation? I'm really not good with kernel, booting, ... - but as far as I understand, the last apt update did mess up the /boot directory. Bookworm started before these updates.. and I would guess, the last 3 are responsible.. armbian-bsp-cli-odroidn2 armbian-config armbian-zsh base-files linux-dtb-current-meson64 linux-image-current-meson64 linux-u-boot-odroidn2-current

Hi, can someone help me, I got an odroid n2 with emmc. For years I was running buster. Now because of end of updates, I upgraded from buster to bullseye - everything was fine there. After upgrading to bullseye I tried to update to bookworm. Upgrade itself seemed ok, all packages installed. I did it like described here After updating to the "default debian bookworm", I commented in the Armbian repository with bullseye in armbian.list, and it updated this packages armbian-bsp-cli-odroidn2 armbian-config armbian-zsh base-files linux-dtb-current-meson64 linux-image-current-meson64 linux-u-boot-odroidn2-current Now, it does not boot any longer. Monitor only shows black, turns on from standby (backlit) and off again. Repeats every 10-30s maybe. How could I figure out what the issue is? After upgrading to bullseye, i got this configuration: # lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye # uname -mrs Linux 5.10.60-meson64 aarch64 # cat /etc/debian_version 11.9 The upgrade output was: user@odroidn2:/etc/apt# apt full-upgrade Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Paketaktualisierung (Upgrade) wird berechnet… Fertig Das folgende Paket wurde automatisch installiert und wird nicht mehr benötigt: armbian-bsp-cli-odroidn2 Verwenden Sie »apt autoremove«, um es zu entfernen. Die folgenden NEUEN Pakete werden installiert: armbian-bsp-cli-odroidn2-current Die folgenden Pakete werden aktualisiert (Upgrade): armbian-bsp-cli-odroidn2 armbian-config armbian-zsh base-files linux-dtb-current-meson64 linux-image-current-meson64 linux-u-boot-odroidn2-current 7 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. Es müssen 57,8 MB an Archiven heruntergeladen werden. Nach dieser Operation werden 36,3 MB Plattenplatz zusätzlich benutzt. Möchten Sie fortfahren? [J/n] Holen:1 http://apt.armbian.com bookworm/main arm64 base-files arm64 24.2.1-12.4+deb12u5-bookworm [53,1 kB] Holen:7 http://imola.armbian.com/apt bookworm/main arm64 linux-image-current-meson64 arm64 24.2.1 [44,5 MB] Holen:4 http://mirrors.xtom.de/armbian bookworm/main arm64 armbian-config all 24.2.1 [136 kB] Holen:2 http://fi.mirror.armbian.de/apt bookworm/main arm64 armbian-bsp-cli-odroidn2 arm64 24.2.1 [1.288 B] Holen:3 http://fi.mirror.armbian.de/apt bookworm/main arm64 armbian-bsp-cli-odroidn2-current arm64 24.2.1 [430 kB] Holen:5 http://fi.mirror.armbian.de/apt bookworm/main arm64 armbian-zsh all 24.2.1 [11,8 MB] Holen:6 http://fi.mirror.armbian.de/apt bookworm/main arm64 linux-dtb-current-meson64 arm64 24.2.1 [166 kB] Holen:8 http://fi.mirror.armbian.de/apt bookworm/main arm64 linux-u-boot-odroidn2-current arm64 24.2.1 [761 kB] Es wurden 57,8 MB in 7 s geholt (8.664 kB/s). (Lese Datenbank ... 58101 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../base-files_24.2.1-12.4+deb12u5-bookworm_arm64.deb ... Entpacken von base-files (24.2.1-12.4+deb12u5-bookworm) über (12.4+deb12u5) ... base-files (24.2.1-12.4+deb12u5-bookworm) wird eingerichtet ... (Lese Datenbank ... 58101 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../0-armbian-bsp-cli-odroidn2_24.2.1_arm64.deb ... Entpacken von armbian-bsp-cli-odroidn2 (24.2.1) über (23.02.2) ... dpkg: Warnung: Altes Verzeichnis »/usr/share/armbian« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/usr/local/bin« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/usr/local« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/usr/lib/chromium-browser« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/usr/lib/armbian« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer Vormals nicht ausgewähltes Paket armbian-bsp-cli-odroidn2-current wird gewählt. Vorbereitung zum Entpacken von .../1-armbian-bsp-cli-odroidn2-current_24.2.1_arm64.deb ... Armbian 'armbian-bsp-cli-odroidn2-current' for '1-PC13d1-V2d94-H02fb-Ba537-R6632': 'preinst' starting. Armbian 'armbian-bsp-cli-odroidn2-current' for '1-PC13d1-V2d94-H02fb-Ba537-R6632': 'preinst' finishing. Entpacken von armbian-bsp-cli-odroidn2-current (24.2.1) ... Vorbereitung zum Entpacken von .../2-armbian-config_24.2.1_all.deb ... Entpacken von armbian-config (24.2.1) über (23.02.2) ... Vorbereitung zum Entpacken von .../3-armbian-zsh_24.2.1_all.deb ... Entpacken von armbian-zsh (24.2.1) über (23.02.2) ... Vorbereitung zum Entpacken von .../4-linux-dtb-current-meson64_24.2.1_arm64.deb ... Armbian 'linux-dtb-current-meson64' for '6.6.16-current-meson64': 'preinst' starting. Armbian 'linux-dtb-current-meson64' for '6.6.16-current-meson64': 'preinst' finishing. Entpacken von linux-dtb-current-meson64 (24.2.1) über (21.08.1) ... Vorbereitung zum Entpacken von .../5-linux-image-current-meson64_24.2.1_arm64.deb ... Armbian 'linux-image-current-meson64' for '6.6.16-current-meson64': 'preinst' starting. Armbian 'linux-image-current-meson64' for '6.6.16-current-meson64': 'preinst' finishing. Entpacken von linux-image-current-meson64 (24.2.1) über (21.08.1) ... Vorbereitung zum Entpacken von .../6-linux-u-boot-odroidn2-current_24.2.1_arm64.deb ... Entpacken von linux-u-boot-odroidn2-current (24.2.1) über (21.08.1) ... armbian-zsh (24.2.1) wird eingerichtet ... armbian-config (24.2.1) wird eingerichtet ... linux-image-current-meson64 (24.2.1) wird eingerichtet ... Armbian 'linux-image-current-meson64' for '6.6.16-current-meson64': 'postinst' starting. dkms: autoinstall for kernel 6.6.16-current-meson64 was skipped since the kernel headers for this kernel do not seem to be installed. update-initramfs: Generating /boot/initrd.img-6.6.16-current-meson64 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.16-current-meson64 Image Name: uInitrd Created: Wed Apr 3 11:54:06 2024 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16365934 Bytes = 15982.36 KiB = 15.61 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.16-current-meson64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.6.16-current-meson64' update-initramfs: Armbian: done. Remove unused generated file: /boot/initrd.img-5.10.60-meson64 Remove unused generated file: /boot/uInitrd-5.10.60-meson64 Armbian: update last-installed kernel symlink to 'Image'... '/boot/Image' -> 'vmlinuz-6.6.16-current-meson64' Armbian: Debian compat: linux-update-symlinks install 6.6.16-current-meson64 boot/vmlinuz-6.6.16-current-meson64 I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.6.16-current-meson64 I: /initrd.img.old is now a symlink to boot/initrd.img-6.6.16-current-meson64 I: /vmlinuz is now a symlink to boot/vmlinuz-6.6.16-current-meson64 I: /initrd.img is now a symlink to boot/initrd.img-6.6.16-current-meson64 Armbian 'linux-image-current-meson64' for '6.6.16-current-meson64': 'postinst' finishing. linux-dtb-current-meson64 (24.2.1) wird eingerichtet ... Armbian 'linux-dtb-current-meson64' for '6.6.16-current-meson64': 'postinst' starting. Armbian: DTB: symlinking /boot/dtb to /boot/dtb-6.6.16-current-meson64... 'dtb' -> 'dtb-6.6.16-current-meson64' Armbian 'linux-dtb-current-meson64' for '6.6.16-current-meson64': 'postinst' finishing. linux-u-boot-odroidn2-current (24.2.1) wird eingerichtet ... Armbian 'uboot-odroidn2-current' for '2022.10-S4deb-P35fb-H24ab-V33c2-B11a8-R448a': 'postinst' starting. Armbian 'uboot-odroidn2-current' for '2022.10-S4deb-P35fb-H24ab-V33c2-B11a8-R448a': 'postinst' finishing. armbian-bsp-cli-odroidn2-current (24.2.1) wird eingerichtet ... Armbian 'armbian-bsp-cli-odroidn2-current' for '1-PC13d1-V2d94-H02fb-Ba537-R6632': 'postinst' starting. '/boot/boot.cmd' -> '/usr/share/armbian/boot.cmd-1712138049' NOTE: You can find previous bootscript versions in /usr/share/armbian ! Recreating boot script '/usr/share/armbian/boot.cmd' -> '/boot/boot.cmd' sed: -e Ausdruck #1, Zeichen 76: Nicht beendeter »s«-Befehl sed: -e Ausdruck #1, Zeichen 47: Nicht beendeter »s«-Befehl Armbian 'armbian-bsp-cli-odroidn2-current' for '1-PC13d1-V2d94-H02fb-Ba537-R6632': 'postinst' finishing. Trigger für mandb (2.11.2-2) werden verarbeitet ... Trigger für cracklib-runtime (2.9.6-5+b1) werden verarbeitet ... Trigger für initramfs-tools (0.142) werden verarbeitet ... update-initramfs: Generating /boot/initrd.img-6.6.16-current-meson64 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.16-current-meson64 Image Name: uInitrd Created: Wed Apr 3 11:54:31 2024 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16365968 Bytes = 15982.39 KiB = 15.61 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.16-current-meson64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.6.16-current-meson64' update-initramfs: Armbian: done. armbian-bsp-cli-odroidn2 (24.2.1) wird eingerichtet ... user@odroidn2:/etc/apt# I mounted the emmc on another system and the boot directory looks like this: drwxr-xr-x 3 root root 4096 3. Apr 14:29 . drwxrwxrwx 19 root root 4096 3. Apr 11:54 .. -rw-r--r-- 1 root root 161 3. Apr 11:58 armbianEnv.txt -rw-r--r-- 1 root root 161 2. Nov 2021 armbianEnv.txt.old -rw-r--r-- 1 root root 1531 30. Okt 2021 armbian_first_run.txt.template -rw-r--r-- 1 root root 38518 26. Aug 2021 boot.bmp -rw-r--r-- 1 root root 8075 3. Apr 11:54 boot.cmd -rw-r--r-- 1 root root 5579 16. Jun 2023 boot.ini -rw-r--r-- 1 root root 8147 3. Apr 11:54 boot.scr -rw-r--r-- 1 root root 258772 29. Feb 18:56 config-6.6.16-current-meson64 -rwxr-xr-x 1 root root 120 1. Jan 1970 display.bin lrwxrwxrwx 1 root root 26 3. Apr 11:54 dtb -> dtb-6.6.16-current-meson64 drwxr-xr-x 3 root root 4096 3. Apr 11:53 dtb-6.6.16-current-meson64 -rwxr-xr-x 1 root root 256 1. Jan 1970 edid.bin lrwxrwxrwx 1 root root 30 3. Apr 11:54 Image -> vmlinuz-6.6.16-current-meson64 -rw-r--r-- 1 root root 16365968 3. Apr 11:54 initrd.img-6.6.16-current-meson64 -rw-r--r-- 1 root root 0 3. Apr 11:54 .next -rw-r--r-- 1 root root 4424139 29. Feb 18:56 System.map-6.6.16-current-meson64 -rw-r--r-- 1 root root 25461312 9. Dez 2021 uImage lrwxrwxrwx 1 root root 30 3. Apr 11:54 uInitrd -> uInitrd-6.6.16-current-meson64 -rw-r--r-- 1 root root 16366032 3. Apr 11:54 uInitrd-6.6.16-current-meson64 -rw-r--r-- 1 root root 28346880 29. Feb 18:56 vmlinuz-6.6.16-current-meson64 And now, I'm completely lost! No clue what to do or where to look. Any help would be appreciated!

Hi, ok, what a pity. But I have no clue how to update the system to a RC, what would be the only way for now, no time for a setup starting at zero. Or is there a possibility to upgrade from a running 21.08..? With 21.08, I have a rock solid and stable system - no problems at all. I'll try another SD Card after cloning the emmc and updating to the newest 21.08 kernel/uboot, as soon as there is some spare time...

@rpardini I got some time to care about this. I found the "u-boot update" is now available. It wasn't in december, quite sure. Because after the bad update I reverted and set the dtb-current and image-current to hold, and only these 2, to not have this issue again. But I don't think it's a solution to hold back kerne lupdate. So today the u-boot was updated also, as I use an emmc for booting and running, the sd card is used for data. So I got an image of the emmc and updated all packages. Result: sd card won't be detected with error "Kernel message: mmc0: error -84 whilst initialising SD card - repeated every few seconds." with newest kernel and uboot - it does not work. The 21.08.6/21.08.8, versions fail, but the 21.08.1 versions are fine of these packages linux-dtb-current-meson64/buster 21.08.6 arm64 [aktualisierbar von: 21.08.1] linux-image-current-meson64/buster 21.08.6 arm64 [aktualisierbar von: 21.08.1] linux-u-boot-odroidn2-current/buster 21.08.8 arm64 [aktualisierbar von: 21.08.1] So I think this is a bug. The sd card is an A1 card. Any help?

Hi rpadini, well I just did a apt dist-upgrade - don't know if uboot was updated. I also don't know how to update the uboot for the n2, esp. how to get a related u boot version, can you support me? I have a spare emmc which i could my live emmc could be mirrored to for a test.. KR & thanks!

Any help?

I created the armbianmonitor -u logs: http://ix.io/3Ja2 Can someone help?

Hi, please ignore my username, it's quite old. System is an odroid n2+. After updating the system (apt dist-upgrade) and updating linux-image-current-meson64:arm64 21.08.1 to 21.08.6, my sd card could not be mount anymore. New firmware was: linux-image-current-meson64=21.08.6 / 5.10.81-meson64 System runs from emmc. The 256gb sd card is used for more internal storage. Kernel message: mmc0: error -84 whilst initialising SD card - repeated every few seconds. Downgrade back to linux-image-current-meson64=21.08.01 / 5.10.??-meson64 (did not remember minor version while changing kernel in armbian-config): works again as expected! After some digging and comments about sd card size, voltage, ..., i also found this: https://github.com/armbian/build/pull/3154 and the comment there: "remove the UHS-enabling patch, to avoid 1.8v vs 3.3v mess. Make sure to use only A1-rated SD cards as recommended." SD card is this one, labeled as A1: https://www.amazon.de/gp/product/B07H9FVB6M Works gread and flawless with previous kernel since some months. As I don't see this as a feature, is it a bug? If reported, any chance for a fix in a next firmware/kernel,.? Thanks Alex

With linux-image-next-sunxi, linux-dtb-next-sunxi and linux-u-boot-bananapipro-next = 5.31: up time 39 days

After over 20 days uptime without a freeze I got 2 freezes within 24hours. I never rolled back though, running > 20 days with linux-image-next-sunxi: 5.41 linux-dtb-next-sunxi: 5.41 linux-u-boot-bananapipro-next: 5.41 Rolled these 3 now back to 5.31 - let's see... should I downgrade the linux-headers also?

Great, thanks. apt-cache policy shows version 5.35 and 5.31 for uboot and image. image 5.32 has no matching uboot. So I'll try 5.35 first and if it occurs again I'll try 5.31. But so far your help is really appreciated. I really like the armbian project and will use it on my raspberries and banana pi (without pro) soon also. Donation on the way

Hi Igor, thanks for the reply. Does "was found in the latest update" means "it's a known issue, problem found" or "it could be the latest kernel update"? Sorry as obviously i'm not a native speaker.. And - never did this - how do i roll back a kernel? After that I'll freeze for some weeks.. TIA!

I additionaly observed now with armbianmonitor -m that the cpu frequency seems to be fixed at 960mhz with just one lower value 528mhz, even if there is no heavy load (load = 0.15-0.3, %cpu avg. <10%, cpu temp ~33-34°C). So it looks like cpufrequtils are working, but why is the frequency that high..?

Maybe I'll have a look at it, but I'm not sure if this would help at all. If it's an hardware issue (board, sd card, hdd, powering) this wouldn't change anything - also I don't believe it is, as it worked before, and I'll after the next freeze change hdd and sd card back to the "bananian system originals". And if it's an os issue it would stay there with armbian, sooner or later also OMV will use the 5.38 kernel I think (?). But before trying something completely else like OMV I'd like to try to get this freezing issue fixed... just need to know how to find out.. would a serial console UART log help here?

yes I tried it once before setting up my own solution about a year ago. I did not really like it then It seemed slow and overloaded, and I prefer(ed) nextcloud over owncload. But both the old bananian and new armbian systems were/are working really fine, everything is ok - apart from the freezes...

I think I got the same or similar issue with a banana pi pro. I used the board about a year with the latest bananian os without an issue, rock solid, uptimes up to 1 month (then planed shutdown for backup image of the sd card). 2.5" hdd attached through the SATA port. Now I migrated to the latest 5.38 debian with mainline kernel . Output of armbian-monitor -u here: http://ix.io/Fpe Sporadic "freezes" - after just one hour runtime or (max for now) 14h. Symptoms: - no hdmi output after turning on monitor. - the green onboard led was used for "cpu" as trigger - led is just on so I assume 100% CPU usage. - the blue onboard led was used for "mmc0" - zero activity then - green led of eth0 blinks periodic - yellow led of eth0 blinks sporadic - ssh no connect possible After repowering and startup CPU shows high temperature after login (nearly 50°C). System is used as nextcloud and samba server. Installed packages mainly are nginx, mariadb, php7/fpm, samba, default-jdk-headless, proftpd-basic, nfs-kernel-server Every time while freezing there was no special user activity, at night or early in the morning. At max one nextcloud windows client syncing, all other clients (user / hardware :)) sleeping or not at home. So far I tried: 1) Monitoring CPU load / processes with top every minute and write to a file on the sdcard. Last full output @08:13:16 (yesterday) top - 08:13:16 up 1:09, 2 users, load average: 0,09, 0,14, 0,13 Tasks: 128 total, 1 running, 88 sleeping, 0 stopped, 0 zombie %Cpu(s): 2,2 us, 6,1 sy, 0,1 ni, 91,3 id, 0,3 wa, 0,0 hi, 0,0 si, 0,0 st KiB Mem : 1022524 total, 587192 free, 162788 used, 272544 buff/cache KiB Swap: 131068 total, 131068 free, 0 used. 800756 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4499 root 20 0 8664 3092 2680 R 16,7 0,3 0:00.08 top 1 root 20 0 25928 5484 3808 S 0,0 0,5 0:08.51 systemd 2 root 20 0 0 0 0 S 0,0 0,0 0:00.01 kthreadd 4 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/0:+ 6 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 mm_percpu_+ 7 root 20 0 0 0 0 S 0,0 0,0 0:00.16 ksoftirqd/0 ..... Next output 1 min later was interrupted while writing (?) top - 08:14:17 up 1:10, 2 users, load average: 0,08, 0,12, 0,13 Tasks: 128 total, 1 running, 88 sleeping, 0 stopped, 0 zombie %Cpu(s): 2,2 us, 6,1 sy, 0,1 ni, 91,4 id, 0,3 wa, 0,0 hi, 0,0 si, 0,0 st KiB Mem : 1022524 total, 587148 free, 162820 used, 272556 buff/cache KiB Swap: 131068 total, 131068 free, 0 used. 800732 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4528 root 20 0 8664 3116 2704 R 20,0 0,3 0:00.07 top 4481 root 20 0 0 0 0 I 5,0 0,0 0:02.14 kworker/1:0 1 root 20 0 25928 5484 3808 S 0,0 0,5 0:08.52 systemd 2 root 20 0 0 0 0 S 0,0 0,0 0:00.01 kthreadd 4 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/0:+ 6 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 mm_percpu_+ 7 root 20 0 0 0 0 S 0,0 0,0 0:00.16 ksoftirqd/0 8 root 20 0 0 0 0 I 0,0 0,0 0:00.69 rcu_sched 9 root 20 0 0 0 0 I 0,0 0,0 0:00.00 rcu_bh 10 root rt 0 0 0 0 S 0,0 0,0 0:00.03 migration/0 11 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/0 12 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/1 13 root rt 0 0 0 0 S 0,0 0,0 0:00.03 migration/1 14 root 20 0 0 0 0 S 0,0 0,0 0:00.46 ksoftirqd/1 16 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/1:+ 17 root 20 0 0 0 0 S 0,0 0,0 0:00.02 kdevtmpfs 18 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 netns 21 root 20 0 0 0 0 S 0,0 0,0 0:00.00 oom_reaper 22 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 writeback 23 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kcompactd0 24 root 25 5 0 0 0 S 0,0 0, <-- here it ends 2) Using as accesspoint: I used the new armbian system as an access point (wlan0->eth0 bridge) with br0 in /etc/network/interfaces and hostapd. I disabled this again - it was the only difference in usage between bananian and armbian. Did not help 3) Power: powering while using with bananian was done through the micro usb port, and the hdd was attached to the onboard power jack - worked without an issue. I thought about improving this while migrating to armbian and changed to another power supply and powering the hdd directly from this and powering the board through the now unsed jack (which previously powered the hdd). I changed this back to the old power supply and wiring scheme - result unknown, waiting to see if it happens again. Note: other changes from bananian to armbian were: - using another SD card - but same model (transcend ultimate 600x 8GB, as recommended here https://docs.armbian.com/User-Guide_Getting-Started/). The card used for armbian was brand new. Maybe dd the armbian system to the previously used bananian sd card? - 2.5" hdd upgraded from seagate 250GB to western digital 1TB - could this worth the change back? Any ideas what to check / look for? Any help very appreciated. I'm not an expert in linux but got some basic skills and aim to learn