Single Armbian image for RK + AML + AW (aarch64 ARMv8)


balbes150

Recommended Posts

Donate and support the project!

13 hours ago, balbes150 said:

How long do you wait for the launch ?

Which image (exact name) runs normally on your model ?

Hi @balbes150,

i have waited from 2-3 minutes up to 20-30 minutes just to see if something happen, if can help, my monitor tell me that is out of range...

I don't remember the exact image name but in the past i have used many images from this thread without hassle

yesterday i have tried also one of this images but without success, i also have tried LE from the above thread, no success

What are the differences between these images and the new unified images? Are those still being mantained?

It's frustrating...

 

Thanks again!

 

Link to post
Share on other sites
6 minutes ago, Beppe said:

yesterday i have tried also one of this images but without success, i also have tried LE from the above thread, no success

What are the differences between these images and the new unified images? Are those still being mantained?

It's frustrating...

Hmm. Now I checked the latest image with the 5.6 core on my MX10. Recorded the Armbian image with Rosa imagewriter on the SD card. I downloaded the u-boot-3328-mvr file and also recorded it on the same SD card with the Rosa imagewriter program. Opened the file (uEnv.txt) in the text editor changed the settings for rk3328 (commented lines from rk3399 and removed comments from lines for rk3328). I connected the SD card to the MX10, turned on the power, and the system started normally. Show the you contents (uEnv.txt) after setting up. And use the program to write the image and file u-boot (don't use DD).

 

Link to post
Share on other sites
6 hours ago, balbes150 said:

Hmm. Now I checked the latest image with the 5.6 core on my MX10. Recorded the Armbian image with Rosa imagewriter on the SD card. I downloaded the u-boot-3328-mvr file and also recorded it on the same SD card with the Rosa imagewriter program. Opened the file (uEnv.txt) in the text editor changed the settings for rk3328 (commented lines from rk3399 and removed comments from lines for rk3328). I connected the SD card to the MX10, turned on the power, and the system started normally. Show the you contents (uEnv.txt) after setting up. And use the program to write the image and file u-boot (don't use DD).

 

Hi @balbes150, i have done exactly what you told me but no success, attached my screenshots and uEnv.txt

1.png

2.png

3.png

4.png

5.png

6.png

uEnv.txt

Link to post
Share on other sites
1 hour ago, Beppe said:

i have done exactly what you told me but no success, attached my screenshots and uEnv.txt

Do you have any Armbian or LE system that can now work on your TV box from an SD card ? I can suggest that there is a problem with either the card reader or the SD card. By the way, do you have a full-size SD card or micro SD card with an adapter ? You need to check the launch from the USB flash drive. Write the image to a USB flash drive, configure the DTB, connect the previously prepared SD card and USB flash drive together, and turn on the power.

Link to post
Share on other sites
2 hours ago, balbes150 said:

version 20200329

I don’t keep up with you - while I am testing one version, you have already made the following.. :)

Kodi in version  Armbian_20.05.0_Arm-64_buster_current_5.6.0-rc6_desktop_20200328

 

 

Edited by ikkipapir
ad info to version
Link to post
Share on other sites

I'm here again.

At the end I have installed this Armbian_20.05.0_Arm-64_buster_current_5.6.0-rc6_desktop_20200329.img

 

All works: audio by HDMI, wifi, LAN and bt.

 

Anyway the test video and other video that i play in full screen are very slow and laggy..

I'm not an expert in this, but is it possible solve this problem?

 

Inviato dal mio Redmi Note 5 utilizzando Tapatalk

 

 

 

 

Link to post
Share on other sites

just installed Armbian_20.05.0_Arm-64_bullseye_current_5.6.0-rc6_20200326.img.xz on beelink gt-1 (amlogic s912) with FDT=/dtb/amlogic/meson-gxm-q200.dtb and.. all works! but until i'm trying to upgrade or some packages to upgrade some of system libs.. lan dont working (cable, wifi working). in dmesg  there's lines

[ 2590.051321] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
[ 2590.051343] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)

 

