Re: Building custom kernels
Thanks for doing the work and posting the result / solution.
On Wed, 3 Mar 2021 19:19:14 +0100
Julian Sikorski wrote:
> I did actually manage to get this working, big thanks go to
> chenxiaolong for their guide [1]. I did mix-and-match some of the
> info from Fedora docs [2][3], mainly regarding how to create a
> certificate. It basically goes like:
>
> 1. Create certs with openssl
> 2. import them with certutil and pk12util as per [3]
> 3. add self to /etc/pesign/users
> 4. run sudo /usr/libexec/pesign/pesign-authorize
> 5. restart pesign service
> 6. unlock database (pesign-client -u)
> 7. add
> config_opts['plugin_conf']['bind_mount_opts']['dirs'].append(('/var/run/pesign',
>
> '/var/run/pesign')) to mock site-defaults.cfg
> 8. work around bugs
> 9. run mock adding -D 'pe_signing_token NSS Certificate DB' -D
> 'pe_signing_cert foo'
> 10. enroll the cert on the target machine
>
> It is worth noting that for some reason the pe_signing_cert nickname
> was not the one I specified using certutil -n parameter, but an
> amalgamation of O and CN values from the certificate. Check with
> certutil -L to be sure. Moreover, while bug 1508094 mentioned by
> chenxiaolong is fixed, there are two more bugs which need to be
> worked around for all of this to work [4][5].
> Finally, the rationale: given that the Renoir APU s0ix patches have
> just missed 5.12 merge window from the looks of it, I will likely
> have to keep building my own kernels for a while. Getting the rpm
> signed automatically saves me a lot of time. Disabling secure boot
> causes windows to ask for drivelock recovery password so it is not an
> option
>
> Best regards,
> Julian
>
> [1]
> https://gist.github.com/chenxiaolong/520914b191f17194a0acdc0e03122e63
> [2]
> https://docs.fedoraproject.org/en-US/fedora/f33/system-administrators-guide/kernel-module-driver-configuration/Working_with_Kernel_Modules/
> [3]
> https://docs.fedoraproject.org/en-US/quick-docs/kernel/build-custom-kernel/
> [4] https://bugzilla.redhat.com/show_bug.cgi?id=1880858
> [5] https://bugzilla.redhat.com/show_bug.cgi?id=1934719
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Building custom kernels
W dniu 03.03.2021 o 17:01, stan via devel pisze:
On Wed, 3 Mar 2021 14:27:16 +0100
Julian Sikorski wrote:
Am 03.03.21 um 14:00 schrieb Dominik 'Rathann' Mierzejewski:
There seems to be some documentation on the wiki:
https://fedoraproject.org/wiki/BuildingUpstreamKernel#Sign_the_kernel_for_Secure_Boot
Regards,
Dominik
This explains how to sign a kernel build locally with make, not how
to make mock & rpbmbuild use a self-signed certificate for the RPM
package.
I build a custom kernel tuned for my system from Fedora src.rpms
locally using rpmbuild (older technique without mock). I then install it
using dnf -C and sign it using a method similar to the above (pesign
instead of sbsign). What do you gain by having the rpms signed?
My thought is, if a person has the authority to run dnf to install
local packages on the system, secure boot is meaningless as protection.
Is it that you want the build process to sign the kernel in the rpm
package with your local keys so you don't have to go through the
process of signing the kernel after it is installed? If that is what
you want, and you get it working, would you post the technique here.
Hi,
I did actually manage to get this working, big thanks go to chenxiaolong
for their guide [1]. I did mix-and-match some of the info from Fedora
docs [2][3], mainly regarding how to create a certificate. It basically
goes like:
1. Create certs with openssl
2. import them with certutil and pk12util as per [3]
3. add self to /etc/pesign/users
4. run sudo /usr/libexec/pesign/pesign-authorize
5. restart pesign service
6. unlock database (pesign-client -u)
7. add
config_opts['plugin_conf']['bind_mount_opts']['dirs'].append(('/var/run/pesign',
'/var/run/pesign')) to mock site-defaults.cfg
8. work around bugs
9. run mock adding -D 'pe_signing_token NSS Certificate DB' -D
'pe_signing_cert foo'
10. enroll the cert on the target machine
It is worth noting that for some reason the pe_signing_cert nickname was
not the one I specified using certutil -n parameter, but an amalgamation
of O and CN values from the certificate. Check with certutil -L to be sure.
Moreover, while bug 1508094 mentioned by chenxiaolong is fixed, there
are two more bugs which need to be worked around for all of this to work
[4][5].
Finally, the rationale: given that the Renoir APU s0ix patches have just
missed 5.12 merge window from the looks of it, I will likely have to
keep building my own kernels for a while. Getting the rpm signed
automatically saves me a lot of time. Disabling secure boot causes
windows to ask for drivelock recovery password so it is not an option
Best regards,
Julian
[1] https://gist.github.com/chenxiaolong/520914b191f17194a0acdc0e03122e63
[2]
https://docs.fedoraproject.org/en-US/fedora/f33/system-administrators-guide/kernel-module-driver-configuration/Working_with_Kernel_Modules/
[3]
https://docs.fedoraproject.org/en-US/quick-docs/kernel/build-custom-kernel/
[4] https://bugzilla.redhat.com/show_bug.cgi?id=1880858
[5] https://bugzilla.redhat.com/show_bug.cgi?id=1934719
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Building custom kernels
On Wed, 3 Mar 2021 14:27:16 +0100 Julian Sikorski wrote: > Am 03.03.21 um 14:00 schrieb Dominik 'Rathann' Mierzejewski: > > > > There seems to be some documentation on the wiki: > > https://fedoraproject.org/wiki/BuildingUpstreamKernel#Sign_the_kernel_for_Secure_Boot > > > > Regards, > > Dominik > > > This explains how to sign a kernel build locally with make, not how > to make mock & rpbmbuild use a self-signed certificate for the RPM > package. I build a custom kernel tuned for my system from Fedora src.rpms locally using rpmbuild (older technique without mock). I then install it using dnf -C and sign it using a method similar to the above (pesign instead of sbsign). What do you gain by having the rpms signed? My thought is, if a person has the authority to run dnf to install local packages on the system, secure boot is meaningless as protection. Is it that you want the build process to sign the kernel in the rpm package with your local keys so you don't have to go through the process of signing the kernel after it is installed? If that is what you want, and you get it working, would you post the technique here. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Building custom kernels
Am 03.03.21 um 14:00 schrieb Dominik 'Rathann' Mierzejewski:
On Wednesday, 03 March 2021 at 13:53, Julian Sikorski wrote:
[...]
Now that the kernels have built successfully I have another question: is
there an easy way of signing them so that secureboot can stay enabled? I
have generated a key/certificate pair as described in the docs [1] but I was
not able to figure out how to feed these to rpmbuild/mock. The kernel spec
uses two .cer files instead of .priv/.der pair, and the docs [2] are out of
date as %{pe_signing_cert} are nowhere to be found in the spec.
There seems to be some documentation on the wiki:
https://fedoraproject.org/wiki/BuildingUpstreamKernel#Sign_the_kernel_for_Secure_Boot
Regards,
Dominik
This explains how to sign a kernel build locally with make, not how to
make mock & rpbmbuild use a self-signed certificate for the RPM package.
Best regards,
Julian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Building custom kernels
On Wednesday, 03 March 2021 at 13:53, Julian Sikorski wrote:
[...]
> Now that the kernels have built successfully I have another question: is
> there an easy way of signing them so that secureboot can stay enabled? I
> have generated a key/certificate pair as described in the docs [1] but I was
> not able to figure out how to feed these to rpmbuild/mock. The kernel spec
> uses two .cer files instead of .priv/.der pair, and the docs [2] are out of
> date as %{pe_signing_cert} are nowhere to be found in the spec.
There seems to be some documentation on the wiki:
https://fedoraproject.org/wiki/BuildingUpstreamKernel#Sign_the_kernel_for_Secure_Boot
Regards,
Dominik
--
Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Building custom kernels
Am 02.03.21 um 18:24 schrieb Julian Sikorski:
W dniu 02.03.2021 o 18:10, Julian Sikorski pisze:
W dniu 02.03.2021 o 13:42, Justin Forbes pisze:
On Tue, Mar 2, 2021 at 3:32 AM Julian Sikorski
wrote:
Am 01.03.21 um 17:37 schrieb Brandon Nielsen:
On 2/28/21 12:00 PM, Julian Sikorski wrote:
W dniu 27.02.2021 o 20:59, Julian Sikorski pisze:
Hi,
I am trying to test some Renoir s2idle patches [1]. It appears that
Fedora kernel source is now maintained on gitlab as kernel-ark [2].
What I tried is adding the patches to the fedora-5.11 branch and
running make dist-srpm, but it failed due to config mismatch on
CONFIG_INIT_STACK_NONE:
Processing
/home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-aarch64-fedora.config
... Error: Mismatches found in configuration files
Found CONFIG_INIT_STACK_NONE=y after generation, had
CONFIG_INIT_STACK_NONE=is not set in Source tree
make[1]: *** [Makefile:145: dist-configs-check] Błąd 1
Is this expected? Is there a better way of testing patches on Fedora
kernels? Thanks for the help in advance.
Best regards,
Julian
[1] https://gitlab.freedesktop.org/drm/amd/-/issues/1230
[2] https://gitlab.com/cki-project/kernel-ark
Hi,
the same keeps happening if I try to merge os-build into agdf5
tree or
even if I try to make srpm in the ark-latest branch. Is this normal?
Best regards,
Julian
I found the same last week and the documentation[0] feels really
unloved.
I eventually resorted to rebuilding from the SRPM and apply patches
there.
[0] -
https://docs.fedoraproject.org/en-US/quick-docs/kernel/build-custom-kernel/
___
Hi,
there is more documentation available [1], but unfortunately one gets
the error I mentioned above when trying to follow it.
Aha, I seem to have forgotten where this came from. You are actually
missing a buildreq for the kernel. I believe that 'dnf install
gcc-plugin-devel' will fix your issue with the config mismatch. Also,
if you are working with the fedora-5.11 branch, I have included a
script in redhat/fedora-dist-git-test.sh which will generate a test
version of a dist-git update. While that may not be your goal, it
would be worth looking at the command line there for generating a
proper srpm.
Thanks,
Justin
Thanks, 5.11 branch with s0ix patches on top went further now:
Processing
/home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-i686-fedora.config
... Found unset config items, please set them to an appropriate value
CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP=n
os-build no longer cleanly merges with agd5f s0ix branch so fixing the
above is likely the easiest option to get going.
Best regards,
Julian
I fixed it with attached patch, I can generate a SRPM now. Thanks again!
Best regards,
Julian
Now that the kernels have built successfully I have another question: is
there an easy way of signing them so that secureboot can stay enabled? I
have generated a key/certificate pair as described in the docs [1] but I
was not able to figure out how to feed these to rpmbuild/mock. The
kernel spec uses two .cer files instead of .priv/.der pair, and the docs
[2] are out of date as %{pe_signing_cert} are nowhere to be found in the
spec.
[1]
https://docs.fedoraproject.org/en-US/fedora/f33/system-administrators-guide/kernel-module-driver-configuration/Working_with_Kernel_Modules/
[2]
https://docs.fedoraproject.org/en-US/quick-docs/kernel/build-custom-kernel/
Best regards,
Julian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Building custom kernels
W dniu 02.03.2021 o 18:10, Julian Sikorski pisze: W dniu 02.03.2021 o 13:42, Justin Forbes pisze: On Tue, Mar 2, 2021 at 3:32 AM Julian Sikorski wrote: Am 01.03.21 um 17:37 schrieb Brandon Nielsen: On 2/28/21 12:00 PM, Julian Sikorski wrote: W dniu 27.02.2021 o 20:59, Julian Sikorski pisze: Hi, I am trying to test some Renoir s2idle patches [1]. It appears that Fedora kernel source is now maintained on gitlab as kernel-ark [2]. What I tried is adding the patches to the fedora-5.11 branch and running make dist-srpm, but it failed due to config mismatch on CONFIG_INIT_STACK_NONE: Processing /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-aarch64-fedora.config ... Error: Mismatches found in configuration files Found CONFIG_INIT_STACK_NONE=y after generation, had CONFIG_INIT_STACK_NONE=is not set in Source tree make[1]: *** [Makefile:145: dist-configs-check] Błąd 1 Is this expected? Is there a better way of testing patches on Fedora kernels? Thanks for the help in advance. Best regards, Julian [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1230 [2] https://gitlab.com/cki-project/kernel-ark Hi, the same keeps happening if I try to merge os-build into agdf5 tree or even if I try to make srpm in the ark-latest branch. Is this normal? Best regards, Julian I found the same last week and the documentation[0] feels really unloved. I eventually resorted to rebuilding from the SRPM and apply patches there. [0] - https://docs.fedoraproject.org/en-US/quick-docs/kernel/build-custom-kernel/ ___ Hi, there is more documentation available [1], but unfortunately one gets the error I mentioned above when trying to follow it. Aha, I seem to have forgotten where this came from. You are actually missing a buildreq for the kernel. I believe that 'dnf install gcc-plugin-devel' will fix your issue with the config mismatch. Also, if you are working with the fedora-5.11 branch, I have included a script in redhat/fedora-dist-git-test.sh which will generate a test version of a dist-git update. While that may not be your goal, it would be worth looking at the command line there for generating a proper srpm. Thanks, Justin Thanks, 5.11 branch with s0ix patches on top went further now: Processing /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-i686-fedora.config ... Found unset config items, please set them to an appropriate value CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP=n os-build no longer cleanly merges with agd5f s0ix branch so fixing the above is likely the easiest option to get going. Best regards, Julian I fixed it with attached patch, I can generate a SRPM now. Thanks again! Best regards, Julian >From 3e43f8c7cde923f6554aec15fd8619468eb89795 Mon Sep 17 00:00:00 2001 From: Julian Sikorski Date: Tue, 2 Mar 2021 18:23:28 +0100 Subject: [PATCH] Set unset config option --- .../configs/fedora/generic/x86/CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP | 1 + 1 file changed, 1 insertion(+) create mode 100644 redhat/configs/fedora/generic/x86/CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP diff --git a/redhat/configs/fedora/generic/x86/CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP b/redhat/configs/fedora/generic/x86/CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP new file mode 100644 index ..3bb67a6665b4 --- /dev/null +++ b/redhat/configs/fedora/generic/x86/CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP @@ -0,0 +1 @@ +# CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP is not set -- 2.29.2 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Building custom kernels
W dniu 02.03.2021 o 13:42, Justin Forbes pisze: On Tue, Mar 2, 2021 at 3:32 AM Julian Sikorski wrote: Am 01.03.21 um 17:37 schrieb Brandon Nielsen: On 2/28/21 12:00 PM, Julian Sikorski wrote: W dniu 27.02.2021 o 20:59, Julian Sikorski pisze: Hi, I am trying to test some Renoir s2idle patches [1]. It appears that Fedora kernel source is now maintained on gitlab as kernel-ark [2]. What I tried is adding the patches to the fedora-5.11 branch and running make dist-srpm, but it failed due to config mismatch on CONFIG_INIT_STACK_NONE: Processing /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-aarch64-fedora.config ... Error: Mismatches found in configuration files Found CONFIG_INIT_STACK_NONE=y after generation, had CONFIG_INIT_STACK_NONE=is not set in Source tree make[1]: *** [Makefile:145: dist-configs-check] Błąd 1 Is this expected? Is there a better way of testing patches on Fedora kernels? Thanks for the help in advance. Best regards, Julian [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1230 [2] https://gitlab.com/cki-project/kernel-ark Hi, the same keeps happening if I try to merge os-build into agdf5 tree or even if I try to make srpm in the ark-latest branch. Is this normal? Best regards, Julian I found the same last week and the documentation[0] feels really unloved. I eventually resorted to rebuilding from the SRPM and apply patches there. [0] - https://docs.fedoraproject.org/en-US/quick-docs/kernel/build-custom-kernel/ ___ Hi, there is more documentation available [1], but unfortunately one gets the error I mentioned above when trying to follow it. Aha, I seem to have forgotten where this came from. You are actually missing a buildreq for the kernel. I believe that 'dnf install gcc-plugin-devel' will fix your issue with the config mismatch. Also, if you are working with the fedora-5.11 branch, I have included a script in redhat/fedora-dist-git-test.sh which will generate a test version of a dist-git update. While that may not be your goal, it would be worth looking at the command line there for generating a proper srpm. Thanks, Justin Thanks, 5.11 branch with s0ix patches on top went further now: Processing /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-i686-fedora.config ... Found unset config items, please set them to an appropriate value CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP=n os-build no longer cleanly merges with agd5f s0ix branch so fixing the above is likely the easiest option to get going. Best regards, Julian ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Building custom kernels
On Tue, Mar 2, 2021 at 3:32 AM Julian Sikorski wrote: > > Am 01.03.21 um 17:37 schrieb Brandon Nielsen: > > On 2/28/21 12:00 PM, Julian Sikorski wrote: > >> W dniu 27.02.2021 o 20:59, Julian Sikorski pisze: > >>> Hi, > >>> > >>> I am trying to test some Renoir s2idle patches [1]. It appears that > >>> Fedora kernel source is now maintained on gitlab as kernel-ark [2]. > >>> What I tried is adding the patches to the fedora-5.11 branch and > >>> running make dist-srpm, but it failed due to config mismatch on > >>> CONFIG_INIT_STACK_NONE: > >>> > >>> Processing > >>> /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-aarch64-fedora.config > >>> ... Error: Mismatches found in configuration files > >>> Found CONFIG_INIT_STACK_NONE=y after generation, had > >>> CONFIG_INIT_STACK_NONE=is not set in Source tree > >>> make[1]: *** [Makefile:145: dist-configs-check] Błąd 1 > >>> > >>> Is this expected? Is there a better way of testing patches on Fedora > >>> kernels? Thanks for the help in advance. > >>> > >>> Best regards, > >>> Julian > >>> > >>> [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1230 > >>> [2] https://gitlab.com/cki-project/kernel-ark > >> > >> Hi, > >> > >> the same keeps happening if I try to merge os-build into agdf5 tree or > >> even if I try to make srpm in the ark-latest branch. Is this normal? > >> > >> Best regards, > >> Julian > >> > > > > I found the same last week and the documentation[0] feels really unloved. > > > > I eventually resorted to rebuilding from the SRPM and apply patches there. > > > > [0] - > > https://docs.fedoraproject.org/en-US/quick-docs/kernel/build-custom-kernel/ > > ___ > Hi, > > there is more documentation available [1], but unfortunately one gets > the error I mentioned above when trying to follow it. > Aha, I seem to have forgotten where this came from. You are actually missing a buildreq for the kernel. I believe that 'dnf install gcc-plugin-devel' will fix your issue with the config mismatch. Also, if you are working with the fedora-5.11 branch, I have included a script in redhat/fedora-dist-git-test.sh which will generate a test version of a dist-git update. While that may not be your goal, it would be worth looking at the command line there for generating a proper srpm. Thanks, Justin ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Building custom kernels
Am 01.03.21 um 17:37 schrieb Brandon Nielsen: On 2/28/21 12:00 PM, Julian Sikorski wrote: W dniu 27.02.2021 o 20:59, Julian Sikorski pisze: Hi, I am trying to test some Renoir s2idle patches [1]. It appears that Fedora kernel source is now maintained on gitlab as kernel-ark [2]. What I tried is adding the patches to the fedora-5.11 branch and running make dist-srpm, but it failed due to config mismatch on CONFIG_INIT_STACK_NONE: Processing /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-aarch64-fedora.config ... Error: Mismatches found in configuration files Found CONFIG_INIT_STACK_NONE=y after generation, had CONFIG_INIT_STACK_NONE=is not set in Source tree make[1]: *** [Makefile:145: dist-configs-check] Błąd 1 Is this expected? Is there a better way of testing patches on Fedora kernels? Thanks for the help in advance. Best regards, Julian [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1230 [2] https://gitlab.com/cki-project/kernel-ark Hi, the same keeps happening if I try to merge os-build into agdf5 tree or even if I try to make srpm in the ark-latest branch. Is this normal? Best regards, Julian I found the same last week and the documentation[0] feels really unloved. I eventually resorted to rebuilding from the SRPM and apply patches there. [0] - https://docs.fedoraproject.org/en-US/quick-docs/kernel/build-custom-kernel/ ___ Hi, there is more documentation available [1], but unfortunately one gets the error I mentioned above when trying to follow it. Best regards, Julian [1] https://cki-project.gitlab.io/kernel-ark/index.html ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Building custom kernels
Am 01.03.21 um 22:37 schrieb Justin Forbes: On Sun, Feb 28, 2021 at 12:00 PM Julian Sikorski wrote: W dniu 27.02.2021 o 20:59, Julian Sikorski pisze: Hi, I am trying to test some Renoir s2idle patches [1]. It appears that Fedora kernel source is now maintained on gitlab as kernel-ark [2]. What I tried is adding the patches to the fedora-5.11 branch and running make dist-srpm, but it failed due to config mismatch on CONFIG_INIT_STACK_NONE: Processing /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-aarch64-fedora.config ... Error: Mismatches found in configuration files Found CONFIG_INIT_STACK_NONE=y after generation, had CONFIG_INIT_STACK_NONE=is not set in Source tree make[1]: *** [Makefile:145: dist-configs-check] Błąd 1 Is this expected? Is there a better way of testing patches on Fedora kernels? Thanks for the help in advance. Best regards, Julian [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1230 [2] https://gitlab.com/cki-project/kernel-ark Hi, the same keeps happening if I try to merge os-build into agdf5 tree or even if I try to make srpm in the ark-latest branch. Is this normal? I am guessing you are currently on F32? There are unfortunately some config options which are gcc version dependent. I know it has been complained about upstream, but they exist. Justin I am on F33 x86_64. In case F33 is affected too, is there a workaround beyond building the kernel from a rawhide VM? Best regards, Julian ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Building custom kernels
On Sun, Feb 28, 2021 at 12:00 PM Julian Sikorski wrote: > > W dniu 27.02.2021 o 20:59, Julian Sikorski pisze: > > Hi, > > > > I am trying to test some Renoir s2idle patches [1]. It appears that > > Fedora kernel source is now maintained on gitlab as kernel-ark [2]. What > > I tried is adding the patches to the fedora-5.11 branch and running make > > dist-srpm, but it failed due to config mismatch on CONFIG_INIT_STACK_NONE: > > > > Processing > > /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-aarch64-fedora.config > > ... Error: Mismatches found in configuration files > > Found CONFIG_INIT_STACK_NONE=y after generation, had > > CONFIG_INIT_STACK_NONE=is not set in Source tree > > make[1]: *** [Makefile:145: dist-configs-check] Błąd 1 > > > > Is this expected? Is there a better way of testing patches on Fedora > > kernels? Thanks for the help in advance. > > > > Best regards, > > Julian > > > > [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1230 > > [2] https://gitlab.com/cki-project/kernel-ark > > Hi, > > the same keeps happening if I try to merge os-build into agdf5 tree or > even if I try to make srpm in the ark-latest branch. Is this normal? > I am guessing you are currently on F32? There are unfortunately some config options which are gcc version dependent. I know it has been complained about upstream, but they exist. Justin ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Building custom kernels
On 2/28/21 12:00 PM, Julian Sikorski wrote: W dniu 27.02.2021 o 20:59, Julian Sikorski pisze: Hi, I am trying to test some Renoir s2idle patches [1]. It appears that Fedora kernel source is now maintained on gitlab as kernel-ark [2]. What I tried is adding the patches to the fedora-5.11 branch and running make dist-srpm, but it failed due to config mismatch on CONFIG_INIT_STACK_NONE: Processing /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-aarch64-fedora.config ... Error: Mismatches found in configuration files Found CONFIG_INIT_STACK_NONE=y after generation, had CONFIG_INIT_STACK_NONE=is not set in Source tree make[1]: *** [Makefile:145: dist-configs-check] Błąd 1 Is this expected? Is there a better way of testing patches on Fedora kernels? Thanks for the help in advance. Best regards, Julian [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1230 [2] https://gitlab.com/cki-project/kernel-ark Hi, the same keeps happening if I try to merge os-build into agdf5 tree or even if I try to make srpm in the ark-latest branch. Is this normal? Best regards, Julian I found the same last week and the documentation[0] feels really unloved. I eventually resorted to rebuilding from the SRPM and apply patches there. [0] - https://docs.fedoraproject.org/en-US/quick-docs/kernel/build-custom-kernel/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Building custom kernels
W dniu 27.02.2021 o 20:59, Julian Sikorski pisze: Hi, I am trying to test some Renoir s2idle patches [1]. It appears that Fedora kernel source is now maintained on gitlab as kernel-ark [2]. What I tried is adding the patches to the fedora-5.11 branch and running make dist-srpm, but it failed due to config mismatch on CONFIG_INIT_STACK_NONE: Processing /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-aarch64-fedora.config ... Error: Mismatches found in configuration files Found CONFIG_INIT_STACK_NONE=y after generation, had CONFIG_INIT_STACK_NONE=is not set in Source tree make[1]: *** [Makefile:145: dist-configs-check] Błąd 1 Is this expected? Is there a better way of testing patches on Fedora kernels? Thanks for the help in advance. Best regards, Julian [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1230 [2] https://gitlab.com/cki-project/kernel-ark Hi, the same keeps happening if I try to merge os-build into agdf5 tree or even if I try to make srpm in the ark-latest branch. Is this normal? Best regards, Julian ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Building custom kernels
Hi, I am trying to test some Renoir s2idle patches [1]. It appears that Fedora kernel source is now maintained on gitlab as kernel-ark [2]. What I tried is adding the patches to the fedora-5.11 branch and running make dist-srpm, but it failed due to config mismatch on CONFIG_INIT_STACK_NONE: Processing /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-aarch64-fedora.config ... Error: Mismatches found in configuration files Found CONFIG_INIT_STACK_NONE=y after generation, had CONFIG_INIT_STACK_NONE=is not set in Source tree make[1]: *** [Makefile:145: dist-configs-check] Błąd 1 Is this expected? Is there a better way of testing patches on Fedora kernels? Thanks for the help in advance. Best regards, Julian [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1230 [2] https://gitlab.com/cki-project/kernel-ark ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
