Package Details: linux-next-git 20210720.r0.g3568c2c543e2-1

Git Clone URL: https://aur.archlinux.org/linux-next-git.git (read-only, click to copy)
Package Base: linux-next-git
Description: The Linux NEXT kernel and modules
Upstream URL: http://www.kernel.org/
Licenses: GPL2
Provides: VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Submitter: Nefelim4ag
Maintainer: sir_lucjan
Last Packager: sir_lucjan
Votes: 14
Popularity: 0.016538
First Submitted: 2014-10-12 19:04
Last Updated: 2021-07-20 19:03

Dependencies (19)

Required by (7)

Sources (3)

Latest Comments

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

mikoxyz commented on 2021-06-10 07:36

Note: nvidia-dkms fails to build on 210609

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.

https://github.com/torvalds/linux/commit/3351b16af4946fff0d46481d155fb91adb28b1

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

@bennebartsch

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

@ekollof

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?