balbes150

ver 20230302 fixed MTD+USB+NVMe startup.

I checked the fan operation with NVMe. Yes, there is a problem (I observe a different situation - the fan is constantly running at high speed.) - the control does not work, the reason is the change of parameters (when the NVMe is physically connected, the control parameter changes). The control parameter is hard-coded in a binary file that is represented by Firefly. I have requested Firefly sources or a new binary version for NVMe. All these "points" are marketing nonsense that you should not pay attention to. I recommend using ARM-blob, you can take deb packages from Firefly or connect their repository and install them over the network (see their Ubuntu image for details).

the standard extlinux.conf settings file is used. which is many times more convenient and well standardized. information on its options and how to use them is full on the Internet. if you really need to transfer something to u-boot, use a text file /boot/uEnv.txt (this is also a standard settings file for u-boot). It is processed immediately after the extlinux.conf file and after that the standard procedure for loading the kernel\initrd\dtb is started.

Starting from version 20230228, support for overlays has been added. The order of use. # mkdir -p /sys/kernel/config/device-tree/overlays/tsys01 # cd <bin directory under DT-Overlays> # cat tsys01.dtbo > /sys/kernel/config/device-tree/overlays/tsys01/dtbo remove the dtbo feature: # rmdir /sys/kernel/config/device-tree/overlays/dtoverlay https://www.96boards.org/documentation/consumer/dragonboard/dragonboard410c/guides/dt-overlays.md.html#32-loading-overlays-via-configfs https://github.com/starfive-tech/VisionFive2#appendix-ii-using-dtb-overlay-dynamically Please note, I have not tested this functionality.

Nothing should appear on the screen at the first start, you are waiting only for the auto-login to be turned off automatically during this time and at the next reboot you will get a working login screen to choose which version to use (x11 or wayland). You need to switch to the console no earlier than 10-15 minutes, only after all automatic processes are completed.

There are several solutions. The simplest one is after the first login (after the initial setup, when the screen is black with the mouse cursor), wait 10-15 minutes (this is the time to reset the automatic login), turn off the power and turn it on again so that the LIGHTDM screen appears, select the x11 option (do not use wayland until the ARM-BLOB package is installed). Or switch to the console (Ctrl+Alt+F2), and install the ARM-BLOB or Panfork package and reboot the system.

These models are not listed on the report page. BananaPI r2pro - work Khadas EDGE2 - work

Perhaps because of these tests with different u-boot you have a problem. Start by completely clearing SPI\MTD (with the DD command) and physically disabling NVMe. After that, use a power supply without PD with a power of at least 12Vx3A, completely clean the SD card (with the DD command) and record the last image from this topic. Only after these steps, you can reconnect NVMe and run and install u-boot in SPI\MTD+NVMe.

Power supply with PD ?

Just write the new version to the SD card, start the system from it and install it on MTD+NVMe. If you already have the necessary partition on NVMe, no additional manual operations (cleaning SPI\MTD, etc.) are necessary.

@NicoDVersion 20230219. No manual copying of dtb is needed anymore, all support is included in u-boot, i.e. after writing the image to USB\SD, you can use it immediately. The installation on eMMC has been checked. ps All the necessary changes will automatically get into the official relise version, you can build your own version of the images

New version 20230219 with direct support for launching from USB. You don't need to copy anything manually anymore. When installing a new bootloader on eMMC, you get the opportunity to directly start the system from USB without using any additional devices. At the same time, you get the opportunity to start from USB when using SD\eMMC\NVMe, i.e. if you have these media with your system, when you connect USB to the system, when you turn on the power, the system starts from the beginning with USB. This is convenient for quick startup of other systems, without the need to change something or disconnect other media (SD\NVMe). For example, you can install the main Ubuntu system on NVMe and at any time quickly launch another version from USB - Debian, etc.

There is a mirror, where images are updated to the latest version (In a few hours there will be a new version). https://users.armbian.com/balbes150/ I don't use archlinux. As far as I know (I may be mistaken) - this version is assembled from parts of Armbian with the addition of ready-made binary files and settings from other systems, i.e. it is essentially an analogue of twisteros (a prefabricated binary hodgepodge) based on archlinux. u-boot radxa is useless junk with a bunch of errors and hidden problems for users (with any failure to start with NVMe, you will get a problem, you cannot start any system with SD\USB until you physically disable NVMe and other problems). armbian-config is an order of magnitude better and more convenient, it also allows you to easily install\update u-boot in MTD\SPI and simultaneously install the system on NVMe or other media (eMMC\USB). For a long time there have been versions of Armbian with support for different EFI\grub variants (EDK2-EFI and u-boot-efi), see details and links to such images in this topic. So far, OS selection management is available only via UART. Using ARM-blob and additional system performance settings, I get almost 3800 on Rock 5b, on other rk3588s models I get more than 4400 and I have a suspicion that slower memory is used on models with 16GB of RAM, but no one wanted to share the results from rock5b with 8 GB of RAM, with with this system, to determine exactly how reliable it is. Using extlinux.conf or efi\grub (with the correct parameters).

New version 20230219 with direct support for launching from USB. You don't need to copy anything manually anymore. When installing a new bootloader in MTD\SPI, you get the opportunity to directly start the system from USB without using any additional devices (no longer requires SD\eMMC\NVMe). At the same time, you get the opportunity to start from USB when using SD\eMMC\NVMe, i.e. if you have these media with your system, when you connect USB to the system, when you turn on the power, the system starts from the beginning with USB. This is convenient for quick startup of other systems, without the need to change something or disable other media (SD\mmc\NVMe). For example, you can install the main Ubuntu system on NVMe and at any time quickly launch another version from USB - Debian, etc.

Version 20230217 with support for launching from USB media. To enable USB startup, after writing the image to the SD card (or after installing it on eMMC), add the dtb.img file to the / of the first SD\eMMC partition (download link). https://disk.yandex.ru/d/vM36JzR-xyyERw Burn the image to USB connect it to the device and turn on the power. The system starts automatically from USB. For details, see this topic.

There is good news. I am currently testing a new loader u-boot. A version with support for direct start from USB media will be uploaded to the website tomorrow. That is, can have a bootloader in SPI\MTD and only a USB media with the system and fully run the system from USB. Or have a system on NVMe and fully launch another system from USB media, simply by connecting a USB media (disconnected the USB media and the system starts with NVMe).

There are two options for how to implement USB startup support. The first is to do everything automatically, i.e. the user does nothing manually (minus - there will be no compatibility with the official versions). The second option is that some of the operations need to be done manually (copy DTB to the root of the first section), there will be compatibility with the official versions of khadas images. The question is - which is better ? https://users.armbian.com/balbes150/kedge2/

Version 20230217. Added support for installation on eMMC. Important. After installation on eMMC, to enable support for starting the system from USB, you need to copy the file /boot/dtb/rockchip/rk3588s-khadas-edge2.dtb to /dtb.img (that's right, in / the first partition). Initially, I made the system without the need for manual copying, but by default, this option is used in official versions (/dtb.img), and I have not yet decided which option is preferable (for subsequent compatibility with the main kernel and official versions of the system from khadas).

Have you installed all the components ? Look at the topic, there are links to additional packages for ARM-blob. And look at the packages and settings that are used in the Ubuntu image from khodas, maybe you are missing the correct settings.

The order of connected devices is important, the startup works from USB-0 device. If you are using USB hub, try changing the ports where the media with the system is connected. The installation on eMMC works, but in its current form it overwrites u-boot to the test version, which still lacks some of the elements for USB operation from u-boot. I.e. if you install the system, you will lose the ability to run systems from USB. Temporarily, this can be solved - after installing on eMMC, overwrite boot to the previous version (before installing, dd copy of u-boot from eMMC and return it back after installation).

Version 20230216. Added support for automatic fan control.

What exactly is not working ?

The reason is in the power supply. When running with NVMe, it starts to be used intensively and consumption increases. When starting from SD - NVMe, it may be in "hibernation" and there is enough power at the very limit. Try to start intensive data exchange with NVMe when starting from SD, most likely it will turn off.

Please note - DO NOT install on eMMC yet, this mode is not fully ready and tested yet.

MTD = SPI these are new abbreviations , they appeared recently in the installation scripts