Package Base Details: linux-ryzen-git

Git Clone URL: (read-only, click to copy)
Submitter: ssorgatem
Maintainer: navigaid
Last Packager: ssorgatem
Votes: 8
Popularity: 0.000000
First Submitted: 2017-12-01 11:30
Last Updated: 2018-06-12 13:27

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

ssorgatem commented on 2018-02-26 09:18

Currently the GCC optimization patch fails to apply. I've opened an issue upstream:

Until it's fixed you may want to comment out the patch line in the PKGBUILD or just use the linux-git package instead.

gtpitch commented on 2018-02-20 05:23

21544 100 21544 0 0 90142 0 --:--:-- --:--:-- --:--:-- 90142 ==> Validating source files with sha256sums... linux ... Skipped config.x86_64 ... Skipped linux-ryzen-git.preset ... Passed enable_additional_cpu_optimizations_for_gcc_v4.9%2B_kernel_v4.13%2B.patch ... Passed ==> Extracting sources... -> Creating working copy of linux git repo... Cloning into 'linux'... done. Checking out files: 100% (62911/62911), done. ==> Starting prepare()... patching file arch/x86/include/asm/module.h Hunk #1 succeeded at 25 (offset 10 lines). Hunk #2 succeeded at 61 (offset 10 lines). patching file arch/x86/Kconfig.cpu Hunk #1 succeeded at 116 (offset 1 line). Hunk #2 succeeded at 149 (offset 1 line). Hunk #3 succeeded at 158 (offset 1 line). Hunk #4 succeeded at 166 (offset 1 line). Hunk #5 succeeded at 324 (offset 1 line). Hunk #6 succeeded at 334 (offset 1 line). Hunk #7 succeeded at 354 (offset 1 line). Hunk #8 succeeded at 435 (offset 1 line). Hunk #9 succeeded at 472 (offset 1 line). Hunk #10 FAILED at 502. 1 out of 10 hunks FAILED -- saving rejects to file arch/x86/Kconfig.cpu.rej patching file arch/x86/Makefile Hunk #1 succeeded at 124 (offset 3 lines). patching file arch/x86/Makefile_32.cpu Hunk #1 succeeded at 23 (offset 1 line). Hunk #2 succeeded at 43 (offset 1 line). ==> ERROR: A failure occurred in prepare(). Aborting... ==> ERROR: Makepkg was unable to build linux-ryzen-git. ==> Restart building linux-ryzen-git ? [y/N] ==> ----------------------------------------

ssorgatem commented on 2018-02-12 14:13

For those with AMD GPUs, I've rebased this on linux-amd-staging-drm-next-git in the package linux-ryzen-amd-staging-drm-next-git, which should provide the best of both packages.

mrpg commented on 2018-02-09 08:45

Thanks y'all. It's a weird issue, but I tried it again this morning (using -j16) and now it worked. So I can't rule out that there was some temporary hardware problem.

@quasd That's an interesting setting in /etc/security/limits.conf. Will certainly look into it, but for now my problem has been magically fixed.

ssorgatem commented on 2018-02-09 06:42

I do have MAKEFLAGS="-j12" in my makepkg.conf, so maybe that's why I haven't experienced that...

quasd commented on 2018-02-08 22:47


had the same problem while comiling other and this 4.15 kernels. I think I solved it by changing to MAKEFLAGS="-j12" in my makepkg.conf. I did also add following to my /etc/security/limits.conf

myusername soft stack 32768

which fixed the problem not so sure, but haven't seen the problem since. Good luck.

I also think some my other build failures were because of this. those gave errors while copying dvb headers. I don't have the exact error anymore but I think it was around cp drivers/media/dvb-frontends/.h "${pkgdir}/usr/lib/modules/${_kernver}/build/drivers/media/dvb-frontends/"

ssorgatem commented on 2018-02-08 18:25

Hmm, it builds just fine on my Ryzen 5 1600. It doesn't seem to be related to the packaging itself.

mrpg commented on 2018-02-08 17:19

@ssorgatem: Thanks for looking into it. Strangely, however, I now encounter a soft lockup (or some kind of resource starvation while fork()ing) while building the package. This has never happened before. As I can’t directly attribute it to this package (I can’t exclude hardware failure, and can’t currently check for it), do not consider this a bug report, but rather something I wanted to mention should someone else encounters a similar problem. (Ryzen 7 1800x)

Thanks again!

ssorgatem commented on 2018-02-08 15:46

Good call, I didn't know they had enabled CONFIG_RCU_NOCB_CPU.

However, this package enables building the kernel with "-march=native", which should give slightly better performance for some tasks.

For me though... I still prefer the bleeding edge :P (but not as bleeding as to potentially install a broken kernel...)

qrwteyrutiyoup commented on 2018-02-08 15:42

For you guys using this package, have you given a try to the regular linux (now at the 4.15 series)?

It does enable CONFIG_RCU_NOCB_CPU, so you should be able to use rcu_nocbs=0-x boot param (and it should make your life easier by not having to compile the kernel).