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

[Rava]

Ok. Script was updated.

Yay!

[francois]

In your howto you propose nvidia.tar.bz2 which include
/etc/modprobe.d/nvidia-installer-disable-nouveau.conf
but you do nothing with it (does it go with nvidia.sh?):

Notice that /etc/modprobe.d/nvidia-installer-disable-nouveau.conf porteus stock is already set to:

Code: Select all

# generated by nvidia-installer
blacklist nouveau
options nouveau modeset=0

[Rava]

In your howto you propose nvidia.tar.bz2 which include
/etc/modprobe.d/nvidia-installer-disable-nouveau.conf
but you do nothing with it (does it go with nvidia.sh?):

I was wondering about that myself, and I have not have the time to research about all that nvidia.sh and all other components of Blaze method is really doing. I presume he can enlighten us on that enigma.

Notice that /etc/modprobe.d/nvidia-installer-disable-nouveau.conf porteus stock is already set to:

Code: Select all

# generated by nvidia-installer
blacklist nouveau
options nouveau modeset=0

You mean in the .run file? When I recall right about what had to be done to create a nvidia module (which doing all by hand and without Blaze scripted help is years ago, so probably I am not recalling it 100% correct) you also have to set nvidia-installer-disable-nouveau.conf when booting the system to just compile the nvidia driver.

[francois]

blacklist.xzm and nvidia.tar.bz2 are the same. Maybe merging the final driver nvidia.xzm and blacklist.xzm would be the best thing to do, thus blacklisting included in the driver. What do you think?

[Rava]

blacklist.xzm and nvidia.tar.bz2 are the same. Maybe merging the final driver nvidia.xzm and blacklist.xzm would be the best thing to do, thus blacklisting included in the driver. What do you think?

I agree, it should be merged. It is only needed once. And can be inserted into the driver by xzm2dir it out of e.g. nvidia.xzm .

[francois]

mergexzm
mergexzm - merge folder of modules and slack packages

[Blaze]

When I wrote a Russian article, it was 2016, and a lot has changed.

blacklist.xzm and nvidia.tar.bz2 are the same

I know about Now at my job there are a lot of tasks that I need to solve. I will look at this on this hollidays.

Отправлено спустя 1 день 36 минут 37 секунд:
Script and manual was updated.

Thanks.

[Rava]

mergexzm
mergexzm - merge folder of modules and slack packages

Do you have a downloaded Version?
I always get a Internal Server Error and the download fails.

[francois]

The script is in the first post just under the link. You can copy/paste.

[Ed_P]

The EDIT in this posting by donald shows how to merge xzm files, without the script. Kodi Krypton

[francois]

The procedure works well for me:
Linux-x86_64 NVIDIA Driver Version:410.93 was built under porteus most recent version. Moderators will understand.

Thanks

Edited as 20190122

[Rava]

Ok. Script was updated.

About nvidia.sh .

What do you think of the idea of putting blacklist.xzm elsewhere, and not into $PORTDIR/base/blacklist.xzm

In my setup, I put the xzm's needed for compiling into /optional/ and named them all XXX*, e.g. like so:

Code: Select all

root@porteus:/1/Porteus_4.0rc1b/porteus/optional# ls -1 XXX*
XXX05-devel_V20190113.xzm
XXXblacklist.xzm
XXXcrippled_sources_V20190113.xzm

By doing so, I can have one standard startup for XFCE, one for Openbox, and one for NVidia compile for Porteus x.x Kernel y.y without one interfering with the other. All I have to do is separate these via the Porteus start menu entry, done by GRUB's menu.lst like so:

Code: Select all

title Porteus 4.0rc1b x86-64 NVIDIA COMPILE
rootnoverify (hd0,0)
kernel (hd0,0)/Boot/vmlinuz_Porteus_4.0rc1b_x86_64 from=/mnt/sda1/Porteus_4.0rc1b/ ramsize=40% zram=25% timezone=Europe/Berlin volume=75% kmap=de noload=xfce load=openbox;023-mtpaint_dependencies;XXX 3
initrd (hd0,0)/Boot/initrd.xz_Porteus_4.0rc1b_x86_64
boot

title Porteus 4.0rc1b x86-64 Openbox
rootnoverify (hd0,0)
kernel (hd0,0)/Boot/vmlinuz_Porteus_4.0rc1b_x86_64 from=/mnt/sda1/Porteus_4.0rc1b/ ramsize=40% zram=25% timezone=Europe/Berlin volume=75% kmap=de noload=xfce load=openbox;023-mtpaint_dependencies 3
initrd (hd0,0)/Boot/initrd.xz_Porteus_4.0rc1b_x86_64
boot

