All Activity

Hello, Armbian 25.8.1 on Helios64 BookWorm with Linux 6.12.42-current-rockchip64. I have my system booting from SD with OMV7 installed and several docker containers running. Everything is OK. Now I want to boot from emmc. Used armbian-install selecting option boot from emmc - system on emmc. Formatting and copying goes Ok, but when I reboot from emmc (extracting th SD card), OMV7 presents the web frontend, but can't log in. journalctl reports errors accessing the drives, and looking on /etc/fstab, there's only the / partition mounted. Inserting and mounting the SD card in /mnt/sdcard I can see that in /mnt/sdcard/etc/fstab there's a lot of drives ready to be mounted : eclapton@helios64:~$ cat /mnt/sdcard/etc/fstab UUID=a398270d-9378-4f2c-bedd-590b08234484 / ext4 noatime,nodiratime,defaults,commit=120,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 # >>> [openmediavault] /dev/disk/by-uuid/60c885fa-6af1-462c-bfa6-dc7fe706262f /srv/dev-disk-by-uuid-60c885fa-6af1-462c-bfa6-dc7fe706262f ext4 defaults,nofail,user_xattr,usrquota,grpquota,acl 0 2 /dev/disk/by-uuid/a79a14c0-3cf4-4fb9-a6c6-838571351371 /srv/dev-disk-by-uuid-a79a14c0-3cf4-4fb9-a6c6-838571351371 ext4 defaults,nofail,user_xattr,usrquota,grpquota,acl 0 2 /dev/disk/by-uuid/7b71362f-4bb4-48b6-8867-37faaedef2eb /srv/dev-disk-by-uuid-7b71362f-4bb4-48b6-8867-37faaedef2eb ext4 defaults,nofail,user_xattr,usrquota,grpquota,acl 0 2 /dev/disk/by-uuid/1f1ea692-d1bb-4539-a578-0647ef752770 /srv/dev-disk-by-uuid-1f1ea692-d1bb-4539-a578-0647ef752770 ext4 defaults,nofail,user_xattr,usrquota,grpquota,acl 0 2 /dev/disk/by-uuid/fac27973-2eba-43b4-acd3-2c3c2b10a5d7 /srv/dev-disk-by-uuid-fac27973-2eba-43b4-acd3-2c3c2b10a5d7 ext4 defaults,nofail,user_xattr,usrquota,grpquota,acl 0 2 # <<< [openmediavault] So, I thought the actual fstab was going to be copied over, unless it has to be recreated each boot by OMV. Also, I tried to copy /srv/salt and /srv/pillar from the old system on the SD card to the new one on the emmc, as instructed un Kobol's webpage, and it helps making openmediavault-issue start, but the webpage doesn't still work. sudo systemctl status shows nginx is not able to start : eclapton@helios64:~$ sudo systemctl status nginx × nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2025-09-22 23:07:25 CEST; 57s ago Docs: man:nginx(8) Process: 40902 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE) CPU: 82ms sep 22 23:07:25 helios64 systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server... sep 22 23:07:25 helios64 nginx[40902]: 2025/09/22 23:07:25 [emerg] 40902#40902: open() "/var/log/nginx/error.log" failed (2: No such file or > sep 22 23:07:25 helios64 nginx[40902]: nginx: configuration file /etc/nginx/nginx.conf test failed sep 22 23:07:25 helios64 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE sep 22 23:07:25 helios64 systemd[1]: nginx.service: Failed with result 'exit-code'. sep 22 23:07:25 helios64 systemd[1]: Failed to start nginx.service - A high performance web server and a reverse proxy server. I suspect there's somewhere I have to change /dev/mmcblk1p1 for /dev/mmcblk0p1... but where? What am I missing? Thanks for your help.

PR: included fd6551 https://github.com/armbian/build/pull/8666

nice work @Eks Ma thanks for sharing!

Open the box, read the silkscreen on the board, run rk322x-config and configure according to silkscreen name. Probably you have a r29/h20 board

h96-m9s-rk3576_defconfig rk3576-h96-m9s.dts rk3576-h96-m9s1.dts rc.local h96-m9.config rk3576-h96-m9s.dts h96-m9.tvb Compile-configuration.zip

thank you so much for the link, after trying some of the older tinkerboard .deb archives from there I was able to install one that didn't have the two missing deps eventually and, lo and behold, I could even feel the accelerated desktop from the login window, even before confirming it with the much snappier webgl aquarium test, that jumped from about one fps to almost 60 there are still some kinks, like h264ify being installed but not doing squat (youtube is still av1 and hangs the whole system), but I'll take what I got for now as for the SOC being 2017....I'm fully aware that like everything Asus makes, it becomes e-waste after 2 years, I could probably try to flip this board online for $1 and no one would buy it, but I still believe it should be enough for me to stream video from my NAS on my secondary TV using 5-15W, kind of like those crappy Android sticks that plug into HDMI and an extra USB port I have yet to decide if my next SBC should be a rk3588 board or just bite the bullet and get some N100 SBC that's probably cheaper (I live in Europe, Orange Pi 5 probably goes for more than a used PS5 with all the taxes), can run anything and won't be forever stuck on whatever this year's trending distro is

Hi ! @jpm how exactly did you solve 2) Fixed cedar_ve compilation issues / kernel name ? I'm gettinf the same "modprobe: ERROR: could not insert 'cedar_ve': Exec format error" T.

Since it's an external driver, @Vincenzoernst1 you will still need to do all the process: Edit /boot/armbianEnv.txt to load the overlay user_overlays=tm16xx sudo apt install linux-headers-$(uname -r) # if it works, thats nice #if it doesn't you're cocked. Kernel module and display service Option 1: build and install in a single command Builds then installs module and service git clone https://github.com/jefflessard/tm16xx-display.git cd tm16xx-display make install Option 2: step by step commands make clean make module sudo make module-install sudo make service-install Check your display configuration display-service -c 3 phase display check Check that all leds are ON Check the order of digits and segment mapping (you should see "1234") Check each led name (ex: LAN icon is ON while "LAN" text is shown on the digits) I will include this section into a pull request: /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> #include <dt-bindings/pinctrl/rockchip.h> &{/} { i2c-display { compatible = "i2c-gpio"; sda-gpios = <&gpio0 RK_PB4 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>; scl-gpios = <&gpio0 RK_PB3 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>; i2c-gpio,delay-us = <5>; #address-cells = <1>; #size-cells = <0>; display@24 { compatible = "fdhisi,fd6551"; reg = <0x24>; digits { #address-cells = <1>; #size-cells = <0>; digit@0 { reg = <0>; segments = <1 3>, <1 1>, <1 2>, <1 6>, <1 4>, <1 5>, <1 0>; }; digit@1 { reg = <1>; segments = <2 3>, <2 1>, <2 2>, <2 6>, <2 4>, <2 5>, <2 0>; }; digit@2 { reg = <2>; segments = <3 3>, <3 1>, <3 2>, <3 6>, <3 4>, <3 5>, <3 0>; }; digit@3 { reg = <3>; segments = <4 3>, <4 1>, <4 2>, <4 6>, <4 4>, <4 5>, <4 0>; }; }; leds { #address-cells = <2>; #size-cells = <0>; led@0,0 { reg = <0 0>; function = LED_FUNCTION_ALARM; }; led@0,1 { reg = <0 1>; function = LED_FUNCTION_USB; }; led@0,3 { reg = <0 3>; function = "play"; }; led@0,2 { reg = <0 2>; function = "pause"; }; led@0,4 { reg = <0 4>; function = "colon"; }; led@0,5 { reg = <0 5>; function = LED_FUNCTION_LAN; }; led@0,6 { reg = <0 6>; function = LED_FUNCTION_WLAN; }; }; }; }; };

Hi @jock, Thanks a lot for your work on these RK322x boards. I have an MXQ Pro (RK3229, 2GB RAM / 16GB eMMC). I was able to boot Multitool from SD and successfully create a backup of the eMMC. However, when I burn an Armbian image to flash, the box doesn’t boot—LED blinks, but nothing shows up on HDMI. I’ve tried a few different images with the same result. Could you please guide me on how to debug this?

thanks for all the work you put in to this application. i've done this on most all of my systems and it was a bit tedious and fiddley. with just a few tweeks it ran through with no errors on my hc4 with bookworm. one question, why remove bash-completion and command-not-found packages?

Linux 6.1.31-sun50iw9 #1.0.4 SMP Wed Aug 6 19:06:53 UTC 2025 aarch64 GNU/Linux I couldn't find any known kernel issues.

A crash in the Linux kernel's module loader is not really ZFS's fault, though, right? There's nothing about `resolve_symbol` that's part of ZFS.

I think official stand from open ZFS project is: "ZFS is not designed for 32-bit kernels" ... it still might work(ed). IMO stay on kernel 6.6.y. I doubt there is anything wrong on Armbian side ... worth experimenting with Ubuntu Noble minimal image to rule out possible headers incompatibility.

I grabbed the "Armbian 25.8.1 Bookworm Minimal / IOT" image from https://www.armbian.com/tinkerboard/, landed it on a microSD card, booted it, and ran apt update apt upgrade apt install linux-headers-current-rockchip apt install zfs-dkms zfsutils-linux This gets me linux-image-current-rockchip 25.8.1 (kernel 6.12.44-current-rockchip) and a module built from zfs-dkms 2.3.2-2~bpo12+2. So far so good. And then I ran modprobe zfs.ko and was rewarded with the following panic in the kernel's module loader: [ 1128.728803] spl: loading out-of-tree module taints kernel. [ 1128.859152] zfs: module license 'CDDL' taints kernel. [ 1128.859178] Disabling lock debugging due to kernel taint [ 1128.859401] zfs: module license taints kernel. [ 1128.860612] 8<--- cut here --- [ 1128.860624] Unable to handle kernel paging request at virtual address 5e4f51d0 when read [ 1128.860641] [5e4f51d0] *pgd=00000000 [ 1128.860663] Internal error: Oops: 5 [#1] SMP ARM [ 1128.865857] Modules linked in: spl(O) zram zsmalloc snd_soc_hdmi_codec snd_usb_audio snd_soc_simple_card binfmt_misc snd_soc_rockchip_i2s snd_soc_simple_card_utils snd_hwdep hantro_vpu snd_usbmidi_lib rockchip_vdec(C) snd_ump snd_soc_core r8723bs(C) rockchip_rga rockchip_iep snd_rawmidi v4l2_vp9 panfrost snd_pcm_dmaengine v4l2_jpeg rk_crypto snd_seq_device v4l2_h264 dw_hdmi_i2s_audio snd_pcm videobuf2_dma_contig gpu_sched dw_hdmi_cec v4l2_mem2mem snd_timer syscon_reboot_mode crypto_engine reboot_mode snd dw_wdt rk3288_gpiomem soundcore rockchip_thermal cpufreq_dt fuse gpio_keys realtek [ 1128.924379] CPU: 3 UID: 0 PID: 20465 Comm: modprobe Tainted: P C O 6.12.44-current-rockchip #1 [ 1128.935373] Tainted: [P]=PROPRIETARY_MODULE, [C]=CRAP, [O]=OOT_MODULE [ 1128.942570] Hardware name: Rockchip (Device Tree) [ 1128.947822] PC is at resolve_symbol+0xf8/0x368 [ 1128.952795] LR is at cmp_name+0x14/0x18 [ 1128.957081] pc : [<b01ac790>] lr : [<b01ab960>] psr: 90010013 [ 1128.964083] sp : f1f1dd68 ip : f1f1dca8 fp : f1f1ddbc [ 1128.969919] r10: f1f1ded0 r9 : af1f81dc r8 : af1f62ac [ 1128.975755] r7 : af2489c0 r6 : af248c48 r5 : f1f1de48 r4 : af52c300 [ 1128.983049] r3 : 00000000 r2 : 5e4f51c0 r1 : 00000000 r0 : 00000001 [ 1128.990342] Flags: NzcV IRQs on FIQs on Mode SVC_32 ISA ARM Segment none [ 1128.998318] Control: 10c5387d Table: 0364c06a DAC: 00000051 [ 1129.004737] Register r0 information: non-paged memory [ 1129.010383] Register r1 information: NULL pointer [ 1129.015639] Register r2 information: non-paged memory [ 1129.021283] Register r3 information: NULL pointer [ 1129.026538] Register r4 information: 201-page vmalloc region starting at 0xaf514000 allocated at load_module+0x744/0x1b34 [ 1129.038795] Register r5 information: 2-page vmalloc region starting at 0xf1f1c000 allocated at kernel_clone+0xac/0x340 [ 1129.050759] Register r6 information: 5-page vmalloc region starting at 0xaf247000 allocated at load_module+0x744/0x1b34 [ 1129.062820] Register r7 information: 5-page vmalloc region starting at 0xaf247000 allocated at load_module+0x744/0x1b34 [ 1129.074881] Register r8 information: 3-page vmalloc region starting at 0xaf1f6000 allocated at load_module+0x744/0x1b34 [ 1129.086942] Register r9 information: 3-page vmalloc region starting at 0xaf1f6000 allocated at load_module+0x744/0x1b34 [ 1129.099003] Register r10 information: 2-page vmalloc region starting at 0xf1f1c000 allocated at kernel_clone+0xac/0x340 [ 1129.111062] Register r11 information: 2-page vmalloc region starting at 0xf1f1c000 allocated at kernel_clone+0xac/0x340 [ 1129.123120] Register r12 information: 2-page vmalloc region starting at 0xf1f1c000 allocated at kernel_clone+0xac/0x340 [ 1129.135179] Process modprobe (pid: 20465, stack limit = 0xf191b45c) [ 1129.142183] Stack: (0xf1f1dd68 to 0xf1f1e000) [ 1129.147050] dd60: b01abd14 af52c3fc 00000000 f26174f8 00000100 af2489c0 [ 1129.156193] dd80: 00000000 af1f62ac 00000000 e7df2e2d b4795600 00005a2b f26174f8 f26bcb48 [ 1129.165334] dda0: af6dc2b4 00000000 0006a3d0 f1f1ded0 f1f1deb4 f1f1ddc0 b01ae384 b01ac6a4 [ 1129.174476] ddc0: b02f81d4 b02f2340 f26bcbc0 00000000 00000003 004d6d38 00000000 00000001 [ 1129.183618] dde0: 00000000 b4795600 f26bc508 00000000 af52c3fc 0000001e 00000000 b132bdb0 [ 1129.192759] de00: 00000000 af52c300 af52c300 b1bd8b84 af52c30c b1c8a1a4 00000000 00000001 [ 1129.201901] de20: b5b7e600 f26bcbc0 00459bc0 00459bc0 f1f1de5c f1f1de40 00459bc0 00000000 [ 1129.211041] de40: 7fffffff b5b7e600 00000000 00000000 00000000 00000000 00000000 00000000 [ 1129.220182] de60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 1129.229324] de80: 00000000 e7df2e2d 00000002 00000000 b5b7e600 004d6d38 b5b7e600 b1c8a5b4 [ 1129.238465] dea0: bbba0708 b5b7e600 f1f1df3c f1f1deb8 b01aeedc b01ad31c f1f1decc 7fffffff [ 1129.247607] dec0: 00000000 00000002 00000000 f2263000 f2576523 f24d6640 f2263000 00459bc0 [ 1129.256749] dee0: f26bc508 f26bc388 f25e9c54 0008272c 000a7eac 000a5a90 000c5d78 00000000 [ 1129.265890] df00: 000a5a80 00000028 00000029 00000016 00000000 0000001e 00000000 e7df2e2d [ 1129.275031] df20: 00000001 000000f6 b1c8a1a4 00000001 f1f1dfa4 f1f1df40 b01af2ac b01aee50 [ 1129.284172] df40: 00000000 00000000 004d6d38 b1c8a58c bbba0708 00000000 b1c8a58c 00000000 [ 1129.293314] df60: 00000000 f1f1df64 f1f1df64 fffffffc 00000000 e7df2e2d 000000c0 004d8ad8 [ 1129.302456] df80: 00fa74bc 22b57200 0000017b b01002c8 b4795600 0000017b 00000000 f1f1dfa8 [ 1129.311598] dfa0: b0100060 b01af108 004d8ad8 00fa74bc 00000004 004d6d38 00000000 004d86bc [ 1129.320738] dfc0: 004d8ad8 00fa74bc 22b57200 0000017b 00fa7520 00000000 00000000 004d50bc [ 1129.329879] dfe0: aeb5c0e8 aeb5c0d8 004cf149 a6bc3002 40070030 00000004 00000000 00000000 [ 1129.339018] Call trace: [ 1129.341845] resolve_symbol from load_module+0x1074/0x1b34 [ 1129.347983] r10:f1f1ded0 r9:0006a3d0 r8:00000000 r7:af6dc2b4 r6:f26bcb48 r5:f26174f8 [ 1129.356735] r4:00005a2b [ 1129.359559] load_module from init_module_from_file+0x98/0xd4 [ 1129.365987] r10:b5b7e600 r9:bbba0708 r8:b1c8a5b4 r7:b5b7e600 r6:004d6d38 r5:b5b7e600 [ 1129.374738] r4:00000000 [ 1129.377562] init_module_from_file from sys_finit_module+0x1b0/0x310 [ 1129.384670] r6:00000001 r5:b1c8a1a4 r4:000000f6 [ 1129.389826] sys_finit_module from ret_fast_syscall+0x0/0x54 [ 1129.396154] Exception stack(0xf1f1dfa8 to 0xf1f1dff0) [ 1129.401798] dfa0: 004d8ad8 00fa74bc 00000004 004d6d38 00000000 004d86bc [ 1129.410939] dfc0: 004d8ad8 00fa74bc 22b57200 0000017b 00fa7520 00000000 00000000 004d50bc [ 1129.420079] dfe0: aeb5c0e8 aeb5c0d8 004cf149 a6bc3002 [ 1129.425724] r10:0000017b r9:b4795600 r8:b01002c8 r7:0000017b r6:22b57200 r5:00fa74bc [ 1129.434475] r4:004d8ad8 [ 1129.437302] Code: ea00004a e5922000 e1520006 0a000047 (e5923010) [ 1129.444162] ---[ end trace 0000000000000000 ]--- I have been unable to find debug symbols or a way to get an objdump of the loaded kernel (probably I am just missing something). Please advise what more I can tell you to be useful. I am unable to run armbianmonitor; after the above, lsmod hangs, and upon boot, the machine attempts to load zfs.ko which again crashes as above and userspace is pretty direly stuck. FWIW, I am happily running ZFS on a Tinkerboard with an older system, specifically linux-image-current-rockchip 24.11.1 (which is kernel 6.6.63-current-rockchip) and zfs-dkms 2.2.2-0ubuntu9.1.

