gounthar

Here is the result of my test: http://ix.io/4sgx .

I failed... I installed the image, booted, launched armbian-config, chose the option write to NVMe/MPD, and after the poweroff, I removed the SDCard. Unfortunately, I then get: done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. [...] Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell! The board still boots fine once I put the SDCard back in.

Thanks a lot for taking the time to answer @balbes150. 🙏 The writing on the NVMe is taking place now... But for the latest image, I can't configure WiFi. 🤔

Stupid me had a problem in `/etc/fstab`. Once I got rid of the problem, I got the network (and the rest) back as usual. Well... 🤷‍♂️

Thanks a lot for taking the time to answer @balbes150. 🙏 I'll try that.

Hi, I don't know if this has anything to do with it, but I had a functional Armbian distro on the Rock5B working from the SDCard, and after installing it on the NVMe (which does not boot), I restarted the board from the SDCard (after having removed the NVMe), and I lost my network connections. How could I get the network back on? And the UART regularly asks me: Give root password for maintenance (or press Control-D to continue): Give root password for maintenance (or press Control-D to continue): Something must be broken... root@rock-5b:~# uname -a Linux rock-5b 5.10.110-rockchip-rk3588 #23.02.2 SMP Fri Feb 17 23:59:20 UTC 2023 aarch64 GNU/Linux root@rock-5b:~# 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 2: enP4p65s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:e0:4c:68:03:e4 brd ff:ff:ff:ff:ff:ff 3: wlx4401bb082c96: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 44:01:bb:08:2c:96 brd ff:ff:ff:ff:ff:ff root@rock-5b:~# ifup enP4p65s0 ifup: unknown interface enP4p65s0 root@rock-5b:~# cat /etc/network/interfaces source /etc/network/interfaces.d/* # Network is managed by Network manager auto lo iface lo inet loopback root@rock-5b:~# ls /sys/class/net enP4p65s0 lo wlx4401bb082c96 root@rock-5b:~# `armbian-config` does not give me a way to launch a wireless connection (no menu), and the network configuration file in `armbian-config` does not reflect what is in `/etc/network`.

Hi there, My Rock5B worked well with Armbian until I tried to migrate to an NVMe. Here is a boot log without any SDCard: Now, if I put back the SDCard, I get: That does look the same to me. Why can't it find the SDCard? Thanks.

I have no idea unfortunately. But this board is finicky when it comes to power... It worked well with a dummy 5V power supply for me, and even with my PinePower WC3.0 port. I then added an NVME, and since then, it does not want to boot anymore, with or without NVME...

I'm not so sure I understand correctly the latest news: What does it mean for us?

Hi there 👋 I've tried the CSC edge images Armbian_23.02.0-trunk_Nanopiduo2_lunar_edge_6.1.8.img and Armbian_23.02.0-trunk_Nanopiduo2_sid_edge_6.1.8.img and the machine does not want to boot. Is there a more stable image somewhere? FriendlyCore boots on this board. Thanks. U-Boot SPL 2022.07-armbian (Jan 30 2023 - 06:49:28 +0000) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2022.07-armbian (Jan 30 2023 - 06:49:28 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi NEO DRAM: 512 MiB Core: 60 devices, 17 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Net: phy interface1 eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 1 USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 4077 bytes read in 2 ms (1.9 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 234 bytes read in 2 ms (114.3 KiB/s) 18804544 bytes read in 780 ms (23 MiB/s) 8706400 bytes read in 363 ms (22.9 MiB/s) Found mainline kernel configuration Failed to load '/boot/dtb/allwinner/sun8i-h3-nanopi-duo2.dtb' libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 504 bytes read in 8 ms (61.5 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost0.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 504 bytes read in 8 ms (61.5 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 504 bytes read in 8 ms (61.5 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Error applying DT overlays, restoring original DT Failed to load '/boot/dtb/allwinner/sun8i-h3-nanopi-duo2.dtb' Kernel image @ 0x42000000 [ 0x000000 - 0x84d960 ] ## Loading init Ramdisk from Legacy Image at 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 18804480 Bytes = 17.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image Device 0: unknown device sun8i_emac_eth_start: Timeout missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-81-e1-0b-9c-e0 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/00000000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/0000000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/000000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/00000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/0000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/00 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/0 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default-arm-sunxi sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default-arm sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default sun8i_emac_eth_start: Timeout Config file not found sun8i_emac_eth_start: Timeout sun8i_emac_eth_start: Timeout