balbes150

Because all supported devices from this group strive to have the maximum possible support for media functions.

@Erica I have read your information, but the problem is. that I don't have a working T4 instance for tests. I will try to make a new version of DTB in the coming days, but there are no guarantees that it will work.

I am currently busy preparing the release, all checks will be after the release.

Check this version to work with eDp. Don't change anything, just download, burn to SD card and check eDP operation. I need to figure out if this is going to work or not. https://disk.yandex.ru/d/cN0Nz8Y2RRBpfg

This command is enough to get information about the date of creation of the kernel and its version.

Specify the exact name of the image where there is support.

That's how it should be. While there is no startup interrupt mode (I haven't figured out how it works yet), you will be taken to the EFI menu atomically if there are problems with startup.

Is this when starting with eMMC ? Which ports is the keyboard connected to ?

I am not involved in panfork support. https://github.com/armbian/build/pull/4476#issuecomment-1330101529

Do you have an NVMe module ? It is advisable to check the system startup from all USB ports of the system with EDK2 (if Ubuntu is installed on eMMC, write it to a Debian USB flash drive or vice versa, so that it would be easier to determine which system is starting). After starting the system from USB, update the grub menu in the startup menu, the system on eMMC should appear and then check the selection and launch of systems with eMMC.

Ver 20230129-legacy - image gnome3 and kde5

Ver 20230128-EDK2-EFI for Quartz64-B Added EDK2-EFI support for Quartz64-B,

I checked KD5+wayland, it works well. The interface is fast, there are no freezes on the video when moving the mouse cursor, as on x11. Glmark2 showed more than 400 units. test images from KDE5 on the site.

In the coming days I plan to upload version with Gnome3

PWM causes kernel 6.1\6.2 to panic, so disabled