Would you mind sending this as pull request? https://github.com/armbian/build/pulls

diff --git a/config/sources/families/mvebu64.conf b/config/sources/families/mvebu64.conf index 90b0a97d4..1a78ace60 100644 --- a/config/sources/families/mvebu64.conf +++ b/config/sources/families/mvebu64.conf @@ -28,7 +28,8 @@ BOOTSCRIPT_OUTPUT='boot.scr' OVERLAY_DIR="/boot/dtb/marvell/overlay" ATFSOURCE='https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git' ATFDIR='arm-trusted-firmware-espressobin' -ATFBRANCH='tag:v2.8' +ATFBRANCH='tag:v2.10' +#ATFBRANCH='tag:v2.8' ATF_USE_GCC='> 7.2' if [[ "${SKIP_EXTERNAL_TOOLCHAINS}" == "yes" ]]; then @@ -126,7 +127,7 @@ uboot_custom_postprocess() { local atfdir="$SRC/cache/sources/$ATFDIR/${ATFBRANCH##*:}" local ubootdir="$SRC/cache/sources/u-boot-worktree/$BOOTDIR/${BOOTBRANCH##*:}" local moxbootdir="$SRC/cache/sources/mox-boot" - cd $atfdir + cd $atfdir if [[ $BOARD = macchiatobin-doubleshot ]]; then run_host_command_logged make distclean @@ -139,6 +140,9 @@ uboot_custom_postprocess() { run_host_command_logged cp -pv build/a80x0_mcbin/release/flash-image.bin $ubootdir/$FILENAME else cd $moxbootdir +#$HL + [[ -f Makefile ]] && sed -i "s/aarch64-unknown-linux-gnu-/aarch64-linux-gnu-/" Makefile + [[ -f wtmi/a53_helper/Makefile ]] && sed -i "s/aarch64-unknown-linux-gnu-/aarch64-linux-gnu-/" wtmi/a53_helper/Makefile make clean # @TODO: rpardini: why? run_host_command_logged "CFLAGS=-fdiagnostics-color=always" pipetty make CROSS_CM3=$ATF2 wtmi_app.bin cd $atfdir diff --git a/lib/functions/compilation/atf.sh b/lib/functions/compilation/atf.sh index 2c6b55408..7205c0366 100644 --- a/lib/functions/compilation/atf.sh +++ b/lib/functions/compilation/atf.sh @@ -71,7 +71,8 @@ compile_atf() { display_alert "Binutils version for ATF" "${binutils_version}" "info" if linux-version compare "${binutils_version}" ge "2.39"; then display_alert "Binutils version for ATF" ">= 2.39, adding --no-warn-rwx-segment" "info" - binutils_flags_atf="-Wl,--no-warn-rwx-segment" + #binutils_flags_atf="-Wl,--no-warn-rwx-segment" + binutils_flags_atf="--no-warn-rwx-segment" fi # - ENABLE_BACKTRACE="0" has been added to workaround a regression in ATF. Check: https://github.com/armbian/build/issues/1157 with the patch, I am able to generate a image to run a espressobin v5 board, it should be ok for v7 board.

You need to install rkdeveloptool on your PC. Connect the board to your PC using a USB-C to USB-A cable. Before powering the board, press and hold the mask button, then plug in the power cable. Once this is done, your PC should detect the device, and you can verify it with: rkdeveloptool ld You can follow this guide: https://docs.armbian.com/User-Guide_Getting-Started/#rockchip

Please specify which OS and kernel version. By the way, I recommend building EDGE yourself.

moved Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

