nvidia-legacy304-kernel on -current

JayByrd · 11-28-2022, 06:25 PM

Quote:

Originally Posted by fourtysixandtwo

I didn't go back and read the whole thread

The only time I've seen that kind of message was if I was using a kernel that was compiled with the newer glibc, booted on an older glibc system, and then tried to compile something. You weren't running a kernel downloaded from or complied on -current are you?

No. At the time, I was running 5.15.63 that I compiled myself (on 15.0.)

I did, however, get the kernel source (5.19.17) via Pat's kernel-source package for -current... Could that be the problem?

JayByrd · 11-28-2022, 06:44 PM

Quote:

Originally Posted by JayByrd

No. At the time, I was running 5.15.63 that I compiled myself (on 15.0.)

I did, however, get the kernel source (5.19.17) via Pat's kernel-source package for -current... Could that be the problem?

Well, the answer to that question seems to be "no." I just tried the same procedure in a 15.0 VM, and it's building fine.

Namely: installed Pat's kernel-source-5.19.17 package on 15.0, cd to the source directory, and do "make clean;make prepare;make" and all is good...

EDIT: nevermind... see below.

fourtysixandtwo · 11-28-2022, 06:45 PM

Yes, you can't just use packages linked against the newer glibc. Better to download and build the package from -current source if you want a slackware package.

fourtysixandtwo · 11-28-2022, 06:54 PM

Quote:

Originally Posted by JayByrd

Well, the answer to that question seems to be "no." I just tried the same procedure in a 15.0 VM, and it's building fine.

Namely: installed Pat's kernel-source-5.19.17 package on 15.0, cd to the source directory, and do "make clean;make prepare;make" and all is good...

I was going to mention that, but it defeats the purpose of installing the package imho.

JayByrd · 11-28-2022, 08:15 PM

Quote:

Originally Posted by JayByrd

...I did, however, get the kernel source (5.19.17) via Pat's kernel-source package for -current... Could that be the problem?

Confirmed. I get the "LIBC 2.34" error only when trying to build from the prepackaged kernel-source-5.19.17 shipped with -current.

Lesson learned: when building newer kernels on 15.0, get your kernel source tarball from kernel.org.

JayByrd · 12-01-2022, 10:24 AM

Ok, so I believe I've got everything squared away now, nVidia-wise.

I've put in place patches that have the legacy304 nvidia kernel module compiling and working great on kernels up to and including 6.1-rc7.

Today I'll work on finding and/or creating patches since my last update (the past 10 months, or so) for any CVEs issued pertinent to xorg-server-legacy119.

Once I get that completed, I'll re-post the updated build scripts for the whole thing: nvidia-driver, nvidia-kernel, and xorg-server-legacy119...