balbes150

In order for you to have the correct u-boot in SPI. Follow the instructions from this topic exactly. The image from this theme is used, only it has the correct u-boot for SPI. Download, unpack, burn to SD card. Run on Rock 5b and execute the u-boot update command in SPI in armbian-config. No manual manipulation of files (download, copy, etc.) is needed. Everything you need is included in the image. don't do this nonsense anymore Measuring the speed of SPI is absolutely useless and will not give you anything useful. Remember - SPI is used for storing and loading only u-boot, not to be confused with booting the system (kernel). The size of the u-boot is only a few tens of kilobytes and it absolutely does not matter where it is launched from, it does not affect the boot speed of the system itself (the kernel) in any way. And placing the kernel on eMMC, instead of NVMe - this already significantly affects the boot time. eMMC memory is much slower than NVMe and it takes a lot of empty time to load the kernel from it. you can use eMMC to host the kernel only if the bootloader does not support direct startup of the entire system with NVMe. It won't work (or rather it will work very crookedly and badly) - because you are trying to use old shit (boot.scr), which work very poorly and contain a bunch of hidden problems. Which versions of SPI have you used, how did you install them on SPI? If you use the official versions of u-boot for SPI, they will not work correctly, there are too many bugs and errors in them. do not try to mount it and look for something in it, this part contains specially generated binary code.

Use the first section. Searches for the boot partition only on the first partition.

How did you determine that SPI is not working? Please note that the SPI recording process is very slow, it can take up to 5-7 minutes. After installing the system on NVMe, you need to confirm the replacement \ update of the SPI content, you must wait for the process to complete, when the system itself informs that the process is completed. I also pay attention if you have a u-boot on eMMC (left over from previous installations), it will be used to run. To make sure that SPI is working, disable eMMC or completely erase it with the DD utility (so that the remnants of the previous systems \ bootloader do not affect the startup process). If desired, you can use eMMC as an additional disk (create partitions on it and mount it into the system), but there should be no old u-boot on eMMC (which use the wrong order of starting systems). The SPI+NVMe variant will be the fastest than eMMC+NVMe. If you chose eMMC+NVMe, the kernel will be started from eMMC (reading the kernel, initrd. dtb), which is significantly slower than reading the same files from NVMe. What system are you using (full image name)? The HDMI sound is guaranteed to work in my builds. If this is the DE (XFCE) version, just launch the playback application and, with the application running, open the Volume Control sound Settings applet and select the device for audio output (analog output is enabled there by default). I don't understand what kind of Wi-Fi are we talking about? Are these the official versions from the Armbian website ?

This is normal for the first launch, during which a lot of primary settings (partition expansion, etc.) take place.

the manufacturer's use of a power supply with PD is a big stupidity Now, to solve this problem, have to use a regular power supply (12 or 20 volts) and a jack to USB-C adapter.

Describe your steps in detail. Which devices do you have connected - eMMC, NVMe? Have you recorded something in SPI before? The general procedure for installing the system on SPI+NVMe. If the eMMC module is connected, remove it, it is not needed to work in SPI+NVMe mode. Start the system from the SD card. Create a partition on the NVMe (if the NVMe is new, perhaps create an MBR partition table first). To create a partition, you can use gparted, which is convenient for graphical execution of steps. For example, you can create one partition for the entire NVMe with ext4. And only after that, run armbian-config and select the installation of SPI - NVMe\ SATA. Select the NVMe partition and start the installation. At the end, the system will ask you to update \ install the bootloader on SPI, confirm the choice and wait a few more minutes (the process of writing SPI is slow). If you do everything correctly, after turning off and removing the SD card, when you turn on the system will start with NVMe. Please note that armbian-conf (armbian-install) does not create partitions on NVMe, it uses existing ones, i.e. you must create a partition on NVMe yourself BEFORE starting the installation.

I'm just wondering which power supply do you use (with or without PD function)? What size of RAM do you have , is it correctly determined ? How does starting the system from an SD card work after installing the system on NVMe ?

See the first message of the topic, I changed it and there is a link to the shared directory with all the images.

New version 20221210. I checked the installation of the new version of u-boot on SPI. Everything works correctly. The new version works correctly with the system startup order. If you install the system on NVMe and connect the SD card with another system, the SD card will start. For example, you can install an Ubuntu system on NVMe and run Debian from an SD card. Also, the new u-boot supports the system startup mode with EFI\grub.

