Sorry I missed the replies in my email
I will test disabling the extensions later
I can confirm that these are the same (because I use the same custom kernel and GL/Vulkan/EGL/GLES driverstack):
* lspci -k # to see if the kernel driver changed
* es2_info | grep ^GL_ # to see if the GL driver changed
I will not be able to do this because of no wayland support in the driverstack:
Or by checking the scanout method using MUTTER_DEBUG=kms and grepping the log for "Post" (Wayland only though).
I will check this later as well:
You can test that theory by comparing the windowed performance between jammy and noble.
Sorry I missed the replies in my email
I will test disabling the extensions later
I can confirm that these are the same (because I use the same custom kernel and GL/Vulkan/EGL/GLES driverstack):
* lspci -k # to see if the kernel driver changed
* es2_info | grep ^GL_ # to see if the GL driver changed
I will not be able to do this because of no wayland support in the driverstack:
Or by checking the scanout method using MUTTER_DEBUG=kms and grepping the log for "Post" (Wayland only though).
I will check this later as well:
You can test that theory by comparing the windowed performance between jammy and noble.