Code: Select all
VERSION=340.108 ./download.sh
VERSION=340.108 ./08-nvidia.PorteusBuild
Code: Select all
VERSION=340.108 bash download.sh
VERSION=340.108 bash 08-nvidia.PorteusBuild
Code: Select all
VERSION=340.108 ./download.sh
VERSION=340.108 ./08-nvidia.PorteusBuild
Code: Select all
VERSION=340.108 bash download.sh
VERSION=340.108 bash 08-nvidia.PorteusBuild
I guess, VERSION=340.108 ./download.sh can be downloaded in any Porteus, so it must not be the one set up for compiling the driver?i3slkiller wrote: ↑30 Apr 2024, 05:13BTW in porteusbuild script, you can also specify where temporary files will be saved (TMP=/path/to/tmp, should be empty folder, on disk with sufficient free space and unix permissions, will be created if not exist) and where module will be saved (OUTPUT=/path/to/output, old module with the same name will be replaced).Code: Select all
VERSION=340.108 ./download.sh VERSION=340.108 ./08-nvidia.PorteusBuild
Yes, but only in 64-bit, what I have to fix (by the way, I didn't think earlier that someone may want to use this script to download files for platform other than the one on which was executed).
i3slkiller wrote: ↑30 Apr 2024, 05:13in porteusbuild script, you can also specify where temporary files will be saved (TMP=/path/to/tmp [...]
Code: Select all
SRC=where/to/download/items ./path/to/download.sh
SRC=where/to/download/items ./path/to/08-nvidia.PorteusBuild
So we have SRC for the path for downloading and using the downloaded sourcei3slkiller wrote: ↑30 Apr 2024, 10:13I just added SRC variable where you can type where downloadable items used to build module will be saved (download.sh) and where the build script expect them (08-nvidia.PorteusBuild) [default value is current working dir regardless of from where these scripts are started].
Code: Select all
VERSION=340.108 SRC=where/to/download/items ./path/to/download.sh # downloading
VERSION=340.108 SRC=where/to/download/items ./path/to/08-nvidia.PorteusBuild # driver compiling and module creation
i3slkiller wrote: ↑30 Apr 2024, 05:13you can also specify where temporary files will be saved (TMP=/path/to/tmp, should be empty folder, on disk with sufficient free space and unix permissions, will be created if not exist)
i3slkiller wrote: ↑30 Apr 2024, 05:13and where module will be saved (OUTPUT=/path/to/output, old module with the same name will be replaced).
Code: Select all
TMP=/path/to/tmp OUTPUT=/path/to/output VERSION=340.108 SRC=where/to/download/items ./path/to/08-nvidia.PorteusBuild
download.sh script will work even in Debian.
Code: Select all
cp -a "/mnt/live/memory/images/002-xorg.xzm/etc/profile.d"/vdpau.{,c}sh "$PKG/etc/profile.d"
Code: Select all
cp -a /mnt/live/memory/images/002-gui*.xzm/etc/profile.d/vdpau.{,c}sh "$PKG/etc/profile.d"
I think the blacklisting of nouveau should be part of the created 08-nvidia module.ncmprhnsbl wrote: ↑03 May 2024, 00:13nouveau must be blacklisted before starting ie. eg. via a blacklist.xzm mentioned elsewhere in this topic. (if upgrading an existing 08-nvidia this shouldn't be a problem?)
Doesn't the NV compiler run settings for creating xorg.conf ?ncmprhnsbl wrote: ↑03 May 2024, 00:13the nvidia-settings initially failed for me, because of a blank xorg.conf > solution: run nvidia-xconfig, logout/login (then i de/recompressed the module including /etc/X11/xorg.conf) ...probly no way around this.
Thanks for the heads up. I do want my man pages.ncmprhnsbl wrote: ↑03 May 2024, 00:13line 309: cp -a "/mnt/live/memory/changes/usr/share/man/man1"/nvidia-* "$PKG/usr/man/man1" failed for me, should be:
"/mnt/live/memory/changes/usr/man/man1"/nvidia-*
I also want no 32bit multilib, no wine support, no locales, no doc.ncmprhnsbl wrote: ↑03 May 2024, 00:13the other thing for me would be options for: no 32bit multilib, wine support, locales, man, doc ..
an idea might be a config file outlining all the options ie. version, tmp, and the above that is sourced by the scripts.
yes, it is.
Rather not. I specially forced loading nouveau module on boot (cliexec=modprobe~nouveau) and nvidia-installer invoked by 08-nvidia.PorteusBuild didn't complained about it.
Do I understand correctly that you are executing this script on system with 08-nvidia module loaded? This module shouldn't be loaded when building new 08-nvidia xzm.ncmprhnsbl wrote: ↑03 May 2024, 00:13(if upgrading an existing 08-nvidia this shouldn't be a problem?)
Has nvidia-settings ever worked on "08-nvidia-470.199.02-k.6.5.5-porteus-v5.01-x86_64.xzm" module? Because I see that there is no /etc/X11/xorg.conf file inside. The same about "08-nvidia-535.113.01-k.6.5.5-porteus-v5.01-x86_64.xzm".ncmprhnsbl wrote: ↑03 May 2024, 00:13the nvidia-settings initially failed for me, because of a blank xorg.conf
Code: Select all
Section "ServerFlags"
Option "IgnoreABI" "1"
EndSection
It's strange, it works for me.ncmprhnsbl wrote: ↑03 May 2024, 00:13line 309: cp -a "/mnt/live/memory/changes/usr/share/man/man1"/nvidia-* "$PKG/usr/man/man1" failed for me, should be:
I will consider it.ncmprhnsbl wrote: ↑03 May 2024, 00:13the other thing for me would be options for: no 32bit multilib, wine support, locales, man, doc ..
Does this don't apply for kernel module loading only (which I try to avoid when building porteus module)?ncmprhnsbl wrote: ↑03 May 2024, 04:00in order to compile the nvidia kernel module, nouveau must not be loaded
interesting, cause it very much did complain and quit on mei3slkiller wrote: ↑03 May 2024, 07:42Rather not. I specially forced loading nouveau module on boot and nvidia-installer invoked by 08-nvidia.PorteusBuild didn't complained about it.
i did try it once, but the failure was to do with the man path that time..i3slkiller wrote: ↑03 May 2024, 07:42Do I understand correctly that you are executing this script on system with 08-nvidia module loaded?
which is doubly strange no idea why..
which is the case with my last test, just with nouveau blocked, using framebuffer or vesa or something i believe..i3slkiller wrote: ↑03 May 2024, 07:42Basically, I write this script so that it doesn't matter if module is building when X11 is running or not.
yeah, these have the same issue, i purposely left it out because i figured that the xorg.conf would be specific to my hardware and that wouldn't be good.i3slkiller wrote: ↑03 May 2024, 07:42Has nvidia-settings ever worked on "08-nvidia-470.199.02-k.6.5.5-porteus-v5.01-x86_64.xzm" module? Because I see that there is no /etc/X11/xorg.conf file inside. The same about "08-nvidia-535.113.01-k.6.5.5-porteus-v5.01-x86_64.xzm".
that might be a sensible generic solution.i3slkiller wrote: ↑03 May 2024, 07:42In "08-nvidia-550.67-k.6.8.4-porteux-x86_64.xzm" this file have this content:
Are you sure that you are executing the same script as me (from at least 9d2c4d16 commit)?
Code: Select all
$ sha256sum 08-nvidia.PorteusBuild
692a8532c33a2058fd3f52f3891eb8ba4e8a088408835eecf079553c37b2b88c 08-nvidia.PorteusBuild
hmm, well no, the 7bad4ffc5508862ed80b0a6057a6eea6211b1bf0 commit, but i don't see any changes relevant to this issue..i3slkiller wrote: ↑03 May 2024, 08:04Are you sure that you are executing the same script as me (from at least 9d2c4d16 commit)?