sven-ola

@armfan you start mixing instructions from Xunlong, SpacemiT, and Armbian. That will not work probably. The SoC is able to boot from SD, eMMC, and MTD (in that order). With Armbian started, you can use armbian-install to write u-boot to MTD (which is Memory Technology Device aka the kernel device for SPI flash and other flash mem). That Armbian u-boot is able to indirectly boot from NVME. Or via USB but only with manual u-boot commands you can type into the UART console, see discussion on OpiR2S booting in this thread.

Hi @armfan, you can simply change the append root=UUID=(some uuid) in /boot/extlinux/extlinux.conf to suit your needs.

@Curvy Android Try something like fdtoverlays /boot/dtb/spacemit/overlay/k1-uart9.dtbo, this should trigger some u-boot message like: [ 5.621] Retrieving file: /boot/dtb/spacemit/k1-orangepi-rv2.dtb [ 5.672] Retrieving file: /boot/dtb/spacemit/overlay/k1-uart9.dtbo HTH // Sven-Ola

Hi @rm_, I tried my RV2 with current kernel and disabled bcmdhd. For reference, I have uploaded the image to https://privat-in.de under "Downloads". Prevented bcmdhd.ko from loading. There is no such load. I don't think that waiting a couple of hours will change that. Also, I have zero IPI4 irqs, thus you may need to locate the interrupt source, e.g. with lspci and lsusb. Maybe you changed something in the kernel cfg, please compare attached cfg to your /proc/config.gz). HTH // Sven-Ola config.gz

@rm_ On my RV2, there's no such load. Mine waits at the GDM3 login screen (Wayland), it's booted via NVME, no Wifi nor BT configured, and I have a shell via Ethernet. I see a difference in IPI4 dubbed "IRQ work interrupts" which may cause this but I have no clue about the real root cause. There's a patch with comments on that: https://patchew.org/linux/25833c44051f02ea2fd95309652628e2b1607a1e.camel@lenze.com/ , however I have not investigated which of the patches / corrections are in the actual 6.18.26-current-spacemit. I have 53/57° C temp with cat $(find /sys -name temp), I presume yours is higher... interrupts

