public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: "Kanagarajan, Vijaikumar" <Vijaikumar_Kanagarajan@mentor.com>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	"Gylstorff Quirin" <quirin.gylstorff@siemens.com>,
	"P T, Sarath" <Sarath_PT@mentor.com>
Subject: RE: [cip-dev] [isar-cip-core] [PATCH] scripts/start-efishell.sh: Add -nographic option
Date: Mon, 27 Jun 2022 12:57:16 +0000	[thread overview]
Message-ID: <e932eb87b7564592bacdc82aa1fae449@mentor.com> (raw)
In-Reply-To: <fef66432-ac36-9e2d-7813-5e123d919bbf@siemens.com>



> -----Original Message-----
> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> Behalf Of Jan Kiszka
> Sent: 27 June 2022 18:22
> To: Gylstorff Quirin <quirin.gylstorff@siemens.com>; cip-dev@lists.cip-
> project.org; P T, Sarath <Sarath_PT@mentor.com>
> Subject: Re: [cip-dev] [isar-cip-core] [PATCH] scripts/start-efishell.sh: Add -
> nographic option
> 
> On 27.06.22 10:23, Gylstorff Quirin wrote:
> >
> >
> > On 6/27/22 10:14, Jan Kiszka via lists.cip-project.org wrote:
> >> On 27.06.22 09:12, Sarath P T wrote:
> >>> From: sarath P T <Sarath_PT@mentor.com>
> >>>
> >>> When we launch the start-efishell.sh script for adding the keys into
> >>> OVMF firmware we faced gtk initialization failed error. So it seems
> >>> we need to open the OVMF in nographic mode, hence we added the
> >>> required option to the script.
> >>>
> >>
> >> Which QEMU-Version? Which OVMF version (buster/bullseye/something
> else)?
> >> I'm not seeing this, but I'm facing other issues with that firmware
> >> provided by bullseye (a crash).
> >>  >> Signed-off-by: sarath P T <Sarath_PT@mentor.com>
> >>> ---
> >>>   scripts/start-efishell.sh | 2 +-
> >>>   1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>> diff --git a/scripts/start-efishell.sh b/scripts/start-efishell.sh
> >>> index d451f43..0831f83 100755
> >>> --- a/scripts/start-efishell.sh
> >>> +++ b/scripts/start-efishell.sh
> >>> @@ -2,7 +2,7 @@
> >>>   ovmf_code=${OVMF_CODE:-
> /usr/share/OVMF/OVMF_CODE.secboot.fd}
> >
> > This should be changed to the 4M version.
> >
> > @jan
> > The 4M version does also trigger a crash?
> >
> 
> Yes, it does.

We have not seen such errors. If you share the setup details (Qemu version/host distro/OVMF version) we can give it a try.

Thanks,
Vijai Kumar K

> 
> Jan
> 
> --
> Siemens AG, Technology
> Competence Center Embedded Linux

  reply	other threads:[~2022-06-27 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220627071206.21277-1-Sarath_PT@mentor.com>
2022-06-27  8:14 ` [cip-dev] [isar-cip-core] [PATCH] scripts/start-efishell.sh: Add -nographic option Jan Kiszka
2022-06-27  8:23   ` Gylstorff Quirin
2022-06-27 12:52     ` Jan Kiszka
2022-06-27 12:57       ` Kanagarajan, Vijaikumar [this message]
2022-06-27 13:04         ` Jan Kiszka
2022-06-27  8:47   ` Kanagarajan, Vijaikumar

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=e932eb87b7564592bacdc82aa1fae449@mentor.com \
    --to=vijaikumar_kanagarajan@mentor.com \
    --cc=Sarath_PT@mentor.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=quirin.gylstorff@siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox