Jump to content

talraash

Members
  • Posts

    101
  • Joined

  • Last visited

Reputation Activity

  1. Like
    talraash got a reaction from zogu in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    hardkernel take blob's from mali compiled for specific kernel. For "videos from browser" it's not mali gpu part. 
  2. Like
    talraash got a reaction from zogu in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    It's bad idea use swap on microsd, bad for sd card) youtube now work with standart armbian image, it use psd and store cache and profile in tmpfs... If you disable in chromium settings all kind hw acceleration it can smoooth play 720p in youtube with software decoding... 
  3. Like
    talraash got a reaction from balbes150 in The list of models that are running Armbian (Amlogic, Rockchip, Allwinner etc)   
    Nexbox a95x(soc amlogic s905 ram 1 storage 8)
    All image with kernel 3.14 work with generic gxbb_p200.dtb(old u-boot). Don't have now this box, so don't have opportunity check mainline.  It have some exotic wi-fi module without open sources drivers, so no wi-fi.
     
    Sunvell T95X(soc amlogic s905x ram 2 storage 8).
    All image with kernel 3.14 and mainline. With stock firmware don't need manipulate with .dtb files(3.14 kernel), for mainline need generic p212 dtb. Wi-fi  sci9082c, didn't test.
     
     
  4. Like
    talraash reacted to balbes150 in Armbian for Amlogic S9xxx kernel 5.x   
    Image update 5.55 (20180819).
  5. Like
    talraash got a reaction from balbes150 in Armbian for Amlogic S9xxx kernel 5.x   
    @balbes150 
     
    upd
     
  6. Like
    talraash got a reaction from balbes150 in Armbian for Amlogic S9xxx kernel 5.x   
    On mainline - compile kernel, v4l2 m2m etc. with custom patches or wait when it merge to stable. For 3.14 use kodi. For 3.14(and software decoding in mainline) and x11 - partial solution --vo=x11 and --sws-scaler=fast-bilinear or equal if you don't use mpv.  It cause high cpu usage but give you playable 720p and some 1080p video.  Most problem with mpv - it use by default vo=opengl, it cause huge framedrop(yep, soft mesa) so if you want soft decoding use special flags or vo=x11
    upd @Baloven
     
  7. Like
    talraash reacted to balbes150 in Armbian for Amlogic S9xxx kernel 5.x   
    Information in this topic is very outdated see this topic.
     
     
     
     
     
     
    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.
     
     
    The new version 5.55 of images. In this version, images with a single DE (XFCE) and a server in composition are as close as possible to the official versions. Version with a Mate and Icewm will probably be later and the gathering will be from another branch GIT (specially adapted for this DE). Since now all the images will be collected using the main kernel "4.1 x", have a common structure for the entire line of s9xxx and differ significantly in steps when configuring the system, I open a separate topic for this direction.
     
     
    https://yadi.sk/d/pHxaRAs-tZiei
     
    https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
     
    The primary steps to capture an image, activate multi-boot, and select a dtb file are common with the previous images.
     
     
    Please note that starting with the version number version 20180928.
    Major change. A new algorithm for the use of the dtb. Starting with this version, you no longer need to copy the dtb files and rename it to "dtb.img." In order to specify which dtb file to use, you need to edit the file 'uEnv.ini" (specify the desired file name for use dtb). This is a plain text file and can be easily edited. This change will make it easy to update the kernel from the "deb" file in the future. The new algorithm is now used in the eMMC system installation script.
     
    Be sure to activate multi-boot using the new image. If multiboot previously activated is required to repeat activation using files in a new image.
     
    Pay attention. To use the system with
    u-boot-2015 (regular firmware Android), you need to edit the file "uEnv.ini"
     
    When using
    u-boot-2018, you need to edit the file "/extlinux/extlinux.conf"
     
     
    For those who doubt or do not know what u-boot is used, you can specify the desired name in both files at the same time.
     
     
    To change the used MAC address.
     
    1 options
    You can add the required parameter to the startup files (uEnv.ini and extlinux.conf). To do this, at the end of the line with the launch parameters, you need to add a parameter specifying the desired MAC address.
    For example,
    mac=xx:xx:xx:xx:xx 
    or
    ethaddr=xx:xx:xx:xx:xx
     
     
     
    Old info multiboot
     
    https://sourceforge.net/p/amlogic-s9xxx/code/ci/master/tree/
     
    add info
     
    https://medium.com/@vysmol/how-to-install-ubuntu-on-s905w-and-simular-tv-boxes-ru-eng-7aca3e1011a5
     
     
    Install Armbian to eMMC.
    1. Be sure to activate multi-boot using the new image. If multiboot previously activated is required to repeat activation using files in a new image.
    2. Run Armbian from external media, run "ddbr" and create full backup eMMC.
    3.  install Armbian on eMMC execute script “/root/install.sh”.
     
    Please note, this is a test installation, which was tested only on a few models. Possible errors (Armbian will not boot) when you are working on unverified models which used non-standard distribution of partitions in the eMMC. Therefore, be sure to back up the "ddbr" utility before running the scripts.
     
     
  8. Like
    talraash reacted to balbes150 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    Yes.
    there is not enough time for everything
     
     
    By the way, interesting news, I managed to run the version of Manjaro on TV Box Amlogic, everything starts and works. But while it has to be done in semi-manual mode (i'm need to rebuild the new image with full support for TV boxes). I hope soon there will be another version of the Linux distribution (Manjaro) for the platform Amlogic.
     
  9. Like
    talraash reacted to balbes150 in New branch for version assembly Armbian for TV boxes.   
    The official git armbian\build adds the tvboxes test branch. Everyone is invited to participate in the development , testing and maintenance of different models of TV boxes.
     
    https://github.com/armbian/build/tree/tvboxes
     
  10. Like
    talraash got a reaction from balbes150 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    Mmmm... But help text on screen give all this clue)
  11. Like
    talraash reacted to MOHAMMAD HADI in Multiboot selector for your tv box   
    I updated the image to support Ir remote so you don't need to use your keyboard
  12. Like
    talraash got a reaction from Tido in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    It's pulseaudio problem i saw this problem very often but if delet pulseaudio and alsa-utils problem was gone... But, without pulseaudio in linux(read as alsa) no easy way to use sound mixing(just one sound from one source in same time) 
  13. Like
    talraash got a reaction from balbes150 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    Tried bionic, work fine(install package from repo, uninstall etc. mpv from default repo work fine). I did not find any bugs or problems.... thanks.
  14. Like
    talraash reacted to balbes150 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    Maybe someone will be interested in this information.
     
    http://forum.khadas.com/t/armbian-kodi-ubuntu-debian-for-sd-usb-emmc/825/155?u=balbes150
  15. Like
    talraash got a reaction from balbes150 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    In this topic from 50 pages. i think 5 or more with like you question and answer...
     
    Correct for you android image,  but not for image with kernel 4.9.x for example...
     
    Can compositing from popular DE use gles? Or you need mali for some specific use keys(like qt)?
  16. Like
    talraash reacted to balbes150 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    A corrected version kernel 3.14.29 of the images with mali-6 20180205. Fixed KODI in HW mode.
  17. Like
    talraash reacted to fdopen in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    Yes, I've just noticed it, too. The kernel was compiled without CONFIG_V4L_AMLOGIC_VIDEO. So no /dev/video10 and no hardware acceleration. CONFIG_AMLOGIC_IONVIDEO is also not set.
  18. Like
    talraash reacted to balbes150 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    A little surprise to Chinese New Year holiday. Image update 20180203.
  19. Like
    talraash got a reaction from vuhuy in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    1. Some software you can update via apt from ubuntu/debian repos, but specific system component balbes150 compile witch patch from sources when build new image, If you have time and resources, you can create you own repo, compile this package and give it to other user via apt)
    2. Kodi have great documentation basically you need compile it for framebufer
    4. Main problem when you watch video in windowed mode it's scaling and color conversion with default mpv settings it requires a lot of cpu resources.
    4.2. Mainline kernel good for some project, but not for desktop usage now.
     
     
    If you play video with mpv, and video resolution not same as you screen resolution you can reduce framedrop and  cpu usage if try different scale method.. example screen resolution 720p test file http://www.digital-digest.com/movies/Star_Wars_The_Last_Jedi_1080p_Theatrical_Trailer.html play in fullscreen 1280x720
     

    First - play with fast scale method --sws-scaler=fast-bilinear - 150 frame droped during 150sec of video, second - play video with default scaling method - 253 frame drops during 12sec of video.
     
    Some light test ram consuming and perfomance arm64 and armhf browser chromium 63...
    armhf
     
    arm64
  20. Like
    talraash reacted to MOHAMMAD HADI in Multiboot selector for your tv box   
    Ok, I updated the boot manager so it is now more portable and added some convenience features as well.
    Be aware that it is not beginner friendly, you need at least some knowledge about writing and editing u-boot scripts, Uart cable is not needed but can be useful during testing and setting up.
    I rewrote the script in python using curses so It's now more elegent (in my opinion anyway) I tried to get it as close as I can to look like grub2 interface:

    Now let's explain How it works:
    First, the sdcard must contain at least two fat32 partitions:

    -First partition(fat32) (label=RECOVERY) content:
    This partition contains the main boot manager files:
    1-aml_autoscript is the script that is used to update the u-boot environment to allow for our method to work
    2-dtb.img a dtb file, make sure to replace it with the appropriate one for your device I compiled it from coreelec source https://github.com/CoreELEC/device-trees-
    amlogic
    3-Image is the kernel image of the boot manager
    4- multiboot.script is the script that is executed to display the boot manager
    5-update.zip use this in your update app in android to flash the aml_autoscript above and make the bootloader ready for our boot manager
     
     
    -Second Partition(fat32) (label=BOOT) content:
    This partition contains at least the config.yaml file that contains general settings for the boot manager and the boot entries to be listed.
    Mote that I have a folder(multiboot) that contains the boot files for my distros(kernel,initrd,dtb and boot script) you don't have to put them in this partition you can put them anywhere (another partition on the sd card, a USB drive or even in  the internal EMMC) just make sure to have the correct path and device id for them in the config.yaml file.
    Also If you want to use the remote control instead of a keyboard to select the os place the correct remote.conf of your remote in the root of this partition.
     
    the structure of config.yaml is like this:
    generalSettings: default: 5 rememberboot: true timeout: 10 menu: - bootscript: /multiboot/COREELEC/u-boot.script device: mmc 0:2 devicefs: fat name: COREELEC - bootscript: /multiboot/armbian-3.14.29-mate/u-boot.script device: mmc 0:2 devicefs: fat name: armbian-3.14.29-mate - bootscript: /multiboot/dvb_test/u-boot.script device: mmc 0:2 devicefs: fat name: dvb_test - bootscript: /multiboot/kernel-3.14/u-boot.script first you set the general settings:
    - timeout: this is how many seconds the boot manager should wait before booting into the default boot entry
    - default: this is the zero based index of the default distro that the boot manager will boot to after timeout, note that index 0 is reserved for the internal EMMC boot so your menu starts at index 1.
    - rememberboot: if this is set to true then the manager will remember the entry that you selected and save it's index in the default entry above so the next time you boot this will be your default entry.
     
    after that you add your menu entries:
    - name: is the name of the distribution displayed in the boot menu
    - bootscript: this is the path of the bootscript of the distribution (note that this boot script should be capable of booting the distro on it's on, so it must have the correct path of the boot files and pass the correct root parameter to the kernel, see the example u-boot.script files that are included in each distibution)
    - device is the device that contains the bootscipt using u-boot format so the first mmc and second partition would be mmc 0:2 , the second mmc and third partiton would be mmc 1:3 .
    - devicefs is the filesystem type of the above device, this is usually fat because most of these tv boxes support loading files of only fat32 partitions (except some boards like khadas vim and odroid whose bootloader support ext4 partitions)
     
    now let's see an example of a disto bootscript:
     
    this the same bootscript that was shipped with balbes150 image I only edited the device to mmc 0:2 because this is where I have my kernel and other boot files, also I prepended the correct path before each file name.
    In the uEnv.ini file of this distro I edited the root parameter to use a partition labeled "Debian-3-xfce" and created that partiton using gparted
     
     
    I prepared a boot image that contains the boot manager and two distibutions, Coreelec and Debian server.
    download the image here and burn it to a new sdcard then use the update application in android and update using update.zip, after that you'll see the boot menu after the reboot
    https://drive.google.com/open?id=1dhpcqNrqbW493SK8J_Er9b-ZipJkTfd3
     
     
    Below is the old method
     
    Hi,
    This is my quick and dirty solution to multiboot any amlogic device(actually it can be used on any device that uses u-boot with slight modification):

     

    ***Warning: the following method was only tested on one device which is KII PRO, I made this method for my own use ,it is a long and a bit complicated to setup for non-experienced users if you want to try it you are trying it at your own risk, I take no responsibility for any damage that may occur to your device.
     
     
     
    Preparing the sd card for multiboot:
    1- Download the zip file from the attachments multiboot.zip
    2-wipe everything in your sdcard (i used a 16 gb card) and create 2 partitions:
    -The first one is a fat32 partition, this can be small partition (for me i made it 1gb) it will contain the boot files for the main multiboot system and for any other distributions,i labeled this partition "BOOT".
    -The second partition is ext4 partition which will contain the rootfs of your distributions in raw image format, this need to be a big partition i suggest you assign all remaining available space to this partition, also you need to label it "ROOTFS" (this is mandatory).
    you can use whatever tools you want(gparted,fdisk...etc)
     

     
    3-mount the partitions and extract the zip file to the root of your boot partition(the fat32 partition) and create an empty folder called ‘multiboot’ inside the root of the first and second partitions, so the first partition content should  look like this
    ▶ tree . ├── aml_autoscript ├── aml_autoscript.zip ├── multiboot ├── config.txt ├── dtb.img ├── s905_autoscript ├── s905_autoscript.cmd ├── umbInitrd └── zImage and the second partition should look like this
    ▶ tree /run/media/mohammad/ROOTFS/ └── multiboot the ‘multiboot’ folder in the first partition should contains folders with the name of the distro and inside them are the bootfiles of that distro(kernel,dtb,initramfs and s905_autoscript file) the ‘multiboot’ folder in the second partition should contain the same folders as in the first partition and inside the folder there should be an ext4 image of the rootfs of the distro
    4- The dtb file i used is for kii pro tv box and you should replace that with the dtb of your device, you can get that from any of balbes150 distributions(3.14.29 kernel).
     
    Now you'r ready to boot, all you need is some distros
    Preparing the distros:
    You can make a partition for each distro on your sd card and use it to store the rootfs but i chose a more portable solution by making a raw partition image for each distro and pass it to the initramfs to be mounted as a loop device.
    I will be using one of balbes150 distros as an example (Armbian_5.32_S9xxx_Ubuntu_xenial_3.14.29_mate_20170907.img.xz)
    1-First extract the file 
    ▶xz -k -v -d Armbian_5.32_S9xxx_Ubuntu_xenial_3.14.29_mate_20170907.img.xz 2- Now mount the resulting file partitions to some directories, I use kpartx to do it for me automatically
    ▶sudo kpartx -av Armbian_5.32_S9xxx_Ubuntu_xenial_3.14.29_mate_20170907.img add map loop0p1 (254:0): 0 262144 linear 7:0 2048 add map loop0p2 (254:1): 0 8812544 linear 7:0 264192 now mount the loop devices (i use udiskctl)
     
    ▶ udisksctl mount -b /dev/mapper/loop0p1 Mounted /dev/dm-0 at /run/media/mohammad/BOOT1. ▶ udisksctl mount -b /dev/mapper/loop0p2 Mounted /dev/dm-1 at /run/media/mohammad/ROOTFS1.  
    df -h Filesystem Size Used Avail Use% Mounted on /dev/sdb1 2.0G 215M 1.8G 11% /run/media/mohammad/BOOT #this is my sd card #1 partition /dev/sdb2 13G 6.8G 4.8G 59% /run/media/mohammad/ROOTFS #this is my sd card #2 partition /dev/mapper/loop0p1 128M 53M 76M 42% /run/media/mohammad/BOOT1 #this is the mounted distro image #1 partition /dev/mapper/loop0p2 4.1G 2.9G 1.1G 75% /run/media/mohammad/ROOTFS1 #this is the mounted distro image #2 partition
     
    3- create a folder with the name of the distro in the multiboot folder you created earlier (in the first and second partitions of your sd card) then copy all the boot files of your distro to the folder in the first partition
    ▶ mkdir /run/media/mohammad/BOOT/multiboot/armbian-3.14.29-mate #this is the first(fat32)partition ▶ mkdir /run/media/mohammad/ROOTFS/multiboot/armbian-3.14.29-mate #this is the second (ext4) partition ▶ cp /run/media/mohammad/BOOT1/* /run/media/mohammad/BOOT/multiboot/armbian-3.14.29-mate/ 4- now you need to create an ext4 partition image to contain the rootfs of your distro for me I made a 4GB image
    fallocate -l 4G system.img mkfs.ext4 system.img  
    5-mount the image
     
    ▶ sudo losetup $(losetup -f) system.img ▶ udiskctl mount -b /dev/loop1 Mounted /dev/loop1 at /run/media/mohammad/71545ae9-33c7-4d99-963e-a5a915464078. 6-copy all the files from the rootfs of your distro image to the newly created image
     
    ▶ cp /run/media/mohammad/ROOTFS1/* /run/media/mohammad/71545ae9-33c7-4d99-963e-a5a915464078/ UPDATE: edit the "/etc/fstab" inside the system.img file
    nano /run/media/mohammad/71545ae9-33c7-4d99-963e-a5a915464078/etc/fstab and comment out the lines that start with "LABEL=ROOTFS" and "LABEL=BOOT" by adding a hash at start of each line
    then add these lines to the file :
    /dev/mmcblk1p1 /mnt vfat defaults 0 2 /mnt/multiboot/armbian-3.14.29-mate/ /boot none bind this will fix the 0hdmi.service problem
     
     
    7- unmount everything
     
    ▶ umount /dev/loop1 ▶ umount /dev/mapper/loop0p1 ▶ umount /dev/mapper/loop0p2  
    8-copy the system.img file to your distro folder in the second partition of your sd card
    ▶ cp system.img /run/media/mohammad/ROOTFS/multiboot/armbian-3.14.29-mate 9- move to your distro folder in the first partition of your sdcard:
     
    ▶ cd /run/media/mohammad/BOOT/multiboot/armbian-3.14.29-mate  
    10- now you need to edit the s905_autoscript.cmd file ( I use nano editor, you can use any text editor you like), you need to make two types of edits in this file
      - add loop=${mbpath}/system.img to the kernel arguments
      - add ${mbpath}/ before each of uInitrd, zImage and dtb.img
    so this
     
     
    becomes this
     
     
    Note that I removed the lines of booting from usb to decrease the boot time because I know that I’m booting from the sd card, you can leave them if you want.
     
    11- compile the script
    ▶ mkimage -A arm64 -O linux -T script -C none -d s905_autoscript.cmd s905_autoscript 12-copy the dtb file of your device
    ▶ cp dtb/gxbb_p200_2G.dtb dtb.img  
    Modifying u-boot and booting:
    insert the sd card in the tvbox and then go to the update and backup app and select zip file to update from and choose aml_autoscript.zip that is on the root of the sd card, the device should reboot and you should now be able to use the multiboot function
     
    UPDATE: after booting into the distro disable the resize2fs service using the following command
     
    sudo systemctl disable resize2fs Notes(mostly for other developers):
    1-I’m a very bad shell programmer, I mostly used snippet from stackoverflow to write the main script (bin/wselector) if you could improve the script or anything in my method that would be appreciated.
    2-boot time is very good but there is always a possibility to improve it, somethings that I can think of are:
    -buiding a smaller kernel by disabling everything in the kernel except for the framebuffer,mmc and nand driver, fat32 and ext4 filesystem,unfortunately whenever I disable something in the kernel it fails to build
    -maybe building a minimum dtb file so that the kernel doesn’t spend time initializing peripherals we don’t need.
    -building all binaries in umbInitrd staticaly
     
  21. Like
    talraash reacted to balbes150 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    A little test of the effectiveness of active cooling and the potential use as a media center with KODI. Install network of rap KODI (15.2). Prescribed in the file .xinitrc to run KODI (straight run only KODI, without DM). Started the system from USB stick on i7Pro (PCB without housing, standard radiator + USB fan with separate power supply). Mode 720. Playback test clips (from the image Armbian) occurs in fullscreen mode. The smoothness of the video is not the best, but I was interested in temperature. Connection via UART console , run "armbian -m". Monitoring shows the average temperature when playing video 49-55 Degrees, a frequency of about 2000. The temperature in the idle drops to 35-38 degrees (at a frequency of 250). Thus it is possible to consider this option - a very early alpha for Libreelec on the basis of the usual  Ubuntu, with advantages in a standard package management system and the ability to run as required graphical desktop (XFCE MATE DM etc) with all the advantages of standard office systems. I think if we solve the problem of not properly start the graphical environment for the authorization of entrance and selection of used DM (xdm lightdm lxdm etc), then you can create an easy to use universal system. If you need media center - chose KODI (or other similar systems), you need the desktop version - chose a convenient DM (XFCE MATE KDE, LXQT LXDM etc). 
  22. Like
    talraash reacted to RagnerBG in Orange Pi PC newer MPV versions?   
    The problem is not player related. On older architectures - A10/20 there is OSD and subtitles are fine. On H3>, software solution is used, through Pixman and there is this bug. I thought Pixman is causing the bug i tried to install different versions, but players always used built in version. I didn't thought it could be libvdpau-sunxi issue itself, this is beyond my potentialities. But it's definitely not player issue.
  23. Like
    talraash reacted to balbes150 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    Program to capture video "kazam" (under multimedia).
  24. Like
    talraash got a reaction from balbes150 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    Test new image 20170202 CPU_OVERCKLOCK scaling work good out of box, but i don't see any performance(and temperature, of course we know it few months from  odroid forum) difference between cpufreq_max = 2GHz, 1.75 and 1.53.
    Some sysbench tests...
     
     
    in some scenarios, some advantage give "performance" governor, but it's hot by 1-2 degree in idle.
     
    P.S. Balbes150, what soft do you use to capture video from tvbox?
  25. Like
    talraash reacted to balbes150 in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    Update images (3.14.29 20170201).
     
    Changes.
     
    1. Updated kernel (frequency range limited to 500 - 1536)
    2. Added the package gparted in the desktop version
    3. Fixed setting in the inner memory
    4. Fixed auto-using dtb from the internal memory
    5. Added dtb file for VIM Khadas
    6. Fixed reboot mode
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines