Panfrost Status on Odroid N2

[jgmdev]

I installed Arch Linux xfce panfrost I updated and tried to install compiz. It started but I can't start Compiz config to activate the cube for example. I mention that in the past it worked perfectly.

I added compiz PKGBUILD to repository for recompilation which should fix the issue with the compizconfig settings manager not launching due to updated python versions If my guess is correct. Upgrading compiz should fix the issue, just run yay from a terminal or use the gui package manager pamac.

There is a method to set Compiz manually or to start Compiz manager.

If that is a question, in the past doing xfconf-query --channel xfce4-session --property /sessions/Failsafe/Client0_Command --type string --set 'compiz' --type string --set '--replace' worked great to replace xfwm4 on xfce startup with compiz but it seems that with newer xfce 4.16 the loading of xfwm4 is hard coded so to make it work disable the Compositor from Window Manager Tweaks -> Compositor -> Enable display compositing then add a new startup command in Session and Startup -> Application Autostart with the command compiz --replace

[harddroid]

@ jgmdev
Can you explain how you installed wayfire? Maybe you could add wayfire to the repo, too?

[jgmdev]

@ jgmdev
Can you explain how you installed wayfire? Maybe you could add wayfire to the repo, too?

You can cherry pick from here the packages you want and customizations/config files:
https://github.com/jgmdev/alarm-image-g ... wayfire.sh

And yes it is a good idea to add necessary stable/working wayfire packages to archlinuxdroid repo

[harddroid]

I can confirm that the xfce image with linux-odroid-511 kernel is a very stable configuration with even 2560x1440@60 resolution working flawless. I only have problems with my ethernet connection not coming up from boot to boot.

[amirul]

Upgraded kernel to no ill effects

Code: Select all

amirul@n2plus-pf:~$ uname -a
Linux n2plus-pf 5.10.0-odroid-panfrost-arm64 #1 SMP PREEMPT Ubuntu 5.10.12-202102040913~groovy (2021-02-04) aarch64 aarch64 aarch64 GNU/Linux
amirul@n2plus-pf:~$ glmark2-es2-wayland 
=======================================================
    glmark2 2014.03+git20150611.fa71af2d
=======================================================
    OpenGL Information
    GL_VENDOR:     Panfrost
    GL_RENDERER:   Mali G52 (Panfrost)
    GL_VERSION:    OpenGL ES 3.0 Mesa 21.1.0-devel (git-d49b0fa72f)
=======================================================
[build] use-vbo=false: FPS: 588 FrameTime: 1.701 ms
[build] use-vbo=true: FPS: 613 FrameTime: 1.631 ms
[texture] texture-filter=nearest: FPS: 1461 FrameTime: 0.684 ms
[texture] texture-filter=linear: FPS: 1453 FrameTime: 0.688 ms
[texture] texture-filter=mipmap: FPS: 1488 FrameTime: 0.672 ms
[shading] shading=gouraud: FPS: 383 FrameTime: 2.611 ms
[shading] shading=blinn-phong-inf: FPS: 316 FrameTime: 3.165 ms
[shading] shading=phong: FPS: 336 FrameTime: 2.976 ms
[shading] shading=cel: FPS: 333 FrameTime: 3.003 ms
[bump] bump-render=high-poly: FPS: 131 FrameTime: 7.634 ms
[bump] bump-render=normals: FPS: 1443 FrameTime: 0.693 ms
[bump] bump-render=height: FPS: 1330 FrameTime: 0.752 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 679 FrameTime: 1.473 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 281 FrameTime: 3.559 ms
[pulsar] light=false:quads=5:texture=false: FPS: 1563 FrameTime: 0.640 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 184 FrameTime: 5.435 ms
[desktop] effect=shadow:windows=4: FPS: 946 FrameTime: 1.057 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 230 FrameTime: 4.348 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 220 FrameTime: 4.545 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 292 FrameTime: 3.425 ms
[ideas] speed=duration: FPS: 211 FrameTime: 4.739 ms
[jellyfish] <default>: FPS: 446 FrameTime: 2.242 ms
[terrain] <default>: FPS: 19 FrameTime: 52.632 ms
[shadow] <default>: FPS: 267 FrameTime: 3.745 ms
[refract] <default>: FPS: 31 FrameTime: 32.258 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 1154 FrameTime: 0.867 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 839 FrameTime: 1.192 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 1125 FrameTime: 0.889 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 1128 FrameTime: 0.887 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 817 FrameTime: 1.224 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 1066 FrameTime: 0.938 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 1035 FrameTime: 0.966 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 661 FrameTime: 1.513 ms
=======================================================
                                  glmark2 Score: 699 
=======================================================

[tobetter]

Upgraded kernel to no ill effects

amirul@n2plus-pf:~$ uname -a
Linux n2plus-pf 5.10.0-odroid-panfrost-arm64 #1 SMP PREEMPT Ubuntu 5.10.12-202102040913~groovy (2021-02-04) aarch64 aarch64 aarch64 GNU/Linux

