No, I only updated to the latest upstream kernel bugfix release 5.2.5
.
Search Criteria
Package Base Details: linux-clear
Package Actions
Git Clone URL: | https://aur.archlinux.org/linux-clear.git (read-only, click to copy) |
---|---|
Keywords: | clear clearlinux intel kernel |
Submitter: | metak |
Maintainer: | metak |
Last Packager: | metak |
Votes: | 71 |
Popularity: | 1.28 |
First Submitted: | 2018-01-18 21:47 (UTC) |
Last Updated: | 2024-05-02 19:27 (UTC) |
Packages (2)
Latest Comments
« First ‹ Previous 1 .. 26 27 28 29 30 31 32 33 34 35 36 .. 47 Next › Last »
metak commented on 2019-08-01 16:29 (UTC)
zheiling commented on 2019-08-01 11:40 (UTC) (edited on 2019-08-01 11:40 (UTC) by zheiling)
After upgrading to linux-clear 5.2.5-1, proprietary nvidia driver becomes to work. Have you applied a new fix?
TillySutton commented on 2019-07-31 08:32 (UTC)
Thanks for this https://github.com/clearlinux/distribution/issues/1048 It helped me a lot
zheiling commented on 2019-07-30 13:53 (UTC)
@metak Updated kernel today. No changes are seen. I even can't find Nvidia messages in dmesg, Xorg.0.log also silent about Nvidia. Very strange behavior...
metak commented on 2019-07-29 22:17 (UTC) (edited on 2019-07-29 22:21 (UTC) by metak)
@zheiling On second thought, your issue could be related to this? Latest native kernel issues with custom drivers #1048 Can you try the latest version?
zheiling commented on 2019-07-29 15:04 (UTC)
@danhyal other kernels work normally with switching. In CLI version found this message: Config parsing : unknown option kill_logind in section optimus. Ignoring. Config parsing : unknown option kill_x11 in section optimus. Ignoring. Config parsing : unknown option login_manager_control in section optimus. Ignoring. Config parsing : unknown option pci_reset in section optimus. Ignoring. Config parsing : unknown option terminate_sessions in section optimus. Ignoring. Config parsing : unknown option dri in section nvidia. Ignoring. BTW: how to format text in aurweb? Can't find instructions.
amelia commented on 2019-07-28 21:40 (UTC)
@zheiling Do you still have the problem on the default arch kernel?
zheiling commented on 2019-07-28 21:04 (UTC)
@metak Fully removed nouveau and compiled kernel without nouveau support. The message is disappeared, but the problem with switching still exist. I suppose that an issue can be in patches/flags applied by linux-clear team.
metak commented on 2019-07-27 18:17 (UTC)
@zheiling Can you try unloading nouveau rmmod nouveau
and load nvidia modprobe nvidia
module?
zheiling commented on 2019-07-27 18:03 (UTC) (edited on 2019-07-27 18:15 (UTC) by zheiling)
Addition to my previous post about nVidia: [ 150.341496] nvidia: module license 'NVIDIA' taints kernel. [ 150.341498] Disabling lock debugging due to kernel taint [ 150.355115] calling nvidia_frontend_init_module+0x0/0x93 [nvidia] @ 1580 [ 150.355150] nvidia-nvlink: Nvlink Core is being initialized, major device number 236 [ 150.355540] NVRM: The NVIDIA probe routine was not called for 1 device(s). [ 150.355541] NVRM: This can occur when a driver such as: NVRM: nouveau, rivafb, nvidiafb or rivatv NVRM: was loaded and obtained ownership of the NVIDIA device(s). [ 150.355542] NVRM: Try unloading the conflicting kernel module (and/or NVRM: reconfigure your kernel without the conflicting NVRM: driver(s)), then try loading the NVIDIA kernel module NVRM: again. [ 150.355543] NVRM: No NVIDIA devices probed. Using NVIDIA Corporation GM108M [GeForce 840M] (rev a2) and optimus-manager-qt
Pinned Comments
metak commented on 2022-03-27 13:44 (UTC) (edited on 2022-04-02 13:20 (UTC) by metak)
The PKGBUILD file supports a few different configurable build-time options:
_makenconfig
Tweak kernel options prior to a build via nconfig. Pseudo-graphical menu based on ncurses. 1 2_localmodcfg
Only compile active modules to VASTLY reduce the number of modules built and the build time._subarch
Enable additional optimization/tuning for kernel builds by adding more micro-architectures options. Default isGeneric-x86-64
number36
if nothing else is selected._use_current
Use the current kernel's.config
file. Enabling this option will use the.config
of the RUNNING kernel rather than the ARCH defaults. Useful when the package gets updated and you already went through the trouble of customizing your config options. NOT recommended when a new kernel is released, but again, convenient for package bumps._use_llvm_lto
Compile the kernel with LLVM/Clang._debug
Enabley
some additional debug features present in arch kernel, but not in Clear upstream.n
to force disable or leave empty to ignore.Lastly, build the kernel by setting your environment variable
env _subarch=40 _localmodcfg=y
.metak commented on 2018-01-22 01:49 (UTC) (edited on 2021-12-01 12:47 (UTC) by metak)
1. Binaries available in my repo: http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/x86_64/
THIS IS OPTIONAL:
2. After install adjust your boot cmd line. ClearLinux uses clr-boot-manager which takes care of that. This is upstream default: