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 x75LnMcg014695 for ; Mon, 5 Aug 2019 17:49:22 -0400 Received: by smtp.corp.redhat.com (Postfix) id 5CBF45D712; Mon, 5 Aug 2019 21:49:22 +0000 (UTC) Received: from mx1.redhat.com (ext-mx03.extmail.prod.ext.phx2.redhat.com [10.5.110.27]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 57DB65D6D0 for ; Mon, 5 Aug 2019 21:49:20 +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 07C687FDE5 for ; Mon, 5 Aug 2019 21:49:19 +0000 (UTC) Received: from panix1.panix.com (panix1.panix.com [166.84.1.1]) by mailbackend.panix.com (Postfix) with ESMTP id 462Wct3wpZz1K6y for ; Mon, 5 Aug 2019 17:49:18 -0400 (EDT) Received: by panix1.panix.com (Postfix, from userid 20712) id 462Wct2gybzcbR; Mon, 5 Aug 2019 17:49:18 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by panix1.panix.com (Postfix) with ESMTP id 462Wct2L4dzcbQ for ; Mon, 5 Aug 2019 17:49:18 -0400 (EDT) Date: Mon, 5 Aug 2019 17:49:18 -0400 To: Linux for blind general discussion Subject: Re: No F Key Boot Menu In-Reply-To: <20190805.212710.331.4@[0.0.0.0]> Message-ID: References: <20190805.195033.561.2@0.0.0.0> <20190805.212710.331.4@[0.0.0.0]> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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.27]); Mon, 05 Aug 2019 21:49:19 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Mon, 05 Aug 2019 21:49:19 +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.78 on 10.5.110.27 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: Mon, 05 Aug 2019 21:49:22 -0000 Boot order selection and other internal bios tasks in that kind of bios usually get done with arrow keys and enter. At least that's the way it was the last time I tried to help someone over the phone. What's needed for all of these systems are screen layouts in ascii files so people can know once bios opens arrow down twice and hit enter to get boot order if that actually does boot order, then the selection possibilities in boot order menu. I'm sure many of us can do without the pictures since screen readers don't do pictures. On Mon, 5 Aug 2019, Linux for blind general discussion wrote: > Date: Mon, 5 Aug 2019 17:27:10 > From: Linux for blind general discussion > To: blinux-list@redhat.com > Subject: Re: No F Key Boot Menu > > 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 > --