Jump to content

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


balbes150

Recommended Posts

19 minutes ago, SteeMan said:

Without any information about what box you have or what version you are working with, there isn't enough information to answer your question.  I will however add my general observation that the answer is "maybe but probably not".  For example I don't have any working audio on any of the boxes I am running (not even under HDMI, let alone optical).  I consider working audio in these builds on most boxes to be something you are lucky to have working, but don't expect it to work.  (Much like wifi and bluetooth generally don't work on many boxes, and people shouldn't expect them to work).

You are mistaken, when using the latest armbian-TV 20.05 images (please note, not just take the core, but use a specially assembled and configured image), the HDMI sound works on all models of RK AW AML. SPDIF output I don't check (I don't have such hardware)

 

@Beppe @jeanrhum

Do not clog the topic, do not profile discussions - in a personal account, or in a separate topic. Your messages will be removed from this topic.

Link to comment
Share on other sites

Now I started checking the latest image on RockPI 4 (RK3399) and found that starting from a USB flash drive works fast (there is no longer a long timeout when unpacking uInitrd). Perhaps I made a mistake, please check on the available RK3399.

Link to comment
Share on other sites

27 minutes ago, balbes150 said:

You are mistaken, when using the latest armbian-TV 20.05 images (please note, not just take the core, but use a specially assembled and configured image), the HDMI sound works on all models of RK AW AML. SPDIF output I don't check (I don't have such hardware)

 

@Beppe @jeanrhum

Do not clog the topic, do not profile discussions - in a personal account, or in a separate topic. Your messages will be removed from this topic.

Oh thanks! Where I can found the TV image? I realy appreciate your work

Link to comment
Share on other sites

Hello, I have installed the lastest image posible at today (Armbian_20.05.2_Arm-64_bionic_current_5.7.0-rc1_desktop_20200416) (meson-gxm-q200.dtb) in a H96 Pro Plus 3GB/32GB (S912). It works very well (I use ethernet, I don't know if wifi works), but if I executed glxinfo:

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: VMware, Inc. (0xffffffff)
    Device: llvmpipe (LLVM 9.0, 128 bits) (0xffffffff)
    Version: 19.2.8
    Accelerated: no
    Video memory: 2741MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 3.3
    Max compat profile version: 3.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0

Is this normal? Accelerated: no 

Is graphics driver (GPU Mali 820) installed?

I have read about "Panfrost". Is posible install Panfrost? How?

 

Thank you very much.

Link to comment
Share on other sites

On 3/6/2020 at 4:37 PM, balbes150 said:

The images are compatible , but if you have s905 (not s905x), you probably won 't be able to install the system on eMMC, because many s905s have too old u-boot, it can 't work with the new kernel.


Beelink MiniMX S905 1G/8G.  Running Armbian on SD.

If I try to install on eMMC , will it brick the box or it will not work?

Link to comment
Share on other sites

2 hours ago, balbes150 said:

You are mistaken, when using the latest armbian-TV 20.05 images (please note, not just take the core, but use a specially assembled and configured image), the HDMI sound works on all models of RK AW AML. SPDIF output I don't check (I don't have such hardware)

I will retest.  When I tested last week, I didn't have any audio on my boxes.  I had assumed this was because you were still working on the changes you were making.  But now that you are done with these changes and expect it to work, I will retest and let you know the results.

Link to comment
Share on other sites

1 hour ago, Alessandro Salgoni said:

I don't found Armbian TV image for Amlogic :(

Per the topic of this thread the 'arm-64' images support all three chipsets (rockchip, allwinner, amlogic).  Just follow the instructions in the first post of this thread.  

Link to comment
Share on other sites

Hello balbes150
Thank you for the Armbian firmware provided, so that my PHICOMM N1 box can continue to work again! In the forum, some people feedback that the default "meson-gxl-s905d-phicomm-n1.dtb" load is a bit high, you need to edit the arch / arm64 / boot / dts / amlogic / meson-gxl-s905d-p230.dts file
interrupts = <29 IRQ_TYPE_LEVEL_LOW>;
change into
interrupts = <25 IRQ_TYPE_LEVEL_LOW>;
During the compilation, I am a rookie and I do n’t quite understand the reason for this operation. If this operation is correct, can you consider modifying the default configuration in your firmware?

Link to comment
Share on other sites

5 hours ago, 王艳军 said:

During the compilation, I am a rookie and I do n’t quite understand the reason for this operation. If this operation is correct, can you consider modifying the default configuration in your firmware?

