Jump to content

balbes150

Members
  • Posts

    4435
  • Joined

  • Last visited

Reputation Activity

  1. Like
    balbes150 got a reaction from Werner in Board Bring Up Station P2 rk3568, M2 rk3566   
    The current version of Firefly multi-boot (which is installed in SPI) uses an outdated startup scheme that cannot work with new versions of Armbian. I am communicating with the Firefly developers to fix this issue.
     
    Additional settings are needed to get a working image.
    In the near future I plan to add CSC settings for quartz64.
     
    This hardware is not supported and will not work.
     
    Have you updated u-boot according to the instructions for Armbian?
  2. Like
    balbes150 got a reaction from gounthar in Board Bring Up Station P2 rk3568, M2 rk3566   
    https://en.t-firefly.com/product/industry/itx3588j
     
  3. Like
    balbes150 got a reaction from anhthodien69 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.
  4. Like
    balbes150 got a reaction from William Marquez in RK3288 and RK3188   
    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
  5. Like
    balbes150 got a reaction from MattWestB in RK3288 and RK3188   
    ver 20220205 kernel 5.10.96 for rk3188
     
    Please note, now I am publishing new versions for rk3188 only on yandex disk (in order not to occupy Armbian resources with non-profile and unsupported versions that are released "as is" without any guarantees of work and support)
  6. Like
    balbes150 got a reaction from danboid in Allwinner H6   
    edge is not supported in the build system for TX6
  7. Like
    balbes150 got a reaction from NicoD in Video : Testing KDE Plasma desktop on Armbian / RK3399   
    You are violating the startup order, this is a test version and it does not contain startup scripts from the desktop. It needs to be run as an independent software. After booting the system, DO NOT log in to the desktop. Switch to any console (Ctrl+Alt+F1). We log in as a user (but it's better to use root, then there will be more control options) and launch kodi. The problems of a long startup may be related to new KODI packages or the latest version of the image with the 5.10.88 kernel (you can try earlier versions from yandex disk, there is a version with the 5.10.62 kernel). I have a system with the first versions of these packages, everything works quickly with them and the splash works.
     
    I recommend using the correct package installation order.
     
     su -
     apt update
     apt install <full_patch>/kodi-mainline-bin_18.9-final-18.9bullseye0armbian1_arm64.deb
     apt install <full_patch>/kodi-mainline_18.9-final-18.9bullseye0armbian1_all.deb
    (installing additional packages if they are needed)
     reboot
  8. Like
    balbes150 got a reaction from Werner in Video : Testing KDE Plasma desktop on Armbian / RK3399   
    Download the Bullseye image with kernel 5.10 (for Station P1) and install the KODI package into it.
     
    https://users.armbian.com/jmcc/packages/kodi-mainline/arm64/
     
     
    By the way, the latest images for Station P1 use the media kernel with a full package of patches for HW, which go for LE. If @JMCC builds its mpv and KODI packages based on it, you can have HW acceleration on any Debian and Ubuntu system) with a 5.16 kernel.
     
  9. Like
    balbes150 got a reaction from NicoD in Video : Testing KDE Plasma desktop on Armbian / RK3399   
    You are behind the current state of rk3399 support. Now there is already support for HW GPU and VPU. I'm testing this on Firefly Station P1 (rk3399), everything works fine (kernel 5.1x), including 4k.
     
     
    info glmark2 for Station P1
     
    https://forum.altlinux.org/index.php?topic=36166.msg364846#msg364846
     
     
  10. Like
    balbes150 got a reaction from lanefu in PINE64 Quartz64   
    A question about Quartz64. Can I create a PR for CSC or do we not support it in any form ?
  11. Like
    balbes150 got a reaction from wzgfeixiang 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.
     
     
     
     
  12. Like
    balbes150 got a reaction from hexdump in Jetson Nano   
    The procedure for updating (fixing) the latest version of u-boot for Jetson Nano. Fixes the system startup error when the Initrd size is more than 14 MB.
     
    1. Download the boot.scr file from the link.
    2. Prepare any clean media (you can use any media SD card or USB flash drive of any size). The media must be formatted in FAT32 or EXT2\3\4.
    3. Write the boot.scr file to the media
    4. Connect the media to the Jetson Nano and turn on the power.
    5 Wait 3-4 Minutes and turn off the power, disconnect the media.
     
    This is a one-time procedure that automatically fixes an error in u-boot SPI. After that, you can use any systems from external media.
     
     
    https://disk.yandex.ru/d/p1uI2wyAfpoLRA
  13. Like
    balbes150 reacted to Igor in Armbian 22.02 (Pig) Release Thread   
    Fixed some UX troubles on the download pages, examples:  https://www.armbian.com/banana-pi-m2-plus/ https://www.armbian.com/rpi4b/ https://www.armbian.com/odroid-hc4/
     
    - download list is now completely automated, pulling from build config files https://github.com/armbian/build/blob/master/config/targets.conf
    - added option to advertise recommended targets at download pages https://armbian.atlassian.net/browse/AR-1057 by setting a property in a targets.conf
    - label supported / not supported for kernel is no more. instead label for CLI / Desktop / minimal
    - added "Closed bootloader" property
    - improved FAQ
    - enabled WIP builds for: RPi4, UEFI arm & x86
     
  14. Like
    balbes150 reacted to Igor in New prize: $500 for anyone who can update my DTB file!   
    I am sorry, but that is a terrible and damaging business proposition which I have to turn down. 

    There are thousands of people in the same line where you are standing. I give you my word that I will do everything to prevent you making us more expenses. They are usually in a range of 1000 x bigger than your generous donation.

    Until then, proceed as your support contract says: ... If you can't find answer there and/or with help of general project search engine and documentation, consider hiring an expert. (link to 3rd party resources which are having enough time to deal with and might accept your generous offer)
     
  15. Like
    balbes150 got a reaction from Werner in Board Bring Up Station P1 rk3399, M1 rk3328   
    At the moment, so far only for Buster 4.4 there is a media package with KODI and mpv (HW)  in network repo armbian. As soon as @JMCC releases and places in our repo a new version of the media package for the 5.15 kernel (I have already checked its test build of the package for Bulsey and it works well with full HW acceleration), I want to remove the old version (4.4) from subsequent builds and I will leave the version with the 4.4 kernel only in the archive for those who urgently need it. 
  16. Like
    balbes150 reacted to Heisath in Armbian 22.02 (Pig) Release Thread   
    Release Candidate Code Freeze Date: 2022-02-14
    Release Planning Meeting Date:  2022-01-29 14:00 UTC+1 
    Release Planning Meeting Location: Armbian IRC
    Release Date: 2022-02-28
    Release Branch Link: https://github.com/armbian/build/tree/v22.02
    Release Changelog:
     
     
    Release Coordinator: @Heisath and hopefully some new person on the team
     
    Already creating this release topic for 22.02, to discuss upcoming changes, no longer maintained boards and help new people get into the release / maintain flow.
     
    Current steps:
    - Refine supported/WIP/CSC/etc. board status
    - Update maintainer list
    - Onboard new maintainers / contributors
    - Move Jira issues to new release
    - Select release name 
     
    @Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe  @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013  @rpardini
     
    Pls. ping developers I forgot  
  17. Like
    balbes150 got a reaction from DMC in Board Bring Up Station P2 rk3568, M2 rk3566   
    Version 20211222-edge with 5.16-rc6 kernel.
    Added support for HDMI audio.
  18. Like
    balbes150 got a reaction from DMC in Board Bring Up Station P2 rk3568, M2 rk3566   
    Ver 20211227-current kernel 5.16-rc6 for Station P2 (rk3568) and M2 (rk3566)

    Fixed LAN2. (Station P2 )
    Fixed the reboot and shutdown of the Sd card.
    Added support for the on/off button. Now, after switching off, you do not need to pull the power supply out of the mains, just press the button on the P2 case. Also, the operating system turns off when the button is pressed briefly.
  19. Like
    balbes150 got a reaction from Werner in Board Bring Up Station P2 rk3568, M2 rk3566   
    Ver 20211227-current kernel 5.16-rc6 for Station P2 (rk3568) and M2 (rk3566)

    Fixed LAN2. (Station P2 )
    Fixed the reboot and shutdown of the Sd card.
    Added support for the on/off button. Now, after switching off, you do not need to pull the power supply out of the mains, just press the button on the P2 case. Also, the operating system turns off when the button is pressed briefly.
  20. Like
    balbes150 got a reaction from MattWestB in How to run armbian on MK802 IV (rk3188) box   
    On the contrary, not removed, but developed. But not fast enough yet. I hope to add support for building images for rk3188 to my GIT in the future (and if there is a demand, it is possible to send a PR to the official GIT).
  21. Like
    balbes150 got a reaction from gounthar in Jetson Nano   
    ver 20211219 kernel 5.15.10
    fan work
  22. Like
    balbes150 got a reaction from itsme in Firefly Station P2 (rk3568) M2 (rk3566)   
    To install Armbian, use the standard armbian-config menu, there is everything you need for easy installation of the system on NVMe.
  23. Like
    balbes150 got a reaction from Werner in Board Bring Up Station P1 rk3399, M1 rk3328   
    version 20211209 kernel 5.10.84 and 5.15.7.
  24. Like
    balbes150 got a reaction from itsme in Firefly Station P2 (rk3568) M2 (rk3566)   
    It looks like you didn't understand my answer. I will explain in detail. There are several options for working with NVMe. 1. Starting the system + u-boot completely immediately from NVMe (this option is not known to me on RK). 2. Placing the u-boot on an intermediate medium (SPI\SD\eMMC\USB) and placing the entire system completely on NVMe. This is the simplest and most common way to use the entire NVMe system use SPI.  3. Placing the u-boot and boot partition with the kernel on intermediate media, and placing the system on NVMe. I repeat, u-boot is placed on Station P2\M2 on eMMC and the /boot partition can be placed, during normal operation of the system it is used only during boot and works mainly in read-only mode, it is not used in the rest of the system. The working system uses only NVMe and, accordingly, the speed of the system is determined by the speed of NVMe only. This option works well on all Station M1\M2\P1\P2.
     
    My equipment is in heavy use right now, try asking other owners to run your tests.
  25. Like
    balbes150 reacted to Igor in Rock 3A no longer bootable -- current development status?   
    We have hundreds of tasks waiting for someone. I bet it's possible to find something you can contribute to.
     

    Ahaa, this.  Welcome to the club.
     
    Percentage of people that knows how to deal with this complexity (on their expense!) is notoriously low since ever. New boards are coming out with at higher and higher rate, which means there is more and more pressure on people that knows stuff. Learning is very slow and expensive on the other hand. I understand you would like that your shiny new and good looking board function perfectly, but that will not happen just like that. And certainly not "now". It takes months to year(s), before they are functioning so-so (outside their proprietary kernel) and they need constant investments and love. They are like children with special needs ...
     
     
    I bet you didn't read requirements?  If we would require that maintainers knows how to bring board up and fix bugs, nobody would apply! This is an assistance, to relieve those that knows something. They need help first, consumers of their time (you) optional.
     
    There are other roles that can help in a problems you have. A lot more is needed that you can get what you are asking for:
    https://forum.armbian.com/staffapplications/
    All those things also need to be done, welcome to pick up. All roles can be from a few hours per week to full-time. And none will directly answer any of questions you have. Those roles are related with hard cash investment and since you expect all this for free ...
     

    Like we all do and we have many other problems nobody helps to solve. But has to be done in order that project function.

    If providing your time and expertise for common R&D work is not possible (your time is a lot more valuable, you have no time for this, ...), perhaps covering expenses of what has been asked? It is one click away. To answer some questions, people that understand things, can easily blow a week or more to provide an answer. 

    You can also hire people to jump on problems you have at any time:
    https://www.debian.org/consultants/ 
    https://www.fiverr.com/share/67vQ7B
    Much better than begging us to do more for you. Then person you are paying sends a fix to the problem:
    https://docs.armbian.com/Process_Contribute/
     
     
    Another difference between people that sold you some hardware and us. If Armbian solves problems you have, it support competition that in most cases in this area contributes close to nothing. With which problem I believe you have no problems with, but perhaps Armbian maintainers have? Just a rhetorical question.
     
    Before asking for support, it's worth reading this.
    https://docs.armbian.com/User-Guide_FAQ/

    This is not hardware sellers forum.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines