Frogging-Family / linux-tkg

linux-tkg custom kernels
GNU General Public License v2.0
1.32k stars 163 forks source link

Fedora 36 - nvidia problem - is missing #513

Closed mihail727 closed 1 year ago

mihail727 commented 2 years ago

Describe

customization.cfg ```cfg # linux-TkG config file # Linux distribution you are using, options are "Arch", "Void", "Ubuntu", "Debian", "Fedora", "Suse", "Gentoo", "Generic". # It is automatically set to "Arch" when using PKGBUILD. # If left empty, the script will prompt _distro="Fedora" # Kernel Version - Options are "5.4", "5.7", "5.8", "5.9", "5.10", "5.11", "5.12", "5.13", "5.14", "5.15", "5.16", "5.17" _version="5.17" #### MISC OPTIONS #### # External config file to use - If the given file exists in path, it will override default config (customization.cfg) - Default is ~/.config/frogminer/linux-tkg.cfg _EXT_CONFIG_PATH=~/.config/frogminer/linux-tkg.cfg # [Arch specific] Set to anything else than "true" to limit cleanup operations and keep source and files generated during compilation. # Default is "true". _NUKR="true" # [install.sh specific] Git mirror to use to get the kernel sources, possible values are "googlesource.com" and "kernel.org" _git_mirror="kernel.org" # Custom compiler root dirs - Leave empty to use system compilers # Example: CUSTOM_GCC_PATH="/home/frog/PKGBUILDS/mostlyportable-gcc/gcc-mostlyportable-9.2.0" CUSTOM_GCC_PATH="" # Custom LLVM compiler root dirs - Leave empty to use system llvm compiler # Example: CUSTOM_LLVM_PATH="/home/frog/PKGBUILDS/mostlyportable-llvm/llvm-mostlyportable-11.0.0" CUSTOM_LLVM_PATH="" # Set to true to bypass makepkg.conf and use all available threads for compilation. False will respect your makepkg.conf options. _force_all_threads="true" # Set to true to prevent ccache from being used and set CONFIG_GCC_PLUGINS=y (which needs to be disabled for ccache to work properly) _noccache="false" # Set to true to use modprobed db to clean config from unneeded modules. Speeds up compilation considerably. Requires root - https://wiki.archlinux.org/index.php/Modprobed-db # Using this option can trigger user prompts if the config doesn't go smoothly. # !!!! Make sure to have a well populated db !!!! - Leave empty to be asked about it at build time _modprobeddb="false" # modprobed-db database file location _modprobeddb_db_path=~/.config/modprobed.db # Set to "1" to call make menuconfig, "2" to call make nconfig, "3" to call make xconfig, before building the kernel. Set to false to disable and skip the prompt. _menunconfig="2" # Set to true to generate a kernel config fragment from your changes in menuconfig/nconfig. Set to false to disable and skip the prompt. _diffconfig="" # Set to the file name where the generated config fragment should be written to. Only used if _diffconfig is active. _diffconfig_name="" # [install.sh specific] Use tmpfs as a work directory, recommended when RAM >= 32GB to reduce HDD/SSD usage. For more information, see https://wiki.archlinux.org/title/Tmpfs _use_tmpfs="false" # [install.sh specific] tmpfs folder path, only used when _use_tmpfs="true". # Creates a linux-tkg work folder within that pathmake sure to have nothing important in "$_tmpfs_path/linux-tkg" _tmpfs_path="/tmp" # [install.sh: Generic and Gentoo specific] Dracut options when generating initramfs _dracut_options="--lz4" #### KERNEL OPTIONS #### # Name of the default config file to use for the kernel # Default (empty) : "config.x86_64" from the linux-tkg-config/5.y folder. # "running-kernel" : Picks the .config file from the currently running kernel. # It is recommended to be running an official kernel before running this script, to pick off a correct .config file # "config_hardened.x86_64" : config file for a hardened kernel, available for kernel version "5.13", "5.10" and "5.4" . # To get a complete hardened setup, you have to use "cfs" as _cpusched. # User provided value : custom user provided file, the given path should be relative to the PKGBUILD file. This enables for example to use a user stripped down .config file. # If the .config file isn't up to date with the chosen kernel version, any extra CONFIG_XXXX is set to its default value. # Note: the script copies the resulting .config file as "kernelconfig.new" next to the PKGBUILD as a convenience for an eventual re-use. It gets overwritten at each run. # One can use "kernelconfig.new" here to always use the latest edited .config file. modprobed-db needs to be used only once for its changes to be picked up. _configfile="" # Determine whether to call "olddefconfig" (default) or "oldconfig" for manual config updating interaction. _config_updating="olddefconfig" # Disable some non-module debugging - See PKGBUILD for the list _debugdisable="false" # Strip the vmlinux file after build is done. Set to anything other than "true" if you require debug headers. Default is "true" _STRIP="true" # LEAVE AN EMPTY VALUE TO BE PROMPTED ABOUT FOLLOWING OPTIONS AT BUILD TIME # CPU scheduler - Options are "upds" (TkG's Undead PDS), "pds", "bmq", "muqss", "cacule" or "cfs" (kernel's default) _cpusched="pds" # Compiler to use - Options are "gcc" or "llvm". # For advanced users. _compiler="gcc" # Force the use of the LLVM Integrated Assembler whether using LLVM, LTO or not. # Set to "1" to enable. _llvm_ias="" # Clang LTO mode, only available with the "llvm" compiler - options are "no", "full" or "thin". # ! This is currently experimental and might result in an unbootable kernel - Not recommended ! # "no: do not enable LTO" # "full: uses 1 thread for Linking, slow and uses more memory, theoretically with the highest performance gains." # "thin: uses multiple threads, faster and uses less memory, may have a lower runtime performance than Full." _lto_mode="" # Apply PREEMPT_RT patchset to the kernel. # ! Only CFS CPU scheduler is compatible with this patchset ! # Set to "1" to enable. _preempt_rt="" # Forcibly apply the PREEMPT_RT patchset to the kernel, even when upstream does not officially support the kernel subversion. # ! This will still not apply when the patch itself or linux-tkg (see _version) do not support the kernel major version - Not recommended ! # Set to "1" to enable. _preempt_rt_force="" # CPU sched_yield_type - Choose what sort of yield sched_yield will perform # For PDS and MuQSS: 0: No yield. (Recommended option for gaming on PDS and MuQSS) # 1: Yield only to better priority/deadline tasks. (Default - can be unstable with PDS on some platforms) # 2: Expire timeslice and recalculate deadline. (Usually the slowest option for PDS and MuQSS, not recommended) # For BMQ: 0: No yield. # 1: Deboost and requeue task. (Default) # 2: Set rq skip task. _sched_yield_type="0" # Round Robin interval is the longest duration two tasks with the same nice level will be delayed for. When CPU time is requested by a task, it receives a time slice equal # to the rr_interval in addition to a virtual deadline. When using yield_type 2, a low value can help offset the disadvantages of rescheduling a process that has yielded. # MuQSS default: 6ms" # PDS default: 4ms" # BMQ default: 2ms" # Set to "1" for 2ms, "2" for 4ms, "3" for 6ms, "4" for 8ms, or "default" to keep the chosen scheduler defaults. _rr_interval="default" # Set to "true" to disable FUNCTION_TRACER/GRAPH_TRACER, lowering overhead but limiting debugging and analyzing of kernel functions - Kernel default is "false" _ftracedisable="true" # Set to "true" to disable NUMA, lowering overhead, but breaking CUDA/NvEnc on Nvidia equipped systems - Kernel default is "false" _numadisable="false" # Set to "true" to enable misc additions - May contain temporary fixes pending upstream or changes that can break on non-Arch - Kernel default is "true" _misc_adds="true" # Set to "0" for periodic ticks, "1" to use CattaRappa mode (enabling full tickless) and "2" for tickless idle only. # Full tickless can give higher performances in various cases but, depending on hardware, lower consistency. Just tickless idle can perform better on some platforms (mostly AMD based). _tickless="0" # Set to "true" to use ACS override patch - https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#Bypassing_the_IOMMU_groups_.28ACS_override_patch.29 - Kernel default is "false" _acs_override="true" # Set to "true" to add Bcache filesystem support. You'll have to install bcachefs-tools-git from AUR for utilities - https://bcachefs.org/ - If in doubt, set to "false" _bcachefs="" # Set to "true" to enable support for fsync, an experimental replacement for esync found in Valve Proton 4.11+ - https://steamcommunity.com/games/221410/announcements/detail/2957094910196249305 # Can be enabled alongside _futex_waitv on 5.13+ to use it as a fallback for older Proton builds _fsync="true" # Set to "true" to enable support for futex2, an experimental interface that can be used by proton-tkg and proton 5.13 experimental through Fsync - Can be enabled alongside fsync to use it as a fallback # https://gitlab.collabora.com/tonyk/linux/-/tree/futex2-dev _futex2="true" # Set to "true" to enable backported patches to add support for the futex_waitv() syscall, a new interface for fsync. It will appear in mainline at Linux 5.16 release and requires a wine/proton with builtin support for it. It's expected to be available in Valve Proton 6.3 stable soon - https://github.com/ValveSoftware/wine/pull/128 # !! Disables futex2 interfaces support !! # https://github.com/andrealmeid/futex_waitv_patches _futex_waitv="false" # Set to "true" to enable support for winesync, an experimental replacement for esync - requires patched wine - https://repo.or.cz/linux/zf.git/shortlog/refs/heads/winesync4 # ! Can't be used on multiple kernels installed side-by-side, which will require https://aur.archlinux.org/packages/winesync-dkms/ instead of this option ! _winesync="false" # Set to "true" to enable Binder and Ashmem, the kernel modules required to use the android emulator Anbox. ! This doesn't apply to 5.4.y ! _anbox="" # A selection of patches from Zen/Liquorix kernel and additional tweaks for a better gaming experience (ZENIFY) - Default is "true" _zenify="true" # compiler optimization level - 1. Optimize for performance (-O2); 2. Optimize harder (-O3); 3. Optimize for size (-Os) - Kernel default is "1" _compileroptlevel="1" # CPU compiler optimizations - Defaults to prompt at kernel config if left empty # AMD CPUs : "k8" "k8sse3" "k10" "barcelona" "bobcat" "jaguar" "bulldozer" "piledriver" "steamroller" "excavator" "zen" "zen2" "zen3" (zen3 opt support depends on GCC11) # Intel CPUs : "mpsc"(P4 & older Netburst based Xeon) "atom" "core2" "nehalem" "westmere" "silvermont" "sandybridge" "ivybridge" "haswell" "broadwell" "skylake" "skylakex" "cannonlake" "icelake" "goldmont" "goldmontplus" "cascadelake" "cooperlake" "tigerlake" # Other options : # - "native_amd" (use compiler autodetection - Selecting your arch manually in the list above is recommended instead of this option) # - "native_intel" (use compiler autodetection and will prompt for P6_NOPS - Selecting your arch manually in the list above is recommended instead of this option) # - "generic" (kernel's default - to share the package between machines with different CPU µarch as long as they are x86-64) # # https://en.wikipedia.org/wiki/X86-64#Microarchitecture_Levels) # - "generic_v2" (depends on GCC11 - to share the package between machines with different CPU µarch supporting at least x86-64-v2 # - "generic_v3" (depends on GCC11 - to share the package between machines with different CPU µarch supporting at least x86-64-v3 # - "generic_v4" (depends on GCC11 - to share the package between machines with different CPU µarch supporting at least x86-64-v4 _processor_opt="native_intel" # MuQSS only - Make IRQ threading compulsory (FORCE_IRQ_THREADING) - Default is "false" _irq_threading="false" # CacULE only - Enable Response Driven Balancer, an experimental load balancer for CacULE _cacule_rdb="false" # CacULE only - Load balance time period - Default is 19 # https://github.com/hamadmarri/cacule-cpu-scheduler/blob/master/patches/CacULE/RDB/rdb.patch#L56 _cacule_rdb_interval="19" # MuQSS and PDS only - SMT (Hyperthreading) aware nice priority and policy support (SMT_NICE) - Kernel default is "true" - You can disable this on non-SMT/HT CPUs for lower overhead _smt_nice="" # Trust the CPU manufacturer to initialize Linux's CRNG (RANDOM_TRUST_CPU) - Kernel default is "false" _random_trust_cpu="false" # MuQSS only - CPU scheduler runqueue sharing - No sharing (RQ_NONE), SMT (hyperthread) siblings (RQ_SMT), Multicore siblings (RQ_MC), Symmetric Multi-Processing (RQ_SMP), NUMA (RQ_ALL) # Valid values are "none", "smt", "mc", "mc-llc"(for zen), "smp", "all" - Kernel default is "smt" _runqueue_sharing="" # Timer frequency - "100" "500", "750" or "1000" ("2000" can be set for cacule cpu sched, and will fallback to default if set while on another schedulers) - More options available in kernel config prompt when left empty depending on selected cpusched with the default option pointed with a ">" _timer_freq="1000" # Default CPU governor - "performance", "ondemand", "schedutil" or leave empty for default (schedutil) _default_cpu_gov="performance" # Use an aggressive ondemand governor instead of default ondemand to improve performance on low loads/high core count CPUs while keeping some power efficiency from frequency scaling. # It still requires you to either set ondemand as default governor or to select it in some way at runtime. _aggressive_ondemand="false" # [Advanced] Default TCP IPv4 algorithm to use. Options are: "yeah", "bbr", "cubic", "reno", "vegas" and "westwood". Leave empty if unsure. # This config option will not be prompted # Can be changed at runtime with the command line `# echo "$name" > /proc/sys/net/ipv4/tcp_congestion_control` where $name is one of the options above. # Default (empty) and fallback : cubic _tcp_cong_alg="" # You can pass a default set of kernel command line options here - example: "intel_pstate=passive nowatchdog amdgpu.ppfeaturemask=0xfffd7fff mitigations=off" _custom_commandline="intel_pstate=passive" # Selection of Clearlinux patches _clear_patches="true" #### SPESHUL OPTION #### # If you want to bypass the stock naming scheme and enforce something else (example : "linux") - Useful for some bootloaders requiring manual entry editing on each release. # !!! It will also change pkgname - If you don't explicitely need this, don't use it !!! _custom_pkgbase="" # [non-Arch specific] Kernel localversion. Putting it to "Mario" will make for example the kernel version be 5.7.0-tkg-Mario (given by uname -r) # If left empty, it will use "-tkg-${_cpusched}${_compiler}" where "${_cpusched}" will be replaced by the user chosen scheduler, ${_compiler} will be replaced by "-llvm" if clang is used (nothing for GCC). _kernel_localversion="" # Set to "true" to add back missing symbol for AES-NI/AVX support on ZFS - This is a legacy option that can be ignored on 5.10+ kernels - https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/kernel/export_kernel_fpu_functions.patch _zfsfix="true" #### USER PATCHES #### # community patches - add patches (separated by a space) of your choice by name from the community-patches dir # example: _community_patches="clear_nack_in_tend_isr.myrevert ffb_regression_fix.mypatch 0008-drm-amd-powerplay-force-the-trim-of-the-mclk-dpm-levels-if-OD-is-enabled.mypatch" _community_patches="" # You can use your own patches by putting them in a subfolder called linux-tkg-userpatches (e.g. linux510-tkg-userpatches) next to the PKGBUILD and giving them the .mypatch extension. # You can also revert patches by putting them in that same folder and giving them the .myrevert extension. # Also, userpatches variable below must be set to true for the above to work. _user_patches="true" # Apply all user patches without confirmation - !!! NOT RECOMMENDED !!! _user_patches_no_confirm="false" #### CONFIG FRAGMENTS #### # You can use your own kernel config fragments by putting them in the same folder as the PKGBUILD and giving them the .myfrag extension. # Also, the config fragments variable below must be set to true for the above to work. _config_fragments="true" # Apply all config fragments without confirmation - !!! NOT RECOMMENDED !!! _config_fragments_no_confirm="false" ```
Tk-Glitch commented 2 years ago

