• Posts

  • Joined

  • Last visited

Posts posted by manuti

  1. 46 minutes ago, balbes150 said:

    All the entry works correctly, cause in Your system.


    YES, I'm the problem of course, because nobody has same issues. But with my workaround finally I have your images working on a MXQpro and a MXQpro+.

    The Wi-Fi is not working, I don't know whats happens.

    I need to open the box to see the chipset or can be retrieve this info with some command on the CLI?

    Thanks again for this incredible work!!!

  2. On 9/1/2018 at 4:11 PM, manuti said:

    OK, thanks.

    I don't understond what's happened. I try again with the images on Mega and also with ROSA.

    Hey @balbes150   I don't know what happens with your images but is impossible to me to burn using my Laptop with Ubuntu 16.04. After my first try I ended with a bricked SD card (nested partitions, incorrect partition orden ...  and a sort of things that made impossible to format or recover). I buyed a new one and started having same errors writing the image with Etcher and Rosa and I decided to stop this way. 
    I have created the partition structure with Gparted, I have mounted the image, I copied the /BOOT files in fat16 partition and /ROOTFS to ext4 partition, I have to recreate the permissions for sudoers ... and finally the image boots!!! Thanks!!!

  3. Hey @balbes150 I check the md5 against my yesterday downloads (the 3 ubuntu armbian 5.37 s9xx images) and the checksum are OK but I'm having problems to write the images on SD card and USB drive, I try 2 different SD card and 2 different USB drives. I use Etcher and Disk Utility in Ubuntu 16.04 and also 2 different ports in my Laptop and again I try to use the card reader in the Laptop and a USD card reader. In all the cases the image fail in some point more or less at 80% of the process.

    Are the images correct? What is the correct way to do the step 3? Thanks again


    On 6/5/2016 at 11:59 AM, balbes150 said:

    3. Record an image on the medium

  4. New Tinker Board with cheat power control to prevent the problem they create:




    New power management features include low-voltage input detection on the micro-USB port to ensure stability when using a non-qualified power supply. There’s also a new 2-pin power-on header.


    Product page

  5. I don't know if I use or not, I use the same instruction en every machine: 

    ffmpeg -i input.mkv -vcodec libx264 -profile:v main -level 3.1 -preset medium -crf 23 -x264-params ref=4 -acodec copy -movflags +faststart output.mp4

    Usually the ffmpeg detects the processor capabilities like you can see on the OPiPC2 with H5 with ARMv8 and NEON



  6. The info is in Spanish

    But in short the numbers are:

    • In the Banana PRO that is dual core and running the entire OMV server with Samba, torrent and Plex I have achieved a speed of about 0.15x, that is, to convert a 1h video it takes 6h40.
    • Then I tried the Raspberry Pi 2 with the same video and conversion reaches about 0.40x.
    • We move to the newer model, the Raspberry Pi 3 also reaches about 0.75x
    • Testing with the Orange Pi PC gives us 0.58x
    • And finally the Orange Pi PC2 same SoC reaches 0.9x
    • As a final test, I compared it with a normal laptop, a Lenova Yoga 2 with an intel Core 1.6GHz Intel Core i5 4200U is achieved to 2.85x

    This number are only an example it may vary depending your case.

  7. The S/PDIF output from the Beelink X2 is active and real. But I only can managed to  use with test sound. I don't waste many time messing with the configuration. I only tested with Legacy kernel I don't know if work with Mainline. I'll try to test this X-mas. 

    I'm going to receive a MXQ Pro Plus and a MXQ Pro 4K.  One of these have s/PDIF and thee other don't have enough information in Banggood. When I'll receive the two MXQ my plan is try to install this armbian version. If you whish I'll try also to check the S/PDIF output.