1111Windows Posted Friday at 05:15 AM Posted Friday at 05:15 AM @sven-ola Have you tried booting from a microSD card? I downloaded Armbian-unofficial_26.02.0-trunk_Orangepirv2_trixie_current_6.18.18_gnome_desktop.img and flashed it to my microSD card, but it won't boot. log: sys: 0x200 try sd... bm:3 j... U-Boot SPL 2022.10_armbian-2022.10-Sd61c-P155c-H452d-V4161-B61c5-R448a (Mar 17 2026 - 03:52:17 +0000) [ 0.381] DDR type LPDDR4X [ 0.383] set ddr tx odt to 80ohm! [ 0.393] lpddr silicon init consume 11ms [ 0.394] Change DDR data rate to 2400MT/s [ 0.633] Boot from fit configuration x1_orangepi-rv2 [ 0.635] ## Checking hash(es) for config conf_18 ... OK [ 0.641] ## Checking hash(es) for Image uboot ... crc32+ OK [ 0.652] ## Checking hash(es) for Image fdt_18 ... crc32+ OK [ 0.674] ## Checking hash(es) for config config_1 ... OK [ 0.677] ## Checking hash(es) for Image opensbi ... crc32+ OK [ 0.725] U-Boot 2022.10_armbian-2022.10-Sd61c-P155c-H452d-V4161-B61c5-R448a (Mar 17 2026 - 03:52:17 +0000) [ 0.732] CPU: rv64imafdcv [ 0.734] Model: ky x1 orangepi-rv2 board [ 0.738] DRAM: 2 GiB [ 0.830] Core: 414 devices, 29 uclasses, devicetree: board [ 0.843] WDT: Started PMIC_WDT with servicing (60s timeout) [ 0.848] WDT: Started watchdog@D4080000 with servicing (60s timeout) [ 0.857] MMC: [ 0.956] *** Warning - bad CRC, using default environment [ 0.961] initialize_console_log_buffer [ 0.962] Have allocated memory for console log buffer [ 0.967] In: serial [ 0.969] Out: serial [ 0.971] Err: serial [ 1.116] k1x_qspi spi@d420c000: qspi iobase:0x0x00000000d420c000, ahb_addr:0x0x00000000b8000000, max_hz:26500000Hz [ 1.124] k1x_qspi spi@d420c000: rx buf size:128, tx buf size:256, ahb buf size=512 [ 1.131] k1x_qspi spi@d420c000: AHB read enabled [ 1.136] k1x_qspi spi@d420c000: bus clock: 26500000Hz, PMUap reg[0xd4282860]:0x0000075b [ 1.143] k1x_qspi spi@d420c000: AHB buf size: 512 [ 1.148] SF: Detected XM25QU128C with page size 256 Bytes, erase size 64 KiB, total 16 MiB List of MTD devices: [ 1.159] * nor0 [ 1.160] - device: flash@0 [ 1.163] - parent: spi@d420c000 [ 1.166] - driver: jedec_spi_nor [ 1.170] - path: /soc/spi@d420c000/flash@0 [ 1.173] - type: NOR flash [ 1.176] - block size: 0x10000 bytes [ 1.180] - min I/O: 0x1 bytes [ 1.183] - 0x000000000000-0x000001000000 : "nor0" [ 1.188] - 0x000000000000-0x000000010000 : "bootinfo" [ 1.193] - 0x000000010000-0x000000020000 : "private" [ 1.198] - 0x000000020000-0x000000060000 : "fsbl" [ 1.203] - 0x000000060000-0x000000070000 : "env" [ 1.208] - 0x000000070000-0x0000000a0000 : "opensbi" [ 1.213] - 0x0000000a0000-0x000001000000 : "uboot" [ 1.219] Failed to get fastboot key config: -19 [ 1.222] Failed to probe HUSB239: -19 [ 1.227] RGMII interface [ 1.228] eth0: ethernet@cac80000 [ 1.231] MAC mapping file path not set in environment [ 1.236] K1X: :_load_env_from_blk [ 1.247] Can't set block device [ 1.248] Net: eth0: ethernet@cac80000 [ 1.254] Hit any key to stop autoboot: 0 Loading K1-X Environment ... [ 2.260] [ 2.261] Running NVMe Scan ... [ 2.272] pcie_dw_k1x pcie@ca400000: has no power-on-status flag, use default. [ 2.277] Now init Rterm... [ 2.279] pcie prot id = 1, porta_init_done = 0 [ 2.283] Now waiting portA resister tuning done... [ 2.288] porta redonly_reg2: 00005d37 [ 2.292] pcie_rcal = 0x00005d37 [ 2.295] pcie port id = 1, lane num = 2 [ 2.298] Now int init_puphy... [ 2.301] waiting pll lock... [ 2.304] Now finish init_puphy.... [ 2.307] pcie_dw_k1x pcie@ca400000: Unable to get phy0 [ 2.312] pcie_dw_k1x pcie@ca400000: Unable to get phy1 [ 2.317] pcie_dw_k1x pcie@ca400000: PCIe interface power on, set gpio 116 to 1 [ 3.426] PCIE-0: Link down [ 3.438] pcie_dw_k1x pcie@ca800000: has no power on gpio. [ 3.441] pcie_dw_k1x pcie@ca800000: has no power-on-status flag, use default. [ 3.448] Now init Rterm... [ 3.450] pcie prot id = 2, porta_init_done = 0 [ 3.455] Now waiting portA resister tuning done... [ 3.459] porta redonly_reg2: 00005d37 [ 3.463] pcie_rcal = 0x00005d37 [ 3.466] pcie port id = 2, lane num = 2 [ 3.470] Now int init_puphy... [ 3.472] waiting pll lock... [ 3.475] Now finish init_puphy.... [ 3.479] pcie_dw_k1x pcie@ca800000: Unable to get phy0 [ 3.484] pcie_dw_k1x pcie@ca800000: Unable to get phy1 [ 4.590] PCIE-1: Link down [ 4.642] pcie_dw_k1x pcie@ca400000: has no power-on-status flag, use default. [ 4.646] Now init Rterm... [ 4.648] pcie prot id = 1, porta_init_done = 0 [ 4.653] Now waiting portA resister tuning done... [ 4.657] porta redonly_reg2: 00005d37 [ 4.661] pcie_rcal = 0x00005d37 [ 4.664] pcie port id = 1, lane num = 2 [ 4.668] Now int init_puphy... [ 4.671] waiting pll lock... [ 4.673] Now finish init_puphy.... [ 4.677] pcie_dw_k1x pcie@ca400000: Unable to get phy0 [ 4.682] pcie_dw_k1x pcie@ca400000: Unable to get phy1 [ 4.687] pcie_dw_k1x pcie@ca400000: PCIe interface power on, set gpio 116 to 1 [ 5.795] PCIE-0: Link down [ 5.807] pcie_dw_k1x pcie@ca800000: has no power on gpio. [ 5.810] pcie_dw_k1x pcie@ca800000: has no power-on-status flag, use default. [ 5.817] Now init Rterm... [ 5.819] pcie prot id = 2, porta_init_done = 0 [ 5.824] Now waiting portA resister tuning done... [ 5.828] porta redonly_reg2: 00005d37 [ 5.832] pcie_rcal = 0x00005d37 [ 5.835] pcie port id = 2, lane num = 2 [ 5.839] Now int init_puphy... [ 5.841] waiting pll lock... [ 5.844] Now finish init_puphy.... [ 5.848] pcie_dw_k1x pcie@ca800000: Unable to get phy0 [ 5.853] pcie_dw_k1x pcie@ca800000: Unable to get phy1 [ 6.959] PCIE-1: Link down [ 6.963] no nvme partition table available [ 6.964] Couldn't find partition nvme 0:1 [ 6.968] Couldn't find partition nvme 0:1 [ 6.972] Couldn't find partition nvme 0:1 [ 6.976] Couldn't find partition nvme 0:1 [ 6.980] Couldn't find partition nvme 0:1 => 0 Quote
sven-ola Posted Friday at 08:49 AM Author Posted Friday at 08:49 AM vor 3 Stunden schrieb 1111Windows: U-Boot SPL 2022.10_armbian-2022.10-Sd61c-P155c-H452d-V4161-B61c5-R448a (Mar 17 2026 - 03:52:17 +0000) Hello @1111Windows, you are booting an unknown u-boot from NVME that does not find any meaningful data stored on the NVME. You may need to re-insert the SD card or swap to a working SD card or so. I attach the (timestamp stripped for better diff) version from you (forum.txt) and the expected UART output on my RV2 (minicom.txt). The latter I have captured after re-downloading and SD-flashing the mentioned trixie-gnome img which has a root file system with UUID=8f6e5f9c-3108-4e4d-8fbd-10a8295d396e. HTH // Sven-Ola forum.txt minicom.txt 0 Quote
lewa_j Posted 14 hours ago Posted 14 hours ago Hello @sven-ola, big thank you for all you work on RV2 support! I was wondering, is it possible to enable CONFIG_DRM_POWERVR for 6.18 and up? I guess more than that is required to actually use it though. 0 Quote
maxsub Posted 13 hours ago Posted 13 hours ago The R2S has an internal eMMC and a USB port. After debugging the default u-boot scripts I found that it does not boot from USB once you have Armbian installed on eMMC. To reinstall a fresh copy of Armbian or any other OS, you have to use the fastboot based KyTool which does not usually work on a modern Windows PC with USB 3.0 ports. So you could end up in a state where you have to manually interrupt U-boot, or worse if you corrupt the eMMC. I rewrote the u-boot flow on the R2S. I also cleaned up the nand-sata-install and added a lot of safety checks. It will look at USB and boot from there. After that you can safely install to eMMC. Below is the link. Please let me know if it is worth submitting a PR. The changes will not touch anything in the main system, it adds these scripts to /usr/local/lib and /usr/local/sbin. https://github.com/arvindmaxar/u-boot-tools 0 Quote
1111Windows Posted 12 hours ago Posted 12 hours ago Hello@sven-ola After flashing the image correctly, I found that running `sudo apt upgrade` to update the system caused the kernel to fail to load; the issue appears to stem from the kernel update. Installing the `linux-image-current-spacemit 26.2.1` update causes the kernel to fail to load. I noticed that the kernel version in the image is 6.18.18-current-spacemit, while the kernel version in the Armbian repository is 6.6.99-current-spacemit. I think this is likely the root of the problem; I should not have used apt to update the kernel. In any case, thank you for porting Armbian to the OrangePi RV2. 0 Quote
sven-ola Posted 2 hours ago Author Posted 2 hours ago vor 11 Stunden schrieb lewa_j: is it possible to enable CONFIG_DRM_POWERVR for 6.18 and up Hello @lewa_j, there already is a CONFIG_POWERVR_ROGUE=y in the 6.18 kernel. This was required for Wayland and subsequently for Spacemit-GPU-Binary-Support (see https://github.com/armbian/build/pull/9515). What exactly will work additionally with this option (I am not a GPU expert)? Hello @1111Windows, doing "apt-get upgrade" on my GPU demo image this will downgrade the kernel from 6.18.18 to 6.6.99. Probably b/c recently the 6.6.99 was changed "current->legacy" and the 6.18 changed "edge->current". Also, OpiRV2 is not a really / full official Armbian image right now. So we probably need to wait until build pipelines catch up. I'll place a "apt-mark hold linux-image*" on my todo for those images. @maxsub The R2S does not have a NOR flash (or "MTD") that it boots from in the first place? That little project of yours does not look like an Armbian fork ready to be merged in. I may need some time to dig in and understand how it works. Have you considered changing the u-boot enviroment (...that can be save with "env save")? 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.