@rvlobato @astroty Sorry I can't be more helpful with the nvidia because I don't have any nvidia cards.
@astroty The extramodules-clear folder was removed in sync with the stock arch kernel package.
Git Clone URL: | https://aur.archlinux.org/linux-clear.git (read-only, click to copy) |
---|---|
Package Base: | linux-clear |
Description: | Linux kernel with patches from Clear Linux which allow for higher performance. This package includes the kernel and compiled modules. |
Upstream URL: | https://git.staropensource.de/JeremyStarTM/aur-linux-clear |
Keywords: | clear clearlinux intel kernel |
Licenses: | GPL-2.0-only |
Provides: | KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE |
Submitter: | metak |
Maintainer: | JeremyStarTM |
Last Packager: | JeremyStarTM |
Votes: | 74 |
Popularity: | 0.96 |
First Submitted: | 2018-01-18 21:47 (UTC) |
Last Updated: | 2024-11-19 01:15 (UTC) |
« First ‹ Previous 1 .. 27 28 29 30 31 32 33 34 35 36 37 .. 51 Next › Last »
@rvlobato @astroty Sorry I can't be more helpful with the nvidia because I don't have any nvidia cards.
@astroty The extramodules-clear folder was removed in sync with the stock arch kernel package.
After some searching, it seems that my Nvidia driver was failing to load because of this flag in my /etc/default/grub: pci=nommconf I didn't need to do that in another kernel I have though, so I don't know what might've caused this
Also, is it just me or are these new packages not generating a new extramodules-clear folder?
@calin @metak I was having the same issue, seems that the conflict was between nvidiafb and nvidia, after blacklisting the nvidiafb (the nvidia-dkms blacklist nouveau) the nvidia modules were loaded.
@calin I've already disabled CONFIG_MODULE_SIG_FORCE
by default to make it easier and you should not need module.sig_unenforce
. Check logs for more clues?
The nvidia drivers fail to load even when using module.sig_unenforce, they used to work, not anymore unfortunately, is anyone else having this issue?
@Elanzer Sorry about that. The pkgbuild file in obs wasn't synced fully and dell smbios should've been enabled long ago (as it is here in aur). The repo binary is already building.
@metak can you compile lts-2018 with CONFIG_DELL_SMBIOS_SMM=y or CONFIG_DELL_SMBIOS_WMI=y?? I dont know which one works for mine. My touchpad is weird with 5.3 so I rolledback to LTS. And with the older kernel i'm getting SMBIOS messages again. My laptop is old and it takes forever to compile a kernel, your binaries are a life-saver. Thanks.
@toki1990 I believe it should work on amd cpus, but I don't have amd cpus to try. If you can post some logs maybe someone can help.
kernel build complete without error. but kernel not work over amd ryzen processor. is there a way run over amd ?
It seems that I need the cpio
package to correctly build linux-clear. Maybe this is due to some kernel options I enabled, but not sure which ones.
Pinned Comments
JeremyStarTM commented on 2024-11-08 18:33 (UTC) (edited on 2024-11-08 18:33 (UTC) by JeremyStarTM)
Proposal update
The package has been updated to 6.11.7 (clr 6.11.6-1477), and with that landlock support has been enabled the package source moved to https://git.staropensource.de/JeremyStarTM/linux-clear.
JeremyStarTM commented on 2024-08-06 19:37 (UTC) (edited on 2024-11-08 18:36 (UTC) by JeremyStarTM)
Information comment
This comment provides useful information about this package. Make sure to read it through, you won't regret it.
Repository URL
This package is hosted at sos!git. If you want to contribute to the package, you can do it here: https://git.staropensource.de/JeremyStarTM/aur-linux-clear
Updates
I usually publish updates 0-3 days after a kernel release, depending on how busy I am.
If I however get wind of security-relevant updates or any vulnerabilities I will try to update the kernel as soon as possible and write a comment about the vulnerability/update. So make sure to subscribe to this package's comment mailing list.
The PKGBUILD file supports customization via environment variables. Here's a list of all of them:
_makemenuconfig
: Invokesmake menuconfig
(ncurses-based default configuration menu) before compilation starts_makenconfig
: Invokesmake nconfig
(ncurses-based nicer configuration menu) before compilation starts_makexconfig
: Invokesmake xconfig
(X11-based GUI configuration menu) before compilation starts_use_current
: Will use the configuration of the running kernel, if the running kernel is compiled withIKCONFIG_PROC
_copyfinalconfig
: Copies the final kernel configuration into the repository root askconfig-new
before compilation starts_localmodcfg
: Only compiles modules found in modprobed-db's database (which decreases compilation time and kernel size)_use_llvm_lto
: Compiles the kernel with LLVM instead of GCC. Should work, if not write a comment_subarch
: Specifies the sub architecture to compile for (see the PKGBUILD file for a list of all subarches). Default is40
(Generic-x86-64), which is compatible with all amd64 processors. Must be a number_debug
: Force enables debug options when set toy
, force disables debug options when set ton
or uses the config defaults when unsetAll of these variables just need to be set for them to apply, except for
_subarch
and_debug
. See their descriptions for more information.GPG errors
If makepkg complains about invalid PGP keys, try running this command first:
gpg --locate-keys torvalds@kernel.org gregkh@kernel.org sashal@kernel.org benh@debian.org
. This command only needs to be executed once.Issue handling
Please only submit issues in the package's repository if they aren't bug reports about the package or help requests. Please keep them to the AUR only. Tihs prevents unnecessary signups.
Build tool
If you want a dead simple way to compile this package, you can try out my build tool. It includes a few no nonsense changes to the kernel configuration and allows you to configure the PKGBUILD file in a simple manner and decrease build time. And if you don't want that, using
makepkg
as-is works fine too.