From: Udit Kumar <udit.kumar@nxp.com>
To: Laszlo Ersek <lersek@redhat.com>, "afish@apple.com" <afish@apple.com>
Cc: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Zeng, Star" <star.zeng@intel.com>
Subject: Re: Help on boot manager 'Boot Manager Menu' and direct boot
Date: Thu, 29 Nov 2018 13:12:13 +0000 [thread overview]
Message-ID: <VI1PR04MB464081612B1B483430D3B91991D20@VI1PR04MB4640.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <80adb57c-ffa2-d5d6-5d14-eeb9513a1328@redhat.com>
Thanks Laszlo,
> I can only think of some terminal control sequences that are *not* printed to
> the terminal when you don't enter UiApp manually. I don't understand how that
> could cause the exact symptom you describe, but I have no better explanation.
>
> Can you try other serial communication programs on your desktop? Such as
> "minicom" or "screen"?
Screen didn't help.
Moreover , using different OS distributions show same similar behavior !!
> Also, can you try changing your "console=..." kernel param(s)?
You meant baud-rate ?
On uefi side, could you help me if there is some extra information passed to OS in path
UiApp -> BootDevice,
I could see , some of additional protocols are installed in above path, I am not sure if those are
used by OS or OS Loader (grub in my case) somehow.
> Thanks
> Laszlo
next prev parent reply other threads:[~2018-11-29 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 1:42 Help on boot manager 'Boot Manager Menu' and direct boot Udit Kumar
2018-11-29 1:52 ` Andrew Fish
2018-11-29 3:09 ` Udit Kumar
2018-11-29 10:21 ` Laszlo Ersek
2018-11-29 13:12 ` Udit Kumar [this message]
2018-11-29 18:01 ` Laszlo Ersek
2018-11-30 9:13 ` Udit Kumar
2018-12-03 9:56 ` Laszlo Ersek
2018-12-03 10:03 ` Udit Kumar
2018-12-03 13:45 ` Laszlo Ersek
2018-12-03 14:04 ` Ard Biesheuvel
2018-12-03 14:54 ` Udit Kumar
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-list 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=VI1PR04MB464081612B1B483430D3B91991D20@VI1PR04MB4640.eurprd04.prod.outlook.com \
--to=devel@edk2.groups.io \
/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