Yes you can generate one from manjaro arm installer Or I might do one for testing this weekend.
Yes I think there is some config issue somewhere. Will look into this
Yes soon once we have gpu support.
This is only for S922X-H soc and no one really knows what is the difference between -H and -J as beelink version of S922 is -H and those are the only ones which have kernel panic.
I will all beelink to send a sample to neil who is the lead kernel developer for amlogic soc.
Btw please tag me when asking something coz without the tag I won’t get any notification.
Thanks for taking interest in manjaro For amlogic.
If i get such an overwhelming support then I will be able to look into it now.
I also have mainline uboot image for Vim3 which can be directly flashed to emmc but only when there is nothing in the emmc like no Android uboot present.
@spikerguy I also (with s922x-j) get freezes/lockups but not so often (I can have the box running more than a day on low load). (A freeze on my system is just a freeze; frozen screen, unresponsive, impossible to ssh in.) When a freeze happens, it is usually preceded by loss of Bluetooth (or, perhaps one of those graphics glitches, I’m not sure if these are correlated). I managed to salvage a bit of dmesg from last time it happened and there is a kernel Oops there:
@spikerguy I have Armbian with Balbes latest kernel 5.9.0 (his general multiboard arm-64 tag/branch/family) running 100% stable on my (s922x-j) box. (I have used Armbian on the box for a couple of months.)
Edit: Clarification.
Edit2: I have also had Armbian kernel 5.8.10 (I think it was .10) running w/o problem on the box.
Thanks for the response. I am interested in trying out the latest Manjaro 20.10 on Beelink GTKing Pro but am very new in Linux so to compile or generate one from majaro arm installer is most likely beyond me unless with a lot of guidance with detailed steps.
If you are building one image for GTKPro for testing would it be possible release/share for those that is interest to test it?
The Manjaro VIM3 20.06 with kernel 5.7 is too unstable for GTKPro as it is. I can’t get pass basic system updating without kernel panic or freezing (eg. during fresh "pacman -Syu, was able to complete download of all the packages (500-700MB) but will hit kernel panic during “checking available disk space or unpacking of up to 5 packages then freeze.” The latest was during boot up “kernel panic” (cannot boot up anymore).
Looking forward to test Manjaro Arm with kernel 5.9.1 and above soon.
@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.
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.
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.
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 …
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?
(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.
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.
) (I haven’t used this image myself, since I have a running Manjaro ARM system, updated “manually”.)