last thing before its became broken was upgrading: sudo apt-get install binutils (full log in spoiler

Spoiler

user@arm:~$  sudo apt-get install binutils
[sudo] password for hotery:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 binutils : Depends: binutils-aarch64-linux-gnu (= 2.34-5) but 2.34-4 is to be installed
 binutils-aarch64-linux-gnu : Depends: binutils-common (= 2.34-4) but 2.34-5 is to be installed
                              Depends: libbinutils (= 2.34-4) but 2.34-5 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
user@arm:~$  apt-mark unhold binutuls-aarch64-linux-gnu
E: Unable to locate package binutuls-aarch64-linux-gnu
E: No packages found
user@arm:~$  apt-mark unhold binutils-aarch64-linux-gnu
dpkg: error: required read/write access to the dpkg database directory /var/lib/dpkg
E: Sub-process dpkg --set-selections returned an error code (2)
E: Executing dpkg failed. Are you root?
user@arm:~$  sudo apt-mark unhold binutils-aarch64-linux-gnu
Canceled hold on binutils-aarch64-linux-gnu.
user@arm:~$  sudo apt-get install binutils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  libprocps7
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  binutils-aarch64-linux-gnu binutils-common libbinutils libctf0
Suggested packages:
  binutils-doc
The following packages will be upgraded:
  binutils binutils-aarch64-linux-gnu binutils-common libbinutils libctf0
5 upgraded, 0 newly installed, 0 to remove and 13 not upgraded.
Need to get 4,570 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://httpredir.debian.org/debian bullseye/main arm64 libctf0 arm64 2.34-5 [41.7 kB]
Get:2 http://httpredir.debian.org/debian bullseye/main arm64 binutils-aarch64-linux-gnu arm64 2.34-5 [1,936 kB]
Get:3 http://httpredir.debian.org/debian bullseye/main arm64 libbinutils arm64 2.34-5 [470 kB]
Get:4 http://httpredir.debian.org/debian bullseye/main arm64 binutils arm64 2.34-5 [59.0 kB]
Get:5 http://httpredir.debian.org/debian bullseye/main arm64 binutils-common arm64 2.34-5 [2,063 kB]
Fetched 4,570 kB in 10s (445 kB/s)
(Reading database ... 37614 files and directories currently installed.)
Preparing to unpack .../libctf0_2.34-5_arm64.deb ...
Unpacking libctf0:arm64 (2.34-5) over (2.34-4) ...
Preparing to unpack .../binutils-aarch64-linux-gnu_2.34-5_arm64.deb ...
Unpacking binutils-aarch64-linux-gnu (2.34-5) over (2.34-4) ...
Preparing to unpack .../libbinutils_2.34-5_arm64.deb ...
Unpacking libbinutils:arm64 (2.34-5) over (2.34-4) ...
Preparing to unpack .../binutils_2.34-5_arm64.deb ...
Unpacking binutils (2.34-5) over (2.34-4) ...
Preparing to unpack .../binutils-common_2.34-5_arm64.deb ...
Unpacking binutils-common:arm64 (2.34-5) over (2.34-4) ...
Setting up binutils-common:arm64 (2.34-5) ...
Setting up libbinutils:arm64 (2.34-5) ...
Setting up libctf0:arm64 (2.34-5) ...
Setting up binutils-aarch64-linux-gnu (2.34-5) ...
Setting up binutils (2.34-5) ...
Processing triggers for libc-bin (2.29-10) ...
Processing triggers for man-db (2.9.1-1) ...

 

things like apt-cache showpkg libbinutils or sudo apt-get install binutils-aarch64-linux-gnu-2.34.4 gives nothing, and in http://ftp.debian.org/debian/pool/main/b/binutils/ no such version.  but maybe thats not a reason of broken lan.. please help to repair it..

Link to post
Share on other sites
10 hours ago, ikkipapir said:

Kodi in version  Armbian

KODI from network repositories does not have HW, so it will run slowly.

 

10 hours ago, emmezeroline said:

Anyway the test video and other video that i play in full screen are very slow and laggy..

I'm not an expert in this, but is it possible solve this problem?

The S905X without HW can provide full-screen video at a resolution of no more than 720p. If you want to watch a full-screen video with a different resolution, either build and add components with HW yourself, or use Libreelec (it supports 4K video).

 

8 hours ago, thehotery said:

but maybe thats not a reason of broken lan.

You need the correct DTB.

Link to post
Share on other sites

Screenshot_2020-03-30_13-58-06.png.e50526396ec372c5b2868f9fedf50c71.png

Some kernel process has been going on using cpu for a while now. Anyone know how to track it down?

Armbian_20.05.0_Arm-64_bionic_legacy_5.6.0-rc7_desktop_20200324

 

It has settled down now, no clue what caused it

Edited by amirul
update
Link to post
Share on other sites
On 3/30/2020 at 3:14 PM, balbes150 said:

 

The S905X without HW can provide full-screen video at a resolution of no more than 720p. If you want to watch a full-screen video with a different resolution, either build and add components with HW yourself, or use Libreelec (it supports 4K video).

 

Hi, It looks like Kernel 5.7 will get HW acceleration.  Can you make image with 5.7 RC1?

Link to post
Share on other sites
3 minutes ago, psxsnake said:

what you mean? becouse the "appropriate script" should be armbian-config, in according with document page

https://docs.armbian.com/User-Guide_Armbian-Config/

but this 20.05 version doesnt have the part with INSTALL ON NAND

The standard armbian documentation only applies to the standard armbian builds.  The builds by balbes150 in this thread are a fork of the standard armbian code and therefore you can't use the standard documentation.  Look in your /root directory as I indicated and you will see the install script you need to run for installation into emmc.

Link to post
Share on other sites
2 minutes ago, SteeMan said:

The standard armbian documentation only applies to the standard armbian builds.  The builds by balbes150 in this thread are a fork of the standard armbian code and therefore you can't use the standard documentation.  Look in your /root directory as I indicated and you will see the install script you need to run for installation into emmc.

i can't find... my root of sd is this... (ssh on box)

 

root@arm-64:~# ls -lrt /
total 64
dr-xr-xr-x 284 root root     0 Jan  1  1970 proc
drwxr-xr-x   5 root root  4096 Jan  1  1970 boot
dr-xr-xr-x  12 root root     0 Jan  1  1970 sys
lrwxrwxrwx   1 1023 1023     7 Mar 19 06:48 bin -> usr/bin
lrwxrwxrwx   1 1023 1023     8 Mar 19 06:48 sbin -> usr/sbin
lrwxrwxrwx   1 1023 1023     7 Mar 19 06:48 lib -> usr/lib
drwxr-xr-x   2 1023 1023  4096 Mar 19 06:48 mnt
drwxr-xr-x   2 1023 1023  4096 Mar 19 06:48 srv
drwxr-xr-x   2 1023 1023  4096 Mar 19 06:48 opt
drwxr-xr-x   2 1023 1023  4096 Mar 19 06:48 media
drwxr-xr-x  10 1023 1023  4096 Mar 19 06:48 usr
drwxrwxr-x   2 1023 1023  4096 Mar 26 07:32 selinux
drwxr-xr-x  12 1023 1023  4096 Mar 26 07:33 var
drwx------   2 1023 1023 16384 Mar 26 07:56 lost+found
drwxr-xr-x   3 1023 1023  4096 Apr  1 15:29 home
drwxr-xr-x  18 root root  4380 Apr  1 15:29 dev
drwx------   5 1023 1023  4096 Apr  1 15:29 root
drwxr-xr-x 114 1023 1023  4096 Apr  1 15:34 etc
drwxrwxrwt   8 root root  4096 Apr  1 15:39 tmp
drwxr-xr-x  25 root root   820 Apr  1 15:46 run
root@arm-64:~#

Link to post
Share on other sites

ok i got it

:)