You have very fresh cookie kernel.

[istanbulls]

Step by step we are moving towards smoother 4K video. Thanks @tobetter and other contributors.

Code: Select all

n2p@odroid:~$ uname -a
Linux odroid 5.10.0-odroid-panfrost-arm64 #1 SMP PREEMPT Ubuntu 5.10.12-202102040913~groovy (2021-02-04) aarch64 aarch64 aarch64 GNU/Linux

[harddroid]

Im back to testing panfrost on my odroid n2+ and Im wondering if there is something wrong with the performance. I did test xonotic @ 2560x1440 and get around 20fps and if I lower all the graphicsettings I also get around 20fps.
And this dmesg line looks strange as well. I dont know if its the clockrate of mali g52, but it should be something around 800mhz.

Code: Select all

[    7.088900] panfrost ffe40000.gpu: clock rate = 24000000

Arch Linux - XFCE @ Linux alarm 5.11.0-rc5-5-ARCH #1 SMP PREEMPT Fri Jan 29 04:24:04 AST 2021 aarch64 GNU/Linux with local/mesa-arm-git 21.1.0_devel.134548.09e421846d6-1

[mad_ady]

Perhaps you need to change the gpu governor to performance too.

[chewitt]

In stock Linux 5.10/5.11 the GPU governor will remain on base frequency which is bad for performance. In 5.11 many/most folks have raided my patchset which initially forced the GPU governor to performance, but now has less hacky changes which allow the GPU to reach max freq quicker and work properly. I'm hoping the changes get merged for 5.12 (until then, they are in my branch).

[harddroid]

Perhaps you need to change the gpu governor to performance too.

This does really help with more consistent fps. If anyone wants to know how to do this:

Code: Select all

echo performance > /sys/devices/platform/soc/ffe40000.gpu/devfreq/ffe40000.gpu/governor

In stock Linux 5.10/5.11 the GPU governor will remain on base frequency which is bad for performance. In 5.11 many/most folks have raided my patchset which initially forced the GPU governor to performance, but now has less hacky changes which allow the GPU to reach max freq quicker and work properly. I'm hoping the changes get merged for 5.12 (until then, they are in my branch).

There is already "simple_ondemand" governor active on the 5.11 kernel Im using. Should be based on tobetters branch (Linux alarm 5.11.0-rc6-6-ARCH #1 SMP PREEMPT Fri Feb 5 16:07:08 AST 2021 aarch64 GNU/Linux).

[chewitt]

@harddroid the problem with the simple_ondemand governor is that it ramps up slowly. In Kodi it is (was) very noticeable that when you start scrolling in a long list, it would "stutter" at first and only scroll smooth once the max frequency is reached a few seconds later. Forcing performance governor works, but with the following commit the userspace hack in the post above ^ is not required. The GPU scales up to max freq. quickly, then scales back down when the system is idle.

See https://github.com/chewitt/linux/commit ... 4a242fb976 which will be merged for 5.12

NB: there are a number of other panfrost bug/issue fixes in my branch which are missing from @tobetter branches.

[jgmdev]

For those that haven't read it yet a new bifrost scheduler was added by panfrost developers to latest mesa which seems to improve performance significantly

https://www.phoronix.com/scan.php?page= ... -Scheduler

Here a glmark2-es2-wayland benchmark running on Wayfire which shows better numbers than before:

Code: Select all

=======================================================
    glmark2 2020.04
=======================================================
    OpenGL Information
    GL_VENDOR:     Panfrost
    GL_RENDERER:   Mali G52 (Panfrost)
    GL_VERSION:    OpenGL ES 3.0 Mesa 21.1.0-devel (git-df48267c65)
=======================================================
[build] use-vbo=false: FPS: 655 FrameTime: 1.527 ms
[build] use-vbo=true: FPS: 688 FrameTime: 1.453 ms
[texture] texture-filter=nearest: FPS: 1707 FrameTime: 0.586 ms
[texture] texture-filter=linear: FPS: 1702 FrameTime: 0.588 ms
[texture] texture-filter=mipmap: FPS: 1780 FrameTime: 0.562 ms
[shading] shading=gouraud: FPS: 435 FrameTime: 2.299 ms
[shading] shading=blinn-phong-inf: FPS: 436 FrameTime: 2.294 ms
[shading] shading=phong: FPS: 400 FrameTime: 2.500 ms
[shading] shading=cel: FPS: 417 FrameTime: 2.398 ms
[bump] bump-render=high-poly: FPS: 157 FrameTime: 6.369 ms
[bump] bump-render=normals: FPS: 1870 FrameTime: 0.535 ms
[bump] bump-render=height: FPS: 1757 FrameTime: 0.569 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 1057 FrameTime: 0.946 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 394 FrameTime: 2.538 ms
[pulsar] light=false:quads=5:texture=false: FPS: 1957 FrameTime: 0.511 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 249 FrameTime: 4.016 ms
[desktop] effect=shadow:windows=4: FPS: 1054 FrameTime: 0.949 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 242 FrameTime: 4.132 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 239 FrameTime: 4.184 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 259 FrameTime: 3.861 ms
[ideas] speed=duration: FPS: 271 FrameTime: 3.690 ms
[jellyfish] <default>: FPS: 568 FrameTime: 1.761 ms
[terrain] <default>: FPS: 32 FrameTime: 31.250 ms
[shadow] <default>: FPS: 305 FrameTime: 3.279 ms
[refract] <default>: FPS: 39 FrameTime: 25.641 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 1327 FrameTime: 0.754 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 1323 FrameTime: 0.756 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 1308 FrameTime: 0.765 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 1339 FrameTime: 0.747 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 1327 FrameTime: 0.754 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 1284 FrameTime: 0.779 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 1283 FrameTime: 0.779 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 1059 FrameTime: 0.944 ms
=======================================================
                                  glmark2 Score: 876 
=======================================================

This latest version of mesa is now available on latest N2/N2+ Wayfire Image:
viewtopic.php?p=321029#p321029

[harddroid]

@harddroid the problem with the simple_ondemand governor is that it ramps up slowly. In Kodi it is (was) very noticeable that when you start scrolling in a long list, it would "stutter" at first and only scroll smooth once the max frequency is reached a few seconds later. Forcing performance governor works, but with the following commit the userspace hack in the post above ^ is not required. The GPU scales up to max freq. quickly, then scales back down when the system is idle.

See https://github.com/chewitt/linux/commit ... 4a242fb976 which will be merged for 5.12

NB: there are a number of other panfrost bug/issue fixes in my branch which are missing from @tobetter branches.

I did build your kernel and it works good (cant say if it has better performance, because I only tested xonotic and it has no benchmark), but HDMI audio isnt working and I cannot use 2560x1440 as resolution. So Tobetter has some important patches and you have more panfrost patches?

@jgmdev
Thats great news. Ive already tested it and its even better on the desktop now with xfwm. But the newest mesa did kill supertuxkart (screenshot attached).

[jgmdev]

@jgmdev
Thats great news. Ive already tested it and its even better on the desktop now with xfwm. But the newest mesa did kill supertuxkart (screenshot attached).

Works here with latest mesa-arm-git package, maybe some of the mesa master updates was broken but it should be fixed now.

[chewitt]

I did build your kernel and it works good (cant say if it has better performance, because I only tested xonotic and it has no benchmark), but HDMI audio isnt working and I cannot use 2560x1440 as resolution. So Tobetter has some important patches and you have more panfrost patches?

Bifrost support is under 6-months old so the driver is very young and I care about stability more than performance. You may find performance things in various private mesa branches but trying to pick WIP from them is difficult without really understanding the code and you'll probably end up in "two steps forwards, one step backwards" situations frequently. Optimisation is being worked upon by many people and will come with time. It is easier and probably more productive to just track mesa master than worship the branches of a single contributor.

The AXG audio driver used on G12 devices like N2 does not currently support the IEC958 controls needed for "HDMI" output and there are issues with the hacky/experimental patches I added for a while (and have since removed). The kernel has good PCM output (on the HDMI port) and if you follow my alsa-lib changes I also sorted out the channel mapping issues (RR/RL/FC/LFE were messed up). I will not revisit "HDMI" output in my branch until someone codes the missing controls. I'm hopefull that LibreComputer might fund that work, but otherwise nobody is working on it that I know of and other Amlogic oriented manufacturers (looking at you HK) sadly do not sponsor development in that way.

I haven't picked @tobetter patch for extra resolutions or the "pinky grey" issue as I have no requests/reports of it being an issue in the LibreELEC codebase I support - likely because LE targets TV devices which use supported CEA resolutions, and we have no Desktop. Dongjin should send these patches upstream to the linux-amlogic mailing list. The extra resolution patch maybe accepted as-is, although it would be better to add support for a wider set/class of desktop resolutions than just one. The pinky-grey patch is a hack and will not be accepted, but unless he reports/raises the issue it works around, the maintainers do not know about it. Engaging and reporting issues to the maintainers and working with them to resolve issues is the only way things will get fixed in future kernel releases. Fixing things upstream is the only way to reduce the technical-debt that accumulates in working branches.

[harddroid]

@ chewitt

Im just using PCM over HDMI, but with your kernel I no longer saw the HDMI output. If this is already working I try to generate a patch for the resolution, so you can add this feature to the kernel. Its not a patch for specific resolution, it removes limits at 1920x1200 to allow a higher resolution. But it will add a pixelclock setting for 2560x1440 and not for any other high resolution.

This is the old patch:

Code: Select all

diff --git a/drivers/gpu/drm/meson/meson_vclk.c b/drivers/gpu/drm/meson/meson_vclk.c
index fdf26dac9..23b16e059 100644
--- a/drivers/gpu/drm/meson/meson_vclk.c
+++ b/drivers/gpu/drm/meson/meson_vclk.c
@@ -357,6 +357,8 @@ enum {
 	MESON_VCLK_HDMI_594000,
 /* 2970 /1 /1 /1 /5 /1  => /1 /2 */
 	MESON_VCLK_HDMI_594000_YUV420,
+/* 4830 /2 /1 /2 /5 /1  => /1 /1 */
+	MESON_VCLK_HDMI_241500,
 };
 
 struct meson_vclk_params {
@@ -467,6 +469,18 @@ struct meson_vclk_params {
 		.vid_pll_div = VID_PLL_DIV_5,
 		.vclk_div = 1,
 	},
+	[MESON_VCLK_HDMI_241500] = {
+		.pll_freq = 4830000,
+		.phy_freq = 2415000,
+		.venc_freq = 241500,
+		.vclk_freq = 241500,
+		.pixel_freq = 241500,
+		.pll_od1 = 2,
+		.pll_od2 = 1,
+		.pll_od3 = 2,
+		.vid_pll_div = VID_PLL_DIV_5,
+		.vclk_div = 1,
+	},
 	{ /* sentinel */ },
 };
 
@@ -859,6 +873,10 @@ static void meson_vclk_set(struct meson_drm *priv, unsigned int pll_base_freq,
 			m = 0xf7;
 			frac = vic_alternate_clock ? 0x8148 : 0x10000;
 			break;
+		case 4830000:
+			m = 0xc9;
+			frac = 0xd560;
+			break;
 		}
 
 		meson_hdmi_pll_set_params(priv, m, frac, od1, od2, od3);
diff --git a/drivers/gpu/drm/meson/meson_venc.c b/drivers/gpu/drm/meson/meson_venc.c
index f93c725b6..ebe4f2a92 100644
--- a/drivers/gpu/drm/meson/meson_venc.c
+++ b/drivers/gpu/drm/meson/meson_venc.c
@@ -866,10 +866,11 @@ meson_venc_hdmi_supported_mode(const struct drm_display_mode *mode)
 			    DRM_MODE_FLAG_PVSYNC | DRM_MODE_FLAG_NVSYNC))
 		return MODE_BAD;
 