after installing the image from EFI\Grub on Nvme, I tried to connect an SD card with an EDK2-EFI image and voila, there is a Grub menu in the UART console and the system starts and works normally. But I found a strange bug. When starting using u-boot-efi, the system in u-boot shows 15.7 GB of RAM available (this is normal), but after starting the entire system, it gives out that there is only 4GB of RAM. With the launch of EDK2-EFI - 8GB of RAM is reflected in it And the system sees 8 GB. What is the reason.I haven't found out yet. The link to the image with EDK2-EFI, it needs to be written to the SD card instead of u-boot-efi. https://disk.yandex.ru/d/V5AxXNN2yJnOfg

The Gnome interface is the ugliest and moronic craft. 😎

A test version of Armbian images to run from NVMe without having to write the curve of the official u-boot version to SPI (which breaks the launch of other systems from SD cards and other media). The whole system works completely with NVMe . https://disk.yandex.ru/d/V5AxXNN2yJnOfg The installation of the system on NVMe and u-boot in SPI was checked using the standard tools of the armbian-config utility. Everything works correctly. Also in this new u-boot, the ability to start the system in EFI mode is available. To install a system with EFI\grub on NVMe. Install a new bootloader in SPI. Start the system from the SD card and burn the system image with the EFI\grub DD utility to NVMe. images with EFI\grub support are located in directories with the extension "EFI"

I can add PR to the official Armbian build system for RISC-V (then the kernel will have an automatic update), but I'm not sure it will be accepted.

To automatically update the kernel, you need to have a network repository, I don't have such an opportunity yet. I've heard that someone is working on creating such a repository for this build system. If it is, then the kernel will be updated automatically. In principle, I can add kernel packages to the image directory for manual updates (in case there is a significant kernel change).

use an image without XFCE in the name . Armbian_22.08.0-trunk_Nezha_jammy_current_6.1.0.img

You inattentively read the info earlier. I specifically wrote that Debian (sid) requires ADDITIONAL manual work to run (copying additional files, editing the configuration file, etc.). Use Ubuntu versions, there is nothing you need to change after writing the image, it connects and will work.

Describe in detail what the problem is, what steps did you take? My system runs fine and runs on mangoPIMqpro. All images from this theme are collected on a PC in cross-compilation mode. I also checked the full image build on StarFive1 (i.e. directly on the RISC-V device), it works the same, but so far I don't have a fast enough RISC-V device to switch to a fully native build. I know that there are some Discord-Risc-v participants who build on ARM devices (including in cluster mode on multiple devices at the same time). You can clarify all the details in the corresponding Disord topic.

Version 20221206 with kernel 6.1.0-rc8. Update EDK2 - added screensavers for Station. fixed microfreezes during system operation.

New version 20221204-EDK-EFI for Station M2\P2. With support for direct launch of the entire system from an SD card. i.e., a separate USB media is no longer required to launch. Burn the system to an SD card, connect it to the device, turn on the power and immediately get the launch of a full-fledged system completely from the SD card. The old option of starting from USB media is also preserved. That is, you can write another system to USB (in which EFI support is enabled) and when connected together with the SD card, the system will start from USB.

Tnx. Ok.

@amazingfateSorry, I'm not an expert on ffmpeg. As a silly assumption. Have you tried changing the player settings from DRM to EGL ?

I was able to run Debian in EFI mode (to Allwinner D1, can do the same on StarFive) . I built a Debian image for the EFI variant (I uploaded the images to the site), but without grub-efi packages and got the exact same structure as in Ubuntu-efi when writing to the SD card. I copied the binaries manually (all dir EFI) from Ubuntu SD card to the EFI partition and the /boot/grub directory to the /boot directory Debian. Edited the UUID (see extlinux.conf) in grub.cfg. After that, the system started up perfectly and works.

Licherv Doc and MangoPI MQ pro - I don't have the equipment to check WiFi operation, but sees WiFi networks

At the first start of the system, the primary setup wizard should start, where you set the password for ROOT, the user name and password. There should be an invitation on the screen or in the UART console to change the password and other steps. How are you connected to the device ? By default, the password 1234 for ROOT is set at the first start.

I have already checked on MangoQ Pro, it works. by the way, when testing on different D1 devices, I noticed that USB is always detected and works.