I just updated to the Manjaro ARM 2020-11-08 release and now I have a green screen (on my Ugoos).
The package list suggested for install seemed harmless (in particular, no kernel upgrade). However, it seems that some install script has rebuilt my initrd. (This is the only reason I can see right now for the green screen.)
Edit: It seems that there is a simple workaround: Just go to display settings (I use the xfce thingy) and change resolution back and forth and the display/screen becomes normal again.
I have a slightly situation on green screen issue I think a week ago. For whatever reason the green screen suddenly come up during boot up (where the last boot before it boot up normally), reboot still the same issue green screen. The I tried booting up Android and then shutdown Android and reboot Manjaro and it boot up normal.
linux-vim kernel 5.9.0-2 is available, just manage to upgrade the linux-wim kernel 5.9.0-2.
[Edit] Looking forward to kernel 5.9.6 to try out Panfrost on GT King Pro.
Just pushed 5.9.8 to unstable and tried mesa-git-21.0 on it, panfrost is much smooth and no font or color issue but it still seem to get stuck after few mins which means we need 5.10 to get stable panfrost
Tested on GT King pro
3 dtb to 5.9.8 balbes branch kernel as a patch.
Gt king Pro
GS King X
You are right:
I have tried linux-vim again (now with kernel 5.9.8) and when using Panfrost it has the same instability I had with linux-vim 5.9.0-1 kernel (as you wrote above).
… I don’t think so.
As I wrote before: After I changed to the linux package the crashes were gone (to be precise: it is not crash free but almost). Even with kernel 5.9.1-3. So there are 5.9 kernels which work stable with Panfrost.
In my opinion it might help to have a closer look at what the differences between the linux kernel and the linux-vim kernel are.
In that way it might be possible to find out why system is unstable with linux-vim kernel and stable with linux kernel when using Panfrost. On the other hand, it might be possible to find the reason why linux-vim kernel does recognize sound cards while linux kernel does not.
I just notice in the stable branch now, Linux kernel 5.9.6-1 is available (per the Manjaro Package Manager). I just upgrade from linux-vim kernel 5.9.0-1 to kernel 5.9.0-2. I wonder whether there is any benefit to install linux kernel 5.9.6-1 over linux-vim 5.9.0-2 especially for Beelink GT King Pro as linux-vim kernel 5.9.8 is at Unstable Branch.
Strit reports that mesa 21.0.0 is working well on his Odroid N2 which has Mali G52.
Did you find differences in the source code regarding the power controller?
I am asking because I found out something which might only be related to my TV box but maybe it is also related to the system hanging after a short while when using panfrost with linux-vim kernel. (I mean: the box does not crash and reboots or turns off but rather it still displays an image and is completely unresponsive/frozen.)
I try to keep it short: After changing from linux-vim to linux my box did not boot with ‘meson-sm1-sei610.dtb’ anymore. Fortunately, it did with ‘meson-g12a-sei510.dtb’. So I had a closer look at the differences in the respective .dts files and after quite some testing I found out that I have to change the following in ‘meson-sm1-sei610.dts’ to make my box boot again:
[I also had to add some stuff to make ethernet work again, had to delete ‘power-domains’ in ‘usb@ffe09000’ for usb to work correctly and had to delete ‘pinctrl-0’ in ‘audio-controller@61000’ because there were interactions with ‘ethernet’.]
As said: Maybe only a problem with my box … but maybe more. I am just trying to help (with the very limited knowledge I have).
Just rename the old version of the file to e.g. brcmfmac4356-sdio.bin.myversion and let the installer proceed and install the new version. Most likely the new version will work just fine and you will have WiFi (unless something else has been screwed up; dmesg will be your friend).
Evidently this was put there manually in some manjaro-arm install script (since it did not specify what package owned it) because it did not exist yet in that location and the linux-firmware package has now added it to their package.
I am not involved with GTKPro but I believe @spikerguy is and it probably needs to be chased down on how that firmware got placed there since linux-firmware is now putting it there.
Just an update after installing linux kernel 5.9.6-1 over linux-vim kernel 5.9.0-2.
Ethernet works after reboot with linux kernel 5.9.6-1
Wifi does not work after reboot eventhough the wifi driver “brcmfmac4356-sdio.bin” is available in /usr/lib/firmware/brcm/. Did a comparison with the “brcmfmac4356-sdio.bin” (copied from Armbian) driver that works on Manjaro linux-vim kernel 5.9.0-1 and 5.9.0-2 with the copy of "“brcmfmac4356-sdio.bin” from linux kernel 5.9.6-1. The file size is different!
So I used the “brcmfmac4356-sdio.bin” from Armbian that had work before and it work with linux kernel 5.9.6-1. This is surprising, the “brcmfmac4356-sdio.bin” that came with linux kernel 5.9.6-1 does not work.
[jfl@GTKPro ~]$ sudo chmod a+x /usr/bin/g12_sound.sh
[sudo] password for jfl:
[jfl@GTKPro ~]$ systemctl enable sound --now
CLI: chmod a+x /usr/bin/g12_sound.sh does not enable sound.
Tried also /usr/bin/sound.sh from Armbian
jfl@GTKPro ~]$ /usr/bin/sound.sh
aplay: device_list:274: no soundcards found…
Other than that, linux kernel 5.9.6-1 work so far on GT King Pro just NO Sound.
Fyi, brcmfmac4356-sdio.bin does not exist on the Manjaro VIM3 image, I copied it from an Armbian build to get wifi to work in Manjaro VIM3.
The brcmfmac4356-sdio.bin driver from linux kernel 5.9.6-1 package does not work with Beelink GT King Pro. I have to re-use the brcmfmac4356-sdio.bin from Armbian build to get wifi to work do know why. I am using meson-g12b-gtking-pro.dtb from linux kernel 5.9.6-1 package.
I think you can get WiFi working with the .bin file that was just installed from Manjaro. Look what you get with “dmesg | grep brcm” and see if it is is not missing some other firmware file (which may already exist, but under another name than what the kernel module expects). Essentially, you can go through the same procedure as the first time you got WiFi working, I guess.
This is going to be an issue every time the linux-firmware package updates if only brcmfmac4356-sdio.bin is the problem.
Put your new firmware in the /usr/lib/firmware/ directory so it can get picked up first then reboot and see if you have wifi. If not chase down what script is loading the firmware and change the path to /usr/lib/firmware/brcmfmac4356-sdio.bin and reboot.