[SOLVED] Xorg doesn't start after mesa-19.1.1 update ("no unwind info found" error).

ponce · 06-28-2019, 02:47 PM

Quote:

Originally Posted by pee_bee

Slightly different - actually k5.1.15 currently - but equivalent update status.

maybe there's no difference, but have you tried with the stock kernel in current?

Jefferson · 06-28-2019, 04:30 PM

Quote:

Originally Posted by orbea

@Jefferson That seems like an improvement as its now using nouveau instead of swrast (software), but that didn't seem to solve all of your problems... Can you try compiling mesa from source yourself again, I hope at least that works now? It may be worth to also try newer (git) or older versions to see if they are better.

I tried to build 19.1.1 using slackbuild (untouched). But i get same result (see attached Xorg.0.log).
When i tried to build 19.1.1 with removed libglvnd and "-Dglvnd=false" in Slackbuild, i get these errors:

Code:

/usr/bin/ld: cannot find -lGL
/usr/bin/ld: cannot find -lEGL
collect2: error: ld returned 1 exit status

Earlier i wrote that i had no problems with self-built 19.0.7.
Will try mesa from git later.

mats_b_tegner · 06-28-2019, 04:44 PM

The older nVidia legacy drivers (340.xxx and 304.xxx) are not compatible with libglvnd as far as I know. I solved it by removing/blacklisting libglvnd and rebuilding mesa 19.0.7 without libglvnd i.e removing

Code:

--enable-libglvnd

from the mesa.SlackBuild-script.

Edit:
Sorry I noticed that you are using nouveau.

orbea · 06-28-2019, 05:07 PM

Quote:

Originally Posted by Jefferson

I tried to build 19.1.1 using slackbuild (untouched). But i get same result (see attached Xorg.0.log).
When i tried to build 19.1.1 with removed libglvnd and "-Dglvnd=false" in Slackbuild, i get these errors:

Code:

/usr/bin/ld: cannot find -lGL
/usr/bin/ld: cannot find -lEGL
collect2: error: ld returned 1 exit status

Earlier i wrote that i had no problems with self-built 19.0.7.
Will try mesa from git later.

I had hoped we got past that one already... Hmm, this is 32-bit Slackware right? Maybe could you make sure that older meson versions have the same problem or not? Temporarily replacing the meson in current with the version from SBo should be fine for testing. Maybe its unrelated, but I am reading about issues with newer meson and 32-bit mesa on irc.

Edit: You could also try removing mesa before recompiling mesa to see if that helps...

Jefferson · 06-29-2019, 10:16 AM

That's right, 32-bit.
I tried to build 19.1.1 with meson 0.49.
When build process reaches 'mesa-demos-8.4.0 configure', it fails with an error:

Code:

checking for GL... no
checking GL/gl.h usability... no
checking GL/gl.h presence... no
checking for GL/gl.h... no
configure: error: GL not found

I removed mesa before compilation.
Also tried removing libglvnd with edited out libglvnd in Slackbuild - same result.

orbea · 06-29-2019, 10:42 AM

Quote:

Originally Posted by Jefferson

That's right, 32-bit.
I tried to build 19.1.1 with meson 0.49.
When build process reaches 'mesa-demos-8.4.0 configure', it fails with an error:

Code:

checking for GL... no
checking GL/gl.h usability... no
checking GL/gl.h presence... no
checking for GL/gl.h... no
configure: error: GL not found

I removed mesa before compilation.
Also tried removing libglvnd with edited out libglvnd in Slackbuild - same result.

Sorry, I forgot about the mesa-demos and it seems the SlackBuild doesn't consider if mesa has already been installed or not when building them. You can just temporarily comment, remove or otherwise disable the mesa-demos build process in the mesa.SlackBuild before trying again. They are not important for this test.

Jefferson · 06-29-2019, 01:19 PM

Built it without demos - same result.

orbea · 06-29-2019, 02:25 PM

So its not meson or libglvnd, I would try the mesa git master next to make sure its not already fixed.

Jefferson · 06-29-2019, 04:12 PM

I tried git version of mesa. Result is the same.
Looks like blacklisting mesa wasn't such a bad idea after all. At least temporarily.

orbea · 06-29-2019, 05:06 PM

Could you try compiling the previous release from source yourself? It would be good to make sure it still works.

Jefferson · 06-30-2019, 04:06 AM

orbea, i can build it, but i need Slackbuild or precise "./configure" command line to do it.
I did compile 19.0.7 earlier, like i said, but i did it using Autotools with following keys: "--prefix=/usr --enable-autotools", iirc.
I don't know how to do it with meson (mesa's meson page wasn't helpful).

pee_bee · 06-30-2019, 05:26 AM

I have reverted just /usr/lib/xorg/modules/dri/nouveau_dri.so
to the version in:
mesa-19.0.6-i586-1.txz
which does not have the dependency on libsensors.so.5

but apart from this reversion the system is built with mesa-19.1.1-i586-1.txz

with this sole reversion, the system and glxgears works as expected

orbea · 06-30-2019, 09:06 AM

Quote:

Originally Posted by Jefferson

orbea, i can build it, but i need Slackbuild or precise "./configure" command line to do it.
I did compile 19.0.7 earlier, like i said, but i did it using Autotools with following keys: "--prefix=/usr --enable-autotools", iirc.
I don't know how to do it with meson (mesa's meson page wasn't helpful).

You should be able to compile the previous version with the meson command-line found in Pat's SlackBuild, just make sure to provide the correct mesa tarball. Upstream mesa switched to meson for a while and Pat only switched when the deprecated autotools build was removed. It would be good to confirm its not an issue in mesa's new meson build by building an older version with meson.

pee_bee · 07-01-2019, 01:12 AM

The answer?

Sun Jun 30 22:45:12 UTC 2019
x/mesa-19.1.1-i586-2.txz: Rebuilt.
Don't build the swr Gallium driver on IA32 - it leads to an illegal
instruction startup crash with CPUs that lack AVX support.
Thanks to Jefferson and Johnson.

pee_bee · 07-01-2019, 03:06 AM

Yes - fixes