I don't have such hardware, this DTB is provided by another user. You need to contact him. And the best solution is to send all patches directly to the main kernel.

Link to comment
Share on other sites

Hello,
I am trying to install on rk3328.
I downloaded the rk3328-mvr9 image but I don't know how to do it with the commands:
dd if = u-boot-rk3328-mvr9.img of = / dev / <SD_card> conv = fsync bs = 1 count = 442
and
dd if = u-boot-rk3328-mvr9.img of = / dev / <SD_card> conv = fsync bs = 512 skip = 1 seek = 1


on windows with cmd ?
on mac with terminal ?

Link to comment
Share on other sites

3 hours ago, almotra said:

Hello,
I am trying to install on rk3328.
I downloaded the rk3328-mvr9 image but I don't know how to do it with the commands:
dd if = u-boot-rk3328-mvr9.img of = / dev / <SD_card> conv = fsync bs = 1 count = 442
and
dd if = u-boot-rk3328-mvr9.img of = / dev / <SD_card> conv = fsync bs = 512 skip = 1 seek = 1


on windows with cmd ?
on mac with terminal ?

If you have access to the terminal app on a mac then you can do the following:

1) Identify the correct disk that your sd card is mounted as:

  diskutil list

(from the output find the SD card mounted as /dev/disk<n>? where <n> is the number of the mount i.e. /dev/disk2 or /dev/disk3)

2) Unmount the disk

  diskutil unmountDisk /dev/disk<n>

3) Copy the image to the SD card

  sudo dd if=u-boot-<model>.img of=/dev/disk<n> bs=1 count=442

  sudo dd if=u-boot-<model>.img of=/dev/disk<n> bs=512 skip=1 seek=1

  sync

4) Safely eject the SD card

 

(I don't use windows so I can't give you instructions for that environment)

Link to comment
Share on other sites

On 4/15/2020 at 6:40 PM, balbes150 said:

If you don't run any pirate shit and follow the instructions exactly, after a one-time activation of the multi-boot, it is saved, including after installing the system in eMMC (this means that starting from USB works after installing the system correctly in eMMC). No compression is required at all.

Apparently doesn't work for my device. Stock android of my device doesn't support multi-boot, until flashing a 3rd party rom. But after installing armbian to emmc it doesn't work again.

Shrink image is not compression. It is not required, but a good practice. Refer to official Armbian release or other projects.

Link to comment
Share on other sites

1 hour ago, Binbin Qian said:

Stock android of my device doesn't support multi-boot

UART log and output of printenv commands.

 

1 hour ago, Binbin Qian said:

Shrink image is not compression. It is not required, but a good practice. Refer to official Armbian release or other projects.

If you don't know why it was done this way, it's better not to write and make erroneous conclusions.

Link to comment
Share on other sites

16 hours ago, SteeMan said:

If you have access to the terminal app on a mac then you can do the following:

1) Identify the correct disk that your sd card is mounted as:

  diskutil list

(from the output find the SD card mounted as /dev/disk<n>? where <n> is the number of the mount i.e. /dev/disk2 or /dev/disk3)

2) Unmount the disk

  diskutil unmountDisk /dev/disk<n>

3) Copy the image to the SD card

  sudo dd if=u-boot-<model>.img of=/dev/disk<n> bs=1 count=442

  sudo dd if=u-boot-<model>.img of=/dev/disk<n> bs=512 skip=1 seek=1

  sync

4) Safely eject the SD card

 

(I don't use windows so I can't give you instructions for that environment)

Thank you @SteeMan,

I managed to start on my h96max+

Now I am trying to boot on an X96max S905X2, I have tried all the .dtb, some boot but no Ethernet.

Anyone have a .dtb that works with the latest .img armbian?

I got there with the old .img but not with the new .img

 

Alex

Link to comment
Share on other sites

3 hours ago, almotra said:

I managed to start on my h96max+

Good to hear you got that working.

 

 

3 hours ago, almotra said:

Now I am trying to boot on an X96max S905X2, I have tried all the .dtb, some boot but no Ethernet.

Anyone have a .dtb that works with the latest .img armbian?

I am successfully using yesterday's build (20200417) on my H96 Max X2 (which is S905X2 based) with the meson-g12a-x96-max-rmii.dtb

You indicate that this was working for you in the past, what was the last build you were successful in running and what dtb file were you using then?

Link to comment
Share on other sites

