Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - linux-mainline

Package Base Details: linux-mainline

Git Clone URL: https://aur-dev.archlinux.org/linux-mainline.git (read-only)
Submitter: miffe
Maintainer: miffe
Last Packager: miffe
Votes: 188
Popularity: 5.668634
First Submitted: 2011-07-22 06:50
Last Updated: 2017-01-30 14:12

Latest Comments

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

darkbasic commented on 2016-02-02 09:58

@miffe I definitely prefer testing/linux please, I don't need a flag.

prazola commented on 2016-02-01 16:24

@miffe I go for the testing one, or you can add a flag to switch between two configs.

miffe commented on 2016-01-28 12:29

@darkbasic: I merge the core/linux config on every mainline-rc1 release. If enough people want it, I guess i could merge with testing/linux every rc release instead.

darkbasic commented on 2016-01-28 10:28

@miffe: Do you really use the config from core/linux? testing/linux would be a far better candidate. For example my laptop needed some config changes with 4.4, so I filed a bug and asked to fix it, which they did. If you still use the 4.3 config I will miss the improvements which will land in 4.4 once it will hit core. Since everyone expects linux-mainline being much more unstable than testing/linux, then aiming to use the testing config is the natural choice IMHO.

miffe commented on 2016-01-25 22:55

@lordheavy: I won't change the config from whats in core/linux.
@prazola: sed '215,242d' -i PKGBUILD

prazola commented on 2016-01-25 14:07

Header compile error if you exclude dvb configs from .config.

lordheavy commented on 2016-01-25 00:38

Can you enable powerplay with 4.5rc1 kernel ? Thks


prazola commented on 2016-01-17 21:38

One question: are compile flags present in "Makefile" of this kernel overrided by the /etc/makepkg.conf flags?

T4cC0re commented on 2016-01-13 05:13

It installed fine, but somehow the generated ramdisk missed the nvme and btrfs modules present in the 'real' kernels ramdisk. I needed to manually add them to mkinitcpio.conf.
How are those detected? Is this a problem of this package or a general kernel-building issue?

bradmccormack100 commented on 2016-01-10 23:45

The problem with cp: cannot stat ‘arch//Makefile’: No such file or directory is due to the scope of the KARCH variable

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-mainline#n110 is where it is defined.

Its not within scope here https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-mainline#n160

The quickest way to fix is to just move the KARCH variable to the top so it has global scope.

Perhaps around here https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-mainline#n39

There is already a patch listed here too https://bugs.archlinux.org/task/43885 that could be adopted.