Jump to content

balbes150

Members
  • Posts

    4457
  • Joined

  • Last visited

Everything posted by balbes150

  1. For me, gnome = shit, I don't use it and have no idea what's wrong with it.
  2. Why install something that is not needed???? The correct system check is to record a clean image and carry out all the steps strictly according to the initial instructions, on a completely clean \ new system.
  3. IMHo - all these checks and the "problems" found in patches have no practical use. A practical test of applying a patch to the source code, with a detailed indication of exactly which part of the patch code is not applied. You can see an example in the Libreelec build system. There is a detailed patch overlay log and you can immediately see which piece of patch code is problematic. This is especially true for large patches with a large number of fix points in different places. Now there is a patch overlay log in the build log, and there is only scanty information there, which makes it difficult to understand where the problem is in patches, especially if there are many changes in one file.
  4. Please note that these are packages that he is trying to install into the host system, i.e. these dependencies are written somewhere as mandatory for the host system where the build is launched. The assembly with GIT-Master works fine on the same host system, i.e. all the packages and dependencies necessary for the assembly system to work are already installed and the assembly works without problems. But the NEXT version is trying to install all this extra junk. You can easily reproduce it yourself. Take any ARM device (power and other parameters do not matter), run for example from SD\USB a ready-made Armbian Jammy image for this device and see what happens when you try to start building any image.
  5. Checked the startup using system-boot. Two variants of u-boot with EFI support and EDK2-EFI. I took the original image from u-boot, which includes support for EFI, it is guaranteed to work and the system starts in EFI\grub mode without any problems. With the standard installation of additional kernel with the "apt install" command, the new kernel is automatically added to the grub startup list and works fine without any manual manipulations (I installed 4 kernel to check and checked their launch). Re-recorded launched this image. I uninstalled GRUB and installed system-boot ("bootctl install"), checked that the necessary files were created in the EFI partition and there were no errors during installation. Rebooted the system and ... the system does not start. Conducted similar check with EDK2-EFI. The result is similar, grub works fine and automatically adds the kernel during installation by standard means (without any manual manipulations), allows to select any kernel at startup and runs it perfectly. System-boot behavior with EDK2 - no startup works. I admit that if it takes a long and tedious tinkering with manual settings and commands, can make it work, but the question was about an easy installation by an ordinary user. I pay special attention to the fact that all additional cores are standard DEB packages (from network repositories) with the correct structure and content, which are perfectly installed by standard APT or SYNAPTIC modules without manual manipulation. By the way, I am currently testing the installation on rk3399\rk356x\rk3588 Armbian on eMMC\NVMe in EFI mode (u-boot and EDK2) and it works fine with GRUB.
  6. I tried Jammy in Ubuntu - the package is missing. Further discussion does not make sense. P.S. Installing the kernel root system (kernel-install Balbes-ornery /usr/lib/linux/linux-6.1-balbes150 /usr/lib/linux/initrd) is very bad advice.
  7. The system is a specific version of a full-fledged Armbian system (for example, Debian-22.11-XFCE, Ubuntu 22.08-server, etc.). The kernel is several versions of the kernel installed simultaneously (6.0.10 and 6.0.15 and 6.1.1). Which the user can choose independently at startup. I really want to see how system-boot will "guess" the thoughts of users, which version of the kernel (from the installed 2-3) needs to be launched at a given time. I work with Armbian and it is Armbian support that is being discussed here, so I am absolutely indifferent to "other distributions". Let their developers puzzle over how to work with them. Or are you suggesting that Armbian should pay out of pocket for fun for "other distributions"? "other distributions" too often use ready-made Armbian solutions and get money and bonuses for it. Which the user must manually configure. let "other distributions" deal with this masochism. show simple instructions for regular users for easy installation and automatic configuration for system-boot.
  8. Version 20221224 is EDK2-EFI. EDK2-EFI\grub is used to run. Burn the image simultaneously to two media - an SD card and a USB flash drive.After recording, connect the SD card and USB flash drive at the same time. If you have a UART console, you can control the startup process.
  9. How does it make it difficult to manage multiple systems\cores? On the contrary, a single control point, you add any number of systems, cores. The only limitation is that to use the selection, you need support for monitor output and USB for u-boot. For rk3399 - it is implemented. Everything written is wrong. grub does an excellent job with the AUTOMATIC (no manual manipulation needed) addition of a new kernel when installing it, supports all standard functions, as on regular PCs, and so on. excessively complex and poorly supported in Debian\Ubuntu systems, it is not widespread even on PCs.
  10. I looked at the table by the link. I don't understand what practical use it is? "No description of mbox" - has no use. "rebase" - it is not clear why. the rest of the items are the same. does not do the main thing - does not check the error when using patches https://rpardini.github.io/linux/armbian-next-media-6.1-20221220.html
  11. I tried armbian-next to run a native build (on an ARM device), and got errors. Why is a bunch of unnecessary shit being put on ARM (snap, gcc-riscv, etc.)? 👉] Reading package lists... [👉] Building dependency tree... [👉] Reading state information... [👉] Package ccze is not available, but is referred to by another package. [👉] This may mean that the package is missing, has been obsoleted, or [👉] is only available from another source [👉] Package python3-pip is not available, but is referred to by another package. [👉] This may mean that the package is missing, has been obsoleted, or [👉] is only available from another source [👉] Package distcc is not available, but is referred to by another package. [👉] This may mean that the package is missing, has been obsoleted, or [👉] is only available from another source [👉] No apt package "axel", but there is a snap with that name. [👉] Try "snap install axel" [👉] No apt package "tree", but there is a snap with that name. [👉] Try "snap install tree" [👉] E: Package 'distcc' has no installation candidate [👉] E: Package 'python3-pip' has no installation candidate [👉] E: Unable to locate package python2-dev [👉] E: Package 'ccze' has no installation candidate [👉] E: Unable to locate package colorized-logs [👉] E: Unable to locate package tree [👉] E: Unable to locate package pbzip2 [👉] E: Unable to locate package axel [👉] E: Unable to locate package crossbuild-essential-armel [👉] E: Unable to locate package crossbuild-essential-amd64 [👉] E: Unable to locate package gcc-riscv64-linux-gnu [👉] --> 🧽 78: 3365 - 3365 - 3365: hBE: trap: main_trap_handler [ ERR and 100 trap_manager_error_handled: short_stack:/home/user/armbian-build-next/lib/functions/logging/runners.sh:186 ] [💥] 👆👆👆 Showing logfile above 👆👆👆 [ /home/user/armbian-build-next/.tmp/logs-599221b8-4094-41cf-af68-4d18190ab396/004.000.prepare_host.log ] [💥] Error occurred in main shell [ code 100 at /home/user/armbian-build-next/lib/functions/logging/runners.sh:186 run_host_command_logged_raw() --> ./lib/functions/logging/runners.sh:186 run_host_command_logged() --> ./lib/functions/logging/runners.sh:169 host_apt_get() --> ./lib/functions/logging/runners.sh:139 host_apt_get_install() --> ./lib/functions/logging/runners.sh:132 install_host_side_packages() --> ./lib/functions/host/host-utils.sh:60 install_host_dependencies() --> ./lib/functions/host/prepare-host.sh:291 prepare_host() --> ./lib/functions/host/prepare-host.sh:111 do_with_logging() --> ./lib/functions/logging/logging.sh:112 main_default_build_single() --> ./lib/functions/main/default-build.sh:27 cli_standard_build_run() --> ./lib/functions/cli/cli-build.sh:16 armbian_cli_run_command() --> ./lib/functions/cli/utils-cli.sh:121 cli_entrypoint() --> ./lib/functions/cli/entrypoint.sh:154 main() --> ./compile.sh:52
  12. Version 20221222 is EDK-EFI. The launch from USB media works (all ports work). The order of launching this version. Burn the same image to two media at once - an SD card and a USB flash drive. Connect both media SD card and USB flash drive and turn on the power. The system starts automatically from a USB flash drive (the SD card is used as a carrier for the EDK2-EFI\grub bootloader). If you have a UART console, you can control the process of starting and selecting the system\kernel. Please note that the system startup speed from USB can take up to 10-30 seconds (before the image appears on the monitor). Important. If the correct u-boot version is installed in SPI and there is a configured working system on NVMe, the new version of the system allows you to check the operation of the system in EDK2-EFI\grub mode from external media (SD+USB) without affecting the working system on NVMe.
  13. No, initially there was an attempt to use the normal version (extlinux.conf) for rock 5b, but under the pressure of retrogrades, there was a rollback to this old stuff. Odroid is the stupidest choice and obsession with all sorts of old shit (boot.ini, piteboot). rk35xx (rk356x rk3588) - should initially focus on normal, new versions of startup systems (EFI\Grub). For rk356x - EDK2 has been available for a long time with a choice of system\kernel on the screen (for the headless option, this also works fine). For rk3588 - test versions are already available and in the coming weeks \ month there will be a working version with monitor support. With whom and what to discuss if retrogrades don't even understand how extlinux or efi\grub works and squeal at every corner that these are "very bad decisions"? At the same time, they do not understand elementary things - that switching at least to extlinux gives a huge step forward and allows you to atomize the installation of several cores at the same time (it is not necessary to make a choice of the core on the screen, it is important to keep the ability to easily roll back to the primary core if the new one has problems). Try using boot.scr to implement two\three\N cores installed in the system at the same time. When using boot.scr - updating the system\kernel, this is a lottery, with a high probability of getting a serious problem (strictly there is no kernel anymore. and the new one is not working).
  14. Using boot.scr is initially a bad idea. This old junk has been "obsolete" for a long time and it's time to get rid of it. Changing boot.scr - you will not solve the problem, it is only a disguise laying a time bomb.
  15. And now try to start the system from the SD card (imitation of problems with updating the kernel and you need a recovery system from an external media).
  16. 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"
  17. 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
  18. Alpha version of Armbian images for OrangePi 800. https://disk.yandex.ru/d/3Xta87KhFem-Bw
  19. 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
  20. 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/
  21. 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
  22. New version ArmbianTV of images for RK3288 and RK3188. rk3288 \ rk3188 https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ rk3188 https://disk.yandex.ru/d/7wqSh5Z5bv9q1g?w=1 rk3288 https://disk.yandex.ru/d/fRZwre9HDgAKHw?w=1 This link contains images with Libreelec for rk3288 and rk3188, testing these images can help with the development of media functions for rk3288 and rk3188. https://disk.yandex.ru/d/8vNYuuxynz1L0w?w=1
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines