balbes150

@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

By the way, when installing panfork on a system with DE running x11 (XFCE\KDE5\Mate etc), support for HW appears. The result of the glmark2 test on x11 with XFCE is approximately 1100 parrots.

These are the test results for Khadash EDGE 2 with performance mode enabled in XFCE with panfork - 1092 parrot installed. Below is a link to the general test from the @tkaiser page I'm not a test specialist, so I don't know how well the test went. http://ix.io/4nUy @NicoD Version 20230213 . added support for Wi-fi. I don't use Wi-Fi, can you check if it works or not?

Yes. To use Name, start the system from the SD card and perform the installation using arm bin-config (use the SPI + NVMe\SATA installation option). Please note - my version does NOT support PD power supplies

@NicoDVersion 20230211 Armbian for khadas edge2 - added support for HW 3D . The result of gnome3+wayland+arm-blob gave about 3800 parrots. For details on how to install HW and testing, see this topic.

Version 20230209 with kernel 5.10.110 with added HW support. Test results. [function] fragment-complexity=medium:fragment-steps=5: FPS: 4379 FrameTime: 0.228 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 4636 FrameTime: 0.216 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 4973 FrameTime: 0.201 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 4869 FrameTime: 0.205 ms ======================================================= glmark2 Score: 3851 ======================================================= user@rock-5b:~$ PAN_MESA_DEBUG=gofaster glmark2-es2-wayland arm_release_ver of this libmali is 'g6p0-01eac0', rk_so_ver is '6'. arm_release_ver of this libmali is 'g6p0-01eac0', rk_so_ver is '6'. ======================================================= glmark2 2021.02 ======================================================= OpenGL Information GL_VENDOR: ARM GL_RENDERER: Mali-LODX GL_VERSION: OpenGL ES 3.2 v1.g6p0-01eac0.ba52c908d926792b8f5fe28f383a2b03 ======================================================= [build] use-vbo=false: FPS: 4336 FrameTime: 0.231 ms [build] use-vbo=true: FPS: 4783 FrameTime: 0.209 ms [texture] texture-filter=nearest: FPS: 4729 FrameTime: 0.211 ms [texture] texture-filter=linear: FPS: 5175 FrameTime: 0.193 ms [texture] texture-filter=mipmap: FPS: 5091 FrameTime: 0.196 ms [shading] shading=gouraud: FPS: 4258 FrameTime: 0.235 ms [shading] shading=blinn-phong-inf: FPS: 4404 FrameTime: 0.227 ms [shading] shading=phong: FPS: 3972 FrameTime: 0.252 ms [shading] shading=cel: FPS: 4183 FrameTime: 0.239 ms [bump] bump-render=high-poly: FPS: 2528 FrameTime: 0.396 ms [bump] bump-render=normals: FPS: 5949 FrameTime: 0.168 ms [bump] bump-render=height: FPS: 6005 FrameTime: 0.167 ms [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 4548 FrameTime: 0.220 ms [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 3866 FrameTime: 0.259 ms [pulsar] light=false:quads=5:texture=false: FPS: 5457 FrameTime: 0.183 ms [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 1829 FrameTime: 0.547 ms [desktop] effect=shadow:windows=4: FPS: 4512 FrameTime: 0.222 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 528 FrameTime: 1.894 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 495 FrameTime: 2.020 ms [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 817 FrameTime: 1.224 ms [ideas] speed=duration: FPS: 2543 FrameTime: 0.393 ms [jellyfish] <default>: FPS: 3489 FrameTime: 0.287 ms [terrain] <default>: FPS: 299 FrameTime: 3.344 ms [shadow] <default>: FPS: 3963 FrameTime: 0.252 ms [refract] <default>: FPS: 633 FrameTime: 1.580 ms [conditionals] fragment-steps=0:vertex-steps=0: FPS: 4990 FrameTime: 0.200 ms [conditionals] fragment-steps=5:vertex-steps=0: FPS: 4897 FrameTime: 0.204 ms [conditionals] fragment-steps=0:vertex-steps=5: FPS: 4423 FrameTime: 0.226 ms [function] fragment-complexity=low:fragment-steps=5: FPS: 4529 FrameTime: 0.221 ms [function] fragment-complexity=medium:fragment-steps=5: FPS: 4752 FrameTime: 0.210 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 4532 FrameTime: 0.221 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 4175 FrameTime: 0.240 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 4724 FrameTime: 0.212 ms ======================================================= glmark2 Score: 3800 ======================================================= For details of the new features, see this topic. https://forum.armbian.com/topic/22986-firefly-station-m3-rk3588s/?do=findComment&comment=159554

Version 20230208 kernel 5.10.110. The kernel configuration has changed, driver support has been added to install additional packages with HW 3D support (ARM blobs and panfork). When testing different variants on Station M3, the results were obtained. steps to run HW with the latest images When using DE with x11 (KDE5 XFCE + mesa-panfork) - glmark2 shows about 1100 parrots. sudo add-apt-repository ppa:liujianfeng1994/panfork-mesa sudo apt dist-upgrade reboot When using gnome3+ARM bob, glmark2-es2-wayland showed about 4,400 parrots. download https://github.com/numbqq/mali-debs/blob/master/jammy/arm64/Edge2/wayland/linux-gpu-mali-wayland_1.0-g610-20220510_arm64.deb and install it into the system with the command : sudo dpkg -i --force-overwrite linux-gpu-mali-wayland_1.0-g610-20220510_arm64.deb reboot First of all, I was interested in running KDE5 + wayland, but checking both options (ARM blobs or panfork) did not give results, the GUI does not run in wayland mode, although when using the main kernel + panfrost on rk33xx rk356x, KDE5+wayland works well. surprisingly, even the weakest system (station m1 rk3328 with 1 GB of RAM) was able to work acceptably even with 1920 x 1080 desktop settings (plays full-screen video). Running panfork on gnome 3 + wayland didn't work, I think I made some mistakes, but gnome 3 doesn't interest me, so I didn't waste time on it. Add info steps to run HW with the latest images.

By default, wayland is enabled, you need to switch to x11 or use XFCE.

Ask the Firefly manufacturer.

Alpha version of Armbian for Khades EDGE 2 (rk3588s). Launch. Download, unpack, burn to USB media (you can use an SD card if there is an additional module with a card reader for an SD card). Connect to any USB port on EDGE 2 and turn on the power. The system starts automatically. It would be interesting to run tests on this version. I pay attention - there is no 3D acceleration yet, general performance tests for the Armbian image are interesting. Wi-Fi is not working yet, need to use USB-LAN, this will be fixed in future versions. https://disk.yandex.ru/d/QMgdvGqF3jpgJw

Read carefully - only LAN works on the EDGE version, HDMI does not work.