I don't see anything above about your boot-loader being updated. i.e. u-boot or grub. If you're using u-boot, was your uInitrd in your /boot directory updated? The initrd-image needs to be converted to its u-boot format of uinitrd. Instructions for how to do that are located at the bottom of your boot.cmd file (using the mkimage command from the u-boot-tools package). Though that may be a generic example that you'll have to update for your system. Also if you have an armbianEnv.txt (or an equivalent) in your /boot directory, be sure it's up to date for your current kernel's devicetree file location and name. If that doesn't solve it read on.... I keep seeing everywhere that kernel 6.12 is broken. Not sure if that applies to all systems. I use the edge kernel (6.16) in my OrangePI-5-Plus. I've found that to work much better than Vendor (6.1). To chroot in from an another identical system. This works on Debian Trixie. I'm not sure about other OS's. Note: I don't know much about this, I recently found this from searching and used it myself. I found it works great to install new packages and also to run update-initramfs. mount -t proc proc /mnt/proc mount -t sysfs sysfs /mnt/sys mount -t devtmpfs devtmpfs /mnt/dev mount --bind /dev/pts /mnt/dev/pts # If you need for the chrooted system to be able to access the internet, the link at its: (/etc/resolv.conf) must be valid, so add this as well: mount --bind /run/systemd /mnt/run/systemd Then chroot in (I'm not sure if the /bin/bash) is necessary - or if you're using something else than bash, put that there instead?) chroot /mnt /bin/bash [Do what you need to do in there] i.e. install a different kernel, and be sure update-initramfs has been run or run it yourself, and the u-boot (or grub) is updated. Whenever you're installing a new kernel, it's a good idea to leave the old one there. Once you get it working, it might then be a good idea to remove any non-functioning kernels (like that 6.12), and leave any functioning kernels in. Then to back get out of chroot and return undo the above mounts: # Exit chroot exit # This line is only necessary if you mounted it to use the internet while chrooted: umount /mnt/run/systemd # Unmount the rest umount /mnt/dev/pts umount /mnt/dev umount /mnt/sys umount /mnt/proc umount /mnt

@Ian Coelho Success! I got it working by tweaking the eMMC parameters in the dtb file. Generally I changed the `<max-frequency>` to 50M. I've attached my version if you want to give it a shot, but make sure you have a backup ROM handy. my.dtb

Thanks for this info, just wanted to share that the image for the "Linux v6.1 vendor IOT image for the 5 "Max" model" you linked to also worked for me on my Orange Pi 5 Ultra with no modifications needed. I haven't tested wifi or any use cases besides some simmple stuff over ssh so far, I did get a warning on first boot that it's a developer version of Armbian and shouldn't be used for production, but I suppose that's the case for all "community" builds? I also found this gist with steps to build Armbian from scratch for the 5 Ultra, but I haven't tried this yet. In case anyone else is looking for related info this PR also is also relevant: https://github.com/armbian/build/pull/8252 I still regret not buying a better supported board like the 5 Max board instead but hopefully better support will come for the 5 Ultra with time.

