starman345

  • Content Count

    11
  • Joined

  • Last visited

Posts posted by starman345

  1. On 4/25/2020 at 7:13 AM, balbes150 said:

    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 3.86 kB · 6 downloads

    Latest image works great. Is there any chance to have boot/rootfs  on SD card installed to emmc/nvme via Armbian-config?

  2. 4 hours ago, balbes150 said:

     

    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

     I've been running my NanoPC-T4 boot on eMMC  system on nvme with the 4.xx kernels via armbian-config  It is a lot faster than an SD card or eMMC.  Have you noticed boot time with the 5.xx kernels is faster with this setup?   With SD card I see bootup times around 60-70 seconds.

    Thanks for the script, I'll give it a go.

  3. 35 minutes ago, martinayotte said:

    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

     

     that is what I used to get wifi working. You posted that in another thread a few days(weeks) ago, thanks for that. 

  4. My procedure that works for me:

    Press boot button and hold, press power button and hold for 4-5 seconds, then release both buttons. If I hold more than about 5 seconds the red power light goes out and I need to start over.

  5. 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