From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id x788VpUV019381 for ; Thu, 8 Aug 2019 04:31:51 -0400 Received: by smtp.corp.redhat.com (Postfix) id B18C75D784; Thu, 8 Aug 2019 08:31:51 +0000 (UTC) Received: from mx1.redhat.com (ext-mx17.extmail.prod.ext.phx2.redhat.com [10.5.110.46]) by smtp.corp.redhat.com (Postfix) with ESMTPS id ACA125D772 for ; Thu, 8 Aug 2019 08:31:49 +0000 (UTC) Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 731F930BA06F for ; Thu, 8 Aug 2019 08:31:48 +0000 (UTC) Received: from panix1.panix.com (panix1.panix.com [166.84.1.1]) by mailbackend.panix.com (Postfix) with ESMTP id 4641nH5QRqz1lBC for ; Thu, 8 Aug 2019 04:31:47 -0400 (EDT) Received: by panix1.panix.com (Postfix, from userid 20712) id 4641nH3HF0zcbR; Thu, 8 Aug 2019 04:31:47 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by panix1.panix.com (Postfix) with ESMTP id 4641nH2mjFzcbQ for ; Thu, 8 Aug 2019 04:31:47 -0400 (EDT) Date: Thu, 8 Aug 2019 04:31:47 -0400 To: Linux for blind general discussion Subject: Re: No F Key Boot Menu In-Reply-To: <20190807.185726.951.4@[0.0.0.0]> Message-ID: References: <20190805.195033.561.2@0.0.0.0> <20190805.212710.331.4@[0.0.0.0]> <20190806.012851.270.6@[0.0.0.0]> <6d9c88f5-439c-0859-c5b5-2da72c16e7d7@GMAIL.COM> <20190807.185726.951.4@[0.0.0.0]> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3467208485790211098==" Content-ID: X-Greylist: Sender passed SPF test, Sender IP whitelisted by DNSRBL, ACL 238 matched, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.46]); Thu, 08 Aug 2019 08:31:48 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.46]); Thu, 08 Aug 2019 08:31:48 +0000 (UTC) for IP:'166.84.1.89' DOMAIN:'mailbackend.panix.com' HELO:'mailbackend.panix.com' FROM:'jdashiel@panix.com' RCPT:'' X-RedHat-Spam-Score: -2.3 (RCVD_IN_DNSWL_MED, SPF_HELO_NONE, SPF_PASS) 166.84.1.89 mailbackend.panix.com 166.84.1.89 mailbackend.panix.com X-Scanned-By: MIMEDefang 2.84 on 10.5.110.46 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-loop: blinux-list@redhat.com From: Linux for blind general discussion X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk Reply-To: blinux-list@redhat.com List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2019 08:31:51 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --===============3467208485790211098== Content-Type: text/plain; charset=US-ASCII Content-ID: If you use braille, I think it'll be a good idea to backup that memory. On Wed, 7 Aug 2019, Linux for blind general discussion wrote: > Date: Wed, 7 Aug 2019 14:57:26 > From: Linux for blind general discussion > To: blinux-list@redhat.com > Subject: Re: No F Key Boot Menu > > I ended up memorizing the key presses to set boot order in the bios in the absence of a boot menu. Sigh. So many left arrows, so many down arros, etc. > > ----- Original Message ----- > From: Linux for blind general discussion > To: blinux-list@redhat.com > Date: Wed, 7 Aug 2019 12:08:49 +0100 > Subject: Re: No F Key Boot Menu > > > So I'll leap in here. I've been trying to get my Dell Inspiron to boot > from a Linux stick. No boot menu anywhere, all the articles say oh, you > have to do this and this and that, but......will this actually work? > > On 06/08/2019 02:28, Linux for blind general discussion wrote: > > I think I found the answer: > > ? Fast Boot > > On/Off > > Enabling fast boot will make the initial post/boot slightly faster by bypassing the boot > > device check and using last boot HDD. > > Default: On > > So now I just need some eyeballs to help me get in there and turn that off. > > ----- Original Message ----- > > From: Linux for blind general discussion > > To: blinux-list@redhat.com > > Date: Mon, 5 Aug 2019 20:28:41 -0500 > > Subject: Re: No F Key Boot Menu > > > >> Yes, on my HP Envy, if I hit the F2 key at startup, I can select from a > >> list of boot devices. I do this when I'm installing a new OS from my USB > >> stick. > >> > >> > >> On 8/5/19 4:27 PM, Linux for blind general discussion wrote: > >>> Getting into the bios isn't the problem. It's selecting a device to boot from which is. > >>> > >>> ----- Original Message ----- > >>> From: Linux for blind general discussion > >>> To: Linux for blind general discussion > >>> Date: Mon, 5 Aug 2019 17:21:14 -0400 > >>> Subject: Re: No F Key Boot Menu > >>> > >>>> The delete key can get you into bios on some systems too. > >>>> > >>>> On Mon, 5 Aug 2019, Linux for blind general discussion wrote: > >>>> > >>>>> Date: Mon, 5 Aug 2019 15:59:41 > >>>>> From: Linux for blind general discussion > >>>>> To: blinux-list@redhat.com > >>>>> Subject: Re: No F Key Boot Menu > >>>>> > >>>>> Often the escape key can be used to bring up a boot menu. That being > >>>>> said, there's usually an option in bios to set more than 1 boot drive, > >>>>> such that if the 1st 1 doesn't contain bootable media, it'll move onto > >>>>> the 2nd 1, etc. > >>>>> > >>>>> On 8/5/19, Linux for blind general discussion wrote: > >>>>>> My bios: > >>>>>> Board: EVGA INTERNATIONAL CO.,LTD 131-HE-E995 1.0 > >>>>>> UEFI: American Megatrends Inc. 2.08 06/28/2019 > >>>>>> does not seem to have a function whereby you can select a device to boot > >>>>>> from using one of the function keys. Instead, one must physically go into > >>>>>> the bios and change boot order, if, for example, you wish to boot from a > >>>>>> flash drive to install an OS. And if that flash drive is subsequently > >>>>>> removed, the system will not boot, until you go into the bios and change the > >>>>>> boot order, again. > >>>>>> My question: is this normal bios behavior these days, or is something wrong > >>>>>> in my particular implementation. I turned off the secure boot function in > >>>>>> there. Would turning that on fix this? What else might I look for in the > >>>>>> bios to either (a) allow for falling back on different devices should one be > >>>>>> removed or (b) to allow the function key boot menu found in previous bios > >>>>>> implementations. > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Blinux-list mailing list > >>>>>> Blinux-list@redhat.com > >>>>>> https://www.redhat.com/mailman/listinfo/blinux-list > >>>>>> > >>>>> > >>>> -- > >>>> > >>>> _______________________________________________ > >>>> Blinux-list mailing list > >>>> Blinux-list@redhat.com > >>>> https://www.redhat.com/mailman/listinfo/blinux-list > >>>> > >>> _______________________________________________ > >>> Blinux-list mailing list > >>> Blinux-list@redhat.com > >>> https://www.redhat.com/mailman/listinfo/blinux-list > >> -- > >> Christopher (CJ) > >> Chaltain at Gmail > >> > >> _______________________________________________ > >> Blinux-list mailing list > >> Blinux-list@redhat.com > >> https://www.redhat.com/mailman/listinfo/blinux-list > >> > > > > _______________________________________________ > > Blinux-list mailing list > > Blinux-list@redhat.com > > https://www.redhat.com/mailman/listinfo/blinux-list > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > > -- --===============3467208485790211098== Content-Type: text/plain; charset=us-ascii Content-ID: Content-Description: Content-Disposition: inline _______________________________________________ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list --===============3467208485790211098==--