Yes i am using the kernel from balbes branch only. So our dtb is the same as his.
Ok will try to build one later this weekend.
You can build one on your own using this guide.
Try if you can.
@spikerguy This means that it should be possible to solve this. Let me know if there is something I can do (run tests, possibly build something, etc). Much appreciate your work.
1 Like
Hi Spikerguy,
Thank you. Looking forward to test the Manjaro Arm 20.10 for GTKPro.
In Armbian I notice there are at least two versions of dtb files for meson-ugoos-am6.dtb one with 73K file size and another file size 51K. There is also one from Armbian for GTKPro meson-g12b-gtking-pro.dtb of file size 73K.
@JFL I think this is due to the inclusion of a list of symbols (for use with overlays) in one of them. You can check by decompiling (I outlined this somewhere above) and look near the end of the decompiled file. For our use, I don’t think there is any difference.
Edit: Oops, I forgot that you don’t have a running box but if you are ambitious you can do this on some other Linux box.
Tripole,
Beelink GTKPro is the only Android TV box I have. Thanks for the information.
JFL,
I have followed the Manjaro WiKi mentioned by Spikerguy above (using the section “Building an OEM image”) and produced two versions of a 20.11 image with the vim3 kernel version 5.9.0-1. You can find the images here; xfce-image and minimal-image
As these are files produced by a random person on the internet (me), treat them as such (use only for testing and then discard).
Edit: I don’t know exactly how the versioning works; the images came out with the tag 20.11 but I don’t know exactly what that means in terms of packages (there is also a txt file showing the package versions, but I didn’t upload that). The kernel is 5.9.0-1 though, that is clear.
1 Like
Regarding the versioning it is written in the ‘How to contribute to Manjaro ARM’ wiki that ‘buildarmimg’ has an option ‘-v’ which allows you to set the version name as you like. If you do not use option ‘-v’ it defaults to YY.MM.
Yeah, I kind of knew that but I guess I’m not clear on what that actually means. (I have been too lazy to actually look at the package list, but maybe I’ll get around to that… 
) (I haven’t used this image myself, since I have a running Manjaro ARM system, updated “manually”.)
I guess the ‘-v’ option is just for convenience so that you do not have to rename the final image by hand (since the rest of the name is automatically generated depending on the device and edition you are building).
BTW, I did my first (Gnome) build just some hours ago. I also have an updated XFCE version already running on my X96Max+ TV box (S905X3, Mali G31). After first boot I did not have ethernet on the Gnome version I built while ethernet is working fine on the updated XFCE version. Both sharing the same ‘meson-sm1-sei610-2.dtb’ I used to use on Armbian with the 5.9.0 kernel. Will have to investigate it later …
3 Likes
Hi Tripole,
Thank you. Wow, you are fast and good at it.
I will download your Manjaro OEM image 20.11 with VIM3 kernel 5.9.0-1 build and give it go shortly. Download speed seems slow for now.
I have contacted Beelink Android team and they confirmed that the kernel crash issue is nothing but Android Uboot conflict with Linux kernel.
So I will be trying to coordinate with the Beelink Development team to find a fix for the crash issue.
I hope to find a solution soon for this as I Cannot wait to start using gx King X as my main nas server instead of My current NanoPiNeo2Plus
2 Likes
Hi Tripole and Spikerguy,
Just completed downloading the Manjaro-ARM-xfce-vim3-20.11.img_xz and burn image on a USB Stick. I used meson-g12b-gtking-pro.dtb to boot up. It boot up but no ethernet or wifi connection. It said “Network Manager is not running…” I thought the Network Manager is automatically installed and running?
$ systemclt status NetworkManager
NetwrorkManager.service - Network Manager
Loaded loaded (./usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
Active: inactive (dead)
(Edited uEnv.ini to boot up with meson-g12b–ugoos-am6.dtb and reboot. Still have the same issue “NetwrorkManager is not running…” so still no network Ethernet or Wifi)
Need guidance on how to startup the Network Manager so that I can at least connect to Ethernet and hopefully wifi too. Thanks.
Hi Spikerguy,
Great at least now we know what is causing the Kernel Panic in Beelink GT King Pro. Does it means there will be a new Android Firmware Upgrade from Beelink?
I just burn the VIM3 image that Tripole build and burn on a USB Stick. It boot up but NetworkManager is not running meaning No Ethernet or Wifi. I use meson-g12b-gtking-pro.dtb from Armbian as this VIM3 image does not have gtking-pro.dtb.
Appreciate input to resolve this NetworkManager not running issue. Thanks.
It seems that Network Manager has died and I guess it takes a little troubleshooting to figure out why… You must probably google a little about how to use the command journalctl and filter out error messages from the systemd log that can be relevant for diagnosis. Also, I would suggest that you first restart the box and perform that little ritual that worked for you before (cold boot, or maybe it was warmbooting from Android). Another thing, you can do a
dmesg | grep dwmac
and see what you find (dwmac is a program-glue layer that wraps the physical ethernet device, I think, and therefore this can help diagnose if the physical layer is working). Just my 2 cents…
Edit: Maybe I’m not reading the systemd message correctly. I can’t tell (because of ignorance) if Network Manager never started or it started and has then died. If you do
systemctl start NetworkManager.service
and then immediately do
journalctl | tail -n50
what do you get in the systemd log?
I also notice during start up or shutdown there is message “Failed to configure Network…”
Will try to re-burn the image and start up clean with “meson-g12b-ugoos-am6.dtb” to see whether it boot up with NetworkManager running.
Re-burn image of Manjaro-ARM-xfce-vim3-20.11.img_xz and using meson-g12b-ugoos-am6.dtb still results in “NetworkManager is not running…” No Ethernet or Wifi on GTKPro.
TheMojoMan,
Great that you have a S905X3 box up and running. Could it be that your issue with ethernet (on Gnome build) is somehow related to JFL’s ethernet issue? I mean, both occur on recent (like “today”) image builds… 
Hi Tripole,
thanks for your message. Yes I think that the problems are related. There must be something missing in the build scripts I guess.
Since that was my first build I need to have a closer look into the configuration files as a next step I think. That’s gonna be a hard one …
Hi Tripole & Spikerguy,
Beelink GT King Pro - using meson-g12b-ugoos-am6.dtb from the Manjaro-ARM-xfce-vim3-20.11.img_xz dtbs folder.
From Terminal
$ systemctl start NetworkManager.service
[ 261.167543] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet] (irq=29)
[ 261.194834] meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found
[ 261.196766] meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW
[ 261.203491] meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode
[ 264.821866] meson8b-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
By issue the above command, Ethernet is now available. Thanks for the guidances. Per the ‘dmesg’ output the ‘Link is Up - 1Gbps/Full - flow control rx/tx’.
Manjaro seems not that responsive for now and off and on the screen flashes. Firefox (page/tab load a bit slow) and LibreOffice Writer both took sometime to load up.
Will check the wifi availability after performing “sudo pacman -Syu” update.
No update available as expected as the image is newly build.
After reboot, NetworkManager is not running, need to “systemctl start NetworkManager.service” to be able to access to Ethernet. Still NO Wifi for GTKPro with this image Kernel: Linux 5.9.0-1-MANJARO-ARM.
No sound either. Will try run script /usr/bin/g12_sound.sh.
root@JFL jfl]# script /usr/bin/g12_sound.sh
Script started, output log file is ‘/usr/bin/g12_sound.sh’.
[root@JFL jfl]#
Still no sound after reboot.
By the way any instruction that will Enable/Start NetworkManager.service on Boot Up.
Hi Tripole & Spikerguy,
NetworkManager.service does not start up on Cold Boot has to issue “systemctl start NetworkManager.service” on CLI to start network connection.
Changed to Tripole meson-g12b-gtking-pro-5.9.1-SDIO45MHz.dtb Still No Wifi
Changed to meson-g12b-gtking-pro.dtb also No Wifi
meson-g12b-ugoos-am6.dtb also No Wifi.
I have tried “$ nmcli device wifi list”. No wifi list shown.
dmesg output (with meson-g12b-gtking-pro.dtb):
[ 16.665348] brcmfmac: F1 signature read @0x18000000=0x17224356
[ 16.684622] audit: type=1130 audit(16.870:6): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg=‘unit=systemd-networkd comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
[ 16.715663] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4356-sdio for chip BCM4356/2
[ 16.715855] usbcore: registered new interface driver brcmfmac
[ 16.726013] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac4356-sdio.bin failed with error -2
[ 16.995973] random: crng init done
[ 16.999241] random: 7 urandom warning(s) missed due to ratelimiting
[ 17.035654] Bluetooth: hci0: BCM: chip id 101
[ 17.043301] Bluetooth: hci0: BCM: features 0x2f
[ 17.052164] Bluetooth: hci0: BCM4354A2
[ 17.058678] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0000
[ 18.334091] Bluetooth: hci0: BCM4356A2 ‘brcm/BCM.hcd’ Patch
[ 19.606938] audit: type=1130 audit(19.800:7): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg=‘unit=systemd-rfkill comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
[ 19.683848] audit: type=1130 audit(19.870:8): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg=‘unit=systemd-random-seed comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
[ 20.714959] Bluetooth: hci0: command 0xfc4c tx timeout
[ 22.708372] usbcore: registered new interface driver uas
[ 24.146053] audit: type=1130 audit(24.340:9): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg=‘unit=lvm2-monitor comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
[ 24.623261] audit: type=1131 audit(24.810:10): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg=‘unit=systemd-rfkill comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
[ 25.949601] audit: type=1130 audit(26.140:11): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg=‘unit=systemd-tmpfiles-setup comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
[ 26.050618] audit: type=1127 audit(26.240:12): pid=619 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg=’ comm=“systemd-update-utmp” exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success’
[ 26.073814] audit: type=1130 audit(26.260:13): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg=‘unit=systemd-update-utmp comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
[ 26.428150] audit: type=1130 audit(1604643131.574:14): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg=‘unit=systemd-timesyncd comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
[ 26.526624] audit: type=1130 audit(1604643131.674:15): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg=‘unit=bluetooth-khadas comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
[ 26.551378] audit: type=1130 audit(1604643131.694:16): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg=‘unit=dbus comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
[ 26.573502] audit: type=1130 audit(1604643131.714:17): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg=‘unit=khadas-utils comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
[ 26.592068] audit: type=1334 audit(1604643131.734:18): prog-id=7 op=LOAD
[ 29.274984] Bluetooth: hci0: BCM: Patch command fc4c failed (-110)
[ 29.275546] Bluetooth: hci0: BCM: Patch failed (-110)
Good morning JFL. In your last post above (with meson-g12b-gtking-pro.dtb), the error message
16.726013] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac4356-sdio.bin failed with error -2
is actually good news since it suggests that the (physical) WiFi chip/module is found by the kernel and handled via the kernel module brcmfmac. (The WiFi module appears to the kernel as the mmc0 device, as it should.). Good.
I think that all you now only have left to do is “fiddle with the right firmware files.” It appears that you are missing the file /lib/firmware/brcm/brcmfmac4356-sdio.bin Do you have it?
Edit: To enable Network Manager at boot up do
systemctl enable NetworkManager (or perhaps systemctl enable NetworkManager.service)
Edit2: I see that there are (in your log) are similar failures to find firmware (patches) for your Blutooth so this suggests that some firmware package is missing, I guess. (Sometimes one has to go fishing on the internet to find the right ones. We’ll see.)