@rayzorben You should boot the default arch kernel, plug in all your devices so it loads appropriate modules and then create modprobe.db. It seems like something might be missing in your build and that's why bluetooth is not working? As for the options, I'll add some description in the future.
Search Criteria
Package Details: linux-clear-headers 6.10.10-1
Package Actions
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 header files and scripts for building kernel modules. |
Upstream URL: | https://github.com/clearlinux-pkgs/linux |
Keywords: | clear clearlinux intel kernel |
Licenses: | GPL-2.0-only |
Submitter: | metak |
Maintainer: | JeremyStarTM |
Last Packager: | JeremyStarTM |
Votes: | 73 |
Popularity: | 1.71 |
First Submitted: | 2018-01-18 21:47 (UTC) |
Last Updated: | 2024-09-14 15:49 (UTC) |
Dependencies (12)
- pahole (pahole-gitAUR)
- bc (bc-ghAUR) (make)
- cpio (cpio-gitAUR) (make)
- gettext (gettext-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- libelf (elfutils-gitAUR) (make)
- pahole (pahole-gitAUR) (make)
- perl (perl-gitAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- tar (tar-gitAUR, busybox-coreutilsAUR) (make)
- xz (xz-gitAUR) (make)
- zstd (zstd-gitAUR, zstd-staticAUR) (make)
Required by (0)
Sources (5)
Latest Comments
« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 49 Next › Last »
metak commented on 2022-03-15 19:55 (UTC)
rayzorben commented on 2022-03-13 16:37 (UTC)
Would love to see some basic instructions pinned with what the options are. I discovered them through the PKGBUILD but still wasn't sure what to do with them.
That being said, I had a few trial and errors regardless. I felt like env _subarch=35 _localmodcfg=y _use_current=y
would be the best combo while running my fully functioning system. However it seems that _localmodcfg for some reason is causing issues with bluetooth. Bluetooth was there, it could see devices, it said my mouse was connected, but it would not work. Rebuilding without _localmodcfg
works though.
xuanruiqi commented on 2022-01-22 14:57 (UTC) (edited on 2022-01-22 15:11 (UTC) by xuanruiqi)
OK, turning debug info off works.
(Maybe because I have CONFIG_DEBUG_INFO_BTF
turned on in my kernel config which causes resolve_btfids
to be called during DKMS build. Let me try turning most debug options off.)
metak commented on 2022-01-22 12:41 (UTC)
@xuanruiqi After testing nvidia-dkms I couldn't reproduce it. It builds fine (gcc & llvm). It's definitely something on your system that's causing this. Try building in clean environment?
xuanruiqi commented on 2022-01-22 08:03 (UTC)
I was building nvidia-dkms. Some modules like nvidia need btf info to build properly, so maybe you want to put it under an option or something like that. AFAIK a lot of people use nvidia-dkms.
metak commented on 2022-01-21 23:14 (UTC)
@xuanruiqi I had to comment out that line in PKGBUILD file when I synced it with stock arch because it would fail to build. (not enabled on Clear) It needs some other debugging things enabled like CONFIG_DEBUG_INFO
, CONFIG_DEBUG_INFO_BTF
, CONFIG_PAHOLE_HAS_SPLIT_BTF
which will increase the size and compilation time. I can enable the debug info if others want it, but I would rather not.
As for dkms error, I just tried building random module (rtl88x2bu) and it builds fine. (gcc & llvm) Please specify which module/versions, etc. (whole build log)
xuanruiqi commented on 2022-01-21 17:02 (UTC) (edited on 2022-01-21 20:26 (UTC) by xuanruiqi)
SOLUTION: please fix the PKGBUILD, add this line, otherwise external DKMS modules can't be built:
install -Dt "$builddir/tools/bpf/resolve_btfids" tools/bpf/resolve_btfids/resolve_btfids
See diff in official linux package commit history.
Hey all! With LLVM compiled kernel (5.16.2), I get this error when I try to compile DKMS modules:
/bin/sh: line 1: ./tools/bpf/resolve_btfids/resolve_btfids: No such file or directory
This error is absent in linux-clear <=5.16.1.
GCC doesn't work either. I suspect this is a really silly mistake, but I can't fix it...
k0r0ng commented on 2022-01-12 22:55 (UTC)
@metak Thank you!
metak commented on 2022-01-11 17:37 (UTC)
@k0r0ng It's not enabled by default in CLR config file, I've enabled it in ˙5.15.14-1˙.
Pinned Comments
JeremyStarTM commented on 2024-08-06 19:37 (UTC) (edited on 2024-08-18 08:22 (UTC) by JeremyStarTM)
The PKGBUILD supports customization via environment variables. Here's a list of all of them:
_makemenuconfig
: Invokesmake menuconfig
(default configuration menu) before compilation starts_makenconfig
: Invokesmake nconfig
(nicer configuration menu) before compilation starts_makexconfig
: Invokesmake xconfig
(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
.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 in a simple manner and decrease build time. And if you don't want that, using
makepkg
as-is works fine too.JeremyStarTM commented on 2024-08-06 19:19 (UTC) (edited on 2024-08-06 19:40 (UTC) by JeremyStarTM)
Kernel has been updated and is now maintained again.
Thank you metak for creating this package in the first place.