[SOLVED] compiling proxmox-kernel from git

[liebero3]

Hello,

I'm trying to compile the kernel from git.proxmox.com/git/pve-kernel.git.

After "git clone git://git.proxmox.com/git/pve-kernel.git", I do "cp /boot/config-4.10.8-1-pve .config" and change what I need to change to get a running ubuntukernel with by gigabyte gaming 5 (pinctrl_amd=n).

How do I build the kernel now? Is it just "make"?

Help would be very appriciated.

Cheers,
Till

 

[Alexander Pytlev]

https://kernel-handbook.alioth.debian.org/ch-common-tasks.html

 

[liebero3]

Hi Alexander,

sry, I don't get how it works. I already compiled a kernel for debian before, but this time for proxmox, I don't understand how to do it. Did you already do that? I don't see any similarity to the normal kernel compiling

 

[fabian]

Hi Alexander,

sry, I don't get how it works. I already compiled a kernel for debian before, but this time for proxmox, I don't understand how to do it. Did you already do that? I don't see any similarity to the normal kernel compiling

there is a step in the Makefile where the kernel config is adapted from the Ubuntu defaults - just add your desired option(s) there and then run "make"

 

[liebero3]

Thank you Fabian. I found out just yesterday about that, but still no success. After installing all dependencies (and adjusting the size of the root partition several times...) I still haven't succeeded.

Here are my logs. It does not compile in one single call, no matter what I do.

log2.txt is too large, so I just copied the last lines. All three logs are from one try, it just stopped two times and I restarted with 'make -j16'

Cheers,
Till

 

[fabian]

sorry, I misread a part of your post (I thought you had done the following, but you just called the pve-kernel Makefile with "-j 16"). our kernel Makefile is a bit stupid and doesn't handle parallel execution of its targets (something that's been on my TODO list for quite a while, but unfortunately not very high up ). If you want to compile with 16 threads instead of 8, change the hardcoded "make ... -j 8" call for the actual kernel compilation (line 248) into "-j 16". in any case, you need to call the pve-kernel Makefile with "-j 1", otherwise different stages of the kernel build will be executed in parallel although they are not built for that.

you might want to do a "git reset --hard; git clean -df; git clean -xf; git submodule update" to reset your local copy to a pristine state - but make sure you have your changes committed locally unless you want to redo them, that sequence of commands will delete/reset anything that is "dirty", including untracked files..

(I would also suggest calling the Makefile using "fakeroot", so that the permissions for the headers package are correct - that should probably also get fixed properly in the Makefile..)

 

[liebero3]

Hi Fabian,

stupid me...spotted hints for that kind of problem all the time and after failing that much, i should have tried compiling it without -j16 at least one time.

Now everything works, but regarding the other thread, I kept getting the same error even after setting pinctrl_amd to modular. Now after deactivation everything works fine.

Since I am experimenting all the time, I could test different things, if you are interested in the gigabyte/ryzen problem.

Thank you very much for your support!

EDIT: typos...

 

[fabian]

Hi Fabian,

stupid me...spotted hints for that kind of problem all the time and after failing that much, i should have tried compiling it without -j16 at least one time.

Now everything works, but regarding the other thread, I kept getting the same error even after setting pinctrl_amd to modular. Now after deactivation everything works fine.

Since I am experimenting all the time, I could test different things, if you are interested in the gigabyte/ryzen problem.

Thank you very much for your support!

EDIT: typos...

you probably need to blacklist the module in addition to setting it to modular otherwise, it will be automatically loaded because the kernel thinks your hardware needs it.

 

[liebero3]

I did that inside /etc/modprobe.d/pve-blacklist.conf, but after that it crashed directly after boot. Will try it again, can a typo inside the file cause crashes?

 

[fabian]

no, a typo will just cause the blacklisting to not work.