Hello @rm_, there was a "CPU load bug" with uptime reporting 2.00 on idle. What you show us in your screenshot is far below 2.00. Would you mind to check /proc/interrupts? @armfan I compiled current and edge and uploaded the result to my site (https://privat-in.de). However, I presume you will need extra Wifi drivers enabled, thus you probably need to compile yourself.

Hi @armfan. To answer some of your queries: this is embedded land, we do not boot from USB normally. Just grab an SD card, flash with "dd", insert and boot from that medium. With 7.0 I have successfully booted from SD - other boot methods may or may not work. To compile your own image with 7.1 cutting edge kernel follow the steps mentioned in the following posting in this thread, see "you are on your own..." HTH // Sven-Ola

Hi @falbriard, I don't know where your image is from and to what RISC-V build of Chrome browser you are referring. Anyhow, you are free to test my latest image build from current main commit 3ce7dec74. Go to https://privat-in.de/ follow Downloads and flash Armbian-unofficial_26.05.0-trunk_Orangepirv2_trixie_current_6.18.26_minimal.img from there. You will find a script in /root which installs Gnome with GPU and Chromium. Any GPU stuff is from a mirror of the Bianbu Linux (Chinese Ubuntu variant from SpacemiT). Be warned: You may get a kernel downgrade if you install current Armbian upgrades. The image comes with 6.18.26-current-spacemit (from main) but Armbian repos may deliver 6.6 until that main-current-6.18 makes it to the update repos. HTH // Sven-Ola

Aiee! Installed my old "Noble" image. Updating will remove kernel 6.18.18 and install 6.6.99 and also has the error in the firmware package as decribed above by @VBB. Also, that funny "cli.github.com/packages" repo does not work. While that kernel downgrade is probably caused by linux-image-current-spacemit moved from 6.6.99 to 6.18.x recently (and the Armbian repos are out of date somehow) that firmware package should update without any errors. Will need time to sort this out. Anyhow, the "Noble" image works with GPU-activated Gnome desktop as long as you do not update (downgrade)...

Ah - sorry for the confusion. Those Armbian*.img files are pre-installed. Means: the GPU stuff is already there. I am not sure what happens, if you run that GPU install again (I need to investigate, give me an hour).

Hi @Logan thats probably the reason why your board does not boot from NVME.

There is a Readme.txt stating: opirv2.img is for Nextcloud install, while Armbian is none of that. You probably want the latter.

Hello @Eule - what was you solution? When I had to guess: remove SD card to trigger eMMC boot? @Logan There's a real large bunch of reasons, why you where not able to install. That screen shot probably does not show any hints. Copy and paste your terminal session where you hacked in installation commands to a text file. Then post it here as attachment, then I may be able to help. Best // Sven-Ola

Hello @VBB, those log snippets show no reason why system can freeze. Recompling bcmdhd internal SDIO Wifi driver on kernel updates works as intended. Disabling lightdm and enabling gdm3 is part of the spacemit-gpu-addon.sh you run - gdm3 is the display-manager to use if you want a DM with Wayland (b/c only Wayland works with those closed source GPU stuff). If it's stuck, just rise the loglevel= in /boot/extlinux/extlinux.conf for more output or simply download one of my images and retry running that script (Image -> https://privat-in.de under "Downloads"). HTH // Sven-Ola

@savznkvo Besides rust, dust or wrongly inserted: that may be one of those NVMEs that needs tweaking e.g. has an ASPM issue, search for "ASPM" on page one of this thread. You may also check with lspci if there is a PCI device (beside PCIe bridges). If it does not show up as /dev/nvme?n1 in a standard PC, that may be one of those mSATA SSD with an NGFF (M.2) form factor. HTH // Sven-Ola

@savznkvo if you followed my compile.sh steps from above, you should have a file Armbian-unofficial_26.05.0-trunk_Orangepirv2_trixie_current_6.18.21_minimal.img in ./output/images ready to be flashed to your SD card. Insert and boot. At this point you need TV / Kbd or UART to finish the wizard (set root PW etc). Now start armbian-install (see screen shot). Transfer *.img to /dev/nvme0n1, use netcat or similar. Then power down, remove SD and eMMC (if plugged). Restart from NVME, now you have to complete first time wizard again. Tested with current main and it works flawlessly. Addon: if you apt-get dist-upgrade, a newer kernel package from Armbian nightly builds is installed and the bcmdhd wifi kernel driver module is recompiled - which needs some time. This will DOWNGRADE from 6.18.21 to 6.18.20 currently - this works as designed. HTH // Sven-Ola

@savznkvo Installing headless (blind / via network) on a board this new will fail probably. Get a TV and connect an HDMI display or get a serial adapter and connect that for debug. I'll check later with a spare NVME, but I am pretty sure it works (provided, that you compiled the correct firmware). HTH // Sven-Ola

Hello @savznkvo and @Logan. Directly booting from NVME is not supported by the ROM software burned in the RISCV chip. Instead, the OrangePi RV2 chip is able to boot from SD, eMMC, and Flash / MTD (in this order). You need to prepare the board's internal flash for NVME boot with Boot Armbian from SD card. As root, start armbian-install and select "Install to MTD". Transfer a fresh Armbian image to your NVME. If you do not have the "armbianized" MTD boot config installed, @c0rnelius above hints on booting apply. HTH // Sven-Ola

Hello @1111Windows! Having a portrait HDMI display is rather unusual. Normally, one can buy landscape HDMI displays and simply rotate them via software or video card hardware. However: if reading out the EDID via I2C / HDMI cable does not work correctly, the HDMI display driver may simply fallback to 1920x1080@60 using the compiled-in EDID. You can try to get the EDID from the display with the apt install read-edid tool. If I recall correctly, one can provide a custom EDID binary as file to the kernel via some boot cmd parameter, see https://www.marcusfolkesson.se/blog/custom-edid-in-linux/ for details. Simply configure some mode via video= when the mode is not available in the EDID will not work (as you already found out). It should also be possible to add a custom modeline, but this is deep dive as stated here: https://nyanpasu64.gitlab.io/blog/crt-modeline-cvt-interlacing HTH // Sven-Ola

Found an error in the "use proprietary GPU driver for Spacemit K1" script. Because I cannot edit here is the corrected install script. spacemit-gpu-addon.sh

Hello @lewa_j! Thanks for the explanation. As long as https://docs.mesa3d.org/drivers/powervr.html lists BXE-2-32 as unsupported we stick to the blobs. Of course, you are free to check this for youself, see compiling "getting started" above. HTH // Sven-Ola

@Łukasz Żywczyk Currently no prebuild nightly images. You are on your own. Grab a Debian Trixie on 64 bit PC (8G RAM, 16G Disk), then sudo apt-get install docker.io qemu-user git # add yourself to group docker, logout && login git clone https://github.com/armbian/build.git cd build && ./compile.sh BOARD=orangepirv2 BRANCH=current RELEASE=trixie \ BUILD_MINIMAL=yes KERNEL_CONFIGURE=no KERNEL_BTF=no KERNEL_GIT=shallow should build your image in output/images/*.img ready to be used...

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")?

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

Download the RV2 image. It's basically the same plus DKMS (including headers) for building the bcmdhd wifi driver. You need to change the "fdt" line in /boot/extlinux/extlinux.conf for rv2->r2s (DTB file is there), e.g before uploading with mount -o offset=$(( 512 * 8192 )) Armbian-....img /mnt/