From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: ** X-Spam-Status: No, score=2.5 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C3FE2C433DB for ; Wed, 24 Mar 2021 13:28:21 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3963D61A01 for ; Wed, 24 Mar 2021 13:28:21 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3963D61A01 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94) (envelope-from ) id 1lP3Ya-0007kv-91 for kernelnewbies@archiver.kernel.org; Wed, 24 Mar 2021 09:28:20 -0400 Received: from mail-ed1-x52c.google.com ([2a00:1450:4864:20::52c]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94) (envelope-from ) id 1lP3Wo-0006Jc-57 for kernelnewbies@kernelnewbies.org; Wed, 24 Mar 2021 09:26:30 -0400 Received: by mail-ed1-x52c.google.com with SMTP id h10so27571976edt.13 for ; Wed, 24 Mar 2021 06:26:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=c3hf8z563FMuTpuh3Eq4XF1CMmpF3ATjDzo6qwGim7M=; b=oJ1v9xNGMN8HCIGMLAVKnPCKReBkzMIuALBbEe5+2KSy71N+uESVVIWJCJwzGiOsLa WdSP/bVdYypzXplVb45Ou5TsbSXYrbY5BX+IiD67KVp87ANeeqxcJu5i7IVy1ZOLleOu I5CTFphtBQRThx+JdeGQesMk67hk1g0Vx2GmwvlaubYGT0u/7vj7yFbrM0cCGT93TUD1 knYzKNG8IwBZuGJ0fOSaPmtCh+TSBtLd8q70GSXyk/dXCuJTNvhJNOEDm+Jt0RNWFv+2 O7GaKfkE9y7OYVGR4Eq8XVYzkDnJFMex8rstvkUO4hWWAVJ2PhWMTpzFeojPNFQKjE2+ /l5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=c3hf8z563FMuTpuh3Eq4XF1CMmpF3ATjDzo6qwGim7M=; b=hnU7JP5J4A1wTaZJPFPJoZp1mHDyQKo6OZTuu91D0NKPQkRUYfsX52U1103wKe+ZXu Hp1SHHSZOLF0pCMUM/o2thGxNlQ77N/YAMYvPkWXtjiKUuvAy+y4HxfNj4SDcgnfJ/hh elH75gxZdNhKxU8y5b16/5BfbjvSSxRK0svQyblvFnxaJLU0xBZAQH8uQ0Q/wYrNpMr4 HWEPvtzu4h8sGpQv9ZoePcYsbJIlyFg9QjGj5C9nwBpCyAl0pLDGpEPHZG4Jx+Se4PAC dnvXsEnJH/95k5FJSLWury21/8OdpyYGclm2FBjjM2clJyEp9GC1bEW5FbZpn5h7J8wO jJ4A== X-Gm-Message-State: AOAM532qyooYRWo6cusaK/n+A7If2e2mtlFQ5T5hdzVn+YNqV6n1L7rs ChpMHQ7Po3pYUmXf45DDMpNj7me8Fnvt3r0w1Nw= X-Google-Smtp-Source: ABdhPJyKiciskkd7sRait7NC6PO4KF7stgSeshRxSSMRwPqrnJaLeLluEjGQvJkxQ50MykrEkQmj5B4P6SMwcvbxQCc= X-Received: by 2002:aa7:ccd7:: with SMTP id y23mr3465026edt.190.1616592388629; Wed, 24 Mar 2021 06:26:28 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Aruna Hewapathirane Date: Wed, 24 Mar 2021 09:26:17 -0400 Message-ID: Subject: Re: "Invalid signature" issue on dev kernel launch To: Gidi Gal Cc: Valdis Kletnieks , kernelnewbies X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1668477309813873879==" Errors-To: kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org --===============1668477309813873879== Content-Type: multipart/alternative; boundary="0000000000001229aa05be483f52" --0000000000001229aa05be483f52 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Mar 24, 2021 at 8:58 AM Gidi Gal wrote: > Disabling secure boot should make your invalid signature error go away. >> > > Thanks, Aruna, I managed to launch my kernel after disabling secure boot. > Finally, I am able to continue with my tutorial :-) > See your a kernel hacker now and your are welcome but thank Valdis he said something about secure boot that got me thinking :-) What kind of changes in the kernel require testing with valid signatures ? I frankly have no clue. I never needed signatures so far anyway. Valdis any thoughts please ? > > Thanks, > Gidi > > > On Wed, Mar 24, 2021 at 4:36 AM Aruna Hewapathirane < > aruna.hewapathirane@gmail.com> wrote: > >> >> >> On Tue, Mar 23, 2021 at 12:37 PM Gidi Gal >> wrote: >> >>> Greetings, >>> >>> After receiving a lot of information regarding my query on how to switc= h >>> from installed to dev kernel (thank you to all the people that shared t= heir >>> knowledge on this subject), I am now facing "invalid signature" error w= hen >>> I reboot with my installed dev kernel. I shared the logs for the build, >>> install and also .config and x509.genkey in the following link >>> >>> . >>> Please let me know what additional information can help to solve this >>> issue. >>> >>> I am following the instructions in https://kernelnewbies.org/FirstKerne= lPatch >>> >>> and I am at the step where I am supposed to verify that a printout was >>> added to the log after I reboot my dev kernel. >>> >>> Thanks, >>> Gidi >>> >> >> Gidi, >> >> From your build.log I see you compiled that kernel 6 times: >> Kernel: arch/x86/boot/bzImage is ready (#6) >> >> And the install log tells me: >> Sourcing file `/etc/default/grub' >> Sourcing file `/etc/default/grub.d/50_linuxmint.cfg' >> Sourcing file `/etc/default/grub.d/init-select.cfg' >> >> I am curious are you using linux mint or Debian ? >> >> I also see: >> CC drivers/cpufreq/cpufreq_ondemand.o >> drivers/cpufreq/cpufreq_ondemand.c: In function =E2=80=98od_set_powersav= e_bias=E2=80=99: >> drivers/cpufreq/cpufreq_ondemand.c:446:1: warning: the frame size of 103= 2 >> bytes is larger than 1024 bytes [-Wframe-larger-than=3D] >> 446 | } >> | ^ >> This is what causes the compile time errors with possible missing >> firmware :-) >> >> and all the kernels you have you can boot into by selecting 'Advanced >> options' in the grub menu then >> choosing the kernel you wish to use. >> >> Sourcing file `/etc/default/grub' >> Sourcing file `/etc/default/grub.d/50_linuxmint.cfg' >> Sourcing file `/etc/default/grub.d/init-select.cfg' >> Generating grub configuration file ... >> Found linux image: /boot/vmlinuz-5.12.0-rc3-GIDI-DEV+ >> Found initrd image: /boot/initrd.img-5.12.0-rc3-GIDI-DEV+ >> Found linux image: /boot/vmlinuz-5.12.0-rc3-GIDI-DEV+.old >> Found initrd image: /boot/initrd.img-5.12.0-rc3-GIDI-DEV+ >> Found linux image: /boot/vmlinuz-5.4.0-64-generic >> Found initrd image: /boot/initrd.img-5.4.0-64-generic >> Found linux image: /boot/vmlinuz-5.4.0-58-generic >> Found initrd image: /boot/initrd.img-5.4.0-58-generic >> Adding boot menu entry for UEFI Firmware Settings >> >> Disabling secure boot should make your invalid signature error go away. >> >> Hope this helps - Aruna >> >> --0000000000001229aa05be483f52 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Wed, Mar 24, 2021 at 8:58 AM Gidi Gal <gidi.gal.linux@gmail.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">
Disabling secure boot sh= ould make your invalid signature error go away.