Upon reading the content of RPi5 about 6.12 from this and this , I was under the impression that it's okay to upgrade the Armbian 24.11 based NextCloudPi to a 6.12 kernel. Well, I was wrong and the RPi5 current stuck in the RPi Logo on a black page. Net address seems to be 0.0.0.0. I could really use some advice on how to restore this, perhaps some `chroot` method from another Linux machine to get the right kernel package and intramfs. Here are the steps that got me to the current situation. Maybe a hint on how to restore? 1. Mark `raspi-firmware`, like what was recommended in 1st post. sudo apt-mark hold raspi-firmware [sudo] password for pi: raspi-firmware set on hold. 2. Remove the old bsp for RPi5b specific package? pi@nextcloudpi:~$ sudo dpkg --remove --force-all libraspberrypi0 armbian-bsp-cli-rpi5b-current dpkg: warning: ignoring request to remove libraspberrypi0 which isn't installed (Reading database ... 50983 files and directories currently installed.) Removing armbian-bsp-cli-rpi5b-current (24.11.1) ... Armbian 'armbian-bsp-cli-rpi5b-current' for '1-PC980a-V32ae-H032a-B6e44-R7697': 'postrm' starting. Armbian 'armbian-bsp-cli-rpi5b-current' for '1-PC980a-V32ae-H032a-B6e44-R7697': 'postrm' finishing. Processing triggers for initramfs-tools (0.142+deb12u3) ... update-initramfs: Generating /boot/initrd.img-6.6.63-current-bcm2712 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153b-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-3.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for built-in driver r8152 3. Install the newer RPI4b bsp package, which guessing from the 2nd post, including everything from 3b to 5b. pi@nextcloudpi:~$ sudo apt install armbian-bsp-cli-rpi4b-current Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: armbian-bsp-cli-rpi4b-current 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 1,515 kB of archives. After this operation, 5,411 kB of additional disk space will be used. Get:1 https://mirrors.ustc.edu.cn/armbian bookworm/main arm64 armbian-bsp-cli-rpi4b-current arm64 25.8.1 [1,515 kB] Fetched 1,515 kB in 2s (1,008 kB/s) Selecting previously unselected package armbian-bsp-cli-rpi4b-current. (Reading database ... 50867 files and directories currently installed.) Preparing to unpack .../armbian-bsp-cli-rpi4b-current_25.8.1_arm64.deb ... Armbian 'armbian-bsp-cli-rpi4b-current' for '1-PCee86-Ved8e-H468e-B1e5d-Rf36a': 'preinst' starting. Armbian 'armbian-bsp-cli-rpi4b-current' for '1-PCee86-Ved8e-H468e-B1e5d-Rf36a': 'preinst' finishing. Unpacking armbian-bsp-cli-rpi4b-current (25.8.1) ... Setting up armbian-bsp-cli-rpi4b-current (25.8.1) ... Armbian 'armbian-bsp-cli-rpi4b-current' for '1-PCee86-Ved8e-H468e-B1e5d-Rf36a': 'postinst' starting. Armbian 'armbian-bsp-cli-rpi4b-current' for '1-PCee86-Ved8e-H468e-B1e5d-Rf36a': 'postinst' finishing. Processing triggers for initramfs-tools (0.142+deb12u3) ... update-initramfs: Generating /boot/initrd.img-6.6.63-current-bcm2712 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153b-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-3.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for built-in driver r8152 4. I notice the initrd was still generated for the old kernel image, which is understandable based what is currently installed pi@nextcloudpi:~$ uname -a Linux nextcloudpi 6.6.63-current-bcm2712 #2 SMP PREEMPT Wed Nov 27 10:28:46 UTC 2024 aarch64 GNU/Linux pi@nextcloudpi:~$ dpkg -l | grep linux-image ii linux-image-current-bcm2712 24.11.1 arm64 Armbian Linux current kernel image 6.6.63-current-bcm2712 5. Therefore, I went ahead to install the new 6.12 kernel package pi@nextcloudpi:~$ sudo apt install linux-image-current-bcm2711 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-image-current-bcm2711 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 34.5 MB of archives. After this operation, 212 MB of additional disk space will be used. Get:1 https://mirrors.ustc.edu.cn/armbian bookworm/main arm64 linux-image-current-bcm2711 arm64 25.8.1 [34.5 MB] Fetched 34.5 MB in 5s (7,198 kB/s) Selecting previously unselected package linux-image-current-bcm2711. (Reading database ... 51028 files and directories currently installed.) Preparing to unpack .../linux-image-current-bcm2711_25.8.1_arm64.deb ... Armbian 'linux-image-current-bcm2711' for '6.12.44-current-bcm2711': 'preinst' starting. Armbian 'linux-image-current-bcm2711' for '6.12.44-current-bcm2711': 'preinst' finishing. Unpacking linux-image-current-bcm2711 (25.8.1) ... Setting up linux-image-current-bcm2711 (25.8.1) ... Armbian 'linux-image-current-bcm2711' for '6.12.44-current-bcm2711': 'postinst' starting. update-initramfs: Generating /boot/initrd.img-6.12.44-current-bcm2711 Armbian: update last-installed kernel symlink to 'Image'... '/boot/Image' -> 'vmlinuz-6.12.44-current-bcm2711' Armbian: Debian compat: linux-update-symlinks install 6.12.44-current-bcm2711 boot/vmlinuz-6.12.44-current-bcm2711 I: /vmlinuz is now a symlink to boot/vmlinuz-6.12.44-current-bcm2711 I: /initrd.img is now a symlink to boot/initrd.img-6.12.44-current-bcm2711 Armbian 'linux-image-current-bcm2711' for '6.12.44-current-bcm2711': 'postinst' finishing. 6. Everything looked right to me as there are no errors like before got reported during update-initramfs: pi@nextcloudpi:~$ sudo apt remove linux-image-current-bcm2712 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: linux-image-current-bcm2712 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 155 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 54440 files and directories currently installed.) Removing linux-image-current-bcm2712 (24.11.1) ... Armbian 'linux-image-current-bcm2712' for '6.6.63-current-bcm2712': 'prerm' starting. Armbian 'linux-image-current-bcm2712' for '6.6.63-current-bcm2712': 'prerm' finishing. Armbian 'linux-image-current-bcm2712' for '6.6.63-current-bcm2712': 'postrm' starting. update-initramfs: Deleting /boot/initrd.img-6.6.63-current-bcm2712 Armbian 'linux-image-current-bcm2712' for '6.6.63-current-bcm2712': 'postrm' finishing. 7. As a final check, I ran the upgrade script again pi@nextcloudpi:~$ sudo armbian-upgrade Hit:1 https://mirrors.ustc.edu.cn/debian bookworm InRelease Hit:2 https://mirrors.ustc.edu.cn/debian bookworm-updates InRelease Hit:3 https://mirrors.ustc.edu.cn/debian bookworm-backports InRelease Hit:4 https://mirrors.ustc.edu.cn/debian-security bookworm-security InRelease Hit:5 https://mirrors.ustc.edu.cn/armbian bookworm InRelease Hit:6 https://github.armbian.com/configng stable InRelease Hit:7 https://packages.sury.org/php bookworm InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 8. That's it. After rebooting, I was greeted with a RPi logo on a black page, with some messaging scrolling (trying to attach a photo but failed). It never got to the point to boot the kernel image or systemd booting sequence.