-	if (mode->hdisplay < 640 || mode->hdisplay > 1920)
+	/* support higher resolution than 1920x1080 */
+	if (mode->hdisplay < 640 || mode->hdisplay > 2560)
 		return MODE_BAD_HVALUE;
 
-	if (mode->vdisplay < 480 || mode->vdisplay > 1200)
+	if (mode->vdisplay < 480 || mode->vdisplay > 1600)
 		return MODE_BAD_VVALUE;
 
 	return MODE_OK;

viewtopic.php?p=302145#p302145

[chewitt]

This is merged for 5.12 and will require you to adjust alsa conf: https://github.com/chewitt/linux/commit ... 63319d406a

Also see: https://github.com/chewitt/alsa-lib/commits/amlogic for the conf I'm using. Rename AMLOGIC-HDMI to the ODROID-N2/C4/HC4 etc. device you're using (to match the new card name in device-tree)

[wallyz21]

This is merged for 5.12 and will require you to adjust alsa conf: https://github.com/chewitt/linux/commit ... 63319d406a

Also see: https://github.com/chewitt/alsa-lib/commits/amlogic for the conf I'm using. Rename AMLOGIC-HDMI to the ODROID-N2/C4/HC4 etc. device you're using (to match the new card name in device-tree)

I'm on 5.10 at the moment.

Will the 5.12 update come through automatically via the standard update/upgrade mechanism?

[wallyz21]

The last updates/upgrades completely broke the desktop.

Very bad flickering and most visuals are broken.

I am still on 5.10 Panfrost kernel!

[amirul]

The last updates/upgrades completely broke the desktop.

Very bad flickering and most visuals are broken.

I am still on 5.10 Panfrost kernel!

Mine is broken as well
mesa 202102141635 didn't fix it

[amirul]

To get to desktop
$ sudo service lightdm stop
$ gnome-shell --wayland

[wallyz21]

The last updates/upgrades completely broke the desktop.

Very bad flickering and most visuals are broken.

I am still on 5.10 Panfrost kernel!

Mine is broken as well
mesa 202102141635 didn't fix it

It appears to be all the fonts are not rendering! Is that the same for you?

I had a search for font rendering issues on the web but nothing came up so I imagine this is an issue related to N2 specifics! (Not sure)

[tobetter]

The last updates/upgrades completely broke the desktop.

Very bad flickering and most visuals are broken.

I am still on 5.10 Panfrost kernel!

Mine is broken as well
mesa 202102141635 didn't fix it

It appears to be all the fonts are not rendering! Is that the same for you?

Will you let us know the base OS image and running kernel version with uname -a?

[wallyz21]

The last updates/upgrades completely broke the desktop.

Very bad flickering and most visuals are broken.

I am still on 5.10 Panfrost kernel!

