balbes150

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.

Version 20221201 for Allwinner D1. The 6.1.0-rc3 kernel is used. It is important that it is possible to use DTB separately in the kernel regardless of u-boot. Can manually configure which DTB to use, this is useful for using different hardware on different devices. There is no Debian version yet, because the system has been switched to EFI, while there is no full EFI support in Debian.

See all the news on the development of EDK2 support in this topic. There are new options for bootloader images.

Updated the list of available EDK2 images (version 20221201-next). Added a separate bootloader option for Firefly Station P2 (rk3568-roc-pc). Changed the speed value for UART, now the standard 1500000 speed option is used in all modes.

Test version of the Armbian+EDK2 system (UEFI\grub) is available. The system startup control is performed as on a regular PC - through the menu on the monitor screen, therefore, to fully use all the features of selective startup, you need to have a connected monitor and keyboard To use this option. Download the EDK2 image. https://users.armbian.com/balbes150/edk2/ https://disk.yandex.ru/d/kK6KIqHShRHLyw Unpack and burn to SD card. Download the Armbian image (kernel 6.1.0-rc7), For Station M2 https://disk.yandex.ru/d/C4Ql9v0BvhKPjQ For Station P2 https://disk.yandex.ru/d/5XuGz9WgF7FGCg unpack and burn it to a USB drive (8-16GB flash drives are recommended, I haven't checked other options). Connect the SD card and USB drive. Turn on the power. If the system does not start immediately, go to settings and select the device to start. On the EDK2 boot screen, select "Maintaining Manager boot" in the menu item and configure the device used for startup in it (change "none" to "UEFI ...."). Select Reset. If you did everything correctly, after restarting EDK2, you will receive a GRUB menu with a choice of system\kernel. If you do not select anything, the default system will be started in 5 seconds, and in 10-20 seconds (depending on the type of USB flash drive) there will be a standard Armbian customizer for the first launch. If desired, you can place the entire system on an SD card, but additional steps will be required at startup. At startup, the kernel switches the UART console to the correct value for RK (1500000) and you can monitor the kernel startup process and control the system through the UART console. That is, the parameters 115200 can only be useful for viewing the primary output from EDK2 itself, but this is only necessary for developers, for ordinary users, kernel output and system management are more useful, so I recommend using the standard value for Rockchip of 150000. https://github.com/150balbes/edk2_uefi

The system startup control is performed as on a regular PC - through the menu on the monitor screen, therefore, to fully use all the features of selective startup, you need to have a connected monitor and keyboard

I don't understand what model we are talking about, do you have a link? Only the ones I have, but not all.

Good news. A test version of the Armbian+EDK2 system (UEFI\grub) is available. To use this option. Download the EDK2 image. https://disk.yandex.ru/d/kK6KIqHShRHLyw Unpack and burn to SD card. Download the Armbian image (kernel 6.1.0-rc7), https://disk.yandex.ru/d/n_LneErcHLCQGg unpack and burn it to a USB drive (8-16GB flash drives are recommended, I haven't checked other options). Connect the SD card (eMMC should be disabled), connect the USB flash drive to the lower USB 2.0 port (other ports may work, I have not tested). Turn on the power. If the system does not start immediately, go to settings and select the device to start. On the EDK2 boot screen saver, select "Maintaining Manager boot" in the menu item and configure the device used for startup in it (change "none" to "UEFI ...."). Select Reset. If you did everything correctly, after restarting EDK2, you will receive a GRUB menu with a choice of system\kernel. If you do not select anything, the default system will be started in 5 seconds, and in 10-20 seconds (depending on the type of USB flash drive) there will be a standard Armbian customizer for the first launch. If desired, you can place the entire system on an SD card, but additional steps will be required at startup. Please note, according to the documentation, the UART console in this version of EDK2 runs at a speed of 155200n8 At startup, the kernel switches the UART console to the correct value for RK (1500000) and you can monitor the kernel startup process and control the system through the UART console. That is, the parameters 115200 can only be useful for viewing the primary output from EDK2 itself, but this is only necessary for developers, for ordinary users, kernel output and system management are more useful, so I recommend using the standard value for Rockchip of 150000. https://github.com/150balbes/edk2_uefi