New Bionic version of Armbian Media Script

[JMCC]

Hello everyone. The Armbian community is pleased to announce the Bionic release of Armbian media script. The script is intended to be run on Armbian Bionic Default, and will provide several multimedia enhancements, such as:

• Full 3D acceleration: OpenGL-ES 3.1, WebGL in Chromium, and OpenGL 2.0 via GL4ES wrapper.
  
• OpenCL support.
  
• Video playing acceleration, through Gstreamer, MPV and Kodi 18.0b3. All three players support smooth 4K video playing. Chromium can also play up to 1080p smoothly.
  
• Some other tweaks and enhancements.
  

DOWNLOAD LINKS:

Armbian TinkerBoard Bionic Default desktop image: https://dl.armbian.com/tinkerboard/Ubunt...desktop.7z

Media script forum thread (with instructions, documentation and download link): https://forum.armbian.com/topic/7262-rk3...oard-miqi/

[jschwart]

This one doesn't boot for me (either) when putting it on a 64GB SD card. (Tinker OS does boot from this card, I put it back after everything else I tried failed to boot up.)

[igorpec]

> This one doesn't boot for me

Can you describe non-booing process in details.

How long do you wait? Expanding of 64GB SD card, which happens in 1st boot, can take up to 6 minutes (with latest Samsung 64GB EVO which is among fastest cards) and there is nothing on the screen besides blinking cursor. All output goes to the serial console ... this will be changed in new builds.

[jschwart]

Hi, I guess this might explain why Android didn't appear to boot either. Somehow Tinker OS manages to do this much a lot faster. I will try again and let it sit for some time. Thanks a lot for this info!!

[igorpec]

> Somehow Tinker OS manages to do this much a lot faster.

Much faster is "no root expand" which is used by Tinker OS, Raspbian, ... They rely that you will expand partition to SD card's full size ... or use just a preset (usually 4-8GB) small part of the SD card for the system until you ran out of space.

[jschwart]

Tinker OS shows me this:

Code:

linaro@tinkerboard:~$ sudo fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mmcblk1: 14.7 GiB, 15758000128 bytes, 30777344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x17e72516

Device         Boot  Start     End Sectors Size Id Type
/dev/mmcblk1p1        8192  139263  131072  64M  c W95 FAT32 (LBA)
/dev/mmcblk1p2      139264 4333567 4194304   2G 83 Linux




Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0: 60 GiB, 64424509440 bytes, 125829120 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x58bc1052

Device         Boot  Start       End   Sectors Size Id Type
/dev/mmcblk0p1        8192    139263    131072  64M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      139264 125829119 125689856  60G 83 Linux
linaro@tinkerboard:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        59G  2.5G   55G   5% /
devtmpfs        943M     0  943M   0% /dev
tmpfs          1007M     0 1007M   0% /dev/shm
tmpfs          1007M   17M  990M   2% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs          1007M     0 1007M   0% /sys/fs/cgroup
/dev/mmcblk0p1   63M  7.5M   56M  12% /boot
tmpfs           202M  8.0K  202M   1% /run/user/1000

So I guess it manages to do the expansion with a trick that's faster, but I'll try these images again. Thanks for the info!

Btw. are there currently any advantages with the older kernel version versus the newer one? I think there are also images on the Armbian site based on 4.14 instead of 4.4.

[Z80]

Armbian Bionic seems really fast, Youtube now plays fine, could not get netflix to work.
Tempted to keep using bionic over tinker board OS , will see how it goes, was having the odd freeze with tinker os

[igorpec]

So I guess it manages to do the expansion with a trick that's faster

TinkerOS way:
https://github.com/TinkerBoard/tinker-co...#L380-L413


Armbian way:
https://github.com/armbian/build/blob/ma...filesystem
is much more advanced and some additional safety measures are involved, but it can be optimised.

[jschwart]

Is there a way to see the progress output without using the GPIO pins? I am waiting >30 minutes now and I still do not see anything appear with Armbian.

[igorpec]

Is there a way to see the progress output

Via serial console, described at https://www.armbian.com/tinkerboard/

Powering via GPIO pins is OS independent recommendation. ASUS will tell you to use their cables and their PSU, which solves some problems ...

We wrote that to rule out possible problems which is in our common interest.

If you can't boot (tested) images, you must have miss some crucial part. From your very brief description I can only guess but with guessing we will waste a lot of time.

If you want to run Armbian, start from here and follow (OS independent) instructions: https://docs.armbian.com/User-Guide_Getting-Started/ 

Even you follow instructions, there might be some weird things ... but if you don't follow them, you will almost certainly run into random problems.

We have our own support forum section for Tinkerboard and similar boards: https://forum.armbian.com/forum/21-rockchip-3288-3328/ and when you approach with a problem, you need to provide as much information as possible. This is the only way that someone is able to provide any help. It you say "I installed Armbian and it doesn't work" tells exactly nothing. Nobody can help you. There are different versions, different methods of writing to SD card, different SD cards, different powering, ...