I am trying to see if I can turn my X3-Plus ( S905X3 ) can run Armbian_20.05.2_Arm-64_bionic_current_5.7.0-rc1_desktop_20200418.img as a digital music computer for MIDI application. I tried meson-sm1-sei610.dtb, the sound is working but 'aconnect -l' shows 

 

reggie@arm-64:~$ aconnect -l
ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
can't open sequencer
 

How to fix it?

 

Thanks for the hard work.

Link to comment
Share on other sites

14 hours ago, SteeMan said:

I managed to start on my h96max+

 

Now I am trying to boot on an X96max S905X2, I have tried all the .dtb, some boot but no Ethernet.

Anyone have a .dtb that works with the latest .img armbian?

Hello @SteeMan

You succeeded on h96 max x2, me it's X96 max x2.

I used with the old stretch version, 4.78 or 5.78, I don't know and I didn't keep them.

With .img aml 5.5.0-rc1_20200205, the box starts but no Ethernet.

With .img 5.6.2_20200408, it starts and remains blocked on "flush journal to persistent storage". I have tried all .dtb G12a.

 

Link to comment
Share on other sites

Hello @balbes150,

 

I am in 5.6.2 buster no desktop

after apt-get update and apt-get upgrade, unable to restart on emmc .

During apt-get upgrade, I see that it changes u-boot, it may be the problem :

 

Get:1 https://apt.armbian.com buster/main arm64 linux-image-current-arm-64 arm64 20.05.2 [34.0 MB]

Fetched 42.2 MB in 14s (2,953 kB/s)                                                                                                                                  

(Reading database ... 34130 files and directories currently installed.)

Preparing to unpack .../libgnutls30_3.6.7-4+deb10u3_arm64.deb ...

Unpacking libgnutls30:arm64 (3.6.7-4+deb10u3) over (3.6.7-4+deb10u2) ...

Setting up libgnutls30:arm64 (3.6.7-4+deb10u3) ...

(Reading database ... 34130 files and directories currently installed.)

Preparing to unpack .../git-man_1%3a2.20.1-2+deb10u2_all.deb ...

Unpacking git-man (1:2.20.1-2+deb10u2) over (1:2.20.1-2+deb10u1) ...

Preparing to unpack .../git_1%3a2.20.1-2+deb10u2_arm64.deb ...

Unpacking git (1:2.20.1-2+deb10u2) over (1:2.20.1-2+deb10u1) ...

Preparing to unpack .../linux-image-current-arm-64_20.05.2_arm64.deb ...

update-initramfs: Deleting /boot/initrd.img-5.6.2-arm-64

Unpacking linux-image-current-arm-64 (20.05.2) over (20.05.1) ...

Setting up linux-image-current-arm-64 (20.05.2) ...

update-initramfs: Generating /boot/initrd.img-5.7.0-rc1-arm-64

W: Couldn't identify type of root file system for fsck hook

update-initramfs: Converting to u-boot format

Link to comment
Share on other sites

2 hours ago, almotra said:

after apt-get update and apt-get upgrade, unable to restart on emmc .

During apt-get upgrade, I see that it changes u-boot, it may be the problem :

u-boot has nothing to do with this. Most likely, before starting the installation in eMMC, the source system on external media was not configured correctly (DTB is used not from the image, with manual copying). Or other changes were made to the installation procedure. Show the content (uEnv.txt) from eMMC.

Link to comment
Share on other sites

1 hour ago, balbes150 said:

u-boot n'a rien à voir avec ça. Très probablement, avant de démarrer l'installation dans eMMC, le système source sur un support externe n'était pas configuré correctement (DTB n'est pas utilisé à partir de l'image, avec copie manuelle). Ou d'autres modifications ont été apportées à la procédure d'installation. Affichez le contenu (uEnv.txt) de eMMC.

 

All work very well before update.

In my previous message, we see that the update removes /boot/initrd.img-5.6.2-arm-64 and recreate /boot/initrd.img-5.7.0-rc1-arm-64

When I put a sd, with in uenv.txt (ROOT_EMMC) the box starts but blocks on mnt/boot and it puts in maintenance

I have this problem with x96max + and H96max +, but not with x96mini.

 

I solved this problem in "armbian-config" puis "system and security setting" and "freeze" disable armbian upgrades

Link to comment
Share on other sites

Hello @balbes150,

 

I successfully installed Armbian 20.05.1 on my H96 pro + Alfawise tv box.
It works fine on my SD card. I wanted to install on the EMMC using the script /root/install-aml.sh.
It worked without error. I checked the partitions are well created and the files have been copied with the change of labels (ROOTFS to ROOT_EMMC).
When I want to boot on the EMMC without my sdcard the splash screen freeze (H96 Pro +). After if I restart on my SD card, the partitions of the EMMC returned as originally with Android (see below)

 

Disk /dev/mmcblk1: 29,1 GiB, 31272730624 bytes, 61079552 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: 0x00000000

Device          Boot   Start      End  Sectors  Size Id Type
/dev/mmcblk1p1             0     8191     8192    4M 83 Linux
/dev/mmcblk1p2         73728   204799   131072   64M 83 Linux
/dev/mmcblk1p3        221184  1269759  1048576  512M 83 Linux
/dev/mmcblk1p4       1269760 56344575 55074816 26,3G  5 Extended
/dev/mmcblk1p5       1286144  1302527    16384    8M 83 Linux
/dev/mmcblk1p6       1318912  1384447    65536   32M 83 Linux
/dev/mmcblk1p7       1400832  1466367    65536   32M 83 Linux
/dev/mmcblk1p8       1482752  1499135    16384    8M 83 Linux
/dev/mmcblk1p9       1515520  1531903    16384    8M 83 Linux
/dev/mmcblk1p10      1548288  1613823    65536   32M 83 Linux
/dev/mmcblk1p11      1630208  1695743    65536   32M 83 Linux
/dev/mmcblk1p12      1712128  1777663    65536   32M 83 Linux
/dev/mmcblk1p13      1794048  5988351  4194304    2G 83 Linux
/dev/mmcblk1p14      6004736 61079551 55074816 26,3G 83 Linux



Do you have any idea what is not working?

Thank you for your help

Link to comment
Share on other sites

HW: Beecool M8S Pro L S912 3G 16G DDR3 LB

 

Created sd card from latest arbian buster image with etcher and tried to boot it. Sadly the bootlogo keeps flickering.  Updating via Stock Rom throws the error mentioned here:  https://forum.armbian.com/topic/12988-armbian-for-amlogic-s905x3/?do=findComment&comment=94956

E:Map of '@/cache/recovery/block.map' failed 
E:failed to map file 
Installation aborted

If i got the instructions right i dont need to dd a uboot image to sd-card. I adjusted uEnv.txt to use meson-gxm-q201 or 200 dtb but that didnt work. under android it shows me the following DTB-ID

gxm-q20xrmii_3g

any tips you could give me?

Link to comment
Share on other sites

On 4/12/2020 at 12:22 AM, imrannaqvi83 said:

Hi Everyone,

I have Sunvell Q Plus Allwinner H6 soc with 4GB/32GB, i am trying to install armbian (Armbian_20.05.0_Arm-64_buster_current_5.6.0-rc6_20200403.img.xz) from sd-card.

One quirk about this device is that reset button doesnot work, its rooted and so i can go to shell and type su, reboot recovery to go to recovery but that is not much helpfull to me, or i don't know if it is useful.

 

What i did so far.

 

  1. written Armbian_20.05.0_Arm-64_buster_current_5.6.0-rc6_20200403.img.xz to sdcard in windows 10 using Win32diskImager.
  2. From sd-card, removed .aw from all 4 allwinnder files with replaced existing files.
  3. updated uEnv.txt to use
    • FDT=/dtb/allwinner/sun50i-h6-tanix-tx6.dtb
    • APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
  4. Did not knew what is the procedure is to writing uboot files so just copied (u-boot-allwinner-h6-tanix-tx6.img) to sd-card as u-boot.ext

But device is not booting from sd-card.

Please let me know if you need some other information, i am not sure about step 4 but i don't know what to do next.

 

I have a same box as yours. I use a dtb here , named eachlink h6 mini.dtb by @jernej

 

 

 

I write the @balbes150 's image to sd cards . The box boots with armbian , but cannot connect to the interent , by Ethernet or Wifi.  The system find no internet device.

 

So  is there any perfact dtb for this IMG , or any IMG for this dtb?

 

Thanks to @balbes150  and @jernej

 

Waiting for your responses

Edited by blh7855
spelling mistake
Link to comment
Share on other sites

I successfully installed Armbian_20.05.2_Arm-64_buster_current_5.7.0-rc1_20200418 on my khadas vim2.

 

Everything is ok except when I want to power it off.

 

It stays locked at this step:

 

Quote

detaching DM devices

 

I have to remove power or use reset button.

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines