starman345

  • Content Count

    11
  • Joined

  • Last visited

Reputation Activity

  1. Like
    starman345 reacted to Wizzard in default resolution change   
    Resolution:
     
    to add this line to /boot/armbianEnv.txt
     
    extraargs="video=1280x720@60"
     
  2. Like
    starman345 reacted to balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    ver 20200516 kernel 5.7-rc5
  3. Like
    starman345 reacted to balbes150 in NanoPC T4   
    Script for automatically enabling audio on all known ARM models (in my images, it runs automatically when the system is first started and includes all known audio devices for the model being used).
     
    By the way, today, T4 has almost full support for all hardware (WiFi BT NVMe sound etc) and copes well with any tasks. It remains only to solve the issue with 4K resolution.
    sound.sh
  4. Like
    starman345 reacted to balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    Perhaps this is a feature of publishing new files in the Armbian repository (now there is a huge load on resources and there may be failures).
    Yes, the update should take place automatically (I fixed the packages for this).
     
    P.S. Do not rush, a new version 5.6-rc7 is coming soon.  I plan to send it to the Armbian network repo (I have already uploaded some deb files to my site along with the new version of images). 
  5. Like
    starman345 reacted to balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    New versions of images 20200218.
     
    Important change. With this version, 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.
  6. Like
    starman345 reacted to balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    What does no sound mean ? I have an HDMI sound that works perfectly with the DTB nanopc-t4.
     
    By the way, I uploaded a script for installing the system in NVMe for NanoPC T4 to the site. The rk3399 chip does not support direct launch of u-boot from NVMe, so the combined mode is used, the u-boot and kernel is located on eMMC, and the entire system is on NVMe. I compared working in mode
    1. the entire system is installed on eMMC.
    2. bootloader on eMMC + entire system on NVMe.
    The second option works much faster (this is taking into account that the NVMe version from Orico is used for the test, which has average characteristics).
     
    https://yadi.sk/d/QRBz-035dlDWUw
  7. Like
    starman345 reacted to balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    Important information for Rockchip RK3328\RK3399 and Allwinner H6. If you have written to the SD card any version of the system that uses a GPT table or a non-standard u-boot (for example, an Android image or an Ubuntu image built by the device manufacturer, etc.). Before writing an Armbian or Libreelec image, be sure to zero the entire SD card with the
     
    dd if=/dev/zero  of=/dev/<sd_card> bs=64M
     
    command. Only then can you write the image to the SD card and it will work correctly. If you do not zero the SD card, there will be problems with u-boot from Armbian and Libreelec (u-boot does not start and stops with a partition table error message). For those who use the new version of u-boot, which supports direct launch from USB media, I recommend using USB media to launch, this guarantees that the system will start, regardless of what was previously on the USB media.
  8. Like
    starman345 reacted to balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    Yes, there is (for the test, I tried a cheap NVMe Orico 128GB model). and it is immediately visible in the system. I can use it to host data. Now I have an Armbian version installed in eMMC with the new u-boot and I can run any system from USB media (SD card is no longer required). By the way, the regular fan also works, it works silently. I liked this model, it is well balanced and has everything you need to use as a mini PC. It remains only to deal with analog sound via Jack 3.5.
  9. Like
    starman345 reacted to balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    ver 20.02.0-rc1 20200129
     
    The sound works on all models S9xxx, rk3399 , rk3328 , aw h6.
    Please note that to enable audio on g12 chips s922x s905x2 (models Ugoos AM6, Ugoos x2, Odroid N2 etc), you must follow the instructions specified in the first message.
  10. Like
    starman345 reacted to balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    Version 20200127.
    EMMC installation fixes for NanoPC T4.
     
    Added deb files with the new kernel to the site for manual kernel updates.
  11. Like
    starman345 reacted to martinayotte in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    Try that and reboot :
    mv /lib/firmware/brcm/brcmfmac4356-sdio.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin-ORIG mv /lib/firmware/brcm/brcmfmac4356-sdio.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt-ORIG cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt  
  12. Like
    starman345 reacted to balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    Update to version 19.11.5 (20200120) kernel 5.5.0-rc6.
    Important change. the way DTB is configured has changed. The universal multiload for the AML platform has changed. 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.
     
    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. Important. On models S905\S905X and partially on S912, there may be problems with starting the desktop, management is possible only via SSH or UART.
     
     
    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).
  13. Like
    starman345 reacted to martinayotte in NanoPC T4   
    Maybe you should try another firmware :
    mv /lib/firmware/brcm/brcmfmac4356-sdio.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin-ORIG mv /lib/firmware/brcm/brcmfmac4356-sdio.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt-ORIG cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt And then reboot ...
  14. Like
    starman345 reacted to balbes150 in Plans for the development of Armbian-TV.   
    In the new year, I plan to focus on improving and developing Armbian-TV  (Armbian-TV is a version that is based on the official Armbian, aimed at improved support for media capabilities and ease of use by ordinary users) support for the platforms Rockchip and Allwinner  (perhaps a few more platforms will be added that are not yet in use). To do this, I have already ordered several popular models based on rk3399 (NanoPC T4, RockPi 4, Renegade-Elite), in a complete set with obligatory Support of nvme carriers (I consider this support essentially important, for transition of TV boxes and SBS to the category of mini-PC, as highly effective and improved replacement of the usual PC). I'm plan to buy several more models on Allwinner (I'm still evaluating the capabilities of the selected models). 
    I had plans to buy some more models based on rk3399 from other manufacturers, but there were problems with delivery and / or payment for my country.
     
    If anyone has any suggestions for models that I should consider, I'm willing to listen to reasonable descriptions of the models.
  15. Like
    starman345 reacted to Igor in My most useful Linux terminal commands for Ubuntu/Debian   
    This website might be useful in this context: https://linuxjourney.com/
  16. Like
    starman345 reacted to balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    This chip has long had support in the main core. You need to sort out the settings. Either install the full firmware package or use the correct DTB for your WiF-enabled model. Perhaps the current DTB does not yet have this support. Alas, I do not have this model, I can not check the cause of the lack of WiFi and other problems for the T4.
  17. Like
    starman345 got a reaction from nanopi in USB3.0 connection problem   
    I have had usb3.0 problems with my NanoPC-T4,  close relative of your NanoPi-M4 but not really the same. 
    When using my ZWO ASI294MC pro camera (USB3.0) the first image in any sequence is saved, but then the software goes into a cycle where the countdown continues for the next image, reaches zero  but the image is not saved, this continues over and over.  To reset, I need to shutdown the software and re-boot the NanoPC-T4. The camera works fine when plugged into one of the NanoPC-T4 usb2.0 ports, it just saves images at the usb2.0 speed. That isn't a big problem for me as I just do DSO imaging anyway. Still it would be nice to have it working as I need all three usb ports.
    There are reports from NanoPi-M4 users on the indilib.org forum having the same problem as I have with the ASI294 camera and their usb3.0 ports.
    A few weeks ago I burned the Armbian 5.98 image to an SD card, then upgraded the kernel to 5.3    from Armbian-Config and the usb3.0 problem with my camera was cured, however networking did not work so I am still using the 4.4.192 kernel for now. 
    If you have an extra SD card you could give the 5.3 kernel a try.
    Sorry I can't be more helpful