Added images (kernel 6.2-rc5) from Gnome3. Surprisingly for me (I don't use gnome and built it at the user's request) the interface works well. Glmark2 shows 342 on Station P2. When running glmark2 on XFCE, I get 115-120. Video plays smoothly up to 1440p user@station-p2:~/Desktop$ glmark2 ======================================================= glmark2 2021.02 ======================================================= OpenGL Information GL_VENDOR: Panfrost GL_RENDERER: Mali-G52 r1 (Panfrost) GL_VERSION: 3.1 Mesa 22.0.5 ======================================================= [build] use-vbo=false: FPS: 337 FrameTime: 2.967 ms [build] use-vbo=true: FPS: 349 FrameTime: 2.865 ms [texture] texture-filter=nearest: FPS: 583 FrameTime: 1.715 ms [texture] texture-filter=linear: FPS: 589 FrameTime: 1.698 ms [texture] texture-filter=mipmap: FPS: 595 FrameTime: 1.681 ms [shading] shading=gouraud: FPS: 251 FrameTime: 3.984 ms [shading] shading=blinn-phong-inf: FPS: 252 FrameTime: 3.968 ms [shading] shading=phong: FPS: 244 FrameTime: 4.098 ms [shading] shading=cel: FPS: 249 FrameTime: 4.016 ms [bump] bump-render=high-poly: FPS: 101 FrameTime: 9.901 ms [bump] bump-render=normals: FPS: 662 FrameTime: 1.511 ms [bump] bump-render=height: FPS: 637 FrameTime: 1.570 ms [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 457 FrameTime: 2.188 ms [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 193 FrameTime: 5.181 ms [pulsar] light=false:quads=5:texture=false: FPS: 567 FrameTime: 1.764 ms [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 182 FrameTime: 5.495 ms [desktop] effect=shadow:windows=4: FPS: 526 FrameTime: 1.901 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 85 FrameTime: 11.765 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 84 FrameTime: 11.905 ms [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 72 FrameTime: 13.889 ms [ideas] speed=duration: FPS: 238 FrameTime: 4.202 ms [jellyfish] <default>: FPS: 286 FrameTime: 3.497 ms [terrain] <default>: FPS: 25 FrameTime: 40.000 ms [shadow] <default>: FPS: 166 FrameTime: 6.024 ms [refract] <default>: FPS: 26 FrameTime: 38.462 ms [conditionals] fragment-steps=0:vertex-steps=0: FPS: 445 FrameTime: 2.247 ms [conditionals] fragment-steps=5:vertex-steps=0: FPS: 442 FrameTime: 2.262 ms [conditionals] fragment-steps=0:vertex-steps=5: FPS: 445 FrameTime: 2.247 ms [function] fragment-complexity=low:fragment-steps=5: FPS: 446 FrameTime: 2.242 ms [function] fragment-complexity=medium:fragment-steps=5: FPS: 436 FrameTime: 2.294 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 444 FrameTime: 2.252 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 443 FrameTime: 2.257 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 438 FrameTime: 2.283 ms ======================================================= glmark2 Score: 342 =======================================================

OK. I'll repeat it again with details. Armbian and Radxa images use essentially the same u-boot (in any case, this was the case at the time when I analyzed them). They are assembled from the same sources, so their behavior is the same. My u-boot is significantly different, it is a different source code and configuration, in which errors have been fixed and the configuration has been changed (UART is enabled, the startup order has been fixed, support for PD has been removed, etc.). Therefore, when using a power supply with PD, my version will not work. By the way, I recommend thinking about why radxa disabled the UART console in its u-boot. For the correct launch of my u-boot, you also need to completely erase the SPI, so that its "pieces" do not interfere with the correct launch of the new u-boot from the SD card. For reference, the primary loader (the first stage) is always launched in the strict order of SPI-eMMC-SD polling.

Alpha version 20230124-edge Armbian for Quartz64-B Kernel 6.2-rc5. https://disk.yandex.ru/d/u0ioJbqtXqvJ6w

I explained to you what the problem is and I absolutely don't care what you will use.

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"

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

Alpha version of Armbian images for OrangePi 800. https://disk.yandex.ru/d/3Xta87KhFem-Bw

The first version of Armbian images for Station M3 rk3588s (rk3588s-roc-pc) is available. the launch is very simple - download, unpack, burn to an SD card, connect to the device and turn on the power. The system starts automatically. At the first launch, perform the initial setup in the same way as all Armbian-enabled devices. https://disk.yandex.ru/d/-zSW21XKN0pfIA

Added alpha version of image build support for RISC-V. So far, this is an early version and some of the functions do not work in it. Currently, support has been added for the StarFive model. https://rvspace.org/ Details can be seen in this topic. https://forum.rvspace.org/t/armbian-for-starfive-build-system-ubuntu-debian/468 Added support for Nezha D1 and Lichee RV (Dock) with Allwinner D1 RISC-V chip. To start the system. Download the image, unpack it, burn it to the SD card. Connect the SD card to the device and turn on the power. Further steps for initial setup are similar for all Armbian systems. For the Nezha D1 model, HDMI, LAN, USB, analog audio via 3.5 jack works. For Lichee RV Dock works HDMI WiFi USB USB-LAN Link to download images. https://disk.yandex.ru/d/da8qJ8wyE1hhcQ https://www.cnx-software.com/2021/12/30/sipeed-lichee-rv-risc-v-module-gets-5-carrier-board-with-hdmi-and-usb-ports-optional-wifi/ forum MangoPI https://forum.mangopi.org/

Good news. Thanks to the work of many, there is now a real opportunity to run the Armbian system with the main core on Jetson Nano, and more importantly, it is easy to integrate the image build process into the official GIT Armbian. In the near future, I plan to post ready-made images with the latest kernel 5.10.22 on the download site. To run them, you need to update u-boot to Jetson Nano. This is very easy to do, just run the latest official version of Ubuntu for Jetson Nano from the SD card, it will update itself in SPI (?) u-boot to the latest version (2020.04), after that you can run Armbian from any SD card or USB media. The new u-boot supports automatic system startup from both media or over the network. Also, now you can build an Armbian image for Jetson Nano yourself, easily build the latest kernel with the necessary options, etc. https://users.armbian.com/balbes150/ https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ https://disk.yandex.ru/d/XBRXnig7F1M4rw?w=1