# run your own 4.17 kernel in NRR  for fun and profit

**URL:** https://support.blue-systems.com/t/run-your-own-4-17-kernel-in-nrr-for-fun-and-profit/4408
**Category:** Rolling 2018.01
**Created:** [March 7, 2018, 4:59am UTC](https://support.blue-systems.com/t/run-your-own-4-17-kernel-in-nrr-for-fun-and-profit/4408 "2018-03-07T04:59:22Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![sp2004c](https://support.blue-systems.com/letter_avatar/sp2004c/32/5_5575768a8748004e209b776fc1b2916d.png) [@sp2004c](https://support.blue-systems.com/u/sp2004c)
#### Post date: [March 7, 2018, 4:59am UTC](https://support.blue-systems.com/t/run-your-own-4-17-kernel-in-nrr-for-fun-and-profit/4408/1 "2018-03-07T04:59:22Z")

</div>

[color=#66cc33]The following tutorial is not officially supported, and could potentially harm your system, proceed at your own risk.[/color]

[hr]

now … 😃 git clone (or unZip) this [https://github.com/manjaro/packages-core](https://github.com/manjaro/packages-core) :idea:

and in 417 subdir run

makepkg  
as usual 😪

follow guide: [https://wiki.parabola.nu/Kernel\_native\_compilation](https://wiki.parabola.nu/Kernel_native_compilation)  
more or less 🆒

you get a working kernel and initrd, but there may well be graphics driver problems,  
so you’re stuck in the bash shell. :-/

---

<div class="post-metadata">

### Author: ![sp2004c](https://support.blue-systems.com/letter_avatar/sp2004c/32/5_5575768a8748004e209b776fc1b2916d.png) [@sp2004c](https://support.blue-systems.com/u/sp2004c)
#### Post date: [May 23, 2018, 11:54pm UTC](https://support.blue-systems.com/t/run-your-own-4-17-kernel-in-nrr-for-fun-and-profit/4408/2 "2018-05-23T23:54:58Z")

</div>

with [https://en.wikipedia.org/wiki/Dracut\_(software)](https://en.wikipedia.org/wiki/Dracut_(software)) you get a working RAMDISK for NRR / Manja real quick. 🙂

else use your regular mkinitcpio with -P possibly

---

<div class="post-metadata">

### Author: ![AJSlye](https://support.blue-systems.com/user_avatar/support.blue-systems.com/ajslye/32/263_2.png) [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [May 24, 2018, 2:43am UTC](https://support.blue-systems.com/t/run-your-own-4-17-kernel-in-nrr-for-fun-and-profit/4408/3 "2018-05-24T02:43:14Z")

</div>

One more time, you need to start adding a disclaimer that these tutorials of yours are NOT officially supported.

---

<div class="post-metadata">

### Author: ![sp2004c](https://support.blue-systems.com/letter_avatar/sp2004c/32/5_5575768a8748004e209b776fc1b2916d.png) [@sp2004c](https://support.blue-systems.com/u/sp2004c)
#### Post date: [May 24, 2018, 7:46am UTC](https://support.blue-systems.com/t/run-your-own-4-17-kernel-in-nrr-for-fun-and-profit/4408/4 "2018-05-24T07:46:12Z")

</div>

-march=native no longer works right away. linker breaks now. may still be poss somehow.

always keep a backup copy of a known working “.config” , the corresponding kernel binary “bzImage” and a working initrd in a safe subdir to fall back on in case of crash / hang. In .config (i.e. make xconfig) you have to tread carefully since many options will render the kernel unbootable without further meddling.

keep in mind: you get boot fail if:

mismatch of either one component: kernel-binary “bzImage”, initrd , and stuff under /lib/modules

e.g. at some stage /lib/modules/4.17.0-1-MANJARO+

will be filled by “time sudo make modules\_install” mind the + at the end, without it: BOOT FAIL 😛
