Package Details: linux-next-git 20201001.r0.gd39294091fee-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: 13
Popularity: 0.015898
First Submitted: 2014-10-12 19:04
Last Updated: 2020-10-01 19:26

Dependencies (15)

Required by (8)

Sources (3)

Latest Comments

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

ArthurBorsboom commented on 2020-09-23 08:34

@sir_lucjan, good to know that I was wrong, twice.

After searching, I found the 'following vanilla' comment not in the PKGBUILD, but inside the ZEN patch.

"Our default behavior continues to match the vanilla kernel."

Please disregard my incorrect observation. :)

sir_lucjan commented on 2020-09-17 20:25

@ArthurBorsboom

You are wrong."The normal kernel" has it.

https://github.com/archlinux/linux/commits/v5.8.10-arch1

It is used by default.

https://github.com/archlinux/svntogit-packages/blob/packages/linux/trunk/config#L195

I am trying to make this kernel as consistent as possible with the stock.

In the PKGBUILD it says to follow the vanilla build

Out of curiosity, where did you find it?

ArthurBorsboom commented on 2020-09-17 20:20

I'm wondering if the ZEN patch is (still?) needed in this package.

In the PKGBUILD it says to follow the vanilla build. However, neither the regular Arch [linux] kernel has it, nor linux-git.

https://github.com/archlinux/svntogit-packages/blob/packages/linux/trunk/PKGBUILD https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-git

Might it be outdated?

sir_lucjan commented on 2020-09-12 17:32

Fixed.

gamezelda commented on 2020-09-12 17:20

The sphinx-workaround.patch patch does no longer apply. It looks like it is no longer necessary:

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/Documentation/conf.py?id=afde706afde2fea8a1dff84acaedac4f8dfe84b9

sir_lucjan commented on 2020-05-01 11:40

@blacktea

The git package is never out of date. You will always build the latest possible version.

peeweep commented on 2020-01-04 23:38

A patch for nvidia-dkms

https://github.com/peeweep/nvidia-dkms-fix-drm-drmph-not-found

Ref: https://devtalk.nvidia.com/default/topic/1068332

Ref: https://gitlab.com/snippets/1923197

Aaron1011 commented on 2020-01-01 07:58

in1t3r: I'm getting the same DKMS error with the linux-mainline kernel. Looking at the kernel repository, it looks like this error is legitmate: include/drm/drmP.h no longer exists in the latest kernel.

in1t3r commented on 2019-12-09 08:38

nvidia-dkms fails to install module on the linux-next-git kernel dkms install nvidia/440.36 -k 5.4.0-next-20191208-1-next-git The error in terminal is: Error! Bad return status for module build on kernel: 5.4.0-next-20191208-1-next-git (x86_64)

And the error inside of the log file is:

/var/lib/dkms/nvidia/440.36/build/nvidia-drm/nvidia-drm-utils.h:30:10: fatal error: drm/drmP.h: No such file or directory
   30 | #include <drm/drmP.h>

I hope it helps if someone confirms the error. Also do I need to use some other nvidia dkms package to be able to build with git version of the linux? Or is it the error that is made during writing the PKGBUILD. To mention I haven't changed a single option in PKBUILD left them default.

nekonoor commented on 2019-10-04 12:29

running make htmldocs seperately from make bzImage modules in the PKGBUILD solves the issue. I couldn't find the bugzilla for linux-next and I'm not sure where I should report it.