Please make GT-king Pro compatible with armbian ..

gtkingpro.ac2n · Post time 2021-06-21 21:14:34

Mesa have updated to 21.1.3 => https://docs.mesa3d.org/relnotes/21.1.3.html
I looked at the github that you indicated to me but there has been no update since March 2020 and then I am not very keen to install a repository from I do not know where .. I prefer to keep my original sources.list ..

JFL · Post time 2021-06-22 14:19:27

Edited by JFL at 2021-06-22 21:32

gtkingpro.ac2n replied at 2021-06-21 21:14
Mesa have updated to 21.1.3 => https://docs.mesa3d.org/relnotes/21.1.3.html
I looked at the github t ...

I have not used the Debian Buster link before as pointed out earlier and but I noticed that link has mesa 21.0. so it has been updated not that long ago may be Feb/Mar 2021.  For your information Khadas-Vim3-Focal image comes with Mesa 21.0.1xx.  @darkstar had pointed out to me how to build our own mesa but I have not tried it -http://forum.bee-link.com/forum. ... ra=page%3D1&page=2.  May be you can give it a try or is there a possibility to use Debian Sid repo MESA 21.1.0 on Buster?  If you manage to build the new mesa for Buster do share with us.  It will be great if you manage to build thel latest stable mesa 21.1.3.

To explore Panfrost, I took the easy way out and use Focal with Oibaf graphics drivers PPA and found out later Bullseye with mesa 20.3.4-1 works too and Manjaro Arm which has the latest mesa easily available.

One added advantage of Panfrost in my experience in mpv with vo=gpu it helps to reduce CPU resource usage when playing video and performance wise good up to 1080p/30 (eventhough is does not help in vpu acceleration) and mpv --hwdec=v4l2m2m-copy works up to 1080p/30 also with meson vdec.  But at times without --hwdec-v4l2m2m-copy works better.

Edit: I tried Manjaro KDE Plasma 5.21.5 and Plasma 5.22.1, Plasma (X11) works but somehow Plasma (Wayland) just stuck/freeze at Login Screen.  Manjaro GNOME Wayland and GNOME Xorg works well.  So far my experience with Wayland is only with GNOME or Ubuntu-Wayland.

gtkingpro.ac2n · Post time 2021-07-09 14:49:33

So I try build Mesa 21.1.4 and 21.1.3 but there are dependencies which are only on Bulleyes, and therefore the build fails..
I leave a copy of the log in case some of you have any ideas but I doubt that it is really possible to build Mesa under buster ...

https://paste.yunohost.org/oqefamujeq.vbs

JFL · Post time 2021-07-10 21:08:49

Edited by JFL at 2021-07-10 21:15

gtkingpro.ac2n replied at 2021-07-09 14:49
So I try build Mesa 21.1.4 and 21.1.3 but there are dependencies which are only on Bulleyes, and the ...

Hi @gtkingpro.ac2n,

