From: Stefano Brivio <sbrivio@redhat.com>
To: Deepak R Varma <drv@mailo.com>
Cc: outreachy@lists.linux.dev, Julia Lawall <julia.lawall@inria.fr>,
Sevinj Aghayeva <sevinj.aghayeva@gmail.com>,
Roopa Prabhu <roopa@nvidia.com>
Subject: Re: trouble booting into staging kernel
Date: Mon, 10 Oct 2022 12:54:27 +0200 [thread overview]
Message-ID: <20221010125427.52d5a103@elisabeth> (raw)
In-Reply-To: <Y0MKHfWsqsh4S9ld@lion>
Hi Deepak,
On Sun, 9 Oct 2022 23:21:25 +0530
Deepak R Varma <drv@mailo.com> wrote:
> Hello,
> I am natively running 5.15.0-48-generic on my HP Laptop with Secure boot on. I
> tried to follow the Kernel First patch tutorial steps and managed to build
> Kernel release 6.0.0rc4.
Somewhat unrelated: in a past Outreachy round, we did a bit of work on
a tool with the idea of making these steps easier. It's not mentioned
in the tutorial, as we didn't have time to polish it up completely, but
maybe you want to give it a try. Basic usage demo and source at:
https://mbuto.sh
I'm not mentoring for this round, so I'm just throwing this around
without claiming any responsibility. :)
About the specific issue you're hitting, I don't have any pointer other
than what Julia already shared.
> There were issues during the module building associated
> with the certificates / signing of the modules. I got those supressed by
> emptying the following two config parameters as copied over from the native
> config file:
>
> CONFIG_SYSTEM_TRUSTED_KEYS="debian/canonical-certs.pem"
> CONFIG_SYSTEM_REVOCATION_KEYS="debian/canonical-revoked-certs.pem"
>
> set to new value
>
> CONFIG_SYSTEM_TRUSTED_KEYS=""
> CONFIG_SYSTEM_REVOCATION_KEYS=""
>
> The build was successful, however, I am unable to boot into my new kernel and
> have received following errors:
>
> error: bad shim signature
> Loading initial ramdisk
> error: you need to load the kernel first
>
> I tried to seek from net, but did not find any workable resolution. Can you
> please suggested how can I correct this error or if I missed any steps?
>
> Thank you,
> Deepak.
--
Stefano
next prev parent reply other threads:[~2022-10-10 10:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 17:51 trouble booting into staging kernel Deepak R Varma
2022-10-09 17:56 ` Julia Lawall
2022-10-09 19:01 ` Deepak R Varma
2022-10-09 19:12 ` Julia Lawall
2022-10-09 19:55 ` Deepak R Varma
2022-10-12 20:22 ` Deepak R Varma
2022-10-13 5:21 ` Julia Lawall
2022-10-13 8:44 ` Deepak R Varma
2022-10-13 10:10 ` Deepak R Varma
2022-10-13 14:59 ` Fabio M. De Francesco
2022-10-13 16:38 ` Deepak R Varma
2022-10-16 14:23 ` Deepak R Varma
2022-10-10 10:54 ` Stefano Brivio [this message]
2022-10-10 17:02 ` Deepak R Varma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221010125427.52d5a103@elisabeth \
--to=sbrivio@redhat.com \
--cc=drv@mailo.com \
--cc=julia.lawall@inria.fr \
--cc=outreachy@lists.linux.dev \
--cc=roopa@nvidia.com \
--cc=sevinj.aghayeva@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.