JamesCL Posted June 2 Author Posted June 2 1)Boot Message: U-Boot 2017.09-orangepi (Feb 15 2023 - 16:41:34 +0800) Model: Orange Pi 5 PreSerial: 2, raw, 0xfeb50000 DRAM: 7.7 GiB Sysmem: init Relocation Offset: eda2c000 Relocation fdt: eb9f8c88 - eb9fecb0 CR: M/C/I Using default environment ... 2) in '/boot/dtb/rockchip/overlay' exist: rockchip-rk3588-sata1.dtbo rockchip-rk3588-sata2.dtbo /boot/armbianEnv.txt # if add 'overlays=opi5-sata' error: ** File not found /boot/dtb/rockchip/overlay/rockchip-rk3588-opi5-sata.dtbo ** if add 'overlays=sata1' message: Applying kernel provided DT overlay rockchip-rk3588-sata1.dtfailed on fdt_overlay_apply(): FDT_ERR_NOTFOUND Error applying DT overlays, restoring original DT if add 'overlays=sata2' message: Applying kernel provided DT overlay rockchip-rk3588-sata2.dtTrying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not 'kaslrseed' - try 'help' Starting kernel ... 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. 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! UUID=161a1dc1-0e13-476e-84b6-4423ebac7f9e does not exist. Dropping to a shell! 0 Quote
JamesCL Posted June 2 Author Posted June 2 mount -o loop,offset=$((512*32768)) Armbian_24.5.1_Orangepi5_noble_edge_6.8.10.img /mnt root@debian:/mnt/boot/dtb/rockchip/overlay# ls *sata* rockchip-rk3588-sata1.dtbo rockchip-rk3588-sata2.dtbo root@debian:/mnt/boot# cat /mnt/boot/armbianEnv.txt verbosity=1 bootlogo=false console=both overlay_prefix=rockchip-rk3588 fdtfile=rockchip/rk3588s-orangepi-5.dtb rootdev=UUID=8d4fb7ad-919e-4333-b280-898b77c80f0a rootfstype=ext4 for 'Armbian_24.5.1_Orangepi5_noble_edge_6.8.10.img' what should I add to armbianEnv.txt to start armbian from a m2 sata? Thank you so much 0 Quote
Efe Çetin Posted June 2 Posted June 2 9 hours ago, JamesCL said: 'Armbian_24.5.1_Orangepi5_noble_edge_6.8.10.img' what should I add to armbianEnv.txt to start armbian from a m2 sata? Download https://github.com/armbian/linux-rockchip/blob/rk-6.1-rkr1/arch/arm64/boot/dts/rockchip/overlay/orangepi-5-sata.dts and add it to the system using armbian-add-overlay orangepi-5-sata.dts it seems Like we don't have an overlay for sata0 for edge kernel yet 0 Quote
JamesCL Posted June 4 Author Posted June 4 (edited) @Efe Çetin: thank ... now I'm closer uboot recognizes the disk armbian recognizes it, but after a few seconds it disconnects. (the disk is new and I have no problems connecting it to another computer) I attach more information: root@orangepi5:~# dmesg | grep ata [ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923 [ 0.000000] Memory: 7453648K/8124416K available (17920K kernel code, 2860K rwdata, 6808K rodata, 5056K init, 755K bss, 277552K reserved, 393216K cma-reserved) [ 0.020108] CPU features: detected: Data cache clean to the PoU not required for I/D coherence [ 0.575618] libata version 3.00 loaded. [ 0.654348] ahci-dwc fe210000.sata: supply ahci not found, using dummy regulator [ 0.654403] ahci-dwc fe210000.sata: supply phy not found, using dummy regulator [ 0.654587] platform fe210000.sata:sata-port@0: supply target not found, using dummy regulator [ 0.654686] ahci-dwc fe210000.sata: PMPn is limited up to 5 ports [ 0.654725] ahci-dwc fe210000.sata: masking port_map 0x1 -> 0x1 [ 0.654736] ahci-dwc fe210000.sata: SSS flag set, parallel bus scan disabled [ 0.654744] ahci-dwc fe210000.sata: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl platform mode [ 0.654750] ahci-dwc fe210000.sata: flags: ncq sntf stag pm led clo only pmp fbs pio slum part ccc apst [ 0.654760] ahci-dwc fe210000.sata: port 0 is not capable of FBS [ 0.655531] ata1: SATA max UDMA/133 mmio [mem 0xfe210000-0xfe210fff] port 0x100 irq 42 lpm-pol 0 [ 1.124014] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.126188] ata1.00: ATA-11: NT-512 2242, SN14546, max UDMA/133 [ 1.126199] ata1.00: 1000215216 sectors, multi 1: LBA48 NCQ (depth 32) [ 1.128687] ata1.00: configured for UDMA/133 [ 1.872260] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 84,32 bit host data width,256 deep fifo [ 3.537156] EXT4-fs (sdb2): mounted filesystem f43263a1-3f44-43aa-bb0b-415ba559deab ro with writeback data mode. Quota mode: none. [ 5.099156] systemd[1]: systemd-hwdb-update.service - Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc). [ 5.761788] systemd[1]: systemd-hwdb-update.service - Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc). [ 32.804419] ata1: SATA link down (SStatus 0 SControl 300) [ 38.139094] ata1: SATA link down (SStatus 0 SControl 300) [ 38.139120] ata1: limiting SATA link speed to <unknown> [ 43.472494] ata1: SATA link down (SStatus 0 SControl 330) [ 43.472521] ata1.00: disable device [ 43.472588] ata1.00: detaching (SCSI 0:0:0:0) root@orangepi5:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sdb 8:16 1 29.7G 0 disk ├─sdb1 8:17 1 256M 0 part /boot └─sdb2 8:18 1 29.2G 0 part /var/log.hdd / mtdblock0 31:0 0 16M 0 disk zram0 251:0 0 3.8G 0 disk [SWAP] zram1 251:1 0 50M 0 disk /var/log zram2 251:2 0 0B 0 disk root@orangepi5:~# Edited June 6 by JamesCL Update 0 Quote
0xf1 Posted October 15 Posted October 15 (edited) for me it is the same on 6.10 kernel - just no well defined dts, and if I download something from github, it does not work, I have the same error as you. on 6.1.75 it works well with configuration verbosity=1 bootlogo=false console=both overlay_prefix=orangepi-5 fdtfile=rockchip/rk3588s-orangepi-5.dtb rootfstype=ext4 overlays=sata ls -la /boot/dtb/rockchip/overlay | grep orangepi-5- -rwxr-xr-x 1 root root 398 Aug 24 17:27 orangepi-5-ap6275p.dtbo -rwxr-xr-x 1 root root 281 Aug 24 17:27 orangepi-5-disable-led.dtbo -rwxr-xr-x 1 root root 5367 Aug 24 17:27 orangepi-5-lcd1.dtbo -rwxr-xr-x 1 root root 5454 Aug 24 17:27 orangepi-5-lcd2.dtbo -rwxr-xr-x 1 root root 325 Aug 24 17:27 orangepi-5-plus-disable-leds.dtbo -rwxr-xr-x 1 root root 614 Aug 24 17:27 orangepi-5-plus-hdmi2-8k.dtbo -rwxr-xr-x 1 root root 4194 Aug 24 17:27 orangepi-5-plus-lcd.dtbo -rwxr-xr-x 1 root root 1547 Aug 24 17:27 orangepi-5-plus-ov13850.dtbo -rwxr-xr-x 1 root root 1547 Aug 24 17:27 orangepi-5-plus-ov13855.dtbo -rwxr-xr-x 1 root root 350 Aug 24 17:27 orangepi-5-plus-sata2.dtbo -rwxr-xr-x 1 root root 1631 Aug 24 17:27 orangepi-5-pro-cam1.dtbo -rwxr-xr-x 1 root root 1571 Aug 24 17:27 orangepi-5-pro-cam2.dtbo -rwxr-xr-x 1 root root 325 Aug 24 17:27 orangepi-5-pro-disable-leds.dtbo -rwxr-xr-x 1 root root 3794 Aug 24 17:27 orangepi-5-pro-lcd.dtbo -rwxr-xr-x 1 root root 344 Aug 24 17:27 orangepi-5-pro-sfc.dtbo -rwxr-xr-x 1 root root 350 Aug 24 17:27 orangepi-5-sata.dtbo Edited October 16 by 0xf1 0 Quote
JamesCL Posted October 16 Author Posted October 16 Hi, in my case... after many problems, I decided to use only nvme on my opi5. Regards cat /proc/cmdline root=UUID=f43263a1-3f44-43aa-bb0b-415ba559deab rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart= usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 uname -a Linux orangepi5 6.8.1-edge-rockchip-rk3588 #4 SMP PREEMPT Fri Mar 15 18:19:29 UTC 2024 aarch64 GNU/Linux 0 Quote
dsouza Posted October 19 Posted October 19 Same problem here but with NVMe. It was working fine until I did an apt upgrade/update, then it stopped booting from NVMe with this exact same issue... 0 Quote
JamesCL Posted October 19 Author Posted October 19 In my case, my opi5 never worked no matter how many armbian versions I changed. I was disappointed with the SBC and left it lying around for many months... until one day I tried the "trunk" and error... error of versions, one after another... and suddenly I found a particular version... "24.5.0-trunk.276" and it has been working for months without problems... until now... This versión work fine for me: Armbian_24.5.0-trunk.276_Orangepi5_trixie_edge_6.8.1_minimal.img.tar.gz root@orangepi5:~# dpkg -l | grep '^h' hi armbian-bsp-cli-orangepi5-edge 24.11.0-trunk.204 arm64 Armbian CLI BSP for board 'orangepi5' branch 'edge' hi armbian-firmware 24.5.0-trunk.276 all Armbian - Linux firmware hi linux-dtb-edge-rockchip-rk3588 24.5.0-trunk.276 arm64 Armbian Linux edge DTBs in /boot/dtb-6.8.1-edge-rockchip-rk3588 hi linux-image-edge-rockchip-rk3588 24.5.0-trunk.276 arm64 Armbian Linux edge kernel image 6.8.1-edge-rockchip-rk3588 hi linux-u-boot-orangepi5-edge 24.5.0-trunk.276 arm64 Das U-Boot for orangepi5 root@orangepi5:~# apt-mark showhold armbian-bsp-cli-orangepi5-edge armbian-firmware linux-dtb-edge-rockchip-rk3588 linux-image-edge-rockchip-rk3588 linux-u-boot-orangepi5-edge 0 Quote
haajee Posted October 20 Posted October 20 (edited) Got the same problem after the last update/upgrade... Can't restore because it hangs and did not get a shell.... 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. 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! UUID=db80a2ac-ec37-4fda-91db-92604becfcce does not exist. Dropping to a shell! When i boot in u-boot it looks like it also don't see the nvme drive: => nvme nvme - NVM Express sub-system Usage: nvme scan - scan NVMe devices nvme detail - show details of current NVMe device nvme info - show all available NVMe devices nvme device [dev] - show or set current NVMe device nvme part [dev] - print partition table of one or all NVMe devices nvme read addr blk# cnt - read `cnt' blocks starting at block `blk#' to memory address `addr' nvme write addr blk# cnt - write `cnt' blocks starting at block `blk#' from memory address `addr' => nvme scan => nvme detail => nvme device no nvme devices available => And last update: i puted the nvme drive in a USB3 NVME external drive. And the drive in the USB 3.0 in the USB port and it's just back up and running. I don't know what the nvme broke to work . But i just ordered a new NVME drive because the old one was to small. So a fresh install is also coming maybe it will work again. Edited October 20 by haajee 0 Quote
haajee Posted October 21 Posted October 21 New SSD arrived today. wrote image on it installed the SSD and runs directly! Did also update my SSD to NVME disk and think i broke something. it won't boot even from the USB anymore. Got some errors like can't reset port 1 and a lot more but putty won't save all output. So i think i could make better tomorrow a clean fresh install on the new SSD and restore the files. But all my own fault. 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.