title Porteus 4.0rc1b x86-64 XFCE
rootnoverify (hd0,0)
kernel (hd0,0)/Boot/vmlinuz_Porteus_4.0rc1b_x86_64 from=/mnt/sda1/Porteus_4.0rc1b/ ramsize=40% zram=25% timezone=Europe/Berlin volume=75% kmap=de 3
initrd (hd0,0)/Boot/initrd.xz_Porteus_4.0rc1b_x86_64
boot

This of course only works if there are no other modules names XXX*.xzm, but who would name a module like so, unless it is done to mark special occasion modules, e.g. ones for GPU driver compiling .

And having the path of the Porteus main folder and the kernel and initrd names all follow the same naming convention is done for two reasons:
● to minimise errors by naming the folders and files in a logical, descriptive way.
● to minimise errors when editing the menu.lst by having the same folders and files naming conventions throughout different Porteus versions.

By following the same logic, it is obvious that e.g. initrd for 3.1 x86_64 would be named and to be found like so:

Code: Select all

(hd0,0)/Boot/initrd.xz_Porteus_3.1_x86_64

[fulalas]

Link to nvidia.sh is pointing to blacklist module

[fulalas]

BTW, the script doesn't work for me with NVIDIA-Linux-x86_64-390.87:

Code: Select all

write_file: failed to create file nvidia/.wh..wh.aufs, because Operation not permitted

dir_scan: failed to make directory nvidia/.wh..wh.orph, because Operation not permitted

dir_scan: failed to make directory nvidia/.wh..wh.plnk, because Operation not permitted

create_inode: socket nvidia/tmp/.ICE-unix/5997 ignored

create_inode: socket nvidia/tmp/.ICE-unix/6445 ignored

create_inode: socket nvidia/tmp/.X11-unix/X0 ignored

create_inode: socket nvidia/tmp/.esd-1000/socket ignored
[=========================\                                    ] 2568/6027  42%
create_inode: socket nvidia/tmp/xdg-runtime-guest/keyring/control ignored

create_inode: socket nvidia/tmp/xdg-runtime-guest/keyring/pkcs11 ignored

create_inode: socket nvidia/tmp/xdg-runtime-guest/keyring/ssh ignored

create_inode: socket nvidia/tmp/xdg-runtime-guest/pulse/native ignored

create_inode: failed to create hardlink, because Operation not permitted

create_inode: failed to create hardlink, because Operation not permitted

create_inode: failed to create hardlink, because Operation not permitted

create_inode: failed to create hardlink, because Operation not permitted

create_inode: failed to create hardlink, because Operation not permitted

create_inode: failed to create hardlink, because Operation not permitted

create_inode: failed to create hardlink, because Operation not permitted

create_inode: failed to create hardlink, because Operation not permitted

create_inode: failed to create hardlink, because Operation not permitted

create_inode: failed to create hardlink, because Operation not permitted

create_inode: failed to create hardlink, because Operation not permitted

create_inode: failed to create hardlink, because Operation not permitted

create_inode: socket nvidia/var/run/NetworkManager/private-dhcp ignored

create_inode: socket nvidia/var/run/acpid.socket ignored

create_inode: socket nvidia/var/run/dbus/system_bus_socket ignored
[============================================================\ ] 6016/6027  99%

created 4082 files
created 567 directories
created 91 symlinks
created 1 devices
created 2 fifos
find: cannot delete `/tmp/nvidia/etc/udev': Directory not empty
find: cannot delete `/tmp/nvidia/etc/rc.d': Directory not empty
find: cannot delete `/tmp/nvidia/etc/profile.d': Directory not empty
find: cannot delete `/tmp/nvidia/etc/porteus': Directory not empty
find: cannot delete `/tmp/nvidia/etc/gconf': Directory not empty
find: cannot delete `/tmp/nvidia/etc/X11_': Directory not empty
find: cannot delete `/tmp/nvidia/etc/': Directory not empty
/base/blacklist.xzm does not exist

[Rava]

^
Since I did not write the script, I can only offer you one solution to fix these errors.

Edit the script to abort just prior creating the actual finale module. Not the first initial module that Blaze's script uses to get the altered files from the system. But prior the line creating the 2nd finale one.

Then go as root into that folder that would be converted into the final module and remove everything that is not necessary manually, like all tmp/.ICE-unix or tmp/xdg-runtime-guest and also all hardlinks.

Then do a manual dir2xzm on the just altered source folder.

When the above errors are not the actual final module, but the first one the script creates for just copying all altered files, then the fix is not that easily.

You then would have to stop the script after it does the copy operation for the first, initial module, and also after its deletion of some files.
Just then, like above, remove everything that is not necessary manually, like all tmp/.ICE-unix or tmp/xdg-runtime-guest and also all hardlinks. And again do a manual dir2xzm.

HTH!