balbes150

  • Posts

    3567
  • Joined

  • Last visited

Reputation Activity

  1. Like
    balbes150 got a reaction from NicoD in Board Bring Up Station P1 rk3399, M1 rk3328   
    new version of Armbian  20210614 with core 5.10.43.
    Added support for analog audio and a standard remote control.
  2. Like
    balbes150 got a reaction from Werner in Board Bring Up Station P1 rk3399, M1 rk3328   
    new version of Armbian  20210614 with core 5.10.43.
    Added support for analog audio and a standard remote control.
  3. Like
    balbes150 got a reaction from ghoul in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    The start system in Coreelec is not compatible with LibreELECE  Armbian  etc. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems.
     
    Questions that do not specify exact details (the exact image version, TV box model, detailed steps that were performed for DTB settings, and so on) will be ignored and deleted.
     
    For all. I don't support s905x3. I don't have this equipment. All messages about this platform deleted. What works or doesn't work from this equipment - I don't know. I do not give any answers or comments on the s905x3 chip.
     
    The build and publication of unified test images with a common core for the Rockchip Amlogic Allwinner platform begins.
     
    Y-disk
    https://yadi.sk/d/_rQgn_FosYuW0g
     
    MEGA
    https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
     
    Now you can download the latest versions of images and DEB packages from the official Armbian resource via the link. 
    https://users.armbian.com/balbes150/
     
     
    *********************************************************************************************************************************
    Pay attention. Starting from version 20.08 (20200814), the configuration order for the used DTB changes.
     
    Please note that the algorithm for initial configuration of the system for startup has changed. Instead of a file "uEnv.txt", the file "/extlinux/extlinux.conf " is now used. The rules for editing a file remain the same.
    All Amlogic models now need the "u-boot.ext" file.
    Before launching on Amlogic, you must copy or rename one of the existing files "u-boot-*" to "u-boot.ext".
     
    For s905 (not X) - used u-boot-s905
    For s905x and s912 - used u-boot-s905x-s912
    For s905x2 and s922 - used u-boot-s905x2-s922
     
    For g12a\g12b models, a single file is now used (files u-boot.sd and u-boot.usb now replaces one u-boot-s922 file).
    For the Allwinner platform, you no longer need to rename the scripts "boot.scr".
    All "boot.scr" scripts have been canceled and are not used.
     
    *************************************************************************************************************************************
     
    How to run these images on the Amlogic platform .
    Now all images Armbian and LE has all the files for activate the multi-boot. Anything addition to download and copy to media is not required.
     
    1. Download the image for your device
    2. Unpack
    3. Burn the image on the medium
    4. Configure in the file (uEnv.txt) launch parameters for the desired platform and model (uncomment the desired lines and comment out or delete unused ones)
     
    If universal multi-upload has not yet been activated on this device, you need to activate it once. There are several options for activating multi-loading.
     
    option A
    - Connect the prepared media to the device and turn on the power, boot into Android
    - Open the app "Update&Backup"
    - Click on "Select" local update and chose the file on the removable media aml_autoscript.zip
    - Start "Update"
    - System will reboot twice and start running the system from external media.
     
    option B
    -  try using the "toothpick method"
     
     
    How to run these images on the Rockchip and Allwinner platform .
    1. Download the image for your device
    2. Unpack
    3. Burn the image on the medium
    4. Configure in the file (uEnv.txt) launch parameters for the desired platform and model (uncomment the desired lines and comment out or delete unused ones)
    5. If your device does not support USB startup , you can only use SD cards and you need to add the correct u-boot to the SD card (for details on how to add it, see the text of this message)
    6. Connect the prepared media to the device and turn on the power
     
    Please note that the DTB configuration order has changed.
    Now a single configuration method is used for all Rockchip Allwinner Amlogic platforms. The file (uEnv.txt) is used for configuration DTB all platforms. 
    Now a single configuration method is used for all platforms, using the file (uEnv.txt). You need to edit this file to configure it. You need to uncomment the two lines that are responsible for your platform and specify the correct DTB for your model. If you use this image to run on the one platform, you can delete it from the settings file (uEnv.txt) strings from other platforms.
     
    Need to pick up the option for the file system will run. Pay attention, after you add\change the dtb file, you need to try to run the system and waiting to run 7-10 minutes. If not happened, repeat with a different dtb file.
     
    Pay attention.
    The installation algorithm in eMMC has changed. My recommend that you perform a clean installation in eMMC. Be sure to make a full backup of eMMC before installing it in eMMC.
    The system installation scripts in eMMC have changed accordingly. If you have a system with eMMC core 5 installed on RK33xx, it is advisable to perform a clean installation in eMMC to upgrade to the new version. 
     
    For the aw H6 platform, all scripts are already in the image (which have the ending aw). You need to rename the files with the replacement (remove the ".aw" ending).
     
    Fix for correct color to G12 (Amlogic S905X2 S922X)
    For models based on g12 (s905x2 s922), which have a problem not the correct color , 
    If you are starting the system from an SD card, you need to copy file  u-boot.sd to u-boot.ext,
    If you are starting the system from an USB, you need to copy file  u-boot.usb to u-boot.ext
    When installing in eMMC, you do not need to do anything with your hands, the installation script itself will perform the necessary system configuration and when running from eMMC, the system will work with the correct color.
     
    Please note, this version for the transition to the release of a single image for the platform Rockchip + Amlogic + Allwinner. The new image after writing to external media and after configuring the used dtb (and if necessary adding the desired u-boot option to run from the SD card on the Rockchip and Allwinner) can be used simultaneously on AML (s9xxx), RK (rk3399 and rk3328) and AW (H6). If the TV boxes RK (rk3328 and rk3399) and AW (H6) in eMMC installed a new version of u-boot  with support for starting the system with USB, adding u-boot to SD card is not required, the system will automatically start on with USB.
     
    Important change. With this version (>= 20200218), you can easily add the desired u-boot on any PC (including Windows) .
     
    To do this, new versions of u-boot are downloaded on the site.
     
    https://yadi.sk/d/lTbXkrmZN5Hf6g
     
    Rules for using the new u-boot option. Download, Armbian image, unpack. Write image Armbian to the SD card. Download and write the desired version of the u-boot file to SD card. Configure the DTB and the launch string (APPEND) in (uEnv.txt) for the desired model\platform.
     
    Pay attention. Now you don't need to write u-boot with complex commands, you write the u-boot image with the same program as you usually write an Armbian image. This allows you to configure the system to run (including writing a u-boot image) on any PC (including Windows).
     
    Pay attention. The new version changed the size of the partitions that are obtained when writing an image (all images have a fixed size of 5GB).  This u-boot entry option only applies to the new version 20200218 and subsequent versions. Don't try this for old images. This will not work on older images.
     
    OLD add u-boot
     
     
     
    For RK33xx
    if you have windows and can't use the add u-boot commands to the SD card, use the SD+USB combination , write only the new u-boot to the SD card, and write the Armbian image to a USB storage device. And connect them together to the TV box.
     
    To turn on the sound on models AML
    where it is not present after the initial start. To enable audio , run the script (sound.sh).  You need to run the script
     
    sudo sound.sh
     
     
     
    Odroid N2
    When starting from an SD card on Odroid N2, you must, after recording the image, write uboot to the SD card, configure uEnv.txt, additionally rename the script (boot.scr.aw) in (boot.scr). To be able to start any system from any media (USB SD eMMC), i'm recommend using the updated version of u-boot-SPI. Details about u-boot-SPI for Odroid N2 can be found here.
     
     
     
     
  4. Like
    balbes150 got a reaction from ghoul in Armbian for TV box rk3328   
    A test version of the image Armbian for TV boxes on the basis of RK3328. Tested on MVR9
    http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/653167-bqeel-mvr9-rk3328-quad-core-64bit-cortex-a53-android-7-2-16gb-2-4ghz-wifi-bt4
     
    All basic functions work. For running. Download. Unpack. To record on the SD card. Connect the SD card to TV box, connect a keyboard and mouse. To turn the power on the TV box. The system should start within 2-3 minutes. You must perform the initial configuration of Armbian.

    https://yadi.sk/d/DSO6euzB3ahemo
     
    https://mega.nz/#F!zoZywCTQ!9sNfXIAB3m_DyLl5I8P94w
     
    The system of choosing the correct dtb has changed.
    Please note, now it should be done on a different principle (files do not need to be copied).
    To select the desired dtb, you need to change the line in the text file "/extlinux/extlinux.conf". In the line "FDT" you need to change the name of the file that the system will use at startup. The list of available files (names to specify in the configuration) can be found in the "dtb"directory. If you do not know exactly what file you need , you can enter all available names in turn and check the operation of the system. In accordance with this, the system installation script in eMMC has been changed. The steps to install the system on the eMMC remain the same.
     
    Added a utility to full backup and restore the entire eMMC "ddbr". Checked mode the backup MVR9. Now if you try to check the recovery mode.
     
    The order of installation in eMMC.
     
    1. Download, unzip and burn the image to SD card.
    2. Start Armbian on the TV box and perform the initial setup of the system.
    3. If the system works correctly and you are satisfied, run the utility "ddbr" and create a full backup of eMMC (this is a prerequisite).
    4. Rename the file "/boot/mvr9-uboot.img" in "/boot/uboot.img".
    5. Run as user "root" script "/boot/create-mbr-linux.sh"
    6. To run the script "/root/install.sh"
     
    Pay attention to the correct operation of the installation procedure need to comply strictly with the order of the steps.
  5. Like
    balbes150 got a reaction from ghoul in RK3288 and RK3188   
    New version ArmbianTV of images for RK3288 and RK3188.
     
     
    rk3288 \ rk3188
     
    https://users.armbian.com/balbes150/
     
    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
  6. Like
    balbes150 got a reaction from ghoul in Allwinner H6   
    New Image 20210123 for H6, kernel 5.10.9
     
    https://yadi.sk/d/0a41swJcEAZ0SQ?w=1
     
     
    https://mega.nz/folder/j9QSDQSQ#6WpasOlbZYIInfw6yo4phQ/folder/K9BRjSaZ
  7. Like
    balbes150 reacted to Igor in overlayroot not working as expected   
    If you have bisected my previous replies you would also notice one important information: "we are running with 1/1000 of needed resources". But since you only care about yourself and how to abuse this service to solve your expensive technical case without helping us, you didn't.
     
    Also laziness is something I don't support and have no intention to hide that. If you are lazy and seek for my attention it is your gamble to be treated bad. Have you ever thought this might be taken as an insult?
     
     
    This is not a commercial support service and you are not a client. We pay for this support and it is our gift to you. 99% of questions on this forum has nothing to do with our work so it has no moral relationship to give you support. And in best effort manner. This is my best effort. I don't have time for a betrer one.
     
    Sadly support burden is extreme, while you totally don't care about that. Why should we care? I was very polite and professional in the past, just to see if that change anything. You were more satisfied, absolutely, but the negative impact on our side was even more extreme and I could get insane spending too much time "with my clients" that just takes and give nothing and are even spreading BS like you do.
     
    Your duty is that people that helps (we) feel alright. Not the other way around.
     
    you have to be careful not to waste our time, attention and stress us out by asking questions which were already asked on our expense, you have to be careful not to waste our time, attention and stress us out by asking questions that has nothing to do with our work on our expense, you have to be careful not to waste our time, attention and stress us out by asking questions without supplying any logs on our expense, you have to be careful not to waste our time, attention and stress us out by demanding support on our expense, you have to be careful not to demand from us to fix something for you on our expense, you have to be careful not to demand from us to develop something for you on our expense, you have to be careful not to open stupid replies like this since its your attitude that has to be changed, you don't insult and stress us with your unnecessary questions, you have to check if you can help us prior to asking for help on our expense, you can get at a subscription to show you are not yet another gift abuser on our expense.  
    Check forum rules for more. We invest a lot of our time to provide you a ground for communication without insulting us, but you never read it since you don't care. Its all about your problem. Which I totally don't care about - if that is my personal expense daling with - if you pay, I will make an exception. I only care about our common problems. Once we rule them out, many people can't complain about them anymore ....
     

    After you.
     
     
    Providing polite answer is extremly time consuming (i lost 100 EUR for this polite answer too you and I am sure you will never pay me back) and it can create us much more damage then short answer like this one - with a valuable hint. I don't have intention to chat or make "friendship" with my "clients". 365 day in a year * +10 hours is something I could easily lost if going the suicidal route you recommend. I tried that, but the negative impact is too extreme.
     
    Get some reality touch before giving advices.
  8. Like
    balbes150 reacted to JMCC in What is the best 64bit low cost processor?   
    You must take into account not only the processor specs, but also the kernel support. I would stay away from Amlogic for that reason, and bring in Rockchip into the equation.
  9. Like
    balbes150 got a reaction from gounthar in Jetson Nano   
    Version 20210513. Fixed startup with Legacy kernel, now these images work correctly.
  10. Like
    balbes150 got a reaction from manuti in Armbian for TV box rk3328   
    A test version of the image Armbian for TV boxes on the basis of RK3328. Tested on MVR9
    http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/653167-bqeel-mvr9-rk3328-quad-core-64bit-cortex-a53-android-7-2-16gb-2-4ghz-wifi-bt4
     
    All basic functions work. For running. Download. Unpack. To record on the SD card. Connect the SD card to TV box, connect a keyboard and mouse. To turn the power on the TV box. The system should start within 2-3 minutes. You must perform the initial configuration of Armbian.

    https://yadi.sk/d/DSO6euzB3ahemo
     
    https://mega.nz/#F!zoZywCTQ!9sNfXIAB3m_DyLl5I8P94w
     
    The system of choosing the correct dtb has changed.
    Please note, now it should be done on a different principle (files do not need to be copied).
    To select the desired dtb, you need to change the line in the text file "/extlinux/extlinux.conf". In the line "FDT" you need to change the name of the file that the system will use at startup. The list of available files (names to specify in the configuration) can be found in the "dtb"directory. If you do not know exactly what file you need , you can enter all available names in turn and check the operation of the system. In accordance with this, the system installation script in eMMC has been changed. The steps to install the system on the eMMC remain the same.
     
    Added a utility to full backup and restore the entire eMMC "ddbr". Checked mode the backup MVR9. Now if you try to check the recovery mode.
     
    The order of installation in eMMC.
     
    1. Download, unzip and burn the image to SD card.
    2. Start Armbian on the TV box and perform the initial setup of the system.
    3. If the system works correctly and you are satisfied, run the utility "ddbr" and create a full backup of eMMC (this is a prerequisite).
    4. Rename the file "/boot/mvr9-uboot.img" in "/boot/uboot.img".
    5. Run as user "root" script "/boot/create-mbr-linux.sh"
    6. To run the script "/root/install.sh"
     
    Pay attention to the correct operation of the installation procedure need to comply strictly with the order of the steps.
  11. Like
    balbes150 reacted to Werner in Video : How to install OMV on Armbian Buster and set up a SMB share with it   
    Due to the insane amount of detail you gave with your error description it will take quite a while to sort things out.
  12. Like
    balbes150 reacted to JMCC in RK3288/RK3328 Legacy Multimedia Framework   
    Sorry, I was away. I'll try to fix it ASAP
  13. Like
    balbes150 reacted to lanefu in Armbian v21.05 (Jerboa) Release Thread   
    Congratulations!   Are you marrying S905X?    
  14. Like
    balbes150 reacted to lanefu in Armbian v21.05 (Jerboa) Release Thread   
    Hi! reminding everyone of meeting
     
     
  15. Like
    balbes150 reacted to Igor in Unable to boot 'focal' or 'buster' images on SOPine Clusterboard   
    That is correct. Support: https://docs.armbian.com/#what-is-supported creates costs which are 99% covered by us, which means it will wait for a free slot. This can be stretched from days to years. You have to understand that this vendor never covered us a single minute for supporting troubles their customers have by using (one if not the best available) OS for their hardware. Nor "you" see and feel the necessity to cover support costs you make. Since none of you see value in getting help, there is no warranty we will fix this and you might need to wait months ... 
     
    Workaround = use old builds.
  16. Like
    balbes150 reacted to JMCC in RK3288/RK3328 Legacy Multimedia Framework   
    Search the forums. Don't expect official documents: as we have stated several times, Rock64 is not supported by Armbian, and therefore we won't put resources into it. If you, or any other community member, wants to work on documenting the problems or fixing them, feel free to do it. I don't even own the board.
     
    And please start a different thread on the "Peer-to-Peer Support" subforum. Any further post about the Rock64 problems will be deleted from this thread.
  17. Like
    balbes150 got a reaction from TRS-80 in So, I bought a PinePhone :) (I used to be, well still am in fact, a Librem 5 guy)   
    I'm just starting to get into the specifics of Allwinner, so my interests in this area are limited to H6 and H5 (in the future, H616). A year ago, I was interested in the possibility of acquiring PinePhone and PinebucPro, but due to the peculiarities of delivery in my area, Pine64 politely explained that this is not possible (I have no complaints about them, this is their business, they decide how to run it).
  18. Like
    balbes150 got a reaction from NicoD in Board Bring Up Station P1 rk3399, M1 rk3328   
    Update to version 20210319. Using kernel 5.10.24. Added support for Firefly-rk3399 in station-p1 images (for proper operation, you need to configure DTB in extlinux.conf). With the correct DTB setup, the HDMI audio LAN WiFi BT works in kernel 5.10. In kernel 4.4 worck remote control and analog sound. 
  19. Like
    balbes150 got a reaction from gounthar in Board Bring Up Station P1 rk3399, M1 rk3328   
    Update to version 20210319. Using kernel 5.10.24. Added support for Firefly-rk3399 in station-p1 images (for proper operation, you need to configure DTB in extlinux.conf). With the correct DTB setup, the HDMI audio LAN WiFi BT works in kernel 5.10. In kernel 4.4 worck remote control and analog sound. 
  20. Like
    balbes150 got a reaction from Werner in Board Bring Up Station P1 rk3399, M1 rk3328   
    Update to version 20210319. Using kernel 5.10.24. Added support for Firefly-rk3399 in station-p1 images (for proper operation, you need to configure DTB in extlinux.conf). With the correct DTB setup, the HDMI audio LAN WiFi BT works in kernel 5.10. In kernel 4.4 worck remote control and analog sound. 
  21. Like
    balbes150 got a reaction from manuti in Jetson Nano   
    New version of Armbian 20210311.
    Based on the main core 5.10.23.
    Now anyone can build their own version of Armbian for Jetson Nano without an external PC, the entire process is completely performed on the Jetson Nano itself.

     
  22. Like
    balbes150 got a reaction from manuti in Jetson Nano   
    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
  23. Like
    balbes150 got a reaction from guidol in Jetson Nano   
    New version of Armbian 20210311.
    Based on the main core 5.10.23.
    Now anyone can build their own version of Armbian for Jetson Nano without an external PC, the entire process is completely performed on the Jetson Nano itself.

     
  24. Like
    balbes150 got a reaction from Igor in Jetson Nano   
    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
  25. Like
    balbes150 got a reaction from NicoD in Review videos : NVIDIA Jetson Nano   
    Good news. You can now use the main core to run on Jetson Nano. I have already added the necessary data to the build system and you can build an image for Jetson Nano using the official sources of the main core.
     
     
    U-Boot 2020.04-g6b630d64fd (Feb 19 2021 - 08:37:46 -0800) SoC: tegra210 Model: NVIDIA Jetson Nano Developer Kit Board: NVIDIA P3450-0000 DRAM: 4 GiB MMC: sdhci@700b0000: 1, sdhci@700b0600: 0 Loading Environment from SPI Flash... SF: Detected mx25u3235f with page size 256 Bytes, erase size 4 KiB, total 4 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 338 bytes read in 22 ms (14.6 KiB/s) 1: Armbian Retrieving file: /boot/uInitrd 11330177 bytes read in 512 ms (21.1 MiB/s) Retrieving file: /boot/Image 31306240 bytes read in 1364 ms (21.9 MiB/s) append: root=UUID=de820d8a-ca8e-4b1a-8e96-ce586b2422f3 console=ttyS0,115200 console=tty0 rootflags=data=writeback rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian Retrieving file: /boot/dtb/nvidia/tegra210-p3450-0000.dtb 42868 bytes read in 33 ms (1.2 MiB/s) ## Loading init Ramdisk from Legacy Image at 83200000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 11330113 Bytes = 10.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 83000000 Booting using the fdt blob at 0x83000000 Using Device Tree in place at 0000000083000000, end 000000008300d773 copying carveout for /host1x@50000000/dc@54200000... copying carveout for /host1x@50000000/dc@54240000... Can't set DT prop /bpmp/carveout-start: FDT_ERR_BADOFFSET Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd071] [ 0.000000] Linux version 5.10.22-jetson-nano (root@vbox) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-re1 [ 0.000000] Machine model: NVIDIA Jetson Nano Developer Kit [ 0.000000] efi: UEFI not found. [ 68.257514] systemd[1]: Starting Create System Users... [ 68.270413] systemd[1]: Mounted Kernel Configuration File System. jetson-nano login: root (automatic login) _ _ _ _ | | ___| |_ ___ ___ _ __ | \ | | __ _ _ __ ___ _ | |/ _ \ __/ __|/ _ \| '_ \ | \| |/ _` | '_ \ / _ \ | |_| | __/ |_\__ \ (_) | | | | | |\ | (_| | | | | (_) | \___/ \___|\__|___/\___/|_| |_| |_| \_|\__,_|_| |_|\___/ Welcome to Armbian 21.05.0-trunk Focal with Linux 5.10.22-jetson-nano No end-user support: built from trunk System load: 74% Up time: 1 min Memory usage: 6% of 3.80G IP: Usage of /: 28% of 15G [ General system configuration (beta): armbian-config ] Last login: Wed Mar 10 08:41:35 UTC 2021 on tty1 New to Armbian? Documentation: https://docs.armbian.com Support: https://forum.armbian.com New root password: ****** Repeat password: ****** Choose default system command shell: 1) bash 2) zsh Shell: BASH Creating a new user account. Press <Ctrl-C> to abort Desktop environment will not be enabled if you abort the new user creation Please provide a username (eg. your forename): user Create password: ****** Repeat password: ****** Please provide your real name: User Dear User, your account user has been created and is sudo enabled. Please use this account for your daily work from now on. Now starting desktop environment...