RK3576 nanopi M5 cannot start Waydrod I am trying to use Waydrod on the nanopi M5, and I am starting it up CONFIG_ANDROID_BINDER_IPC=y CONFIG_ANDROID_BINDERFS=y CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder" However, during the actual startup of Waydrod, there was a continuous black screen crash and restart. The following is the error log: nano@nanopi-m5:$ waydroid show-full-ui [13:55:56] Introspect error on :1.103:/ContainerManager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [13:56:21] Failed to unfreeze container. Trying to launch anyways... [13:57:06] Failed to get service waydroidplatform, trying again... [13:57:07] Failed to get service waydroidplatform, trying again... [13:57:08] Failed to get service waydroidplatform, trying again... [13:57:09] Failed to get service waydroidplatform, trying again... [13:57:10] Failed to get service waydroidplatform, trying again... [13:57:11] Failed to get service waydroidplatform, trying again... [13:57:12] Failed to get service waydroidplatform, trying again... [13:57:13] Failed to get service waydroidplatform, trying again... [13:57:14] Failed to get service waydroidplatform, trying again... [13:57:15] Failed to get service waydroidplatform, trying again... [13:57:16] Failed to get service waydroidplatform, trying again...nano@nanopi-m5:$ waydroid log (009909) [13:52:01] % lxc-info --version 5.0.3 (009909) [13:52:01] % mkdir -p /var/lib/waydroid/lxc/waydroid (009909) [13:52:01] % sh -c cat "/usr/lib/waydroid/data/configs/config_base" "/usr/lib/waydroid/data/configs/config_3" "/usr/lib/waydroid/data/configs/config_4" > "/var/lib/waydroid/lxc/waydroid/config" (009909) [13:52:01] % sed -i s/LXCARCH/aarch64/ /var/lib/waydroid/lxc/waydroid/config (009909) [13:52:01] % cp -fpr /usr/lib/waydroid/data/configs/waydroid.seccomp /var/lib/waydroid/lxc/waydroid/waydroid.seccomp (009909) [13:52:01] % systemctl is-active -q apparmor (009909) [13:52:01] % mv /var/lib/waydroid/config_nodes /var/lib/waydroid/lxc/waydroid (006325) [13:52:01] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH STOPPED (006325) [13:52:01] % modprobe -q ashmem_linux (006325) [13:52:01] % chmod 666 -R /dev/binder (006325) [13:52:01] % chmod 666 -R /dev/vndbinder (006325) [13:52:01] % chmod 666 -R /dev/hwbinder (010960) [13:53:11] Starting waydroid session (006325) [13:53:11] % /usr/lib/waydroid/data/scripts/waydroid-net.sh start vnic is waydroid0 (006325) [13:53:11] % systemctl is-active -q nfcd (006325) [13:53:11] % chmod 777 -R /dev/sw_sync (006325) [13:53:11] % chmod 777 -R /sys/kernel/debug/sync/sw_sync (006325) [13:53:11] % chmod 777 -R /dev/dri/renderD130 (006325) [13:53:11] % chmod 777 -R /dev/dri/renderD129 (006325) [13:53:11] % chmod 777 -R /dev/dri/renderD128 (006325) [13:53:11] % chmod 777 -R /dev/fb0 (006325) [13:53:11] % chmod 777 -R /dev/dma_heap/reserved (006325) [13:53:11] % chmod 777 -R /dev/dma_heap/system-uncached (006325) [13:53:11] % chmod 777 -R /dev/dma_heap/system (006325) [13:53:11] % mv /var/lib/waydroid/config_session /var/lib/waydroid/lxc/waydroid (006325) [13:53:11] % mount -o ro /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs (006325) [13:53:11] % mkdir -p /var/lib/waydroid/overlay_work/system (006325) [13:53:11] % mount -t overlay -o ro,lowerdir=/var/lib/waydroid/overlay:/var/lib/waydroid/rootfs,upperdir=/var/lib/waydroid/overlay_rw/system,workdir=/var/lib/waydroid/overlay_work/system,xino=off overlay /var/lib/waydroid/rootfs (006325) [13:53:11] % mount -o ro /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor (006325) [13:53:11] % mkdir -p /var/lib/waydroid/overlay_work/vendor (006325) [13:53:11] % mount -t overlay -o ro,lowerdir=/var/lib/waydroid/overlay/vendor:/var/lib/waydroid/rootfs/vendor,upperdir=/var/lib/waydroid/overlay_rw/vendor,workdir=/var/lib/waydroid/overlay_work/vendor,xino=off overlay /var/lib/waydroid/rootfs/vendor (006325) [13:53:11] % mount -o bind /var/lib/waydroid/waydroid.prop /var/lib/waydroid/rootfs/vendor/waydroid.prop (006325) [13:53:11] Save config: /var/lib/waydroid/waydroid.cfg (006325) [13:53:11] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid -- /init (006325) [13:53:11] New background process: pid=11037, output=background (006325) [13:53:11] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH RUNNING (010960) [13:53:11] Skipping clipboard manager service because of missing pyclip package (011121) [13:55:27] Session is already running (011139) [13:55:56] Introspect error on :1.103:/ContainerManager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (011139) [13:55:56] Executing introspect queue due to error (011139) [13:56:21] Failed to unfreeze container. Trying to launch anyways... (011139) [13:57:06] Failed to get service waydroidplatform, trying again... (006325) [13:57:06] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH RUNNING (011139) [13:57:07] Failed to get service waydroidplatform, trying again... (011139) [13:57:08] Failed to get service waydroidplatform, trying again... (011139) [13:57:09] Failed to get service waydroidplatform, trying again... (011139) [13:57:10] Failed to get service waydroidplatform, trying again... (011139) [13:57:11] Failed to get service waydroidplatform, trying again... (011139) [13:57:12] Failed to get service waydroidplatform, trying again... (011139) [13:57:13] Failed to get service waydroidplatform, trying again... (011139) [13:57:14] Failed to get service waydroidplatform, trying again... (011139) [13:57:15] Failed to get service waydroidplatform, trying again... (011139) [13:57:16] Failed to get service waydroidplatform, trying again... (012115) [13:57:27] % tail -n 60 -F /var/lib/waydroid/waydroid.log (012115) [13:57:27] *** output passed to waydroid stdout, not to this log *** nano@nanopi-m5:~sudo systemctl status waydroid-containerer ● waydroid-container.service - Waydroid Container Loaded: loaded (/usr/lib/systemd/system/waydroid-container.service; enabled; preset: enabled) Active: active (running) since Sun 2025-09-21 13:17:05 CST; 41min ago Main PID: 6325 (waydroid) Tasks: 6 (limit: 9464) Memory: 21.4M (peak: 92.5M) CPU: 4min 20.835s CGroup: /system.slice/waydroid-container.service ├─ 6325 /usr/bin/python3 /usr/bin/waydroid -w container start └─11005 dnsmasq --conf-file=/dev/null -u dnsmasq --strict-order --bind-interfaces --pid-file=/run/waydroid-lxc/dnsmasq.pid --listen-address 192.168.240.1 --dhcp-range 192.168.240.2,192.168.240.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=waydroid0 -> 9月 21 13:17:05 nanopi-m5 systemd[1]: Started waydroid-container.service - Waydroid Container. 9月 21 13:17:52 nanopi-m5 waydroid[6552]: [13:17:52] Downloading https://sourceforge.net/projects/waydroid/files/images/system/lineage/waydroid_arm64/lineage-20.0-20250809-VANILLA-waydroid_arm64-system.zip/download 9月 21 13:34:17 nanopi-m5 waydroid[6552]: [13:34:17] Validating system image 9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: started, version 2.90 cachesize 150 9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset nftset auth cryptohash DNSSEC loop-detect inotify dumpfile 9月 21 13:53:11 nanopi-m5 dnsmasq-dhcp[11005]: DHCP, IP range 192.168.240.2 -- 192.168.240.254, lease time 1h 9月 21 13:53:11 nanopi-m5 dnsmasq-dhcp[11005]: DHCP, sockets bound exclusively to interface waydroid0 9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: reading /etc/resolv.conf 9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: using nameserver 127.0.0.53#53 9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: read /etc/hosts - 10 names nano@nanopi-m5:~$ systemctl status dbus ● dbus.service - D-Bus System Message Bus Loaded: loaded (/usr/lib/systemd/system/dbus.service; static) Active: active (running) since Sat 2025-09-20 21:30:20 CST; 16h ago TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) Main PID: 1455 (dbus-daemon) Tasks: 1 (limit: 9464) Memory: 3.5M (peak: 3.8M) CPU: 2.817s CGroup: /system.slice/dbus.service └─1455 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only 9月 21 13:16:57 nanopi-m5 dbus-daemon[1455]: [system] Reloaded configuration 9月 21 13:17:02 nanopi-m5 dbus-daemon[1455]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=1527 comm="/usr/sbin/NetworkManager --no-daemon") 9月 21 13:17:02 nanopi-m5 dbus-daemon[1455]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 9月 21 13:17:11 nanopi-m5 dbus-daemon[1455]: Unknown username "gnome-remote-desktop" in message bus configuration file 9月 21 13:17:11 nanopi-m5 dbus-daemon[1455]: Unknown username "whoopsie" in message bus configuration file 9月 21 13:17:11 nanopi-m5 dbus-daemon[1455]: [system] Reloaded configuration 9月 21 13:23:17 nanopi-m5 dbus-daemon[1455]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.94' (uid=1000 pid=4015 comm="/usr/bin/gnome-control-center network") 9月 21 13:23:17 nanopi-m5 dbus-daemon[1455]: [system] Successfully activated service 'org.freedesktop.hostname1' 9月 21 13:53:11 nanopi-m5 dbus-daemon[1455]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=1527 comm="/usr/sbin/NetworkManager --no-daemon") 9月 21 13:53:11 nanopi-m5 dbus-daemon[1455]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' nano@nanopi-m5:$ nano@nanopi-m5:$ sudo lxc-attach -n waydroid -- systemctl status dbus lxc-attach: waydroid: ../src/lxc/attach.c: get_attach_context: 406 Connection refused - Failed to get init pid lxc-attach: waydroid: ../src/lxc/attach.c: lxc_attach: 1470 Connection refused - Failed to get attach context nano@nanopi-m5:$ nano@nanopi-m5:$ ls -l /var/lib/waydroid/ ls -l /var/lib/waydroid/lxc/waydroid/ total 52 drwxr-xr-x 2 root root 4096 9月 21 13:52 cache_http drwxr-xr-x 2 root root 4096 9月 21 13:52 host-permissions drwxr-xr-x 2 root root 4096 9月 21 13:51 images drwxr-xr-x 3 root root 4096 9月 21 13:52 lxc drwxr-xr-x 3 root root 4096 9月 21 13:52 overlay drwxr-xr-x 4 root root 4096 9月 21 13:52 overlay_rw drwxr-xr-x 4 root root 4096 9月 21 13:53 overlay_work drwxr-xr-x 1 root root 4096 9月 21 13:52 rootfs -rw-r--r-- 1 root root 472 9月 21 13:52 waydroid_base.prop -rw-r--r-- 1 root root 486 9月 21 13:53 waydroid.cfg -rw-rw-rw- 1 root root 6558 9月 21 13:57 waydroid.log -rw-r--r-- 1 root root 776 9月 21 13:53 waydroid.prop total 16 -rw-r--r-- 1 root root 989 9月 21 13:52 config -rw-r--r-- 1 root root 1860 9月 21 13:52 config_nodes -rw-r--r-- 1 root root 311 9月 21 13:53 config_session -rw-r--r-- 1 root root 346 6月 24 17:18 waydroid.seccomp nano@nanopi-m5:~$ How to reproduce? At present, RK3576 cannot use Waydrod when opening IPC and Android binder. Perhaps it is due to the absence of VNet ANDROID_SHMEM. On which OS are you observing this problem? (for easier diagnosis please provide logs with armbianmonitor -u) Armbian Ubuntu 24.04 Noble

Thank you, it looks like my Nvme was bad. It works now!