Mine is broken as well
mesa 202102141635 didn't fix it

It appears to be all the fonts are not rendering! Is that the same for you?

Will you let us know the base OS image and running kernel version with uname -a?

Standby. The system is at home and so I can only give you that info in several hours time. Sorry!

[tobetter]

The last updates/upgrades completely broke the desktop.

Very bad flickering and most visuals are broken.

I am still on 5.10 Panfrost kernel!

Mine is broken as well
mesa 202102141635 didn't fix it

It appears to be all the fonts are not rendering! Is that the same for you?

Will you let us know the base OS image and running kernel version with uname -a?

Standby. The system is at home and so I can only give you that info in several hours time. Sorry!

No worries...

[amirul]

It appears to be all the fonts are not rendering! Is that the same for you?

I had a search for font rendering issues on the web but nothing came up so I imagine this is an issue related to N2 specifics! (Not sure)

$ uname -a
Linux n2plus-pf 5.10.0-odroid-panfrost-arm64 #1 SMP PREEMPT Ubuntu 5.10.12-202102040913~groovy (2021-02-04) aarch64 aarch64 aarch64 GNU/Linux

mesa 5:21.1.0-devel+202102141635~groovy

With mine lightdm display is broken, although I can log in to desktop with the right password. Gnome-shell seems to be working with occasional random log outs. I've seen no font issues so far.

[tobetter]

@wallyz21 and @amirul, would you update the issue to another thread if you are running the Linux kernel and Ubuntu 20.10 based on the image from me so I can have more whips?
viewtopic.php?f=52&t=40761

[harddroid]

I cannot confirm anything is broken right now. But Im not using ubuntu, but arch from jgmdev.
Here is a current glmark2 score (windowed) running on wayfire:

Code: Select all

=======================================================
    glmark2 2020.04
=======================================================
    OpenGL Information
    GL_VENDOR:     Panfrost
    GL_RENDERER:   Mali G52 (Panfrost)
    GL_VERSION:    3.1 Mesa 21.1.0-devel (git-a740318e42)
=======================================================
[build] use-vbo=false: FPS: 644 FrameTime: 1.553 ms
[build] use-vbo=true: FPS: 697 FrameTime: 1.435 ms
[texture] texture-filter=nearest: FPS: 1670 FrameTime: 0.599 ms
[texture] texture-filter=linear: FPS: 1659 FrameTime: 0.603 ms
[texture] texture-filter=mipmap: FPS: 1684 FrameTime: 0.594 ms
[shading] shading=gouraud: FPS: 458 FrameTime: 2.183 ms
[shading] shading=blinn-phong-inf: FPS: 469 FrameTime: 2.132 ms
[shading] shading=phong: FPS: 437 FrameTime: 2.288 ms
[shading] shading=cel: FPS: 447 FrameTime: 2.237 ms
[bump] bump-render=high-poly: FPS: 166 FrameTime: 6.024 ms
[bump] bump-render=normals: FPS: 1966 FrameTime: 0.509 ms
[bump] bump-render=height: FPS: 1424 FrameTime: 0.702 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 1083 FrameTime: 0.923 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 406 FrameTime: 2.463 ms
[pulsar] light=false:quads=5:texture=false: FPS: 1835 FrameTime: 0.545 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 230 FrameTime: 4.348 ms
[desktop] effect=shadow:windows=4: FPS: 1038 FrameTime: 0.963 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 130 FrameTime: 7.692 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 230 FrameTime: 4.348 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 323 FrameTime: 3.096 ms
[ideas] speed=duration: FPS: 201 FrameTime: 4.975 ms
[jellyfish] <default>: FPS: 657 FrameTime: 1.522 ms
[terrain] <default>: FPS: 34 FrameTime: 29.412 ms
[shadow] <default>: FPS: 305 FrameTime: 3.279 ms
[refract] <default>: FPS: 40 FrameTime: 25.000 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 1349 FrameTime: 0.741 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 1354 FrameTime: 0.739 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 1320 FrameTime: 0.758 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 1335 FrameTime: 0.749 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 1358 FrameTime: 0.736 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 1311 FrameTime: 0.763 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 1321 FrameTime: 0.757 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 1315 FrameTime: 0.760 ms
=======================================================
                                  glmark2 Score: 875
=======================================================

Kernel is Linux alarm 5.11.0-rc7-7-ARCH #1 SMP PREEMPT Thu Feb 11 18:39:06 AST 2021 aarch64 GNU/Linux based on tobetters branch.

[amirul]

@wallyz21 and @amirul, would you update the issue to another thread if you are running the Linux kernel and Ubuntu 20.10 based on the image from me so I can have more whips?
viewtopic.php?f=52&t=40761

OK I'll repeat last message there. Cheers everyone.

[wallyz21]

@jgmdev
Thats great news. Ive already tested it and its even better on the desktop now with xfwm. But the newest mesa did kill supertuxkart (screenshot attached).

Works here with latest mesa-arm-git package, maybe some of the mesa master updates was broken but it should be fixed now.

This is still a problem for me as well. Everything else GL has worked. Not that I have tried a lot. Stellarium, glmark2, extreme tux racer.

but Super Tux Kart is broken!

[trwn2p]

Alot of balony caused by Jdmdev. I use tobetters stuff and all is well. I upgraded my 2 installs Deb 11 LXQT and Ubu Gnome 20.10 both of newest 5.10.16 and panfrost with no issues. I enjoy them alot. I would prefer jdmdev keep his info in one thread and not general threads like this one. I like to track progress on odroid and panfrost. Not a bunch of Arch custom images polluting this thread. Just my take on it. It would be nice if there were'nt tons of threads for this guy like arch wayfire blah blah. How bout a single forum thread for his stuff somewhere. If I'm alone on this ok but I dont like his work and it just pollutes alot of threads. I would think Other OS/Arch is where all his info should go. He started this thread so I guess it stays a garbage dump on an ODROID forum. So many have trouble with his stuff and it bleeds all over tobetters and others threads. That's my gripe.

[jgmdev]

but Super Tux Kart is broken!

It works, on graphics level 2 (more effects may give issues, level 3 works with some issues) using kernel package linux-odroid-511 with latest mesa-arm-git package, here a screenshot on level 2.

Alot of balony caused by Jdmdev. I use tobetters stuff and all is well. I upgraded my 2 installs Deb 11 LXQT and Ubu Gnome 20.10 both of newest 5.10.16 and panfrost with no issues. I enjoy them alot. I would prefer jdmdev keep his info in one thread and not general threads like this one. I like to track progress on odroid and panfrost. Not a bunch of Arch custom crap images polluting this thread. Just my take on it. It would be nice if there were'nt tons of threads for this guy like arch wayfire blah blah. How bout a single forum thread for his stuff somewhere. If I'm alone on this ok but I dont like his work and it just pollutes alot of threads. He started this thread so I guess it stays a garbage dump on an ODROID forum. So many have trouble with his stuff and it bleeds all over tobetters threads. That's my gripe.

What can I say ... my enthusiasm with using a small low energy consumption ARM device as a desktop computer lead me to making lots of posting, testing and staying active on the forums sharing what I found thinking others may find it interesting and learning from other people comments, so sorry for annoying you with my noise and enthusiasm.

