Package Details: linux-next-git-headers 20210409.r0.ge99d8a849517-1

Git Clone URL: (read-only, click to copy)
Package Base: linux-next-git
Description: Headers and scripts for building modules for the Linux NEXT kernel
Upstream URL:
Licenses: GPL2
Submitter: Nefelim4ag
Maintainer: sir_lucjan
Last Packager: sir_lucjan
Votes: 14
Popularity: 0.159918
First Submitted: 2014-10-12 19:04
Last Updated: 2021-04-09 22:13

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Ttz_ztT commented on 2021-01-12 16:45

@habys : same here. builds fine, doesn't want to boot. with an almost identical entry for /boot (nvme0n1p1 instead) on booting kernel.

dmesg gives lots of "BPF:No data" and "failed to validate module [crc*] BTF: -22" ?

The only difference I see in dmesg is that -next finds a numa node on my ryzen 3xxx now...

Edit: 210115 works.

habys commented on 2021-01-09 16:39

This is building for me. Anyone else having their system die as I can't manage to mount /boot? (wrong fs type, bad option, bad superblock).

From my working kernel I see: /dev/nvme1n1p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

eggz commented on 2020-12-07 01:46

confirmed for my part (rc7). revert that commit and the (upstream) kernels wil build. Lets hope upstream will wake up to this soon.

sir_lucjan commented on 2020-12-06 23:41

I suspect that this is the culprit.

eggz commented on 2020-12-06 23:36

Looks like upstream has done nothing yet. This error is now also present in linux v5.10-rc7

sir_lucjan commented on 2020-12-06 21:58


If this is not a problem, I would ask you to read the previous comments and draw the appropriate conclusion from it.

Thank you.

bennebartsch commented on 2020-12-06 21:55

FAILED unresolved symbol __add_to_page_cache_locked make: *** [Makefile:1168: vmlinux] Error 255 ==> ERROR: A failure occurred in build(). Aborting...

sir_lucjan commented on 2020-12-01 14:50


NOT out-of-date!

This is not a packaging error. Report it in upstream and do not mark a package as out of date.

Bednar commented on 2020-11-26 11:40

Hi @sir_lucjan

Thanks, I resolved the below with a clean build.

Now I am getting this:

FAILED unresolved symbol __add_to_page_cache_locked make: *** [Makefile:1168: vmlinux] Error 255 ==> ERROR: A failure occurred in build(). Aborting...

Anyone else?

sir_lucjan commented on 2020-10-15 19:13

I can not confirm:

$ export LANG=C
$ git cl aur:linux-next-git
Cloning into 'linux-next-git'...
remote: Enumerating objects: 616, done.
remote: Counting objects: 100% (616/616), done.
remote: Compressing objects: 100% (422/422), done.
remote: Total 616 (delta 320), reused 472 (delta 194), pack-reused 0
Receiving objects: 100% (616/616), 463.11 KiB | 1.72 MiB/s, done.
Resolving deltas: 100% (320/320), done.
$ cd linux-next-git
$ mkaurball 
==> Making package: linux-next-git 20201013.r0.gf2fb1afc5730-1 (Thu Oct 15 21:12:25 2020)
==> Retrieving sources...
  -> Downloading 0001-ZEN-Add-sysctl-and-CONFIG-to-disallow-unprivileged-C.patch...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  4423    0  4423    0     0  13124      0 --:--:-- --:--:-- --:--:-- 13124
  -> Found config
==> Validating source files with sha512sums...
    linux-next ... Skipped
    0001-ZEN-Add-sysctl-and-CONFIG-to-disallow-unprivileged-C.patch ... Passed
    config ... Passed
==> Entering fakeroot environment...
==> Creating source package...
  -> Adding PKGBUILD...
  -> Generating .SRCINFO file...
  -> Adding config...
  -> Compressing source package...
==> Leaving fakeroot environment.
==> Source package created: linux-next-git (Thu Oct 15 21:12:29 2020)