you mean /root/

root@arm-64:~# ls -lrt /root/
total 56
-rwxr-xr-x 1 1023 1023 4559 Mar 26 07:53 install-rk3399.sh
-rwxr-xr-x 1 1023 1023 4695 Mar 26 07:53 install-rk3399-nanopct4-nvme.sh
-rwxr-xr-x 1 1023 1023 2899 Mar 26 07:53 install-rk3399-rockpi4-nvme.sh
-rwxr-xr-x 1 1023 1023 4559 Mar 26 07:53 install-rk3328.sh
-rwxr-xr-x 1 1023 1023 4399 Mar 26 07:53 install-aml.sh
-rwxr-xr-x 1 1023 1023 4033 Mar 26 07:53 install-aml-s905-emmc.sh
-rwxr-xr-x 1 1023 1023 4510 Mar 26 07:53 install-aw.sh
-rw-r--r-- 1 1023 1023  261 Mar 26 07:53 fstab
drwxrwxr-x 6 1023 1023 4096 Mar 26 07:53 u-boot

Link to post
Share on other sites
20 minutes ago, psxsnake said:

what you mean? becouse the "appropriate script" should be armbian-config, in according with document page

https://docs.armbian.com/User-Guide_Armbian-Config/

but this 20.05 version doesnt have the part with INSTALL ON NAND

