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


Recommended Posts

2 hours ago, gabrielgbs97 said:

Is there the possibility to upgrade my S905 5.3 kernel to 5.7 without reflashing image?

Before updating , create a full backup to external media (using the ddbr utility). After that, you can update the kernel and make sure that the directory with DTB files has been updated BEFORE restarting.

 

8 minutes ago, czosnekltd said:

chance to rescue the box?

Recovery is only possible by closing contacts on eMMC.

Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?

Hi ;)
I need help please :) ( sorry for my bad english)

I have a Beelink GT1 and i want to install already install Armbian once, by now.... i forget what the file (version) that i need to use :/
Some onde can tell me pease ? :(
 

 

Thanks

Link to post
Share on other sites
On 8/26/2020 at 10:11 PM, balbes150 said:

The exact name of the image.

The image name is:  Armbian_20.08_Nanopct4_focal_current_5.7.15.img

This issue only occurs occasionally for several times. 

 

Due to limitation of one day one post, I would like to report another potential bug: 

 

It seems CEC stops working after switching source. At the begining, it works. After switching to another source and switching back, CEC stops working.  I can see only several kind of messages when the issue occurs, like active source, standby. The same TV works well with RPI.  I also collected  CEC trace from RPI (but with tool cec-client) as working example.

 

Logs from nanopc t4: (CEC not work after switching source)



Received from TV to Playback Device 1 (0 to 4): CEC_MSG_GIVE_DEVICE_POWER_STATUS (0x8f)
Transmitted by Playback Device 1 to TV (4 to 0): CEC_MSG_REPORT_POWER_STATUS (0x90):
        pwr-state: on (0x00)
Received from TV to all (0 to 15): CEC_MSG_SET_STREAM_PATH (0x86):
        phys-addr: 1.0.0.0
Transmitted by Playback Device 1 to TV (4 to 0): CEC_MSG_VENDOR_COMMAND (0x89):
        vendor-specific-data: 0x10 0x02 0xff 0xff 0x00 0x05 0x05 0x45 0x55 0x5c 0x58 0x32 (       EU\X2)
Transmitted by Playback Device 1 to TV (4 to 0): CEC_MSG_IMAGE_VIEW_ON (0x04)
Transmitted by Playback Device 1 to all (4 to 15): CEC_MSG_ACTIVE_SOURCE (0x82):
        phys-addr: 1.0.0.0
Transmitted by Playback Device 1 to TV (4 to 0): CEC_MSG_MENU_STATUS (0x8e):
        menu-state: activated (0x00)
Received from TV to Playback Device 1 (0 to 4): CEC_MSG_FEATURE_ABORT (0x00):
        abort-msg: 137 (0x89)
        reason: invalid-op (0x03)
Received from TV to Playback Device 1 (0 to 4): CEC_MSG_USER_CONTROL_PRESSED (0x44):
        ui-cmd: Device Root Menu (0x09)
Received from TV to Playback Device 1 (0 to 4): CEC_MSG_USER_CONTROL_PRESSED (0x44):
        ui-cmd: Down (0x02)
Received from TV to Playback Device 1 (0 to 4): CEC_MSG_USER_CONTROL_RELEASED (0x45)
Received from TV to Playback Device 1 (0 to 4): CEC_MSG_USER_CONTROL_PRESSED (0x44):
        ui-cmd: Down (0x02)
Received from TV to Playback Device 1 (0 to 4): CEC_MSG_USER_CONTROL_RELEASED (0x45)

# Start switching source

Received from TV to Playback Device 1 (0 to 4): CEC_MSG_USER_CONTROL_PRESSED (0x44):
        ui-cmd: Clear (0x2c)
Received from TV to all (0 to 15): CEC_MSG_ACTIVE_SOURCE (0x82):
        phys-addr: 0.0.0.0
Received from TV to all (0 to 15): CEC_MSG_ROUTING_CHANGE (0x80):
        orig-phys-addr: 1.0.0.0
        new-phys-addr: 2.0.0.0
Received from TV to all (0 to 15): CEC_MSG_SET_STREAM_PATH (0x86):
        phys-addr: 2.0.0.0

(warn: State Change events were lost)
Event: State Change: PA: f.f.f.f, LA mask: 0x0000
Received from TV to all (0 to 15): CEC_MSG_ACTIVE_SOURCE (0x82):
        phys-addr: 0.0.0.0
Received from TV to all (0 to 15): CEC_MSG_ROUTING_CHANGE (0x80):
        orig-phys-addr: 2.0.0.0
        new-phys-addr: 1.0.0.0
Received from TV to all (0 to 15): CEC_MSG_SET_STREAM_PATH (0x86):
        phys-addr: 1.0.0.0


# No more event reported except events for switching source and button for device link

Event: State Change: PA: 1.0.0.0, LA mask: 0x0010
Transmitted by Playback Device 1 to all (4 to 15): CEC_MSG_REPORT_PHYSICAL_ADDR (0x84):
        phys-addr: 1.0.0.0
        prim-devtype: playback (0x04)
Transmitted by Playback Device 1 to all (4 to 15): CEC_MSG_DEVICE_VENDOR_ID (0x87):
        vendor-id: 5506 (0x00001582)
Received from TV to Playback Device 1 (0 to 4): CEC_MSG_VENDOR_COMMAND_WITH_ID (0xa0):
        vendor-id: 32837 (0x00008045)
        vendor-specific-data: 0x06 0x04 (  )
Transmitted by Playback Device 1 to TV (4 to 0): CEC_MSG_FEATURE_ABORT (0x00):
        abort-msg: 160 (0xa0)
        reason: unrecognized-op (0x00)


Received from TV to all (0 to 15): CEC_MSG_ACTIVE_SOURCE (0x82):
        phys-addr: 0.0.0.0
Received from TV to all (0 to 15): CEC_MSG_ROUTING_CHANGE (0x80):
        orig-phys-addr: 1.0.0.0
        new-phys-addr: 2.0.0.0
Received from TV to all (0 to 15): CEC_MSG_SET_STREAM_PATH (0x86):
        phys-addr: 2.0.0.0

(warn: State Change events were lost)
Event: State Change: PA: f.f.f.f, LA mask: 0x0000
Received from TV to all (0 to 15): CEC_MSG_ACTIVE_SOURCE (0x82):
        phys-addr: 0.0.0.0
Received from TV to all (0 to 15): CEC_MSG_ROUTING_CHANGE (0x80):
        orig-phys-addr: 2.0.0.0
        new-phys-addr: 1.0.0.0

Event: State Change: PA: 1.0.0.0, LA mask: 0x0000
Transmitted by Playback Device 1 to Playback Device 1 (4 to 4): CEC_MSG_POLL
        Tx, Not Acknowledged (4), Max Retries

Event: State Change: PA: 1.0.0.0, LA mask: 0x0010
Transmitted by Playback Device 1 to all (4 to 15): CEC_MSG_REPORT_PHYSICAL_ADDR (0x84):
        phys-addr: 1.0.0.0
        prim-devtype: playback (0x04)
Transmitted by Playback Device 1 to all (4 to 15): CEC_MSG_DEVICE_VENDOR_ID (0x87):
        vendor-id: 5506 (0x00001582)
Received from TV to all (0 to 15): CEC_MSG_SET_STREAM_PATH (0x86):
        phys-addr: 1.0.0.0
Received from TV to Playback Device 1 (0 to 4): CEC_MSG_VENDOR_COMMAND_WITH_ID (0xa0):
        vendor-id: 32837 (0x00008045)
        vendor-specific-data: 0x06 0x04 (  )
Transmitted by Playback Device 1 to TV (4 to 0): CEC_MSG_FEATURE_ABORT (0x00):
        abort-msg: 160 (0xa0)
        reason: unrecognized-op (0x00)

 

Logs from Rpi (CEC works after switching source)

DEBUG:   [          106377]     logical address changed to Free use (e)
WARNING: [          106410]     unhandled response received: opcode=0 initiator=e destination=0 response=0
WARNING: [          106501]     unhandled response received: opcode=8c initiator=e destination=0 response=0
TRAFFIC: [          106620]     >> 0f:87:00:80:45
DEBUG:   [          106620]     TV (0): vendor = Panasonic (008045)
DEBUG:   [          106620]     device TV (0) status changed to present after command device vendor id
DEBUG:   [          106620]     replacing the command handler for device 'TV' (0)
DEBUG:   [          106621]     >> TV (0) -> Broadcast (F): device vendor id (87)
DEBUG:   [          106623]     logical address changed to Broadcast (f)
DEBUG:   [          106804]     logical address changed to Free use (e)
DEBUG:   [          106894]     logical address changed to Broadcast (f)
DEBUG:   [          107074]     logical address changed to Free use (e)
DEBUG:   [          107165]     logical address changed to Playback 1 (4)
WARNING: [          107317]     unhandled response received: opcode=84 initiator=4 destination=f response=0
WARNING: [          107498]     unhandled response received: opcode=47 initiator=4 destination=0 response=0
WARNING: [          107679]     unhandled response received: opcode=8f initiator=4 destination=0 response=0
TRAFFIC: [          107680]     >> 04:00:47:00
DEBUG:   [          107680]     marking opcode 'set osd name' as unsupported feature for device 'TV'
TRAFFIC: [          107745]     >> 04:90:00
DEBUG:   [          107745]     TV (0): power status changed from 'unknown' to 'on'
WARNING: [          108107]     unhandled response received: opcode=89 initiator=4 destination=0 response=0
WARNING: [          108198]     unhandled response received: opcode=4 initiator=4 destination=0 response=0
WARNING: [          108410]     unhandled response received: opcode=82 initiator=4 destination=f response=0
TRAFFIC: [          108410]     >> 04:00:89:03
WARNING: [          108501]     unhandled response received: opcode=8e initiator=4 destination=0 response=0
WARNING: [          108592]     unhandled response received: opcode=91 initiator=4 destination=0 response=0
TRAFFIC: [          108633]     >> 04:8c
WARNING: [          108784]     unhandled response received: opcode=87 initiator=4 destination=f response=0
TRAFFIC: [          108912]     >> 0f:32:7a:68:6f
DEBUG:   [          108912]     TV (0): menu language set to 'zho'
DEBUG:   [          108912]     >> TV (0) -> Broadcast (F): set menu language (32)
WARNING: [          109003]     unhandled response received: opcode=0 initiator=4 destination=1 response=1
WARNING: [          109093]     unhandled response received: opcode=0 initiator=4 destination=1 response=1
WARNING: [          109184]     unhandled response received: opcode=0 initiator=4 destination=2 response=1
WARNING: [          109275]     unhandled response received: opcode=0 initiator=4 destination=2 response=1
WARNING: [          109366]     unhandled response received: opcode=0 initiator=4 destination=3 response=1
WARNING: [          109456]     unhandled response received: opcode=0 initiator=4 destination=3 response=1
WARNING: [          109547]     unhandled response received: opcode=0 initiator=4 destination=5 response=1
WARNING: [          109638]     unhandled response received: opcode=0 initiator=4 destination=5 response=1
WARNING: [          109729]     unhandled response received: opcode=0 initiator=4 destination=6 response=1
WARNING: [          109820]     unhandled response received: opcode=0 initiator=4 destination=6 response=1
WARNING: [          109910]     unhandled response received: opcode=0 initiator=4 destination=7 response=1
WARNING: [          110001]     unhandled response received: opcode=0 initiator=4 destination=7 response=1
WARNING: [          110092]     unhandled response received: opcode=0 initiator=4 destination=8 response=1
WARNING: [          110182]     unhandled response received: opcode=0 initiator=4 destination=8 response=1
WARNING: [          110273]     unhandled response received: opcode=0 initiator=4 destination=9 response=1
WARNING: [          110363]     unhandled response received: opcode=0 initiator=4 destination=9 response=1
WARNING: [          110454]     unhandled response received: opcode=0 initiator=4 destination=a response=1
WARNING: [          110545]     unhandled response received: opcode=0 initiator=4 destination=a response=1
WARNING: [          110636]     unhandled response received: opcode=0 initiator=4 destination=b response=1
WARNING: [          110727]     unhandled response received: opcode=0 initiator=4 destination=b response=1
WARNING: [          110818]     unhandled response received: opcode=0 initiator=4 destination=c response=1
WARNING: [          110908]     unhandled response received: opcode=0 initiator=4 destination=c response=1
WARNING: [          111119]     unhandled response received: opcode=0 initiator=4 destination=d response=1
TRAFFIC: [          111119]     >> 04:89:10:01:04
WARNING: [          111210]     unhandled response received: opcode=0 initiator=4 destination=d response=1
WARNING: [          111571]     unhandled response received: opcode=89 initiator=4 destination=0 response=0
WARNING: [          111662]     unhandled response received: opcode=0 initiator=4 destination=e response=1
WARNING: [          111753]     unhandled response received: opcode=0 initiator=4 destination=e response=1
TRAFFIC: [          111991]     >> 04:a0:00:80:45:06:04
WARNING: [          112111]     unhandled response received: opcode=0 initiator=4 destination=0 response=0
TRAFFIC: [          112221]     >> 04:00:89:03
WARNING: [          113282]     unhandled response received: opcode=4 initiator=4 destination=0 response=0
WARNING: [          113403]     unhandled response received: opcode=82 initiator=4 destination=f response=0
WARNING: [          113494]     unhandled response received: opcode=8e initiator=4 destination=0 response=0
TRAFFIC: [          126291]     >> 04:44:00
TRAFFIC: [          126495]     >> 04:8b:00





TRAFFIC: [          136898]     >> 04:44:2c
TRAFFIC: [          138666]     >> 0f:82:00:00
DEBUG:   [          138666]     making TV (0) the active source
DEBUG:   [          138666]     >> TV (0) -> Broadcast (F): active source (82)
TRAFFIC: [          138832]     >> 0f:80:10:00:20:00
DEBUG:   [          138832]     >> TV (0) -> Broadcast (F): routing change (80)
TRAFFIC: [          139428]     >> 0f:86:20:00
DEBUG:   [          139429]     >> TV (0) sets stream path to physical address 2000
DEBUG:   [          139429]     >> TV (0) -> Broadcast (F): set stream path (86)
TRAFFIC: [          145098]     >> 0f:82:00:00
DEBUG:   [          145098]     TV (0) was already marked as active source
DEBUG:   [          145098]     >> TV (0) -> Broadcast (F): active source (82)
TRAFFIC: [          145264]     >> 0f:80:20:00:10:00
DEBUG:   [          145264]     >> TV (0) -> Broadcast (F): routing change (80)
WARNING: [          145355]     unhandled response received: opcode=4 initiator=4 destination=0 response=0
WARNING: [          145476]     unhandled response received: opcode=82 initiator=4 destination=f response=0
WARNING: [          145567]     unhandled response received: opcode=8e initiator=4 destination=0 response=0
DEBUG:   [          145630]     GetPhysicalAddress - physical address = 1000
TRAFFIC: [          145868]     >> 0f:86:10:00
DEBUG:   [          145868]     >> TV (0) sets stream path to physical address 1000
DEBUG:   [          145869]     >> TV (0) -> Broadcast (F): set stream path (86)
WARNING: [          145990]     unhandled response received: opcode=82 initiator=4 destination=f response=0
TRAFFIC: [          150013]     >> 04:44:0d
TRAFFIC: [          150219]     >> 04:8b:0d

 

Link to post
Share on other sites
7 minutes ago, test0x01 said:

The image name is:  Armbian_20.08_Nanopct4_focal_current_5.7.15.img

You write in the wrong subject forum. You need to write to another section where the official versions are discussed. This topic discusses unofficial versions of ArmbianTV (images and launch rules for This version can be found at the link in the first message).

 

 

Link to post
Share on other sites
9 hours ago, czosnekltd said:

You can add more details? Where to start? I don't have any eMMC backup

You can use gt1 with vim2 if gt1 is the same as s912 soc. 

 

If not then please share the soc model as gt series is a bit confusing. 

Link to post
Share on other sites
5 hours ago, jonesqpacman said:

Please revert to old method (uEnv.ini)

To switch back to the old method simply rename extlinux.conf.
  e.g. mv extlinux.conf extlinux.conf-disabled
But I don't know if the old files get still maintained.

Link to post
Share on other sites

I've seen some people tried this on a Beelink GT King / Pro. How do you get it to boot from the default Android OS?  I've tried to hold the power button to bring up the switch OS option, but nothing happen if I click that.  I followed the instruction on the first page, and used a DTB from CoreELEC. 

Link to post
Share on other sites
16 hours ago, wenlez said:

..used a DTB from CoreELEC. 

Try those dtbs you get with the image you use and find out which works (best) for your board-that one you try to use doesn't fit to kernel and stuff and there is no chance to boot with wrong dtb..

Link to post
Share on other sites

Thanks for the advice. I got my GT King Pro to boot from the default Android OS.  

 

It looks like only the images that does not include Desktop environment would boot. Others builds (5.7 and 5.9 kernel) with Desktop would just not boot. Blank screen. 

 

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

ver 20200831-dev kernel 5.9.0-rc3

Hi. On my booth kiiipro and s905w USB ports dosn't work.

dmesg message - phy phy-d0078000.phy.0: phy init failed --> -22

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

Hi. On my booth kiiipro and s905w USB ports dosn't work.

dmesg message - phy phy-d0078000.phy.0: phy init failed --> -22

I can report having the same problem on my TX3 mini (s905w) box, running a 5.9.0-rc kernel.  I noticed this yesterday when I built my own 5.9.0-rc2 kernel and installed it, but I didn't have time to dig into the issue.

Link to post
Share on other sites

Hi on my Mecool M8S Pro W (with meson-gxl-s905x-p212.dtb):
1) after installing the images from August I cannot start the remote desktop -even manual installation in the console of xrdp does not solve this problem - (in older images like aml9xxX-Armbian_20.06.0_Arm-64_focal_current_5.7.6_desktop_20200630.img.xz - remote desktop works well and this from armbian-config). It is true that there is a possibility to log in, but the remote desktop does not appear.
2) so far I have not found an image where the built-in BT in Mecool would work - does starting BT require any additional actions?

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

