[SOLVED] Can't buil Nvidia driver on -current x86_64

igadoter · 02-15-2018, 09:55 AM

My life is worsening each day. My first install of 14.2, 64 bit went fine. In my next install of 14.2, 64 bit, I have to set "nomodeset" option for kernel to be able to login in virtual console. Today I just installed -current - without nomodeset option computer freezes , but even that my attempt to install NVIDIA driver failed - installer complains is unable to create kernel module. I looked at log - but the only one thing more or less clear is that installer complains about kernel configuration

Code:

  echo >&2;							\
   echo >&2 "  ERROR: Kernel configuration is invalid.";		\
   echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
   echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";	\
   echo >&2 ;							\

I view all my troubles as constant regression from the first plain Slackware64 14.2 release.

Edit: probably I shouldn't start new thread, some information I found are needed: my -current is running recent kernel version 4.14.19, nvidia driver is 304.137 64 bit.

jmccue · 02-15-2018, 11:05 AM

This will not be of any help, but I really feel your pain.

I also have to use 304.137 and that is marked as the very last release for '304', that means we are SOL, Nvidia Help. No more updates for us when new kernels are released

I still have issues using nouveau, so once Slackware Next is released I will purchase a Intel Graphics Board that has been "Open Sourced".

The system I have uses a embedded Nvida and I was innocent at the time, not expecting Nvidia to pull this, but here we are. BTW, Nvidia has joined my growing list of tech never to purchase or use even if free

Sorry for the rant,
John

ponce · 02-15-2018, 11:19 AM

Hi igadoter,

I just read that the nvidia legacy driver 304.x isn't maintained anymore since the end of 2017

http://nvidia.custhelp.com/app/answers/detail/a_id/3142

that said, I spotted a couple of patches for the latest version of the driver that maybe could help (you probably need just the first)

https://pkgs.rpmfusion.org/cgit/nonf...4_kernel.patch
https://pkgs.rpmfusion.org/cgit/nonf...5_kernel.patch

if you're using the NVIDIA*run file you can probably generate a new patched one passing it the patch with the option "--apply-patch".

igadoter · 02-15-2018, 01:07 PM

@ponce you are the man! The patch really works. But using --apply-patch option with Nvidia installer is little tricky. For others how I did this: file containning patch is 4.14_kernel_patch, so let the Nvidia blob be in /tmp

Code:

$ ls /tmp
NVIDIA-Linux-x86_64-304.137.run

as root

Code:

# cd /tmp
# ./NVIDIA-Linux-x86_64-304.137.run --apply-patch 4.14_kernel.patch
Verifying archive integrity... OK
Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86_64 304.137................................................................................................................................................................
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ur a/kernel/nv-drm.c b/kernel/nv-drm.c
|--- a/kernel/nv-drm.c  2017-09-14 23:51:09.000000003 +0300
|+++ b/kernel/nv-drm.c  2017-12-06 18:47:48.279729889 +0200
--------------------------
File to patch:

when see this "File to patch:" it is query from patch program, you should answer with "kernel/nv-drm.c",now the things go on

Code:

File to patch: kernel/nv-drm.c
patching file kernel/nv-drm.c
Adding files to archive named "NVIDIA-Linux-x86_64-304.137-custom.run"...
./libglx.so.304.137
./libnvidia-ml.so.304.137
.
.
.
./README.txt
./pkg-history.txt
./tls_test_dso.so

CRC: 3850583096
MD5: a6e95808e7e8fc46424aa975829885e8

Self-extractible archive "NVIDIA-Linux-x86_64-304.137-custom.run" successfully created.

finally in /tmp appears new patched driver with extension -custom.run

Code:

# ls /tmp
NVIDIA-Linux-x86_64-304.137-custom.run
NVIDIA-Linux-x86_64-304.137.run

now

Code:

# ./NVIDIA-Linux-x86_64-304.137-custom.run

compiled kernel module and installed correctly driver, at least for me.

I am not specialist bu I may guess problem is in header of patch

Code:

diff -ur a/kernel/nv-drm.c b/kernel/nv-drm.c
--- a/kernel/nv-drm.c   2017-09-14 23:51:09.000000003 +0300
+++ b/kernel/nv-drm.c   2017-12-06 18:47:48.279729889 +0200

I mean look at "a/kernel" vs "b/kernel" paths. Maybe for fully automatic process the header needs to be changed, the prefixes "a/" "b/" should be dropped, so header will be

Code:

diff -ur kernel/nv-drm.c kernel/nv-drm.c
--- kernel/nv-drm.c   2017-09-14 23:51:09.000000003 +0300
+++ kernel/nv-drm.c   2017-12-06 18:47:48.279729889 +0200