From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 5C8A621A18AAB for ; Thu, 27 Apr 2017 02:10:38 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 83A6D8004E; Thu, 27 Apr 2017 09:10:37 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 83A6D8004E Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=lersek@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 83A6D8004E Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-76.phx2.redhat.com [10.3.116.76]) by smtp.corp.redhat.com (Postfix) with ESMTP id DCBEF78351; Thu, 27 Apr 2017 09:10:36 +0000 (UTC) To: "Ni, Ruiyu" References: <43c8bb1a-3f04-e133-211f-0601d6ec9078@redhat.com> <734D49CCEBEEF84792F5B80ED585239D5B93AF36@SHSMSX104.ccr.corp.intel.com> Cc: edk2-devel-01 From: Laszlo Ersek Message-ID: Date: Thu, 27 Apr 2017 11:10:35 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <734D49CCEBEEF84792F5B80ED585239D5B93AF36@SHSMSX104.ccr.corp.intel.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Thu, 27 Apr 2017 09:10:37 +0000 (UTC) Subject: Re: falling back to UiApp? X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2017 09:10:38 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 04/27/17 07:40, Ni, Ruiyu wrote: > Laszlo, > I believe the "Unable to boot" message was added by intention. > > I just checked the UEFI Spec Boot Manager chapter again, still I didn't > find any wording to say what to do, when boot and recovery failure > happens. > > Putting "Unable to boot" message there is to tell platform developer > that system is not in good state (no bootable option), helpful for debugging. > > But rethinking about that, maybe I could also print a user-visible > string "Unable to boot, press any key to enter Boot Manager Menu." to > STD console and redirect to Boot Manager Menu when any key is received. This sounds great! > > I still don't like to silently show UI when this failure happens. I think your suggestion above is better than my original thought (which was just a guess, really). The request I originally received was to show "something" to the user on the screen, rather than just a (more or less invisible) DEBUG message via DebugLib. > What's your opinion? > If you agree, could you please help submit a Bugzilla tracker? I filed . Thank you! Laszlo > >> -----Original Message----- >> From: Laszlo Ersek [mailto:lersek@redhat.com] >> Sent: Wednesday, April 26, 2017 10:23 PM >> To: Ni, Ruiyu >> Cc: edk2-devel-01 >> Subject: falling back to UiApp? >> >> Hi Ray, >> >> the UiApp application is added to the UEFI boot order automatically, but it is not >> invoked automatically, even if BDS gives up and hangs with >> >> [Bds] Unable to boot! >> >> For example, consider the following: >> - no UEFI bootable application available anywhere in the system, >> - ... not even for the default platform recovery option, >> - no shell is built into the firmware image, >> - but UiApp is available in the firmware image. >> >> Is it possible to jump to UiApp in this case, rather than hanging with >> >> [Bds] Unable to boot! >> >> ? >> >> Can (or should) platform code do something about this? >> >> Or would this conflict with the UEFI spec either way? >> >> Thank you, >> Laszlo