Hi on my Mecool M8S Pro W (with meson-gxl-s905x-p212.dtb):
1) after installing the images from August I cannot start the remote desktop -even manual installation in the console of xrdp does not solve this problem - (in older images like aml9xxX-Armbian_20.06.0_Arm-64_focal_current_5.7.6_desktop_20200630.img.xz - remote desktop works well and this from armbian-config). It is true that there is a possibility to log in, but the remote desktop does not appear.

Maybe I found the source of the problem with RDP not working:
Well, in armbian-config in the file https://github.com/armbian/config/blob/master/debian-config-jobs
RDP is installed using:

if! is_package_manager_running; then
debconf-apt-progress - apt-get -y install xrdp vnc4server xorgxrdp
systemctl enable xrdp.service> / dev / null 2> & 1.

As it turns out, there is no such vnc4server package because:

root@arm-64:~# apt-get install vnc4server
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package vnc4server is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'vnc4server' has no installation candidate

Can you get around as this?

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

Maybe I found the source of the problem with RDP not working:
 

Can you get around as this?

As far as packages go, I find focal seems to have less than bionic. As a work around for other none specific packages, you could download the from the bionic repo with wget and install with dpgk.
If you get complaints about dependcies, you could manualy copy in the files after extracting them from the package with ar x pkg.deb ; tar -xvf data.tar.xz

Link to post
Share on other sites

I am trying latest build of 20200831-dev kernel 5.9.0-rc3 on an Amlogic S912 box ( qintaix Q912 Android TV Box )

While it boots ok from USB stick, and with the new u-boot I have HDMI output from u-boot stage, the USB keyboard does not work during u-boot, and I cannot select any other boot options.

It complains that "Failed to get keyboard state from device c0f4:01e0"

Also tried with ver 20200828 kernel 5.7.16, and same behaviour ( as most likely the u-boot is the same )

The keyboard works fine after booting in armbian linux.

Booting with u-boot-s905x-s912 renamed to u-boot.ext

Any ideas of what might be wrong ?

 

 

 

 

Link to post
Share on other sites
On 9/1/2020 at 2:57 AM, balbes150 said:

This is a known problem for 5.8\5.9, the source code sent a patch that broke the USB operation on GXL\GXM. I'm currently testing a new kernel with a patch that fixes this.

Since I am building my own kernels, can you send a link to where I could find this patch?  Also, do you know if this patch is planned for inclusion in 5.8.x and 5.9?  If so when?

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

Since I am building my own kernels, can you send a link to where I could find this patch?  Also, do you know if this patch is planned for inclusion in 5.8.x and 5.9?  If so when?

See the patchwork there is a reverse patch for dw3.

Link to post
Share on other sites

Hello!

Im new in the forum and with armbian.
I have an MXQPro+ 4k device.  Have managed to get armbian up and running from SD card but have trouble getting Network.

And why doesnt the p201 dtb file work with this device. I have to use the nexbox-a95 dtb.

 

My plan is to setup RetroPIe on the device

Thx in advance

Link to post
Share on other sites
3 hours ago, cartridge said:

And why doesnt the p201 dtb file work with this device. I have to use the nexbox-a95 dtb.

Why would you expect the p201 dtb file to work on this specific box?  Each TV box device has unique hardware, from wifi chips, ethernet, memory, etc.  The dtb file is the mapping from the hardware to the software.  So realistically every TV box requires a unique dtb file to work 100% correctly.  Unfortunately the box manufacturers in their quest to offer cheap prices, don't put any effort into providing these dtb files for mainline kernel's.  So we are left finding trying to find a dtb that is close enough for our needs on these TV boxes. Therefore you end up with an 80% fit between the dtb and the actual hardware on your box, and hopefully the 20% that doesn't work isn't something that you don't need for your use case - wifi being the usual example of something that often doesn't work.

Link to post
Share on other sites
Guest
This topic is now closed to further replies.