Thanks, Aruna, I managed to launch my kernel after disabli= ng secure boot. Finally, I am able to continue with my tutorial :-)

See your a kernel hacker now and y= our are welcome but thank Valdis he said something about secure boot that g= ot me thinking :-)

=C2=A0What kind of changes= in the kernel require testing with valid signatures ?

<= /div>
I frankly have no clue. I never needed signatures so far anyway. = Valdis any thoughts please ?

Thanks,
Gidi


On Wed, Mar 24, 2021 at 4:36 AM Aruna Hewapathirane = <arun= a.hewapathirane@gmail.com> wrote:


On Tue, Mar = 23, 2021 at 12:37 PM Gidi Gal <gidi.gal.linux@gmail.com> wrote:
Greeting= s,

After receiving a lot of information regarding= my query on how to switch from installed to dev kernel (thank you to all t= he people that shared their knowledge on this subject), I am now facing &qu= ot;invalid signature" error when I reboot with my installed dev kernel= . I shared the logs for the build, install and also .config and x509.genkey= in the following link.
=
Please let me know what additional information can help to solve this = issue.

I am following the instructions in https://k= ernelnewbies.org/FirstKernelPatch
and I am at the step w= here I am supposed to verify that a printout was added to the log after I r= eboot my dev kernel.

Thanks,
Gidi

Gidi,

Fr= om your build.log I see you compiled that kernel 6 times:
Kernel: arch/= x86/boot/bzImage is ready =C2=A0(#6)

And the i= nstall log tells me:
Sourcing file `/etc/default/grub'
Sou= rcing file `/etc/default/grub.d/50_linuxmint.cfg'
Sourcing file `/et= c/default/grub.d/init-select.cfg'

I am cur= ious are you using linux mint or Debian ?

I also see:
CC =C2=A0 =C2=A0 =C2=A0drivers/cpufreq/cpufreq_ondemand.o
driver= s/cpufreq/cpufreq_ondemand.c: In function =E2=80=98od_set_powersave_bias=E2= =80=99:
drivers/cpufreq/cpufreq_ondemand.c:446:1: warning: the frame siz= e of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=3D]
=C2= =A0 446 | }
=C2=A0 =C2=A0 =C2=A0 | ^
This is what causes the c= ompile time errors with possible missing firmware :-)

and all the kernels you have you can boot into by selecting 'Ad= vanced options' in the grub menu then
choosing the kerne= l you wish to use.

Sourcing file `/etc/default/gru= b'
Sourcing file `/etc/default/grub.d/50_linuxmint.cfg'
Sourc= ing file `/etc/default/grub.d/init-select.cfg'
Generating grub confi= guration file ...
Found linux image: /boot/vmlinuz-5.12.0-rc3-GIDI-DEV+<= br>Found initrd image: /boot/initrd.img-5.12.0-rc3-GIDI-DEV+
Found linux= image: /boot/vmlinuz-5.12.0-rc3-GIDI-DEV+.old
Found initrd image: /boot= /initrd.img-5.12.0-rc3-GIDI-DEV+
Found linux image: /boot/vmlinuz-5.4.0-= 64-generic
Found initrd image: /boot/initrd.img-5.4.0-64-generic
Foun= d linux image: /boot/vmlinuz-5.4.0-58-generic
Found initrd image: /boot/= initrd.img-5.4.0-58-generic
Adding boot menu entry for UEFI Firmware Set= tings

Disabling secure boot should make your inval= id signature error go away.

Hope this helps - Arun= a

--0000000000001229aa05be483f52-- --===============1668477309813873879== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies --===============1668477309813873879==--