Package Details: linux-ck-headers 6.11.10-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base: linux-ck
Description: Headers and scripts for building modules for Linux-ck kernel
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL-2.0-only
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 459
Popularity: 0.20
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-26 13:15 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 308 Next › Last »

graysky commented on 2023-10-31 11:19 (UTC)

Try 6.6-2

graysky commented on 2023-10-31 10:40 (UTC)

Yes, this affects the official package as well: https://bugs.archlinux.org/task/80115

d0rfm4tr4tz3 commented on 2023-10-31 08:58 (UTC) (edited on 2023-10-31 08:58 (UTC) by d0rfm4tr4tz3)

Before the message queenbiscuit311 quoted appears, there is another one before:

Warning: 'make modules_install' requires /doesnt/exist. Please install it. This is probably in the kmod package.

queenbiscuit311 commented on 2023-10-31 02:25 (UTC) (edited on 2023-10-31 04:20 (UTC) by queenbiscuit311)

Building seems to go basically to completion, before getting stuck at

rm: cannot remove '/home/[user]/.cache/yay/linux-ck/pkg/linux-ck/usr/lib/modules/6.6.0-1-ck/source': No such file or directory

and failing during packaging.This also fails directly via makepkg.

graysky commented on 2023-05-02 09:28 (UTC)

https://bbs.archlinux.org/viewtopic.php?id=285413

simona commented on 2023-05-02 09:12 (UTC)

==> dkms install --no-depmod vboxhost/7.0.8_OSE -k 6.3.1-1-ck-generic-v3
Error! Bad return status for module build on kernel: 6.3.1-1-ck-generic-v3 (x86_64)
Consult /var/lib/dkms/vboxhost/7.0.8_OSE/build/make.log for more information.

zerophase commented on 2023-05-02 05:21 (UTC)

Anyone else getting errors when trying to build 6.3.1-1?

btf_encoder__encode: btf__dedup failed!
Failed to encode BTF
  LD      .tmp_vmlinux.kallsyms1
  NM      .tmp_vmlinux.kallsyms1.syms
  KSYMS   .tmp_vmlinux.kallsyms1.S
  AS      .tmp_vmlinux.kallsyms1.S
  LD      .tmp_vmlinux.kallsyms2
  NM      .tmp_vmlinux.kallsyms2.syms
  KSYMS   .tmp_vmlinux.kallsyms2.S
  AS      .tmp_vmlinux.kallsyms2.S
  LD      vmlinux
  BTFIDS  vmlinux
libbpf: failed to find '.BTF' ELF section in vmlinux
FAILED: load BTF from vmlinux: No data available
make[1]: *** [scripts/Makefile.vmlinux:35: vmlinux] Error 255
make[1]: *** Deleting file 'vmlinux'
make: *** [Makefile:1249: vmlinux] Error 2

Fails on both clang and gcc.

gbin commented on 2023-04-11 01:34 (UTC) (edited on 2023-04-11 01:46 (UTC) by gbin)

I have the same one: 57c562c3cd2753f232549cab05c8ad770ed848ae86401619c7581bdffaeea4fe

I just checked the given signature for the file with this hash:

sal ➜  Downloads  xz -cd linux-6.2.10.tar.xz | gpg --verify linux-6.2.10.tar.sign -                                    
gpg: Signature made Thu 06 Apr 2023 05:13:42 AM CDT
gpg:                using RSA key 647F28654894E3BD457199BE38DBBDC86092693E
gpg: Good signature from "Greg Kroah-Hartman <gregkh@linuxfoundation.org>" [unknown]
gpg:                 aka "Greg Kroah-Hartman <gregkh@kernel.org>" [unknown]
gpg:                 aka "Greg Kroah-Hartman (Linux kernel stable release signing key) <greg@kroah.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 647F 2865 4894 E3BD 4571  99BE 38DB BDC8 6092 693E

graysky commented on 2023-04-10 16:30 (UTC)

I agree/I get the same checksum

BS86 commented on 2023-04-10 16:12 (UTC) (edited on 2023-04-10 16:23 (UTC) by BS86)

something is strange.

On my notebook I could build the update on release day. on my Desktop that I can only update now, I get a sha256sum mismatch when trying to build. No matter how often I download https://www.kernel.org/pub/linux/kernel/v6.x/linux-6.2.10.tar.xz the sha256sum I get is 57c562c3cd2753f232549cab05c8ad770ed848ae86401619c7581bdffaeea4fe not 7de856a284e57e23b8744b2708fe49d49aebe3510c3eee2dd6342e3b5e46ecf2 like expected in the PKGBUILD - is upstream broken/infected or is something off on my end?

Edit: I did now download the file on my phone using mobile internet, and the sha256sum is 57c562c3cd2753f232549cab05c8ad770ed848ae86401619c7581bdffaeea4fe too - so something definitely changed upstream after the release ...

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 308 Next › Last »