Archives/nvidia-all
2
0
Fork 0
mirror of https://github.com/Frogging-Family/nvidia-all synced 2024-10-30 15:20:10 +00:00
Code Issues Packages Projects Releases Wiki Activity
5ccee5d449
nvidia-all/customization.cfg

50 lines
2.2 KiB
INI
Raw Normal View History

nvidia-all: 440.66.04 - previous index was here: https://github.com/Tk-Glitch/PKGBUILDS/tree/master/nvidia-all
2020-03-26 12:52:57 +00:00
# nvidia-all config file
#### OPTIONS ####
# External config file to use - If the given file exists in path, it will override default config (customization.cfg) - Default is ~/.config/frogminer/nvidia-all.cfg
_EXT_CONFIG_PATH=~/.config/frogminer/nvidia-all.cfg
# Custom compiler root dirs - For non-dkms builds (see readme to use this with dkms) - Leave empty to use system compilers
# ! If your kernel was built with mostlyportable GCC, you need to use the exact same build here or module compilation will fail !
# Example: CUSTOM_GCC_PATH="/home/frog/PKGBUILDS/mostlyportable-gcc/gcc-mostlyportable-9.2.0"
CUSTOM_GCC_PATH=""
Cleanup pass: - Remove the PRIME_render_offload option that seemingly made little sense anyway. - Remove the coolbits option that somehow didn't work correctly for multiple users, that will at least not interfere with user-set coolbits. - Make a separate nvidia-settings package (optional) for nvidia-settings. - Get rid of legacy/unneeded options and 20-nvidia.conf Xorg file. - Rollback to the usual nouveau blacklisting way, and remove nvidiafb blacklist. If your setup doesn't work correctly with this, it's a setup issue as virtually all other linux nvidia packages are doing it that way :frog: - Remove the prime-oriented intel outputclass from 10-nvidia-drm-outputclass.conf. Nobody does this, and I suspect it creates some issues for some. I'll be waiting for some feedback to offer it optionally if needed. - Double = signs cleanups. Should fix https://github.com/Frogging-Family/nvidia-all/issues/2 but will now require the user to enable coolbits by themselves.
2020-05-16 00:45:34 +00:00
# Allows enforcing kernel patches application for a target kernel, independently of currently installed ones (example: "5.5")
# You typically don't want to use this as a user. The proper way it to install your kernel(s), then run makepkg against nvidia-all's PKGBUILD to get things autodetected.
nvidia-all: Add an option to override kernel target.
2020-04-01 20:09:35 +00:00
_kerneloverride=""
nvidia-all: 440.66.04 - previous index was here: https://github.com/Tk-Glitch/PKGBUILDS/tree/master/nvidia-all
2020-03-26 12:52:57 +00:00
# Put the built packages in a versioned dir in the same folder as the nvidia-all PKGBUILD on exit - Will fail to install if running makepkg with -i option
_local_package_storing="false"
# If you want to ignore some packages, set them to "false". Default is all set to "true" for a complete installation.
_lib32="true"
_opencl="true"
Cleanup pass: - Remove the PRIME_render_offload option that seemingly made little sense anyway. - Remove the coolbits option that somehow didn't work correctly for multiple users, that will at least not interfere with user-set coolbits. - Make a separate nvidia-settings package (optional) for nvidia-settings. - Get rid of legacy/unneeded options and 20-nvidia.conf Xorg file. - Rollback to the usual nouveau blacklisting way, and remove nvidiafb blacklist. If your setup doesn't work correctly with this, it's a setup issue as virtually all other linux nvidia packages are doing it that way :frog: - Remove the prime-oriented intel outputclass from 10-nvidia-drm-outputclass.conf. Nobody does this, and I suspect it creates some issues for some. I'll be waiting for some feedback to offer it optionally if needed. - Double = signs cleanups. Should fix https://github.com/Frogging-Family/nvidia-all/issues/2 but will now require the user to enable coolbits by themselves.
2020-05-16 00:45:34 +00:00
_nvsettings="true"
nvidia-all: 440.66.04 - previous index was here: https://github.com/Tk-Glitch/PKGBUILDS/tree/master/nvidia-all
2020-03-26 12:52:57 +00:00
_eglwayland="true"
# Either "vulkandev" for vulkan developer drivers or "regular" for all others
_driver_branch=""
# Desired driver version - !! needs to be available from the selected branch above !!
Add support for "latest" driver option. (#29)
2021-01-27 14:58:31 +00:00
# Set to "latest" to use the latest driver on the selected branch.
nvidia-all: 440.66.04 - previous index was here: https://github.com/Tk-Glitch/PKGBUILDS/tree/master/nvidia-all
2020-03-26 12:52:57 +00:00
_driver_version=""
Suggested solution for #30, only update if newer driver (#31) * Suggested solution for #30, only update if newer driver * Removed dependency on nvidia-smi, now uses pacman and 'nvidia-utils' as search string
2021-02-09 11:49:53 +00:00
# Only updates if there is a newer version available
# Semi-hack, compares version-strings as strings, i.e. if "460.39" > "455.45.01" update etc
# Set to "true" to enable
_only_update_if_newer=""
nvidia-all: 440.66.04 - previous index was here: https://github.com/Tk-Glitch/PKGBUILDS/tree/master/nvidia-all
2020-03-26 12:52:57 +00:00
# Set to "true" to use DKMS or "false" to use regular modules. You can also use "full" to build both dkms and regular packages (don't use it if you don't know you need it!).
_dkms=""
Cleanup pass: - Remove the PRIME_render_offload option that seemingly made little sense anyway. - Remove the coolbits option that somehow didn't work correctly for multiple users, that will at least not interfere with user-set coolbits. - Make a separate nvidia-settings package (optional) for nvidia-settings. - Get rid of legacy/unneeded options and 20-nvidia.conf Xorg file. - Rollback to the usual nouveau blacklisting way, and remove nvidiafb blacklist. If your setup doesn't work correctly with this, it's a setup issue as virtually all other linux nvidia packages are doing it that way :frog: - Remove the prime-oriented intel outputclass from 10-nvidia-drm-outputclass.conf. Nobody does this, and I suspect it creates some issues for some. I'll be waiting for some feedback to offer it optionally if needed. - Double = signs cleanups. Should fix https://github.com/Frogging-Family/nvidia-all/issues/2 but will now require the user to enable coolbits by themselves.
2020-05-16 00:45:34 +00:00
## LEGACY OPTIONS
# Attempt at fixing PRIME sync on kernel 5.4 and 5.5rc - https://devtalk.nvidia.com/default/topic/1068045/linux/5-4-kernel-breaks-prime-synchronization-/post/5416631/#5416631
_54_prime_fixing_attempt="false"
# Fix for https://bugs.archlinux.org/task/62142 affecting SLi configs
_62142_fix="false"
Reference in New Issue Copy Permalink