From owner-freebsd-questions@freebsd.org Fri Jul 27 18:38:41 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8AD61053720 for ; Fri, 27 Jul 2018 18:38:41 +0000 (UTC) (envelope-from doug@safeport.com) Received: from bucksport.safeport.com (bucksport.safeport.com [198.74.231.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89FAD824E3 for ; Fri, 27 Jul 2018 18:38:41 +0000 (UTC) (envelope-from doug@safeport.com) Received: from bucksport.safeport.com (bucksport.safeport.com [198.74.231.101]) by bucksport.safeport.com (8.14.5/8.14.5) with ESMTP id w6RIDFuZ099571 for ; Fri, 27 Jul 2018 14:13:15 -0400 (EDT) (envelope-from doug@safeport.com) Date: Fri, 27 Jul 2018 14:13:15 -0400 (EDT) From: DTD To: freebsd-questions@FreeBSD.ORG Subject: Getting UEFI working Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (bucksport.safeport.com [198.74.231.101]); Fri, 27 Jul 2018 14:13:15 -0400 (EDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jul 2018 18:38:42 -0000 I solved [my??] UEFI booting problem. A first email on this described all the gory details. This IMO just obscured the larger message. If you want this to work there are two choices if you encounter a problem: (1) find hardware that works; (2) know the internals of the firmware on the failing system and enough about the UEFI boot process so you can find/write a first level module that the firmware in question will recognize. I have used only FreeBSD for my work station since 4.5. So I have installed it a time or two and worked around various software issues. Having to figure out what the PC firmware is looking for takes the problem to another level. TrueOS (iXsystems) seems to think using rEFInd is an answer. Starting with a free range version of that is a bit like rewriting termcap. The guide I found was for ZFS on a version of Windows those partition layout had little in common with what I had. Between the Lenovo BIOS and Windows boot options that could recovery from anything, I eventually got FreeBSD installed. None of the Windows versions (that I encountered in this go-around) had these options. I did all this using the same install medium. The amd64-dvd1 iso and the USB img file (both 11.2). The hardware was Dell, HP, and POWERSPEC (Micro Center's brand). Only the Dell worked. I did a legacy and a UEFI install each taking less than 5 minutes. The POWERSPEC would only boot Windows and entering the BIOS did not work. On the HP I did a GPT install that worked followed by a UEFI ZFS install that rendered the system unusable. Only the Dell recognized the bootable USB which I used for both installs. The rEFInd docs speak to setting various variables that will aid in booting. If rEFInd makes UEFI booting easier/possible it would be really nice if at a minium some of this information made its way into the handbook. _____ Douglas Denault http://www.safeport.com doug@safeport.com Voice: 301-217-9220 Fax: 301-217-9277