coeur-noir@asgard:~$ vulkan-smoketest
INTEL-MESA: warning: Haswell Vulkan support is incomplete
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
terminate called after throwing an instance of 'std::runtime_error'
what(): failed to find any capable Vulkan physical device
Abandon (core dumped)
coeur-noir@asgard:~$
…sounds like it’s a no-go for my haswell cpu ?
Anyway remember I have no flickering shadows problem when booting the same computer on 16.04.
Can it be related to screen refresh rate - that should be 60 Hz or bit lesser. How can I ensure that value ?
coeur-noir@asgard:~$ inxi -G
Graphics: Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
Display Server: x11 (X.Org 1.20.4 ) driver: intel
Resolution: 1920x1080@60.00hz
OpenGL: renderer: Mesa DRI Intel Haswell Desktop version: 4.5 Mesa 19.0.8
coeur-noir@asgard:~$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
HDMI1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
1920x1080 60.00*+
1600x1200 60.00
1680x1050 59.88
1280x1024 75.02 60.02
1440x900 74.98 59.90
1280x960 60.00
1152x864 75.00
1024x768 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
640x480 75.00 72.81 66.67 59.94
720x400 70.08
HDMI2 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
coeur-noir@asgard:~$
edit, later : same problem under ubuntu ( default ) 19.10.
Not much… they labelled the issue as « notourbug » which may be true but does not help me.
I forgot to ask - is this an external screen you are connected to? If so, does connecting via VGA/DVI instead of HDMI and visa-versa work better?
Not a laptop here, so it’s my one and only external monitor, on DVI.
I’ll try VGA, not sure I have an HDMI out on computer ( I have one HDMI in on screen ).
And still, why wouldn’t I suffer the same issues when booting this same setup on 16.04 ?
happy to help - but snowed under for the next few weeks.
A patch exists and therefore the fix is coming in the « official » driver… https://gitlab.freedesktop.org/mesa/mesa/issues/2011#note_277583
( it’s provided through ppa:canonical-x/x-staging )
1 Like
And damn, problem is back when updating mesa from regular official repositories…
coeur-noir@asgard:~$ dpkg -l | grep mesa
ii libegl-mesa0:amd64 19.2.1-1ubuntu1~18.04.1 amd64 free implementation of the EGL API -- Mesa vendor library
ii libegl1-mesa:amd64 19.2.1-1ubuntu1~18.04.1 amd64 transitional dummy package
ii libgl1-mesa-dri:amd64 19.2.1-1ubuntu1~18.04.1 amd64 free implementation of the OpenGL API -- DRI modules
ii libgl1-mesa-dri:i386 19.2.1-1ubuntu1~18.04.1 i386 free implementation of the OpenGL API -- DRI modules
ii libgl1-mesa-glx:amd64 19.2.1-1ubuntu1~18.04.1 amd64 transitional dummy package
ii libgl1-mesa-glx:i386 19.2.1-1ubuntu1~18.04.1 i386 transitional dummy package
ii libglapi-mesa:amd64 19.2.1-1ubuntu1~18.04.1 amd64 free implementation of the GL API -- shared library
ii libglapi-mesa:i386 19.2.1-1ubuntu1~18.04.1 i386 free implementation of the GL API -- shared library
ii libgles2-mesa:amd64 19.2.1-1ubuntu1~18.04.1 amd64 transitional dummy package
ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64 Mesa OpenGL utility library (GLU)
ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU)
ii libglx-mesa0:amd64 19.2.1-1ubuntu1~18.04.1 amd64 free implementation of the OpenGL API -- GLX vendor library
ii libglx-mesa0:i386 19.2.1-1ubuntu1~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library
ii libosmesa6:amd64 19.2.1-1ubuntu1~18.04.1 amd64 Mesa Off-screen rendering extension
ii libosmesa6:i386 19.2.1-1ubuntu1~18.04.1 i386 Mesa Off-screen rendering extension
ii libwayland-egl1-mesa:amd64 19.2.1-1ubuntu1~18.04.1 amd64 transitional dummy package
ii mesa-utils 8.4.0-1 amd64 Miscellaneous Mesa GL utilities
ii mesa-utils-extra 8.4.0-1 amd64 Miscellaneous Mesa utilies (opengles, egl)
ii mesa-va-drivers:amd64 19.2.1-1ubuntu1~18.04.1 amd64 Mesa VA-API video acceleration drivers
ii mesa-vdpau-drivers:amd64 19.2.1-1ubuntu1~18.04.1 amd64 Mesa VDPAU video acceleration drivers
ii mesa-vulkan-drivers:amd64 19.2.1-1ubuntu1~18.04.1 amd64 Mesa Vulkan graphics drivers
coeur-noir@asgard:~$
New version of mesa has just been released in 18.04 as part of the HWE - i.e. 18.04 users have now got the 19.10 graphics stack.
Looks like the maintainer who I guess had the patch in the staging ppa (?) didnt include it in the main release.
Suggest contact the maintainer who you were previously communicating with.
« The fix is available from 19.2.5 version and higher. »
So in 18.04.4 ?
currently 20.04 has 19.2.4 … so highly likely 20.04 will get 19.2.5 or later at release in april. So yes. 18.04.4 will also receive this update in august.
Trying with 19.10 and so mesa 19.2.8 I’ve noticed a new « bug ».
Launch a web browser on a site with notifications enabled ( firefox & deezer in this case ).
Keep the browser running ( minimized window or other workspace ) now play SuperTuxKart full screen.
Each time a web browser notification pops up, there’s a glitch ( site briefly appears ) and a major slow down in framerate in the game, major enough to interfere in playing.
I did not have that in 18.04. And I don’t have that in 16.04.
Think this is where you should disable notifications in raven. I am sure whilst playing you dont want to be disturbed anyway!
Mmm funny answer but wrong one
I’m okay with those notifications while playing - knowing the title songs in background…
And I did not have this problem in 18.04 (budgie). I don’t have it in 16.04 (unity). So it’s a kind of regression.
https://gitlab.freedesktop.org/mesa/mesa/issues/2011#note_448681 suggests it’s not related to mesa but maybe to window manager or compositor.
How narrow down the culprit ?
So is this related to mesa or mutter or something else ?
If of any interest, my most recent issue with « notifications » over STK seems to get solved thanks to
adding a file /etc/X11/xorg.conf.d/20-intel-graphics.conf
containing
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "TripleBuffer" "true"
Option "TearFree" "true"
EndSection
Any hint ?
Hmm… if this makes any sense, intel says