Currently using Mesa 21.1.4-1 (from https://forum.odroid.com/viewtopic.php?f=52&t=5908&start=750) on Armbian-Bullseye-XFCE. It works well and no annoying visual artifact so far (except and only LightDM greeter login screen when Panfrost is Enabled there is visual artifact). On Armbian-Focal-Ubuntu-Wayland-GDM3 NO visual artifact on the greeter login screen.  Use Oibaf-graphics-drivers mesa-git for Armbian Focal, so far could not find a ppa for mesa-fresh for arm64 devices.

Mesa 21.1.4-1 on Bullseye seems more responsive than Mesa 20.3.4-1.

From what I can gather from your log, one dependency is missing/incorrect. "Dependency wayland-client found: NO found 1.16.0 but need: '>=1.18'  mesa-21.1.3/meson.build:1827:2: ERROR: Invalid version of dependency, need 'wayland-client' ['>=1.18'] found '1.16.0'.
Looks like you are almost there!

Based on what I read on https://forum.odroid.com/viewtopic.php?f=52&t=5908&start=750 even for Bullseye to use Mesa 21.1.4, meveric had to build libdrm 2.4.105 or port from Sid repo since the libdrm from Debian Bullseye repo is version 2.4.104-1

Chech with the users from https://forum.armbian.com/topic/11424-playing-with-limamesa-mali-drivers/page/2/.  They might be able to assist.

JFL · Post time 2021-07-27 23:03:14

Hi @gtkingpro.ac2n, "Issue with Armbian switching/installing from linux-image-current-meson64 to linux-image-edge-meson64"

I am having issue installing/switching to linux-image-edge-meson64 (meson64-5.13.5) from linux-image-current-meson64 (meson64-5.10.43). The installation went through with NO error and can see the new linux-image-edge-meson64-5.13.5 related files (Image, uInitrd, initrd.img-5.13.5, vmlinuz-5.13.5-meson64, etc) on the /boot/ partition/folder but these files do NOT actually reside on the FAT32 /boot/ partition! Installing using Terminal Command Line and Synaptic Package Manager, same results.

Once Reboot, all the files on the FAT32 /boot/ partition/folder are the original linux-image-current-meson64-5.10.43 related and NONE of the installed linux-image-edge-meson64-5.13.5. I tried with linux-image-edge-meson64 (trunk96 5.13.4) it is the same. When Reboot, it boot right back into current-meson64-5.10.43! Tried to circumvent this problem by copying all newly created linux-image-edge-meson64 after installation to an external drive and Reboot which boot back to current-meson64-5.10.43 and manually copy the linux-image-edge-meson64-5.13.5 files from external drive to FAT32 /boot/ partition/folder. Managed to boot once to linux-5.13.5 trunk99 but second boot it won't boot anymore NO idea why.

Have you tried installting/switching from current-meson64 to edge-meson64 recently? Previously, no issue doing this but tried this yesterday and today, faced this weird issue.

JFL · Post time 2021-07-27 23:04:51

Hi @gtkingpro.ac2n,  "Issue with Armbian switching/installing from linux-image-current-meson64 to linux-image-edge-meson64"

I am having issue installing/switching to linux-image-edge-meson64 (meson64-5.13.5) from linux-image-current-meson64 (meson64-5.10.43).  The installation went through with NO error and can see the new linux-image-edge-meson64-5.13.5 related files (Image, uInitrd, initrd.img-5.13.5, vmlinuz-5.13.5-meson64, etc) on the /boot/ partition/folder but these files do NOT actually reside on the FAT32 /boot/ partition! Installing using Terminal Command Line and Synaptic Package Manager, same results.

Once Reboot, all the files on the FAT32 /boot/ partition/folder are the original linux-image-current-meson64-5.10.43 related and NONE of the installed linux-image-edge-meson64-5.13.5.  I tried with linux-image-edge-meson64 (trunk96 5.13.4) it is the same.  When Reboot, it boot right back into current-meson64-5.10.43!  Tried to circumvent this problem by copying all newly created linux-image-edge-meson64 after installation to an external drive and Reboot which boot back to current-meson64-5.10.43 and manually copy the linux-image-edge-meson64-5.13.5 files from external drive to FAT32 /boot/ partition/folder.  Managed to boot once to linux-5.13.5 trunk99 but second boot it won't boot anymore NO idea why.

Have you tried installting/switching from current-meson64 to edge-meson64 recently? Previously, no issue doing this but tried this yesterday and today, faced this weird issue.

gtkingpro.ac2n · Post time 2021-08-02 15:18:51

JFL replied at 2021-07-27 16:04
Hi @gtkingpro.ac2n, "Issue with Armbian switching/installing from linux-image-current-meson64 to li ...

Hi @JFL I have never tested linux-image-edge-meson64 I can not tell you .. I have on the other hand switched to Beta mode via armbian-config and so I had some updates, then unfortunately I have had a system freeze without knowing where it came from, I went back to the stable armbian version, and I set the CPU governor in performance mode to 1.7Ghz and for the moment no "freeze" worries ", I am under linux 5.10.51-meson64 ..
What is the difference between linux-image-current-meson64 and linux-image-edge-meson64?

JFL · Post time 2021-08-03 01:12:24

gtkingpro.ac2n replied at 2021-08-02 15:18
Hi @JFL I have never tested linux-image-edge-meson64 I can not tell you .. I have on the other han ...

Hi @gtkingpro.ac2n,

Per my understanding "current" is what Armbian support which uses the 5.10.y LTS linux kernel and "edge" is the latest kernel Armbian uses (which they just switch from 5.12.y to 5.13.y) but not supported.  Anyway this only apply to Armbian supported SBC and not TV Boxes.

So you are able to update to kernel 5.10.51 which I suppose is "current-21.08-trunk.94.arm64" which is in the beta.armbian.com.  I tried to use the Armbian-Config to switch kernel and it does not allow kernel switch via Armbian Config.  It states v20.10 does not support kernel upgrade or something to that effect.  Preferred method is via Terminal Command Line or Synaptic Package Manager.

The current stable released kernel for meson64 is 5.10.43 if not mistaken.  Will see what happen when the next release update v21.08 (August) comes round.

JFL · Post time 2021-08-12 15:14:42

Edited by JFL at 2021-08-20 14:32

Just an update. Updated Armbian Focal to the latest current kernel that is linux-image-current-meson64 5.10.57 v21.05.8 from 5.10.43-meson64. So updating on the same current kernel NO issue.

Edit: 2021-08-20

Still cannot switch or install linux-image-edge-meson64 (with kernel 5.13.y) with current linux-image-current-meson64 v21.05.8 (with kernel 5.10.57).

JFL · Post time 2021-11-01 15:31:58

Edited by JFL at 2021-11-01 15:40

Just t o share. Installed GNOME 41 on Armbian-Bulleye yesterday following the suggestion from https://www.linuxcapable.com/how ... ebian-11-bullseye/. Since GNOME 3.38 was not installed on Armbian-Bullseye earlier need to install gdm3 from the "unstable" branch so that it can start up on gdm3 and GNOME (Wayland) session..

GNOME 41 works fine so far and since did not install GNOME-Desktop, no GNOME-CORE applications are installed at all. All the applications were mainly from Armbian-Bullseye default XFCE. Example, Terminal is still XFCE Terminal and Files Manager is Thunar, etc NONE from GNOME 41.

On start-up Armbian-Bullseye-GNOME-41 RAM usage is aroun 620-680 MB still higer than Manjaro-Arm-GNOME-40 Edition (around 550-600 MB) and Manjaro-Arm-GNOME-40 have the basic GNOME-Core Apps whereas Armbian-Bullseye-GNOME-41 had none of GNOME-Core apps installed but have XFCE apps installed.