32-bit GLX (nvidia) not working after update, unless running with strace

garpu · 05-10-2024, 09:54 AM

Quote:

Originally Posted by af7567

Oh so I guess that is using the mesa libraries then?
I wanted to get an AMD card too since it seemed the best value but then a friend gave me their "old" Nvidia which wasn't really very old

Can't argue with free!

Daedra · 05-21-2024, 10:16 PM

Still not fixed with 555.42.02 beta driver.

UnrelatedMicrowave · 05-28-2024, 04:48 AM

I recompiled glibc after adding

Quote:

-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer

to the CFLAGS.
I saw this on the commit 374116c3 on the glibc from arch.

Now it is working, no segfaults when opening steam, but I'm not good with that stuff, should I recompile gcc-multilib after that? I'm having some problems compiling it. :x

Petri Kaukasoina · 05-28-2024, 05:24 AM

Quote:

Originally Posted by UnrelatedMicrowave

I recompiled glibc after adding -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer to the CFLAGS.
I saw this on the commit 374116c3 on the glibc from arch.

Now it is working, no segfaults when opening steam, but I'm not good with that stuff, should I recompile gcc-multilib after that? I'm having some problems compiling it. :x

You added -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer? But Arch removed them in commit 374116c3.

No need to recompile gcc.

Daedra · 05-28-2024, 11:04 AM

I am going to try this when I get home from work, but if anyone has time here is the Arch commit mentioned above that apparently fixes the issue.
https://gitlab.archlinux.org/archlin...9cf8723b141a90

Daedra · 05-28-2024, 02:37 PM

I had some downtime at work today so I recompiled Alien Bob's glibc multilib package with the fix from Arch and then tested it on my laptop and it does indeed finally fix the problem. I sent Eric an email and hopefully he can add this fix to his multilib packages.

Petri Kaukasoina · 05-28-2024, 02:54 PM

I don't quite understand what you are trying to do. And why it worked for you.

Slackware (and Alien) glibc is built with -O3. That implies -fomit-frame-pointer. It saves one processor register which helps producing more efficient code, especially when the 32-bit instruction set is used, where fewer registers are available. But it can mean trouble for a debugger, and that's why Arch had added -fno-omit-frame-pointer (and -mno-omit-leaf-frame-pointer) to the default compilation flags to make the compiled code use the frame pointer. It means less optimized code but probably it's not a significant loss with the 64-bit instruction set. Adding the frame-pointer to the 32-bit glibc caused the steam error. Now the commit 374116c3 removes that added '-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer' compiler option. But you can't remove it from Slackware CFLAGS because Slackware didn't add it in the first place.

This is the code in commit 374116c3:

Code:

CFLAGS=${CFLAGS/-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer/}

It removes the two options from the default $CFLAGS of Arch for compiling the 32-bit glibc.

So what did you actually change?

Daedra · 05-28-2024, 03:40 PM

Duplicate post ignore.

Daedra · 05-28-2024, 03:41 PM

Hi Petri,

All I did was change Eric's glibc SlackBuild..

Code:

build_glibc() {
  CFLAGS="-g $OPTIMIZ -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/include" \
  ../configure \
    --prefix=/usr \
    --libdir=/usr/lib${LIBDIRSUFFIX} \
    --enable-kernel=4.4 \
    --with-headers=/usr/include \
    --enable-add-ons \
    --enable-profile \
    $DISABLE_NSCD \
    --infodir=/usr/info \
    --mandir=/usr/man \
    --with-tls \
    --with-__thread \
    --without-cvs \
    $TARGET-slackware-linux

I even tested it again, I reinstalled the glibc multilib package from Eric's repo and it seg faulted like before. I then reinstalled the updated glibc multilib package with the above options and everything works as expected. I have only tried this on my laptop, I will try it on my main machine when I get home.

http://www.slackware.com/~alien/mult...lib.SlackBuild

UnrelatedMicrowave · 05-28-2024, 03:44 PM

I added it, I did not removed it.

Quote:

248: CFLAGS="-g $OPTIMIZ -I/usr/include -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer"

file: glibc-multilib.SlackBuild

I thought this was added to the arch build script because the lines were green on the commit, so I just added that stuff there and the problem was solved.
I don't have much idea of what I'm doing, I was only trying to replicate a solution that I saw (a solution that I interpreted wrongly).
It is working thought.

Petri Kaukasoina · 05-28-2024, 04:12 PM

Strange.

This is where Arch added -fno-omit-frame-pointer and -mno-omit-leaf-frame-pointer to the default compilation flags to improve the effectiveness of profiling and debugging tools 3 months ago: https://gitlab.archlinux.org/archlin...a8c7f4d48bbe1c

And 3 weeks ago Arch fixed the lib32-glibc Segmentation fault with Steam on Nvidia by removing -fno-omit-frame-pointer and -mno-omit-leaf-frame-pointer.

Now you added the same flags which caused the error in Arch in the first place!

UnrelatedMicrowave · 05-28-2024, 04:21 PM

Quote:

Originally Posted by Petri Kaukasoina

Strange.

This is where Arch added -fno-omit-frame-pointer and -mno-omit-leaf-frame-pointer to the default compilation flags to improve the effectiveness of profiling and debugging tools 3 months ago: https://gitlab.archlinux.org/archlin...a8c7f4d48bbe1c

And 3 weeks ago Arch fixed the lib32-glibc Segmentation fault with Steam on Nvidia by removing -fno-omit-frame-pointer and -mno-omit-leaf-frame-pointer.

Now you added the same flags which caused the error in Arch in the first place!

Yeah. My bad reading comprehension helped me with something. I really thought they added the flags because "line green = adding".
I guess being dumb isn't that bad in the end.

Petri Kaukasoina · 05-28-2024, 04:22 PM

Quote:

Originally Posted by UnrelatedMicrowave

I thought this was added to the arch build script because the lines were green on the commit, so I just added that stuff there and the problem was solved.

Yes, but look at the green lines carefully. An example script:

Code:

#!/bin/sh
echo The default Arch CFLAGS:
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer"
echo CFLAGS: $CFLAGS
echo The green line:
CFLAGS=${CFLAGS/-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer/}
echo CFLAGS: $CFLAGS

When you run it, you see the two compiler flags are removed. You need to scroll to see the ends of the lines below:

Code:

$ sh script
The default Arch CFLAGS:
CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
After the fix for glibc:
CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection

The green line removed the options you added.

UnrelatedMicrowave · 05-28-2024, 04:32 PM

Quote:

Originally Posted by Petri Kaukasoina

Yes, but look at the green lines carefully. An example script:

Code:

#!/bin/sh
echo The default Arch CFLAGS:
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer"
echo CFLAGS: $CFLAGS
echo The green line:
CFLAGS=${CFLAGS/-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer/}
echo CFLAGS: $CFLAGS

When you run it, you see the two compiler flags are removed. You need to scroll to see the ends of the lines below:

Code:

$ sh script
The default Arch CFLAGS:
CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
After the fix for glibc:
CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection

The green line removed the options you added.

Yeah, I read it again and what you are saying now makes sense to me. I guess I got a little bit less dumb now.

Petri Kaukasoina · 05-28-2024, 04:35 PM

You both succeeded in fixing the Steam problem the same way Arch caused the problem originally.

Hey wait a minute. Alien Bob's glibc was compiled 2024-04-19 with older gcc. Now you compiled it with new CFLAGS and with a new gcc-14.1.0 from two weeks ago, didn't you? Did you check if the new gcc builds a good glibc without any CFLAGS changes, with Alien Bob's original Slackbuild script?