This is the Armbian-TV version. It has a number of differences that are specially made to support TV boxes. First of all, you need to look at the information in the first message of this topic (there are differences from the official version).

 

 

Link to post
Share on other sites
19 minutes ago, psxsnake said:

If I wanna change build, i cannot do update from sd as before so how i proceed?

I'm not sure what you mean by change build.  So I will try to answer the best I can.  Once you have installed a build onto internal storage, you would use the distribution tools to get updates for all of the software packages (i.e. apt update/upgrade).  This will get you patches for everything except the linux kernel.  You are currently stuck at the linux kernel you installed as there aren't currently kernel updates automatically provided via apt for the Armbian TV builds  So to get kernel updates you would either need to completely reinstall everything from a new sd card build, or build your own kernel from source and install it manually.

Link to post
Share on other sites
1 hour ago, SteeMan said:

This will get you patches for everything except the linux kernel.

Updating the kernel works the same way. But before updating it, you need to manually rename the /boot/dtb directory to /boot/dtb-old. And then you can run the standard upgrade procedure (apt upgrade). The kernel will update automatically. This only works for those who have correctly configured the DTB in a text file (uEnv.txt) and did not add its own DTB  to  manual (which is not supported in the kernel).

Link to post
Share on other sites
2 hours ago, SteeMan said:

I'm not sure what you mean by change build.  So I will try to answer the best I can.  Once you have installed a build onto internal storage, you would use the distribution tools to get updates for all of the software packages (i.e. apt update/upgrade).  This will get you patches for everything except the linux kernel.  You are currently stuck at the linux kernel you installed as there aren't currently kernel updates automatically provided via apt for the Armbian TV builds  So to get kernel updates you would either need to completely reinstall everything from a new sd card build, or build your own kernel from source and install it manually.

Yes this i know via apt

but If I wanna change from buster to bionic or focal?

Link to post
Share on other sites
38 minutes ago, psxsnake said:

Yes this i know via apt

but If I wanna change from buster to bionic or focal?

You would repeat the process you just completed.  Create a new sdcard with the desired distribution, then copy that to internal emmc with the provided scripts in the /root directory.  If you boot the box with the sd card inserted, the box will boot from the sd card, thus allowing you to overwrite the contents of the internal emmc.

Link to post
Share on other sites
On 3/30/2020 at 2:00 PM, amirul said:

Screenshot_2020-03-30_13-58-06.png.e50526396ec372c5b2868f9fedf50c71.png

Some kernel process has been going on using cpu for a while now. Anyone know how to track it down?

Armbian_20.05.0_Arm-64_bionic_legacy_5.6.0-rc7_desktop_20200324

 

It has settled down now, no clue what caused it

 

seems to happen after every reboot. Odd

Link to post
Share on other sites
On 3/29/2020 at 6:51 PM, balbes150 said:

Do you have any Armbian or LE system that can now work on your TV box from an SD card ? I can suggest that there is a problem with either the card reader or the SD card. By the way, do you have a full-size SD card or micro SD card with an adapter ? You need to check the launch from the USB flash drive. Write the image to a USB flash drive, configure the DTB, connect the previously prepared SD card and USB flash drive together, and turn on the power.

Hi @balbes150,

no, i don't have any system that actually work on my MX10...
i have a microSD with an adapter, and i have tried to write image from another PC and consequently from another sd card writer just to see if that can be the problem,

tried also the sd + USB option but nothing...

The only thing that has changed since it worked is that the tv box has been (Officially) updated from Android 8.1 to Android 9 ... could this be the problem?

 

Thaks for all @balbes150!

Link to post
Share on other sites
On 4/2/2020 at 10:31 AM, Beppe said:

The only thing that has changed since it worked is that the tv box has been (Officially) updated from Android 8.1 to Android 9 ... could this be the problem?

You could not immediately write that your firmware has changed ? I spent a lot of time on unnecessary checks. The new firmware is a different u-boot that is not known to work. Without output from the UART console, I can't help you in any way.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...