I wasn't planning on doing ArchLinux images but some people wrote me private messages asking me to do after writing the Howto's, so I decided to give it a shot and it has been fun so far. I have already read on the forums negative comments from other debian flavor distro developer calling the stuff I share unprofessional or me directly/indirectly a noob (which I am, we learn new stuff everyday doesn't we?) but I ignored the comments so far since I have enjoyed putting the various working ArchLinux images (at least they work for me) for the nice Odroid N2/N2+ which is the kind of device I waited for some years, and sharing it without asking anything back, my intention has never been doing wrong to anyone, this is not about competition but about choice. But, I guess some people can get competitive, and the worst part, derogative/hateful towards others.

Some years ago I enjoyed ubuntu or plain debian but then found ArchLinux and felt in love with its rolling release model. You enjoy Ubuntu? that is great! But, I know others like me enjoy the ArchLinux way of things, not because I stopped using debian I started writing negative comments about it on public forums or denigrating people contributions towards it. But it seems that people take their fanaticism and rage against others. I guess we all have to deal with that kind of behavior from the corporate world to the open source collaborative/community world (which is sad, so far working on this images was like therapy for me ). Anyways, we all have acted the same at some point in life so I'm not a suitable person to point fingers.

Sorry again for irritating you...

[trwn2p]

I'm not trying to discourage you from having fun with Arch, Odroid images or any distro you enjoy and want to share your enthusiasm here. I too enjoy and use Arch Manjaro LFS Debian 11 UBU 20.10 on my N2+ and i share about them too. Just that one day it's about panfrost here then it's off track into your stuff and troubleshooting that.

[mægpie]

... He started this thread so I guess it stays a garbage dump on an ODROID forum.

And if this thread weren't that before, it would turn soon into it by more posts like that
No, really, I'm totally with you ... we shoul'd stay on-topic:

Code: Select all

uname -srv
Linux 5.11.0-1-ARCH #1 SMP PREEMPT Sun Feb 21 18:08:04 AST 2021
glmark2
=======================================================
    glmark2 2021.02
=======================================================
    OpenGL Information
    GL_VENDOR:     Panfrost
    GL_RENDERER:   Mali G52 (Panfrost)
    GL_VERSION:    3.1 Mesa 21.1.0-devel (git-e08a04a140)
=======================================================
[build] use-vbo=false: FPS: 702 FrameTime: 1.425 ms
[build] use-vbo=true: FPS: 722 FrameTime: 1.385 ms
[texture] texture-filter=nearest: FPS: 1963 FrameTime: 0.509 ms
[texture] texture-filter=linear: FPS: 1954 FrameTime: 0.512 ms
[texture] texture-filter=mipmap: FPS: 2002 FrameTime: 0.500 ms
[shading] shading=gouraud: FPS: 489 FrameTime: 2.045 ms
[shading] shading=blinn-phong-inf: FPS: 512 FrameTime: 1.953 ms
[shading] shading=phong: FPS: 478 FrameTime: 2.092 ms
[shading] shading=cel: FPS: 480 FrameTime: 2.083 ms
[bump] bump-render=high-poly: FPS: 175 FrameTime: 5.714 ms
[bump] bump-render=normals: FPS: 2311 FrameTime: 0.433 ms
[bump] bump-render=height: FPS: 1885 FrameTime: 0.531 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 1387 FrameTime: 0.721 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 529 FrameTime: 1.890 ms
[pulsar] light=false:quads=5:texture=false: FPS: 2282 FrameTime: 0.438 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 240 FrameTime: 4.167 ms
[desktop] effect=shadow:windows=4: FPS: 1165 FrameTime: 0.858 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 215 FrameTime: 4.651 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 214 FrameTime: 4.673 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 238 FrameTime: 4.202 ms
[ideas] speed=duration: FPS: 303 FrameTime: 3.300 ms
[jellyfish] <default>: FPS: 683 FrameTime: 1.464 ms
[terrain] <default>: FPS: 34 FrameTime: 29.412 ms
[shadow] <default>: FPS: 315 FrameTime: 3.175 ms
[refract] <default>: FPS: 41 FrameTime: 24.390 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 1542 FrameTime: 0.649 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 1546 FrameTime: 0.647 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 1520 FrameTime: 0.658 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 1545 FrameTime: 0.647 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 1548 FrameTime: 0.646 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 1506 FrameTime: 0.664 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 1507 FrameTime: 0.664 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 1505 FrameTime: 0.664 ms
=======================================================
                                  glmark2 Score: 1016 
=======================================================

Display resolution was 1920x1080@60Hz.
What further performance increases can I expect in the optimal case?
How performs the latest Mali-driver in this benchmark and would the results be significant and comparable? And Android? Is Panfrost feature complete?
I would appreciate any comments on that very much.
So - what's the current Panfrost status?

[cdu13a]

What further performance increases can I expect in the optimal case?
How performs the latest Mali-driver in this benchmark and would the results be significant and comparable? And Android? Is Panfrost feature complete?
I would appreciate any comments on that very much.
So - what's the current Panfrost status?

The panfrost driver has not really seen much work on performance. So there should be a good amount of room for improvements in that area. When they get to performance optimizations that is. Feature development comes first however.

Panfrost is still not feature complete, but making good progress. see https://gitlab.freedesktop.org/mesa/mes ... atures.txt if you want to see what is currently complete.

[jgmdev]

Also just in case, tobetter patched the dts files to add a higher clock speed for the gpu from 800mhz to 1ghz https://github.com/tobetter/linux/commi ... b0c8e8f201 I haven't done proper testing yet comparing glmark running on 800mhz and 1ghz but I suppose it should improve performance.

[tobetter]

Also just in case, tobetter patched the dts files to add a higher clock speed for the gpu from 800mhz to 1ghz https://github.com/tobetter/linux/commi ... b0c8e8f201 I haven't done proper testing yet comparing glmark running on 800mhz and 1ghz but I suppose it should improve performance.

I have not seen noticeable improvement with Panfrost between 800MHz and 1GHz while Bifrost shows differences only with Wayland. It would be nice someone try it out with ArchLinux.

[mægpie]

..1ghz but I suppose it should improve performance.

I made the benchmark above on linux-odroid-5.11 and last uboot of your repo, and the GPU was already clocked to 1GHz by default.

@cdu13a : Thanks for the very promising evaluation and the link!
So benchmarking will continue to be as entertaining as in the recent weeks... Fine!

@tobetter : Such a chart is exactly, what I've been asking for. So it seems that after a score of 1100 on 1080p we are near at the maximum, that is the hardware capable of?

P.S.I really would like to help you out, but I migrated completely to the Odroid-N2 now, and am not willing to install an entire Gnome-Desktop for Benchmarking purposes...

EDIT: You know what? If until tomorrow no one has posted the requested Benchmarks, I will install Gnome and provide you the results. Until then - GN8

[tobetter]

@tobetter : Such a chart is exactly, what I've been asking for. So it seems that after a score of 1100 on 1080p we are near at the maximum, that is the hardware capable of?

The score of 1100 is with ARM Mali Bifrost driver, it came from ARM and Amlogic. So...I believe that's most hardware capable score as of now. If CPU freq is also raised up, Panfrost performance is also a bit improved, but not like Bifrost.

[jgmdev]

I made the benchmark above on linux-odroid-5.11 and last uboot of your repo, and the GPU was already clocked to 1GHz by default.

Whoa that score of 1016 is almost 200 points up from last time nice...

EDIT: You know what? If until tomorrow no one has posted the requested Benchmarks, I will install Gnome and provide you the results. Until then - GN8

I'm looking forward for those results , also notice that in the past benchmarks gnome performed lower than wayfire, lets see how it goes now.

[tobetter]

EDIT: You know what? If until tomorrow no one has posted the requested Benchmarks, I will install Gnome and provide you the results. Until then - GN8

I'm looking forward for those results , also notice that in the past benchmarks gnome performed lower than wayfire, lets see how it goes now.

I think different desktop will give different benchmark scores, I've run the same benchmark on KDE and it gives relatively poor scores than GNOME and probably Wayfire or other lightweight desktop could give better figures.

[istanbulls]

I have KDE-wayland, Gnome Wayland, Wayfire images installed on my SSD, I can test each image separately in 1 few minutes.
I'm looking at video performance and I don't see much difference. Really, I focus more on the performance I get while using it than on tests, so I go with what's the best desktop experience (best for me)

How should I test? If you show me a way, I'll do the tests. A few small tips would be helpful.

[istanbulls]

** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
** Failed to set swap interval. Results may be bounded above by refresh rate.

I keep getting these errors. What is wrong?

Code: Select all

n2p@odroid:~$ uname -a
Linux odroid 5.10.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.10.16-202102191318~groovy (2021-02-19) aarch64 aarch64 aarch64 GNU/Linux
2p@odroid:~$ glmark2
** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
** Failed to set swap interval. Results may be bounded above by refresh rate.
=======================================================
    glmark2 2021.02
=======================================================
    OpenGL Information
    GL_VENDOR:     Mesa/X.org
    GL_RENDERER:   llvmpipe (LLVM 11.0.0, 128 bits)
    GL_VERSION:    3.1 Mesa 21.1.0-devel (git-14b2dc0013)
=======================================================
** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
** Failed to set swap interval. Results may be bounded above by refresh rate.
[build] use-vbo=false: FPS: 146 FrameTime: 6.849 ms

[tobetter]

** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
** Failed to set swap interval. Results may be bounded above by refresh rate.

I keep getting these errors. What is wrong?

Code: Select all

n2p@odroid:~$ uname -a
Linux odroid 5.10.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.10.16-202102191318~groovy (2021-02-19) aarch64 aarch64 aarch64 GNU/Linux
2p@odroid:~$ glmark2
** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
** Failed to set swap interval. Results may be bounded above by refresh rate.
=======================================================
    glmark2 2021.02
=======================================================
    OpenGL Information
    GL_VENDOR:     Mesa/X.org
    GL_RENDERER:   llvmpipe (LLVM 11.0.0, 128 bits)
    GL_VERSION:    3.1 Mesa 21.1.0-devel (git-14b2dc0013)
=======================================================
** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
** Failed to set swap interval. Results may be bounded above by refresh rate.
[build] use-vbo=false: FPS: 146 FrameTime: 6.849 ms

Looks like Panfrost driver is not loaded since log says GL_RENDERER is llvmpipe which has to be Panfrost. Check if Panfrost driver is loaded with lsmod | grep panfrost or check if you are running Bifrost driver.

[mægpie]

So - here are the quite interesting results of my benchmarking yesterday:



At first I have to apologize : I wasn't able to reproduce the very high score of my last post :
I use the tiling plugin of Wayfire with added padding, so the render-window of glmark2 seems to have been scaled down or cut off. I guess, that explains the ~10% difference to the last result.

So the benchmark was made with floating windows on Wayfire, without wallpaper on both DE's, and additionally I turned tracker off on GNOME3 - otherwise that would have been an unfair comparision, I guess.
The benchmarks were executed in series on each DE on the same user-account by an script and the stout piped to the files containing the results.

As an suprising summary GNOME/Mutter performed through the line considerably better than Wayfire on the glmark-wayland benchmarks, but nearly failed on the other benchmarks.
BUT - that doesn't reflect the user experience in ANY WAY.
I invite everyone to test this out: GNOME's rendering of GTK3, the font-rendering and even the wallpaper looks awful in relation to Wayfire. There are artifacts here and there, The whole desktop feels sluggy input-wise and all effects are lagging. Not that GNOME isn't useable on the Odroid-N2 with my system, but the difference in response time's and rendering quality is so evident in relation to Wayfire that the numerical benchmark results have wonderstrucked me...

I hope this results are of use for someone here, and if the community is interested, I would update the results when something relevant happens to my setup with the coming updates - now, that I have the scripts and the Templates. If someone is interested in the results of other Kernels or anything else, I could help out as long as I have GNOME installed. So you shouldn't hesitate to ask for soon.

EDIT: The result also shows that performance-governor doesn't provide any big advantages anymore as @chewitt stated, although it appears to me, that WebGL- Aquarium and Dynamic Cubemap are performing a little bit more fluent with it.
2nd EDIT: GNOME's performance seems to suffer remarkably more than Wayfire by simple_ondemand governor...