So far dkms works but akmod doesn't. But Fedora doesn't offer a nvidia dkms package so.. Currently, on Fedora you'll want to install from Nvidia's .run packages in dkms mode.

If someone knows what's missing to fix this issue on Fedora, please let me know.

Tk-Glitch commented 2 years ago

https://github.com/Frogging-Family/linux-tkg/issues/375

mihail727 commented 2 years ago

So far dkms works but akmod doesn't. But Fedora doesn't offer a nvidia dkms package so.. Currently, on Fedora you'll want to install from Nvidia's .run packages in dkms mode.

If someone knows what's missing to fix this issue on Fedora, please let me know.

very strange and it is not clear why this is so ..... liquorix also does not provide the devel-matched package, but drivers are loaded with it ...

mihail727 commented 2 years ago

So far dkms works but akmod doesn't. But Fedora doesn't offer a nvidia dkms package so.. Currently, on Fedora you'll want to install from Nvidia's .run packages in dkms mode.

If someone knows what's missing to fix this issue on Fedora, please let me know.

I managed to install and run linux-tkg along with Nvidia drivers by manually installing from the official site .run file. But I couldn't install nvidia-settings because this package is pulled from the official repository, and it in turn pulls the official kernel back....

flindeberg commented 2 years ago

nvidia-settings is part of the nvidia-driver-package from Nvidia. If you install using the .run-file it should install it as well? (I haven't done this in a while though, I've only installed Nvidia-drivers via nvidia-all the last couple of years)

Do you have a dependency issue with nvidia-settings which is not satisfied since you install it directly instead of via the package manager?

AdelKS commented 2 years ago

The weird thing is that Fedora is splitting their RPM packages differently than what the kernel build system has when we tell it to make RPMs through make rpm-pkg. I will need to look into it, last time I checked I couldn't find much documentation.

mihail727 commented 2 years ago

nvidia-settings is part of the nvidia-driver-package from Nvidia. If you install using the .run-file it should install it as well? (I haven't done this in a while though, I've only installed Nvidia-drivers via nvidia-all the last couple of years)

Do you have a dependency issue with nvidia-settings which is not satisfied since you install it directly instead of via the package manager?

Everything is fine. For some reason, on the second attempt, nvidia-settings was installed

AdelKS commented 1 year ago

Hello! Please try PR #610 to confirm that it fixes this issue. It worked like a charm in my VM.

Adel

Tk-Glitch commented 1 year ago

Should be fixed with https://github.com/Frogging-Family/linux-tkg/commit/1d063ca32634997616d9cb1da81253bdedc67054