-
Posts
4457 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by balbes150
-
ver current (kernel 6.2) work HDMi
-
Show the full UART log, only there you can see real startup errors. How do you do the installation on NVMe ? To do this, you need to use only armbian-config, do not do any manual copying. This option will not work with kernel 6.2 (pancsfc). panfork only works with Jammy If you use a barrel (5.5x2.1) to USB-C adapter with a conventional power supply 12v-3\4A (without PD), this is enough.
-
1. Completely erase MTD\SPI from all old versions. If you tried to use the versions from radxa or the official armbian, it will not work correctly. 2. Run the latest legacy version (5.10.110) of this theme from the SD card and completely erase the NVMe. 3. Using a power supply without PD. 4. Only after completing all the previous steps, start the system from the SD card, create a partition on NVMe with EXT4 and run the installation on NVMe+MTD.
-
Please add support for FireFly ITX-3588J
balbes150 replied to BillFleming's topic in Framework and userspace feature requests
I hope there will be working versions for this model soon. -
ver 20230428-EDK2-EFI kernel legacy and current
-
where is the system installed ? If on USB\SD, you can connect the media to the PC and open the log file and see the full output (/var/log) and find the reason that causes the kernel to panic. If the system is on SATA\NVMe - start the system from SD\USB media, mount SATA\NVMe and see the same logs.
-
What kind of core panic are you writing about ? I don't see any messages about legacy kernel panic.
-
add image XFCE and Gnome3 kernel 5.10.110
-
add image XFCE and Gnome3 kernel 5.10.110
-
ver 20230427-EDK2-EFI-current kernel 6.2 ( work HDMI USB LAN etc )
-
Why such difficulties ? Just use normal images in which the NVMe + MTD installation works correctly via armbian-install.
-
ver 20230426-EDK2-EFI-edge kernel 6.3 (HDMI not work)
-
ver 20230426-EDK2-EFI-edge kernel 6.3 (HDMI not work)
-
Try. Starting from an SD card does not affect the installed system (if you yourself do not manually run special procedures for installing\replacing the system on NVMe\MTD). If you are lucky and your current u-boot is able to work with normal systems, the system will work from an SD card.
-
All the sources from which these images are assembled (including the kernel) are freely available in my git. The images from this topic are not related to the current official build system (the new official build system is broken).
-
you are trying to install the system with EDK2 - these images do not yet have an installation on NVMe, running only from external media (SD USB). To install on NVMe, you can use images from directories on the site without specifying EDK2. Direct recording of the entire image on NVMe is a bad practice imposed by ignoramuses who do not know how to properly assemble a system with a normal installation through the armbian-config\armbian-install script. All images from this theme (except versions with EDK2) have a normal installation procedure on NVMe. Use the appropriate images. Do not install the loader version from the EDK2 image in MTD\SPI, this loader only works with images collected in UEFI mode and does not work with extlinux.con mode, which is used in other images.
-
An SD card with a working system (with a working u-boot) must be installed in the device. Closing contacts only blocks the launch of u-boot from SPI (switches the launch to the SD card) and does not change anything \ does not erase in SPI. Cleaning SPI\MTD is performed from the system running from the SD card.
-
Try replacing DTB with this option. https://disk.yandex.ru/d/D5Xnjz_ciB_nvQ no
-
Version 20230401 with kernel 6.2 (pancsf-midstream). With HDMI USB support. https://disk.yandex.ru/d/W8pOOhizVjq91A To enable HW acceleration, install the mesa package with the forced overwrite option or an archive to enable acceleration for wayland. To enable wayland acceleration, you need to replace the files in the /usr/lib/aarch64-linux-gnu directory with the contents of the archive (with file replacement). After that, acceleration will work with wayland. X11 and wayland acceleration works the same way on Debian Sid (the images are the same as Ubuntu). After starting the system and initial configuration, replace the files from the archive in the same way and acceleration will work. The results of running in Debian Sid Gnome for x11 and wayland. dpkg -i --force-overwrite mesa_23.0.0-dev-2_arm64.deb After installation and reboot, HW acceleration will work in x11 and wayland. Please note, this is a test version of mesa for the initial evaluation of the work, some of the functions do not work in it and there may be bugs. With x11, the system works more stably, but the test results are lower than in gnome+wayland. deb\archive https://disk.yandex.ru/d/h8c-Y2FfAvx76g
-
Version 20230325-edge with kernel 6.2 (pancsf-midstream). With HDMI USB LAN support. https://disk.yandex.ru/d/Xt36QdVcxRdEDA
-
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
- 8 replies
-
- Station M2
- Station P2
-
(and 1 more)
Tagged with:
-
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/
- 189 replies
-
2
-
- MangoPi MQ Pro
- Sipeed Nezha
-
(and 1 more)
Tagged with:
