[HOWTO] make a xzm module driver for NVIDIA video card

[Blaze]

rych, well, don't remove glibc-2.35

[ncmprhnsbl]

An interesting thread on compatibility of NVidia drivers with 6.0 kernels: https://forums.developer.nvidia.com/t/4 ... l/229735/4
Basically, I might have to apply a patch. But anyway, I'm not even getting to that stage, at the moment my porteus doesn't pass NVidia's "CC sanity check"

pretty sure the latest 470.161 release doesn't need to patched for 6.* kernels any more.. and the 5.25 series for newish cards is fine too..

[Rava]

Working on creating the NV driver 340.108 for kernel 6.1.1, will use the *run as provided by beny.
Since Blaze wrote

Note 1: Compiler that was used.
for kernel 6.1.1: 11.2.0-x86_64

and that is the very same version as in the 05-devel module of Porteus 5.0:

Code: Select all

root@porteus:/mybin/linux/porteus/5.0/x86-64# md5sum 05-devel.xzm 
4ad2c0217ec914cb02aab3b77fd55fe5  05-devel.xzm
root@porteus:/mybin/linux/porteus/5.0/x86-64# mloop 05-devel.xzm
using /dev/loop11

Please wait while I gather some info ....


 Nothing is mounted in /mnt/loop.



 #################################
 Your module has been mounted at: 
/mnt/loop

 You can unmount it by typing uloop

 Here is a list of the files:
etc  lib  lib64  usr  var

root@porteus:/mybin/linux/porteus/5.0/x86-64# /mnt/loop/usr/bin/cc --version
cc (GCC) 11.2.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

all should be ready to set up the compile-boot with kernel 6.1.1, with its 000-kernel.xzm and its 06-crippled_sources-6.1.1-64bit.xzm and of course the generic blacklist module, and of course boot into mode 3 (text mode, virtual terminal mode)

Or am I still missing things?

[beny]

when you have to use save-changes script to save the nvidia package is better that you do this task on a clean system to reduce to add files that isn't for the nvidia driver,but i can go wrong on this....

[Rava]

^
you are correct, aside from the needed modules as named above I think I will only load 000- 001- and 002- modules.
not even any 003- should be needed since you cannot and should not startx prior the compilation of the driver for NVIDIA GPU.

[i3slkiller]

I wrote the script which builds nvidia driver module unattendedly https://gitlab.com/i3slkiller/porteusbu ... type=heads
I need to know from nvidia card owners if this module (not) works (no, I don't have nvidia card).

[Blaze]

i3slkiller, I don't have NVIDIA card too, but your script looks very nice.

Thanks.

[Ed_P]

I wrote the script which builds nvidia driver module unattendedly https://gitlab.com/i3slkiller/porteusbu ... type=heads

I don't have a NVIDIA card either and when I went to your link nothing I clicked on downloaded it. Do I have to be a gitlab member to download files?

[i3slkiller]

Do I have to be a gitlab member to download files?

No.

[Ed_P]

Thank you for the picture i3slkiller.

For others that come this way it should be noted the image posted is what displays when the Code v button in the upper right hand corner is pressed.

[Rava]

I try it out. The issue is: some nvidia drivers need patches.
For now I was to lazy to work my way through the wasteland that are such high level patches, therefore I still use the old 010-nvidia-340.108-k.5.4.30-porteus-v5.0-x86_64_rava.xzm
The NV driver version is 340.108 and the last kernel that was able to be compiled for without patches is 5.4.30-porteus.

I wish there was a way, I could try your script, but since I think I have to update Port first. This is my current system:

Code: Select all

001-core.xzm:20231229
002-xorg.xzm:20231229
002-xtra.xzm:20231229
003-xfce.xzm:20231229
06-man.xzm:20230915
initrd.xz:20220928

When your script can handle the nvidia driver patching, I will try it out. If it does not, hopefully some of us manage to figure out how that patching must be done.

[i3slkiller]

some nvidia drivers need patches

Oops... I didn't think about it earlier, mainly because 550.67 builds on virtualbox vm without any patches. I modified this script that it builds both 340.108 and 550.67 driver, and included patches for older one.

And of course run this script on Always Fresh mode.

[ncmprhnsbl]

thanks for this, looks great

I modified this script that it builds both 340.108 and 550.67 driver

an option for the 470.* branch too will be no doubt appreciated

[i3slkiller]

an option for the 470.* branch too will be no doubt appreciated

470.239.06 driver builds without issues for 6.6.20 kernel without patches, not sure if it will work

[Rava]

i3slkiller, I looked into the .SlackBuild script code.
Looks like it uses the newest NV driver version, unless $VERSION is specified.
How do I tell the .SlackBuild what version to use?