Search the Community

Using a 256G emmc and the server image v6.12 my Odroid N2+ doesn't boot. Here is the log. The Homeassistant image works. Would be nice to understand why it doesn't boot. <00><00><00>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: 196470 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: 000347a9 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: 0x00060200, des: 0xfffd0000, size: 0x0000c000, part: 0 Load ddrfw from eMMC, src: 0x00038200, 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==94 ps 8 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==425 bdlr_100_min==425 bdlr_100_max==425 bdlr_100_cur==425 aft test bdlr_100_average==425 bdlr_100_min==425 bdlr_100_max==425 bdlr_100_cur==425 non-sec scramble use zero key ddr scramble enabled 100bdlr_step_size ps== 425 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: 0x0006c200, des: 0x0175c000, size: 0x0009aa00, 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 03 0d 00 00 07 39 31 4e 31 53 50 [0.019859 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 <debug_uart> serial_meson serial@3000: pincu U-Boot 2022.10-armbian-2022.10-S4deb-Pa713-H24ab-V6e0a-Bb703-R448a (Jan 24 2025 - 02:39:57 +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: 2 <08><08><08> 1 <08><08><08> 0 starting USB… Bus usb@ff500000: Register 3000140 NbrPorts 3 Starting the controller USB XHCI 1.10 scanning bus usb@ff500000 for devices… Failed to get keyboard state from device 1915:1047 3 USB Device(s) found scanning usb for storage devices… 0 Storage Device(s) found Device 0: unknown device Card did not respond to voltage select! : -110 unable to select a mode : -5 MMC Device 2 not found no mmc device at slot 2 Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.1.179 (29 ms) *** Warning: no boot file name; using ‘C0A801B3.img’ Using ethernet@ff3f0000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.179 Filename ‘C0A801B3.img’. Load address: 0x1000000 Loading: *<08>T T T T T T T T T T Retry count exceeded; starting again missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-00-1e-06-42-56-3a Speed: 1000, full duplex Using ethernet@ff3f0000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.179 Filename ‘pxelinux.cfg/01-00-1e-06-42-56-3a’. Load address: 0x1080000 Loading: *<08>T T T T T T T

I have been trying to diagnose a QHYCCD camera problem on a N2 running INDI server. Everything appears to work fine but after several minutes the device fails to respond. The device is only supported by QHY on a true USB3 slot. Looking on other forums USB and cable stability are a common problem with these QHY devices so falling onto the wrong USB bus would definitely be a problem. However looking at lsusb I can see the device has dropped onto the wrong USB bus: $ lsusb Bus 002 Device 002: ID 05e3:0620 Genesys Logic, Inc. USB3.1 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04a9:3217 Canon, Inc. Canon Digital Camera Bus 001 Device 008: ID 1618:0716 QHYCCD QHY715U3G20-20230106 Bus 001 Device 006: ID 1a86:7523 QinHeng Electronics CH340 serial converter Bus 001 Device 005: ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu [AC1200 Techkey] Bus 001 Device 004: ID 0483:5740 STMicroelectronics Virtual COM Port Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The QHYCCD is showing up on USB bus 1 (which I'm sure is the USB2 480M) Confirmed here by lsusb -ttv $ lsusb -ttv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 1: Dev 4, If 0, Class=Communications, Driver=cdc_acm, 12M ID 0483:5740 STMicroelectronics Virtual COM Port |__ Port 1: Dev 4, If 1, Class=CDC Data, Driver=cdc_acm, 12M ID 0483:5740 STMicroelectronics Virtual COM Port |__ Port 2: Dev 5, If 0, Class=Vendor Specific Class, Driver=rtl88x2bu, 480M ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu [AC1200 Techkey] |__ Port 3: Dev 6, If 0, Class=Vendor Specific Class, Driver=ch341, 12M ID 1a86:7523 QinHeng Electronics CH340 serial converter |__ Port 4: Dev 8, If 0, Class=Vendor Specific Class, Driver=usbfs, 480M ID 1618:0716 |__ Port 2: Dev 2, If 0, Class=Imaging, Driver=usbfs, 480M ID 04a9:3217 Canon, Inc. I'm running the Armbian version of Ubuntu 22.04 with kernel 6.12.22 Linux odroidn2-1 6.12.22-current-meson64 #1 SMP PREEMPT Mon Apr 7 08:08:37 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux. Further : This only occurs if the USB3 device is connected during boot. If the same USB3 device is plugged in well after boot it is correctly detected as a HIGH speed USB device. I'm looking for any ideas on forcing this device to be detected as a high speed USB3 device during boot time. So I don;t have to keep remembering to unplug and plug it back in. Also posted in the Odroid and INDI forums. Further update : More testing shows the boot selection for USB bus is random. Sometimes the device is detected as USB2 and other times USB3. Walter Zambotti N2 - 22.04 Armbian xfce desktop N2+ - CoreElec KODI

Dear all, I am trying to install ZFS on my ODROID N2+ without success. I am sure this question has been asked before, but I don't think the answers I found are still relevant, unfortunately. Linux odroid 6.6.47-current-meson64 #3 SMP PREEMPT Mon Aug 19 04:04:32 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux BOARD=odroidn2 BOARD_NAME="Odroid N2" BOARDFAMILY=meson-g12b BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=89476e86f LINUXFAMILY=meson64 ARCH=arm64 BOOT_SOC= IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image KERNEL_TARGET=current,edge KERNEL_TEST_TARGET=current FORCE_BOOTSCRIPT_UPDATE=yes FORCE_UBOOT_UPDATE= OVERLAYDIR="/boot/dtb/amlogic/overlay" 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="yes" BOOTSCRIPT_DST="boot.cmd" VERSION=24.8.4 REVISION=24.8.4 BRANCH=current Using armbian-config, I installed the kernel headers, and also the full firmware for good measure. After restarting the board, I run `apt install zfs-dkms zfsutils-linux`, but I get Preparing to unpack .../zfsutils-linux_2.2.6-0arter97~ubuntu22.04.1_arm64.deb ... Unpacking zfsutils-linux (2.2.6-0arter97~ubuntu22.04.1) ... Selecting previously unselected package zfs-dkms. Preparing to unpack .../zfs-dkms_2.2.6-0arter97~ubuntu22.04.1_all.deb ... Unpacking zfs-dkms (2.2.6-0arter97~ubuntu22.04.1) ... Setting up zfsutils-linux (2.2.6-0arter97~ubuntu22.04.1) ... modprobe: FATAL: Module zfs not found in directory /lib/modules/6.6.47-current-meson64 Trying to create a pool raises this error zpool create wdred_zpool raidz2 x y z The ZFS modules cannot be auto-loaded. Try running 'modprobe zfs' as root to manually load them. modprobe zfs modprobe: FATAL: Module zfs not found in directory /lib/modules/6.6.47-current-meson64 Any ideas? Thank you in advance.

I am having trouble installing specific hardware dkms because the dkms requires the linux header files for the installed kernel version which are not available or do not exist. Armbian 23.05.1 Ubuntu 22.04 desktop version is build with kernel 6.6.63 but an apt search for the relevant headers finds none. Headers exist for 6.2, 6.5 and 6.8 but not for 6.6. How can I address this?

Odroid N2+ booting from eMMC with a 4TB USB drive. With the USB drive disconnected, the system boots fine and very quickly. With the USB drive connected, it throws hundreds of errors for about 30 seconds before finally moving on and booting from the eMMC. I have no desire to ever boot from SD or USB, so I would like to just disable those options. I found this topic https://forum.armbian.com/topic/10349-disable-u-boot-usb-support/ but I can't really follow what they're talking about and I have no idea how to patch U-boot or build a new boot image. Is there an easier way to do this? Here's what the errors look like: Hit any key to stop autoboot: 2 1 0 starting USB... Bus usb@ff500000: Register 3000140 NbrPorts 3 Starting the controller USB XHCI 1.10 scanning bus usb@ff500000 for devices... GPT: first_usable_lba incorrect: 800 > 0 find_valid_gpt: *** ERROR: Invalid GPT *** GUID Partition Table Header signature is wrong: 0xF0F7C330 != 0x5452415020494645 find_valid_gpt: *** ERROR: Invalid Backup GPT *** GPT: first_usable_lba incorrect: 800 > 0 find_valid_gpt: *** ERROR: Invalid GPT *** GUID Partition Table Header signature is wrong: 0xF0F7C330 != 0x5452415020494645 find_valid_gpt: *** ERROR: Invalid Backup GPT *** GPT: first_usable_lba incorrect: 800 > 0 >>>>> ( Repeated a few hundred times ) <<<< find_valid_gpt: *** ERROR: Invalid GPT *** GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645 find_valid_gpt: *** ERROR: Invalid Backup GPT *** ** Invalid partition 1 ** Couldn't find partition usb 0:1 Card did not respond to voltage select! : -110 switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr >>>>>>>( Then it boots normally )<<<<<<<<<<

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!

After an update to Armbian 23.05.1 Ubuntu one of my Wifi adapters no longer sees any access point and can't be forced to connect blindly. The two adapters are very similar: The two adapters are very similar: Working Wifi Module 5B: |__ Port 2: Dev 9, If 2, Class=Vendor Specific Class, Driver=rtl8821cu, 480M ID 0bda:c820 Realtek Semiconductor Corp. /sys/bus/usb/devices/1-1.2 /dev/bus/usb/001/009 Not working Wifi Module 5A: |__ Port 4: Dev 10, If 0, Class=Vendor Specific Class, Driver=rtl88XXau, 480M ID 0bda:a811 Realtek Semiconductor Corp. RTL8811AU 802.11a/b/g/n/ac WLAN Adapter /sys/bus/usb/devices/1-1.4 /dev/bus/usb/001/010``` nmcli shows both devices nmcli device DEVICE TYPE STATE CONNECTION wlx200bd04dc584 wifi connected asuszamb 2 wlx40a5eff399ea wifi disconnected -- p2p-dev-wlx200bd04dc584 wifi-p2p disconnected -- p2p-dev-wlx40a5eff399ea wifi-p2p disconnected -- eth0 ethernet unavailable -- lo loopback unmanaged -- wlx40a5eff399ea is the device that has stopped working. if I display the access points visible to each device: nmcli device wifi list ifname wlx200bd04dc584 IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY 3C:7C:3F:6B:EA:2C asuszamb Infra 36 540 Mbit/s 95 ▂▄▆█ WPA2 3C:7C:3F:6B:EA:28 asuszamb Infra 2 405 Mbit/s 74 ▂▄▆_ WPA2 32:46:9A:FF:E2:B9 asuszamb_EXT Infra 10 130 Mbit/s 64 ▂▄▆_ WPA2 4C:0F:6E:AD:AB:07 PS3-1880660 Infra 10 54 Mbit/s 39 ▂▄__ WPA1 6A:19:4D:28:72:DD -- Infra 161 540 Mbit/s 25 ▂___ WPA2 B0:92:4A:C7:E2:BD OPTUS_C7E2BBM Infra 11 540 Mbit/s 20 ▂___ WPA2 WPA3 72:19:4D:28:72:DC OPTUS_C7E2BBM Infra 11 130 Mbit/s 17 ▂___ WPA2 WPA3``` The other adapter should show the same access points but: nmcli device wifi list ifname wlx40a5eff399ea IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY Attempting to make a connection via the not working adapter results in: nmcli con up 175a67a0-d58d-4ebe-8d02-6f3c741c460b ap 3C:7C:3F:6B:EA:2C ifname wlx40a5eff399ea Error: device 'wlx40a5eff399ea' not compatible with connection 'asuszamb'.

I would like to update/upgrade to the latest dist for the Armbian N2 without completely re-installing. Is this supported and possible?In order to update to the latest Armbian

I have multiple n2s and I don't want them all to be called odroidn2. What is the recommended way to change the hostname of an armbian system?

In my quest to use an ODROID N2 as a time server, I had to figure out how to enable UART_EE_A. Device trees for other boards sometimes enable UART A in the base device tree but the ODROID N2/N2+ does not. I am not sure why device trees don't fully define devices like UART_A and then just leave them disabled instead of partially defining them with missing "pinctrl" entries (as in the N2 device tree). Anyway, I've attached `meson-g12b-odroid-uart-ee-a.dtso` as an example of how to enable UART_EE_A. Additionally: The DT overlays for Meson UARTs (e.g. `/boot/dtb/amlogic/overlay/meson-uartA.dtbo`) are not compatible with the N2. It's a source of confusion for new users. I noticed a problem in the current `armbian-config` scripting. I originally named the overlay as `meson-g12b-odroid-uartA` but selecting it would also enable `meson-uartA`. Probably a regexp/sed issue. meson-g12b-odroid-uart-ee-a.dtso

Hi, I've been using the /dev/ttyAML1 UART port on my Odroid N2+ at the GPIO pins 8 and 10 with buster. With the update to bullseye, the /dev/ttyAML1 device disappeared. Also now in bookworm it is no longer present. Now I happen to need the UART at GPIO 8 and 10 again and did some more persistent research and came across this post over in the DietPI forum. It provided an alternative meson-g12b-odroid-n2-plus.dtb which I installed in my system. Since then my /dev/ttyAML1 device is back and I can use the UART at GPIO 8 and 10 as I wished. However, I am a bit nervous, since I just installed some binary dtb file to my system at a path which is owned by the linux-dtb-current-meson64 package. So it is endangered by a system update. Is there an "official" way to get back my /dev/AML1 UART device which is sustainable? Thank you very much

Hi I was trying out Armbian_24.2.1_Odroidn2_bookworm_current_6.6.16_cinnamon_desktop.img.xz and its not booting when you have a usb hdd connected. It works pefectly fine on bullseye image. Also tryed some other hdd on usb Board variant: n2-plus Net: dunac_neson8b ethernet@ff3f0000: Can't get reset: -2 ethe: ethernet@ff310000 Hit any key to stop autoboot: 0 starting USB... Bus usb@ff500000: Register 3000140 MbrPorts 3 Starting the controller USB XHCI 1.10 scanning bus usbeff500000 for devices... unable to get device descriptor (error-1) WARN halted endpoint, queueing URB anyway. Unexpected XHCI event TRB, skipping... (f0f719c0 00000000 13000000 04008400) the https://paste.armbian.com/peromuzibi is the bullseye one.

Hello all, I am using an Odroid N2 with a 16Gb emmc and Armbian Bookworm. However as this got a bit small, I installed Armbian Bookworm to a new 64Gb emmc (Armbian is installed on an SD and can then be copied/installed to emmc). This seemed to work fine, and I had a running system. However, on the 3rd or 4th reboot, I got the error that the file "boot.scr" wasn't readable. With that, the emmc was not bootable anymore. I reinstalled multiple times, and each time, the emmc would work for a 2-5 boots, but no more. Each time, i got the error as above, or the error as below (partition could not be found) I never had this issue with the 16Gb emmc? Does anyone know this behaviour, or better: does anyone know what is causing this and how to solve it? thanks,

I was hoping to get some idea if it would be possible to build Armbian for the ODroid OGU (S922X, similar to N2+) using a different Kernel. Specifically, using the version from JelOS (https://github.com/JustEnoughLinuxOS/distribution) who have made really good progress for this specific device. I've been building JelOS and modifying packages etc, but would prefer to use Armbian if possible. Any help appreciated.

Has anyone updated their odroid-HC4 with the latest kernel and firmware versions? I am currently running Armbian 24.2.1 Bookworm with Linux 6.1.63-current-meson64.

I upgraded the kernel today via apt-get update/upgrade and it seems kernel for armbian 23.08 is being pushed to users with 23.02 breaking a bunch of stuff. After upgrading the kernel ethernet stops working and requires the user to manually downgrade kernel, uboot (and dtb?). I am currently on "current" kernel (6.1.11-meson64) I'm thinking of downgrading to legacy (5.xx) via armbian-config, does anyone know if this is safe?

Armbian_23.11.1_Odroidn2_bookworm_current_6.1.63.img.xz was downloaded and flashed to SD card. System booted OK from the SD card and successfully started the OS. Then I used armbian-config to write the root file system to an SSD. After reboot, the system appears to get through the boot stage OK. It also proceeds to start up the OS OK, but then services fail to start. Further action stops temporarily, but pressing the escape key or a function key makes the screen go black for a second or so, returning with what's shown in the last image. No other keys have any effect. The system appears to be locked up and unusable at that point.

Hello, i need to activate the serial port on the odroid N2-plus, the serial port is on pins (J2 - 2x20 PINS) 8/10. Usually this uart with ubuntu is at /dev/ttyS1. If I try to use it on armbian I get an input/output error. I read the following post, I understand that it is not implemented yet. Can anyone point me in the direction of trying to do this?

Installing Bullseye from download list works fine, but after `apt update / apt upgrade` or a firmware update through armbian-config, boot process gets stuck with Uboot logo in the corner and won't proceed any further. Any ideas? Using a EMMC card and BalenaEtcher to burn.

Hello, Since I upgraded my Odroid N2+ to Armbian 23.11, when connecting to SSH, I can read the following: Welcome to Armbian 23.11.1 Buster with Linux 6.1.63-current-meson64 No end-user support: community creations & unsupported (buster) userspace! Since 23.08 I had the first part about only community creation, which I already did not understand but now it looks worse as it also mention Buster when I use Bookworm. What can cause this strange information? And what can I try to solve this?

Hi all, This used to work absolutely fine for me a couple of years ago but for some reason it isn't working at all now. I had to format the eMMC and re-flash it. Using either Bookworm or Jammy, when I try to run the script for boot from eMMC / system on NVME after the reboot it won't boot again. I've tried on both, tried before / after apt-update etc. Just doesn't seem to want to work when it used to in the past. This is what I'm seeing, apologies for phone photos, as I was in my living room, no way to take a screenshot. Any ideas? Thank you!

Hi all, Using Armbian Focal for a couple of years now and booting from an SSD plugged to USB (used the armbian installer to move to it) and it always worked perfectly but after an apt-update (stupid of me I know) I'm now stuck on a boot loop, it looks like the entire system is fubar'd. I don't mind formatting and reinstalling everything, the problem is that I lost the eMMC to USB converter I had and can't find any in the UK... Attached an image of what I'm seeing. Anything I can do to either salvage or do a fresh new install without the eMMC converter? Can be removed. Did a full format.

I'm using the Odroid N2/N2+ 23.5 Jammy minimal image. I then updated and upgraded successfully. I then attempted to install MATE via tasksel (which I installed) but that immediate fails with an apt package missing error. SO then I tried to install MATE manually by: $ sudo apt install mate-desktop-environment mate-desktop-environement-extras $ reboot There didn't seem to be any display manger installed so I stalled lighdm $ sudo apt install lightdm lighdm-gtk-greeter $ reboot Then I noticed that Xserver was not installed (really, that's no a MATE dependency!!!) $ sudo aqt install xserver-xorg $ reboot But the xserver was not starting and so I noticed xinit was not installed (really. why wouldn't this be a dependency of MATE or the xserver) $ sudo apt install xinit $ reboot Now it boots and starts everything and then switches to console tty07 but is just a black screen. I can see from console tty01 that all the correct (I assume) processes have started but nothing but a black screen. Xorg is running lightdm session is running lightdm-greeter-session is running lightdm-gtk-greeter is running But still no login screen (or mouse) is visible (just a blank screen) I can see the ~/.Xauthority file is blank so don't know what has happened. What else have I missed?

Armbian boot logo shows and also on shutdown.... just doesn't want to display the desktop. Gnome desktop image. 6.1.50-current-meson6 #2 SMP PREEMPT Wed Aug 30 14:11:13 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

Hi, On Debian 11 / n2+, I have updated 2 times my kernel. The first time: network was lost and the second, USB and NFS support was lost... Is there a good way to update kernel and firmware without loose anythink ? For information, the first upgrade (5.1 to 6.1) just after install is OK.