MarkP Posted April 15, 2023 Posted April 15, 2023 After updating my Odroid N2+ today, lo is the only network interface shown when running 'ip a' The update was 18 packages: root@odroidn2p10:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: armbian-config armbian-firmware armbian-zsh libldap-2.5-0 libldap-common libnss-myhostname libpam-systemd libsystemd0 libudev1 linux-dtb-current-meson64 linux-image-current-meson64 linux-u-boot-odroidn2-current python3-tz sudo systemd systemd-sysv tzdata udev 18 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 75.4 MB of archives. After this operation, 94.1 MB disk space will be freed. Do you want to continue? [Y/n] Get:7 http://ports.ubuntu.com jammy-updates/main arm64 libsystemd0 arm64 249.11-0ubuntu3.9 [314 kB] Get:1 http://armbian.chi.auroradev.org/apt jammy/main arm64 armbian-config all 23.05.0-trunk--1-SAed8f-Ba894 [134 kB] Get:2 http://armbian.tnahosting.net/apt jammy/main arm64 armbian-firmware all 23.05.0-trunk--1-SA56ad-Bf566 [10.1 MB] Get:3 http://armbian.chi.auroradev.org/apt jammy/main arm64 armbian-zsh all 23.05.0-trunk--1-SAb4f9-B379b [12.7 MB] Get:6 http://mirror.albony.xyz/armbian jammy/main arm64 linux-image-current-meson64 arm64 23.05.0-trunk--6.1.24-S0102-De8b2-Pc5ba-C072bHfe66-HK01ba-Ve377-Bf77d [43.5 MB] Get:8 http://ports.ubuntu.com jammy-updates/main arm64 systemd-sysv arm64 249.11-0ubuntu3.9 [10.5 kB] Get:9 http://ports.ubuntu.com jammy-updates/main arm64 libpam-systemd arm64 249.11-0ubuntu3.9 [205 kB] Get:10 http://ports.ubuntu.com jammy-updates/main arm64 systemd arm64 249.11-0ubuntu3.9 [4,421 kB] Get:4 http://armbian.chi.auroradev.org/apt jammy/main arm64 linux-u-boot-odroidn2-current arm64 23.05.0-trunk--2022.10-S4deb-P9295-Ha354-Ve16f-Baf4d [760 kB] Get:5 http://armbian.chi.auroradev.org/apt jammy/main arm64 linux-dtb-current-meson64 arm64 23.05.0-trunk--6.1.24-S0102-De8b2-Pc5ba-C072bHfe66-HK01ba-Ve377-Bf77d [132 kB] Get:11 http://ports.ubuntu.com jammy-updates/main arm64 udev arm64 249.11-0ubuntu3.9 [1,541 kB] Get:12 http://ports.ubuntu.com jammy-updates/main arm64 libudev1 arm64 249.11-0ubuntu3.9 [74.9 kB] Get:13 http://ports.ubuntu.com jammy-security/main arm64 sudo arm64 1.9.9-1ubuntu2.4 [807 kB] Get:14 http://ports.ubuntu.com jammy-security/main arm64 tzdata all 2023c-0ubuntu0.22.04.0 [335 kB] Get:15 http://ports.ubuntu.com jammy-updates/main arm64 libldap-2.5-0 arm64 2.5.14+dfsg-0ubuntu0.22.04.2 [181 kB] Get:16 http://ports.ubuntu.com jammy-updates/main arm64 libldap-common all 2.5.14+dfsg-0ubuntu0.22.04.2 [15.8 kB] Get:17 http://ports.ubuntu.com jammy-updates/main arm64 python3-tz all 2022.1-1ubuntu0.22.04.1 [30.7 kB] Get:18 http://ports.ubuntu.com jammy-updates/universe arm64 libnss-myhostname arm64 249.11-0ubuntu3.9 [53.4 kB] Fetched 75.4 MB in 17s (4,545 kB/s) Preconfiguring packages ... (Reading database ... 45489 files and directories currently installed.) Preparing to unpack .../libsystemd0_249.11-0ubuntu3.9_arm64.deb ... Unpacking libsystemd0:arm64 (249.11-0ubuntu3.9) over (249.11-0ubuntu3.7) ... Setting up libsystemd0:arm64 (249.11-0ubuntu3.9) ... (Reading database ... 45489 files and directories currently installed.) Preparing to unpack .../systemd-sysv_249.11-0ubuntu3.9_arm64.deb ... Unpacking systemd-sysv (249.11-0ubuntu3.9) over (249.11-0ubuntu3.7) ... Preparing to unpack .../libpam-systemd_249.11-0ubuntu3.9_arm64.deb ... Unpacking libpam-systemd:arm64 (249.11-0ubuntu3.9) over (249.11-0ubuntu3.7) ... Preparing to unpack .../systemd_249.11-0ubuntu3.9_arm64.deb ... Unpacking systemd (249.11-0ubuntu3.9) over (249.11-0ubuntu3.7) ... Preparing to unpack .../udev_249.11-0ubuntu3.9_arm64.deb ... Unpacking udev (249.11-0ubuntu3.9) over (249.11-0ubuntu3.7) ... Preparing to unpack .../libudev1_249.11-0ubuntu3.9_arm64.deb ... Unpacking libudev1:arm64 (249.11-0ubuntu3.9) over (249.11-0ubuntu3.7) ... Setting up libudev1:arm64 (249.11-0ubuntu3.9) ... (Reading database ... 45489 files and directories currently installed.) Preparing to unpack .../00-sudo_1.9.9-1ubuntu2.4_arm64.deb ... Unpacking sudo (1.9.9-1ubuntu2.4) over (1.9.9-1ubuntu2.3) ... Preparing to unpack .../01-tzdata_2023c-0ubuntu0.22.04.0_all.deb ... Unpacking tzdata (2023c-0ubuntu0.22.04.0) over (2022g-0ubuntu0.22.04.1) ... Preparing to unpack .../02-armbian-config_23.05.0-trunk--1-SAed8f-Ba894_all.deb ... Unpacking armbian-config (23.05.0-trunk--1-SAed8f-Ba894) over (23.02.2) ... Preparing to unpack .../03-armbian-firmware_23.05.0-trunk--1-SA56ad-Bf566_all.deb ... Unpacking armbian-firmware (23.05.0-trunk--1-SA56ad-Bf566) over (23.02.2) ... Preparing to unpack .../04-armbian-zsh_23.05.0-trunk--1-SAb4f9-B379b_all.deb ... Unpacking armbian-zsh (23.05.0-trunk--1-SAb4f9-B379b) over (23.02.2) ... Preparing to unpack .../05-libldap-2.5-0_2.5.14+dfsg-0ubuntu0.22.04.2_arm64.deb ... Unpacking libldap-2.5-0:arm64 (2.5.14+dfsg-0ubuntu0.22.04.2) over (2.5.14+dfsg-0ubuntu0.22.04.1) ... Preparing to unpack .../06-libldap-common_2.5.14+dfsg-0ubuntu0.22.04.2_all.deb ... Unpacking libldap-common (2.5.14+dfsg-0ubuntu0.22.04.2) over (2.5.14+dfsg-0ubuntu0.22.04.1) ... Preparing to unpack .../07-linux-u-boot-odroidn2-current_23.05.0-trunk--2022.10-S4deb-P9295-Ha354-Ve16f-Baf4d_arm64.deb ... Unpacking linux-u-boot-odroidn2-current (23.05.0-trunk--2022.10-S4deb-P9295-Ha354-Ve16f-Baf4d) over (23.02.2) ... Preparing to unpack .../08-python3-tz_2022.1-1ubuntu0.22.04.1_all.deb ... Unpacking python3-tz (2022.1-1ubuntu0.22.04.1) over (2022.1-1ubuntu0.22.04.0) ... Preparing to unpack .../09-libnss-myhostname_249.11-0ubuntu3.9_arm64.deb ... Unpacking libnss-myhostname:arm64 (249.11-0ubuntu3.9) over (249.11-0ubuntu3.7) ... Preparing to unpack .../10-linux-dtb-current-meson64_23.05.0-trunk--6.1.24-S0102-De8b2-Pc5ba-C072bHfe66-HK01ba-Ve377-Bf77d_arm64.deb ... Armbian 'linux-dtb-current-meson64' for '6.1.24-meson64': 'preinst' starting. + rm -rf /boot/dtb + rm -rf /boot/dtb-6.1.24-meson64 + set +x Armbian 'linux-dtb-current-meson64' for '6.1.24-meson64': 'preinst' finishing. Unpacking linux-dtb-current-meson64 (23.05.0-trunk--6.1.24-S0102-De8b2-Pc5ba-C072bHfe66-HK01ba-Ve377-Bf77d) over (23.02.2) ... Preparing to unpack .../11-linux-image-current-meson64_23.05.0-trunk--6.1.24-S0102-De8b2-Pc5ba-C072bHfe66-HK01ba-Ve377-Bf77d_arm64.deb ... Armbian 'linux-image-current-meson64' for '6.1.24-meson64': 'preinst' starting. + export 'DEB_MAINT_PARAMS=upgrade 23.02.2 23.05.0-trunk--6.1.24-S0102-De8b2-Pc5ba-C072bHfe66-HK01ba-Ve377-Bf77d' + DEB_MAINT_PARAMS='upgrade 23.02.2 23.05.0-trunk--6.1.24-S0102-De8b2-Pc5ba-C072bHfe66-HK01ba-Ve377-Bf77d' + export INITRD=Yes + INITRD=Yes + test -d /etc/kernel/preinst.d + run-parts --arg=6.1.24-meson64 --arg=/boot/vmlinuz-6.1.24-meson64 /etc/kernel/preinst.d + mountpoint -q /boot + set +x Armbian 'linux-image-current-meson64' for '6.1.24-meson64': 'preinst' finishing. Unpacking linux-image-current-meson64 (23.05.0-trunk--6.1.24-S0102-De8b2-Pc5ba-C072bHfe66-HK01ba-Ve377-Bf77d) over (23.02.2) ... Setting up systemd (249.11-0ubuntu3.9) ... Setting file flags is only supported on regular files and directories, cannot set on '/var/log/journal'. Setting file flags is only supported on regular files and directories, cannot set on '/var/log/journal'. Setting up libldap-common (2.5.14+dfsg-0ubuntu0.22.04.2) ... Setting up libldap-2.5-0:arm64 (2.5.14+dfsg-0ubuntu0.22.04.2) ... Setting up armbian-zsh (23.05.0-trunk--1-SAb4f9-B379b) ... Setting up tzdata (2023c-0ubuntu0.22.04.0) ... Current default time zone: 'America/Chicago' Local time is now: Sat Apr 15 08:56:22 CDT 2023. Universal Time is now: Sat Apr 15 13:56:22 UTC 2023. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up armbian-config (23.05.0-trunk--1-SAed8f-Ba894) ... Setting up linux-image-current-meson64 (23.05.0-trunk--6.1.24-S0102-De8b2-Pc5ba-C072bHfe66-HK01ba-Ve377-Bf77d) ... Armbian 'linux-image-current-meson64' for '6.1.24-meson64': 'postinst' starting. + export 'DEB_MAINT_PARAMS=configure 23.02.2' + DEB_MAINT_PARAMS='configure 23.02.2' + export INITRD=Yes + INITRD=Yes + test -d /etc/kernel/postinst.d + run-parts --arg=6.1.24-meson64 --arg=/boot/vmlinuz-6.1.24-meson64 /etc/kernel/postinst.d * dkms: running auto installation service for kernel 6.1.24-meson64 [ OK ] update-initramfs: Generating /boot/initrd.img-6.1.24-meson64 update-initramfs: Converting to u-boot format Remove unused generated file: /boot/uInitrd-6.1.11-meson64 Remove unused generated file: /boot/initrd.img-6.1.11-meson64 + echo 'Armbian: update last-installed kernel symlink to '\''Image'\''...' Armbian: update last-installed kernel symlink to 'Image'... + ln -sfv vmlinuz-6.1.24-meson64 /boot/Image '/boot/Image' -> 'vmlinuz-6.1.24-meson64' + touch /boot/.next + set +x Armbian 'linux-image-current-meson64' for '6.1.24-meson64': 'postinst' finishing. Setting up linux-dtb-current-meson64 (23.05.0-trunk--6.1.24-S0102-De8b2-Pc5ba-C072bHfe66-HK01ba-Ve377-Bf77d) ... Armbian 'linux-dtb-current-meson64' for '6.1.24-meson64': 'postinst' starting. + cd /boot + ln -sfT dtb-6.1.24-meson64 dtb + set +x Armbian 'linux-dtb-current-meson64' for '6.1.24-meson64': 'postinst' finishing. Setting up udev (249.11-0ubuntu3.9) ... Setting up libnss-myhostname:arm64 (249.11-0ubuntu3.9) ... Setting up sudo (1.9.9-1ubuntu2.4) ... Setting up linux-u-boot-odroidn2-current (23.05.0-trunk--2022.10-S4deb-P9295-Ha354-Ve16f-Baf4d) ... Setting up armbian-firmware (23.05.0-trunk--1-SA56ad-Bf566) ... Setting up systemd-sysv (249.11-0ubuntu3.9) ... Setting up python3-tz (2022.1-1ubuntu0.22.04.1) ... Setting up libpam-systemd:arm64 (249.11-0ubuntu3.9) ... Processing triggers for libc-bin (2.35-0ubuntu3.1) ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for dbus (1.12.20-2ubuntu4.1) ... Processing triggers for initramfs-tools (0.140ubuntu13.1) ... update-initramfs: Generating /boot/initrd.img-6.1.24-meson64 update-initramfs: Converting to u-boot format root@odroidn2p10:~# This seems like a udev issue as plugging in a USB network adapter does not create a network interface, but plugging it in does create an entry in dmesg: [ 439.264709] usb 2-1.2: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00 [ 439.264723] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 439.264730] usb 2-1.2: Product: USB 10/100/1000 LAN [ 439.264736] usb 2-1.2: Manufacturer: Realtek [ 439.264742] usb 2-1.2: SerialNumber: 000001000000 [ 445.532274] usb 2-1.2: reset SuperSpeed USB device number 4 using xhci-hcd root@odroidn2p10:/etc/udev/rules.d# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever Thanks for any assistance. 0 Quote
MarkP Posted April 15, 2023 Author Posted April 15, 2023 This has something to do with the installation being on eMMC. - I just did an install on a uSD card and upgraded. It works as it should. When I boot to the borked install an the eMMC it says: Welcome to Armbian 23.02.2 Jammy with Linux 6.1.11-meson64 Even though the upgrade installed the 6.1.24 kernel. I have this in /boot root@odroidn2p10:/boot# ls -l total 90448 -rw-r--r-- 1 root root 161 Apr 15 10:37 armbianEnv.txt -rw-r--r-- 1 root root 1536 Aug 26 2021 armbian_first_run.txt.template -rw-r--r-- 1 root root 38518 Aug 26 2021 boot.bmp -rw-r--r-- 1 root root 8075 Mar 4 08:18 boot.cmd -rw-r--r-- 1 root root 5579 Mar 4 08:18 boot.ini -rw-r--r-- 1 root root 8147 Mar 4 08:18 boot.scr -rw-r--r-- 1 root root 249957 Apr 13 11:01 config-6.1.24-meson64 lrwxrwxrwx 1 root root 18 Apr 15 2023 dtb -> dtb-6.1.24-meson64 drwxr-xr-x 3 root root 4096 Apr 15 2023 dtb-6.1.24-meson64 lrwxrwxrwx 1 root root 22 Apr 15 2023 Image -> vmlinuz-6.1.24-meson64 -rw-r--r-- 1 root root 17005270 Apr 15 2023 initrd.img-6.1.24-meson64 -rw-r--r-- 1 root root 4296342 Apr 13 11:01 System.map-6.1.24-meson64 -rw-r--r-- 1 root root 27066944 Mar 4 08:18 uImage lrwxrwxrwx 1 root root 22 Apr 15 2023 uInitrd -> uInitrd-6.1.24-meson64 -rw-r--r-- 1 root root 17005334 Apr 15 2023 uInitrd-6.1.24-meson64 -rw-r--r-- 1 root root 26903040 Apr 13 11:01 vmlinuz-6.1.24-meson64 I used the uSD card install to chroot into the eMMC install and forced a reinstall of the kernel, the dtb, and u-boot but nope still says kernel 6.1.11 0 Quote
MarkP Posted April 15, 2023 Author Posted April 15, 2023 Now I think that this is actually a u-boot / eMMC issue as I see this early in the boot process: [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 3 ms (1.8 MiB/s) ## Executing script at 04000000 0 bytes read in 2 ms (0 Bytes/s) Found mainline kernel configuration HDMI cable is NOT connected 161 bytes read in 3 ms (51.8 KiB/s) ** File not found uImage ** 27066944 bytes read in 756 ms (34.1 MiB/s) ** File not found dtb/amlogic/meson-g12b-odroid-n2-plus.dtb ** 79315 bytes read in 12 ms (6.3 MiB/s) ** File not found uInitrd ** 23213175 bytes read in 653 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: 27066880 Bytes = 25.8 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: 23213111 Bytes = 22.1 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 = 0x02a50200 libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND [rsvmem] fdt get prop fail. Loading Ramdisk to 3c1dc000, end 3d7ff437 ... OK Loading Device Tree to 000000001ffe9000, end 000000001ffff5d2 ... OK Starting kernel ... Man, I hate u-boot 0 Quote
Solution MarkP Posted April 15, 2023 Author Solution Posted April 15, 2023 (edited) The 23.05.0 dtb, kernel, and u-boot were pulled from the repository sometime today after I installed this update. - I don't see any mention of it in Issues or Pull Requests at https://github.com/armbian/build . I manually downloaded the 3 packages and installed them. A reboot brought my N2 back online. Is there a way to mark this question/post solved? Edited April 15, 2023 by MarkP How to mark as solved 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.