-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are these patches included in last edge kernel? #76
Comments
Hi, As far as I can tell, they are currently not included in the Linux stable builds. If you add these patches to the |
Ok, thanks, I will try that. |
Hi, I do not have a lot of experience, I have installed all the dependencies, added the two patches to the folder, downloaded the source and I am stuck just before building, where it says "Afterwards, select the branch of your likings (e.g. v5.8.x).", I have no idea how to select the branch. Also, since I am using a zen1 cpu, I would like to add znver1 parameter to the compiler, but I am not completely sure where it goes. Also, a suggestion, instead of the two options you offer to install dwarves > 1.16, dwarves 1.19 is in buster-backports. I think it would be simpler to suggest adding deb http://ftp.de.debian.org/debian buster-backports main to sources.list and then do apt update and apt install dwarves=1.19-1~bpo10+1 . Anyway, just a suggestion for "newbies" like me. |
I figured out. |
I got an error while compiling. I selected 5.11-8 and only added PVE_BUILD_CFLAGS='-march=znver1'. The mistake has to do with workaround #48 . This is the output:
Is this a error of the script or am I missing something installed? Seems module.lds.S is missing and these lines were added in a recent patch. |
Check whether you have updated the submodules:
|
I did, I run both sumodule lines after I cloned the source and cd into the folder. |
I can confirm the error is happening, following exactly the instructions in the README. Selected 5.11-9 and added PVE_BUILD_CFLAGS='-march=znver1'. Make fails with the same mistake as before. |
Could you go to git log |
|
So it seems the submodule is at 5.9, while you are trying to build for Linux 5.11. So, before you build, but after you have switched branches, you should run: git submodule update --depth 1 submodules/ubuntu-mainline |
Hi, I do not think I am selecting the branch appropiately because I am getting the same error. Can you indicate me how I am supposed to select the branch? |
Like this (for v5.11.x) git checkout v5.11.x
git submodule update --init --depth 1 submodules/ubuntu-mainline
git submodule update --init --recursive submodules/zfsonlinux |
Ok, that fixes that error. I am succesfully compiling the kernel now. You made a typo in your last comment, missing '--init' and an 's', in case anyone check all of this it should be like in your README:
The last command does not work also, the 's' on the last submodules is missing and even when added it complains about missing --init. Again, the order in your README:
seems to pull zfsonlinux fine. My only doubt now is how do I select the patchlevel? git checkout selects the major and minor, but, for example, in the case of 5.11 it selects 5.11.8 automatically. If I wanted to select 5.11.9, how would I do it? Would you accept a pull request to improve the instructions on the README? There might be a reason why you want the instructions as they are now, and if that is the case I will respect that and not lose my time, but if you are open to it, I can write a pull request and then you can decide if it improves the README or not. Lastly, I have some doubts when it comes to installation. The procedure has created several deb files: pve-edge-headers-5.11.8-1_5.11.8-1_amd64.deb Which of them should I install? And apart from installing the deb files and changing the apparmor configuration as per the README, is there anything else to do to properly install the new kernel? When I install pve-edge-kernel-XXXXX.deb and pve-edge-headers-XXXXX.deb I get this message:
My guess is that it is fine, but just want to confirm. I have thank you before, but I want to thank you again for taking the time to babysit me through the whole process. |
Thank you for spotting the typo! I updated my comment in case others are looking at this issue as well. I am also happy to accept pull requests updating/clarifying the documentation (or for that matter any useful change). As for your other questions:
|
Hi
Due to this issue , I need this and this patches in the kernel.
Does the last of your kernels include those patches? If not, how hard would it be to include them? Thanks.
The text was updated successfully, but these errors were encountered: