Package Details: linux-mainline 4.8rc8-1

Git Clone URL: (read-only)
Package Base: linux-mainline
Description: The Linux-mainline kernel and modules
Upstream URL:
Licenses: GPL2
Submitter: miffe
Maintainer: miffe
Last Packager: miffe
Votes: 174
Popularity: 2.810464
First Submitted: 2011-07-22 06:50
Last Updated: 2016-09-26 13:11

Latest Comments

miffe commented on 2016-09-15 10:50

@mirh: They dont change that often. See
And it seems pointless to update them just to get another version string in a comment.

mirh commented on 2016-09-14 19:37

They can even be a week old, but if this is 4.8rc6, why the header of the file mentions 4.7.3-2 ?

miffe commented on 2016-08-29 14:04

They are a week old. And they are necessary.

mirh commented on 2016-08-29 13:22

Config files this package comes with are, for as much default, quite old and trigger some warnings.
Could they be updated?

Or even better, do we really need to ship them?

talonz commented on 2016-07-09 22:49

I got a problem trying to get r8168-dkms working it fails to build the module
Is there something I need to add to the package build to get it working, this fails on both mainline and git kernels

Your kernel headers for kernel cannot be found at
/usr/lib/modules//build or /usr/lib/modules//source.

Edit: i have linux-mainline-headers installed and the git one as well

Edit 2:
$ cat /var/lib/dkms/r8168/8.042/build/make.log
DKMS make.log for r8168-8.042 for kernel 4.7.0-rc7-gfa3a9f574 (x86_64)
Sat Jul 16 08:00:11 AEST 2016
make: Entering directory '/usr/lib/modules/4.7.0-rc7-gfa3a9f574/build'
CC [M] /var/lib/dkms/r8168/8.042/build/src/r8168_n.o
/var/lib/dkms/r8168/8.042/build/src/r8168_n.c: In function ‘rtl8168_init_one’:
/var/lib/dkms/r8168/8.042/build/src/r8168_n.c:22799:28: error: ‘struct net_device’ has no member named ‘gso_min_segs’; did you mean ‘gso_max_segs’?
dev->gso_min_segs = NIC_MIN_PHYS_BUF_COUNT;
/var/lib/dkms/r8168/8.042/build/src/r8168_n.c:22807:28: error: ‘struct net_device’ has no member named ‘gso_min_segs’; did you mean ‘gso_max_segs’?
dev->gso_min_segs = NIC_MIN_PHYS_BUF_COUNT;
/var/lib/dkms/r8168/8.042/build/src/r8168_n.c: In function ‘rtl8168_start_xmit’:
/var/lib/dkms/r8168/8.042/build/src/r8168_n.c:24969:12: error: ‘struct net_device’ has no member named ‘trans_start’; did you mean ‘mem_start’?
dev->trans_start = jiffies;
make[1]: *** [scripts/ /var/lib/dkms/r8168/8.042/build/src/r8168_n.o] Error 1
make: *** [Makefile:1457: _module_/var/lib/dkms/r8168/8.042/build/src] Error 2
make: Leaving directory '/usr/lib/modules/4.7.0-rc7-gfa3a9f574/build'

any help would be much appreciated as i am currently tethering off of my phone for a week ;[

kgizdov commented on 2016-07-09 16:47

I'm getting the following warning:

Hunk #1 succeeded at 39 (offset 2 lines).
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --olddefconfig Kconfig
.config:1614:warning: symbol value 'm' invalid for RXKAD
.config:7711:warning: symbol value 'm' invalid for ASYMMETRIC_KEY_TYPE
# configuration written to .config
scripts/kconfig/conf --silentoldconfig Kconfig

I wonder if it's a misconfiguration some where.

Jhackler commented on 2016-06-11 15:46

I had the same issue as craftyguy and his solution fixed it.

craftyguy commented on 2016-06-06 04:05

FYI, after installing 4.7rc2, I got an "error loading" error when trying to start X11. Reinstalling systemd and libsystemd resolved the issue. Not sure if there's anything you can do in the PKGBUILD for that, but thought I would mention it here in case others hit this.

oniram commented on 2016-05-25 20:19

Package community/bbswitch-dkms fails to build the module on this kernel (linux-mainline-4.6-1). I've tracked the problem down to a new user-space utility (objtool) that comes with 4.6 and needs to be installed.

In the core/linux package they handle it like this:

Jhackler commented on 2016-04-26 19:00

"I just wanted to know if something changed in the package to trigger the bad behaviour in yaourt or if it was an helper update which I didn't notice.

P.S. I really don't know why everybody hates helpers so much. Using makepkg is easy but tedious when you have lots of packages from aur: helpers are a great thing, especially since they allow you to edit the pkgbuilds on the fly."

darkbasic, the issue comes because it is clear that either the process of doing it manually is unknown, or the poster was not willing to put forward the effort to test it manually.

One should make sure it was the AUR package and not the helper first. The correct thing to do when it fails is, do it manually, then if it succeeds file the report with yaourt devs not the perfectly fine Aur package.

I use Yaourt and did not come here asking about the issue. Actually in this case rebooting the system and running yaourt again worked out. I doubt anyone hates people using helpers, they just are not interested in going out of the way to support them in their packages. Don't worry I have been lazy at times as well and got varied degrees of grief over it.

All comments